Kbase 21758: OCOM/OROL Not Written to dataserv.lg File -- ORACLE DSV 9.1C
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/02/2002 |
|
SUMMARY:
This Solution applies to Progress ORACLE DataServer Version 9.1A through 9.1C.
In these Progress versions, even if you have turned on VERBOSE logging for DataServer, OCOM is not logged when a transaction is committed and OROL is not logged when a transaction is rolled back. This is a known, minor defect in the logging process. The OCI calls are still passed even though they are not logged.
EXPLANATION:
Progress DataServer for ORACLE is an ORACLE client. The ORACLE RDBMS handles transaction roll back and recovery. When a transaction that updates an ORACLE database ends successfully, Progress sends a
COMMIT to the ORACLE instance via the OCI layer. OCOM is passed for committing transactions and OROL is passed for rollbacks.
SOLUTION:
In Progress 9.1D, this problem is corrected. In 9.1D, Both OCOM and OROL are recorded in dataserv.lg file if VERBOSE is set.