This can occur if a HUT lock is explicitly released during an ARC job, or if multiple jobs are run concurrently on the same object with the same Teradata user, with each job specifying the RELEASE LOCK option. For example, a database-level archive, with one or more tables excluded, is run concurrently with a table-level archive of the excluded tables. In this situation, the RELEASE LOCK for the database-level job will release the table-level locks if the job completes first.
Use different Teradata users for each archive job when running concurrent archives against the same objects. This ensures that locks placed by one job are not released by another.
For the purposes of locking, a set of cluster archive jobs, with each job archiving different clusters, counts as only a single job running against the object. If all concurrent jobs running on an object archive different sets of clusters, it is acceptable to use the same Teradata user for each of the cluster archive jobs.