|Oracle® Database Provider for DRDA User's Guide
12c Release 1 (12.1) for Linux x86-64
Part Number E27316-07
|PDF · Mobi · ePub|
This chapter discusses issues of Diagnostics and Maintenance.
This chapter contains these topics:
Diagnostics for Oracle Database Provider for DRDA consist of the trace facility, which is configurable through the trace level before the application runs, and may be adjusted by the command-line tool. Oracle Database Provider for DRDA uses the Automatic Diagnostic Repository (ADR) to hold all logs, traces and dump records. See Chapter 10, "Command-line Utility for Oracle Database Provider for DRDA" and section "Automatic Diagnostic Repository (ADR)" in Oracle Database Administrator's Guide.
The trace logs DRDA protocol errors before, during, and after each client session. There are specific DRDA architecture error alerts that are intended to diagnose a protocol violation. Additional errors from the OCI session may also be logged there.
Diagnostics may be summarized as the ability to trace, or collect diagnostic information, usually in a file.
The trace directory may be specified by the user. By default, Oracle Database Provider for DRDA creates a trace directory in
/log/diag. Within this root directory, Oracle Database Provider for DRDA stores trace files in
instance is the instance name used in the
drdaas.ora file. The
adrci utility enables viewing and manipulation of trace files.
Depending on the application, different levels of diagnostic detail might become necessary. By default, diagnostic depth is set to off, for performance reasons. However, incidents are logged in the repository if the AS fails.
To communicate with the Application Server, Oracle provides an external command interface. The command interface supports the following interactions:
Starting the server
Stopping the server
Determining server status
Displaying connected client sessions
Displaying details of client sessions, which includes:
Session state (command being executed, such as preparing, executing, fetching, idle, and so on)
Last SQL statement prepared
Client IP address and port number
Oracle SQL Session Id
Pausing a SQL session
Terminating a SQL session
Reloading server configuration
See Chapter 10, "Command-line Utility for Oracle Database Provider for DRDA" for details of these operations.