User`s guide

Troubleshooting
8-8 Oracle Database Installation and Administration Guide
You can use a character host variable in the AT clause, as the following example
shows:
EXEC SQL BEGIN DECLARE SECTION;
db_name1 CHARACTER(10);
db_name2 CHARACTER(10)
EXEC SQL END DECLARE SECTION;
.
.
set db_name1 = 'PAYROLL'
set db_name2 = 'MANAGERS'
.
.
EXEC SQL AT :db_name1 UPDATE...
EXEC SQL AT :db_name2 UPDATE...
For more information, refer to the respective sections in the Pro*COBOL Programmer's
Guide and Pro*C/C++ Programmer's Guide that discusses concurrent logons.
Note:
■ Application servers must not create Oracle database connections
of their own. Therefore, an openUTM user is not allowed to issue
CONNECT statements within an openUTM program. Any work
performed by them would be outside the global transaction, and
may confuse the connection information given by openUTM.
■ SQL calls must not occur in the openUTM start exit routine,
however may occur in the conversation exit routine
(
Vorgangs-Exit )
8.5 Troubleshooting
This section discusses how to recover data if there are problems or a system failure.
Both trace files and recovering pending transactions are discussed in the following
sections.
8.5.1 Trace Files
The Oracle XA library logs any error and tracing information to its trace file. This
information is useful in supplementing the XA error codes. For example, it can
indicate whether an open failure is caused by an incorrect open string, failure to find
the Oracle Database instance, or a login authorization failure. The name of the trace
file is:
ORAXALOG.pid-db_name-date.TRC
where
pid is the process identifier (TSN)
db_name is the database name you specified in the open string field DB = db_name
date
is the date when the trace file is created
8.5.1.1 Trace File Examples
Examples of two types of trace files are discussed in this section.