My Oracle Support Banner

RDBPROD: DBMS: Using SDA To Determine Cause of Process Stall (Doc ID 63163.1)

Last updated on APRIL 16, 2024

Applies to:

Oracle CODASYL DBMS - Version 7.0 and later
HP OpenVMS VAX
HP OpenVMS Alpha
HP OpenVMS Itanium

Purpose

Occasionally when you attempt to access an Oracle CODASYL DBMS database, you will be appear to be 'hung'. The reason for this may be a conflict in trying to access some part of the database which is currently locked by another user. When the access is set to WAIT until the resource is free, no message is returned and the process will be 'stalled' until the process controlling the resource releases it.

Previously, GETLKI was used to determine which process controls a lock that is causer another to stall, but this was time consuming because all locks on the system were shown. Also, it was difficult to track an individual process's locks before they changed.

Scope

 

Details

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.