The following table describes the things to consider when using the RELEASE MLOAD statement.
To release the target tables, the release function must first obtain an exclusive lock on each specified table. This is not possible, and the RELEASE MLOAD statement will fail if either a database lock or an Update operator write lock has been placed on any of the specified tables.
An Update operator normally places write locks on the target tables:
If the RELEASE MLOAD statement is executed before the Update operator task reaches these critical points, the release function completes before the utility can place write locks on the target tables.
|Messages Returned||A release completed message indicates that all of the specified tables were releasable and the release function completed without error.
If the release function encounters a table that cannot be released, it terminates with an error message identifying the table and the reason it could not be released.
Acquisition phase error conditions include:
|Releasing Application Locks||The IN APPLY option of the RELEASE MLOAD statement releases the application locks on the target tables that satisfy one of the following conditions:
If none of these conditions is true, and the table has no permanent journals, then the Update operator changes the application lock to a restoration lock that prevents the Update operator from restarting and allows the following table accesses:
If permanent journals are defined on the table, the only option is to drop the target table. If the target table belongs to a replication group and change data capture is active (for example, the replication group status is not Defined nor Terminated), then the following steps must be completed to drop the table:
|Releasing Application Locks when the target table has fallback||
Follow these steps to release MLOAD locks entirely.
|Required Privilege||Only the owner of the database or a user with one of the following privileges on the specified tables can use the RELEASE MLOAD statement:
|Table Requirements||All of the tables that specified must have been involved in an Update operator task. If a specified table is not involved in an Update operator task, Teradata Database rejects the RELEASE MLOAD statement.|