RDBPROD: Using Database Scope to See Attach Method of a Process
(Doc ID 65062.1)
Last updated on OCTOBER 23, 2019
Applies to:Oracle Rdb Server on OpenVMS - Version 6.0 and later
HP OpenVMS VAX
HP OpenVMS Alpha
HP OpenVMS Itanium
You want to determine what DBKEY SCOPE argument is being used by a process or processes and whether a process is using SCOPE IS ATTACH or TRANSACTION.
The "DBKEY SCOPE IS ATTACH" or "DBKEY SCOPE IS TRANSACTION" arguments control when the database key of an erased record can be used again.
The default argument is "DBKEY SCOPE IS TRANSACTION". This means that Rdb cannot use the dbkey of an erased row again to store another row until the transaction that erased the original row completes with a COMMIT statement.
The "DBKEY SCOPE IS ATTACH" argument means that a process cannot use the dbkey of an erased row again to store another row until the process that erased the original row detaches from the database with a DISCONNECT statement.
If all active users use the "DBKEY SCOPE IS TRANSACTION" argument, then the dbkey scope is set to TRANSACTION for all users. However, if just one user attaches to the database using the "DBKEY SCOPE IS ATTACH" argument, then the dbkey scope is reset to ATTACH for all users.
For further information, see section 2.6.5 Database Keys in the Oracle Rdb™ SQL Reference Manual.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!