My Oracle Support Banner

RDBPROD: DBMS: Using the DBM$BIND_WAIT_RECORD_LOCKS Logical (Doc ID 63164.1)

Last updated on FEBRUARY 13, 2020

Applies to:

Oracle CODASYL DBMS - Version 4.0a and later
HP OpenVMS Itanium
HP OpenVMS Alpha


When an Oracle CODASYL DBMS database is created, one of the qualifiers,


specifies whether to wait on record lock conflicts or treat lock conflicts as errors.

Specify /WAIT_RECORD_LOCKS (the default) to wait until the lock is granted or a deadlock occurs.

Specify /NOWAIT_RECORD_LOCKS to return an error message whenever a record lock conflict occurs.

There may be some instances where the global database definition of the qualifier may need to be overridden.  For instance, the database may have been created with /WAIT_RECORD_LOCKS but it would be better for a certain batch job to fail should a record lock conflict occur.  With the way the database was created to handle lock conflicts, the batch job will wait until the lock conflict is resolved.

The reverse would occur if the database was created with the qualifier /NOWAIT_RECORD_LOCKS.  The job submitted to the batch queue would fail if a record lock conflict occurred, and that might not be desirable.


CODASYL DBMS DBAs and programmers


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.