User`s guide

Troubleshooting
openUTM Product Set 8-9
The following example shows a trace file for an application's task '1234' that was
opened on April 2nd 1999. The
DB field for this application was not specified in the
open string when the resource manager was opened
ORAXALOG.1234-NULL-990402.TRC
The following example shows a trace file that was created on December 15th 1998 by
task
5678 . The DB field was specified as FINANCE in the open string when the resource
manager was opened.
ORAXALOG.5678-FINANCE-981215.TRC
Each entry in the trace file contains information that looks like this:
1032.2: xa_switch rtn ORA-22
where 1032 is the time when the information is logged, 2 is the resource manager
identifier,
xa_switch is the module name, and ORA-22 is the returned Oracle database
information.
8.5.2 Debugging
You can specify the DbgFl (debug flag) in the open string. For more information, refer
to the Oracle XA chapter in Oracle Database Advanced Application Developer's Guide.
Depending on the debugging level (
low:DbgFl=1,high:DbgFl=15 ) you can get more or
less debug entries in the trace file
ORAXALOG . pid-db_name-date . TRC (refer to the
preceding section).
8.5.3 In-Doubt or Pending Transactions
In-doubt or pending transactions are transactions that have been prepared but not yet
committed to the database. Generally, openUTM resolves any failure and recovery of
any in-doubt or pending transaction. However, the Database Administrator may have
to override an in-doubt transaction in working with UTM-F, that is,
APPLIMODE = FAST ,
for example when the in-doubt transaction is:
■ Locking data that is required by other transactions
■ Not resolved in a reasonable amount of time
Note: Overriding in-doubt transactions can cause inconsistency
between openUTM and the database. For example, if the DB
transaction is committed by the Database Administrator and the
openUTM application rolls back the transaction in the warm-start
phase, then the Oracle Database cannot roll this committed transaction
back, therefore, causing an inconsistency.
8.5.4 Oracle Database SYS Account Tables
There are four tables under the Oracle Database SYS account that contain transactions
generated by regular Oracle Database applications and Oracle Database/openUTM
applications. These are as follows:
■ DBA_2PC_PENDING
■ DBA_2PC_NEIGHBORS
■ DBA_PENDING_TRANSACTIONS