Teradata schema locked during DataStage job run due to RELEASE MLOAD statement.

Technote (troubleshooting)


Problem(Abstract)

When the DataStage Teradata Connector stage performs a bulk update, a RELEASE MLOAD statement is issued which locks the schema, preventing updates to other objects in the same schema until the job completes.

Resolving the problem

The DataStage Teradata Connector stage does not directly issue the RELEASE MLOAD statement. Rather it is issued by the Teradata TPT layer if a specific property has been set in the Teradata Connector stage properties.

Open the Teradata Connector stage properties and examine the setting of the Startup option. When Startup=Clean, Teradata will clean up the table and issue the RELEASE MLOAD command when the job starts. If the Startup option is instead set to "Restart" then the RELEASE MLOAD statement does not occur during job run.

NOTE: some jobs may depend upon the clearing of existing data in target table at start of job run, so before changing the Startup option from Clean to Restart, you need to examine the usage of the data in that table to determine if not clearing the table will cause errors or incorrect results for your job.

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere DataStage

Software version:

8.1, 8.5, 8.7, 9.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1620650

Modified date:

2013-01-21

Translate my page

Machine Translation

Content navigation