RDBPROD: Prestarted Transaction Recommendations -- Timeout (Doc ID 1088050.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Rdb Server on OpenVMS - Version 7.1 and later
Oracle CODASYL DBMS - Version 7.1 and later
HP OpenVMS Alpha
HP OpenVMS Itanium

Goal

When a read write transaction in Oracle Rdb or Oracle CODASYL DBMS is committed, the next read write transaction is started immediately. This is called a prestarted transaction.

Prestarting the next read write transaction saves an IO to the root file, which can improve performance. Unfortunately, if the process then sits idle, the prestarted transaction can remain open for a long time. This can cause problems, such as preventing the reclamation of snapshot file space.

Solution

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 hundreds of Community platforms