Trace and log files, similar to those generated for Oracle Database with Oracle RAC, are also available for the Oracle Clusterware components. For Oracle Clusterware, Oracle Database stores these under a unified directory log structure.
See the Oracle Clusterware Administration and Deployment Guide for more information about troubleshooting Oracle Clusterware.
B.1 Where to Find Files for Analyzing Errors
Oracle Database records information about important events that occur in your Oracle RAC environment in trace files. The trace files for Oracle RAC are the same as those in noncluster Oracle databases. As a best practice, monitor and back up trace files regularly for all instances to preserve their content for future troubleshooting.
ORA-600 errors appear in the
.log file for each instance where SID is the instance identifier.
The alert log and all trace files for background and server processes are written to the Automatic Diagnostic Repository, the location of which you can specify with the
DIAGNOSTIC_DEST initialization parameter. For example:
Oracle Database creates a different trace file for each background thread. Oracle RAC background threads use trace files to record database operations and database errors. These trace logs help troubleshoot and also enable Oracle Support to more efficiently debug cluster database configuration problems. The names of trace files are operating system specific, but each file usually includes the name of the process writing the file (such as LGWR and RECO). For Linux, UNIX, and Windows systems, trace files for the background processes are named
Oracle Database Administrator's Guide and Oracle Database 2 Day + Real Application Clusters Guide for more information about monitoring errors and alerts in trace files
Trace files are also created for user processes if you set the
DIAGNOSTIC_DEST initialization parameter. User process trace file names have the format
process_identifier is a 5-digit number indicating the process identifier (PID) on Linux and UNIX systems, and
thread_identifier is the thread identifier on Windows systems.
B.2 Managing Diagnostic Data in Oracle RAC
Problems that span Oracle RAC instances can be the most difficult types of problems to diagnose.
For example, you may need to correlate the trace files from across multiple instances, and merge the trace files. Oracle Database 12c release 2 (12.2) includes an advanced fault diagnosability infrastructure for collecting and managing diagnostic data, and uses the Automatic Diagnostic Repository (ADR) file-based repository for storing the database diagnostic data. When you create the ADR base on a shared disk, you can place ADR homes for all instances of the same Oracle RAC database under the same ADR Base. With shared storage:
You can use the ADRCI command-line tool to correlate diagnostics across all instances.
ADRCI is a command-line tool that enables you to view diagnostic data in the ADR and package incident and problem information into a zip file for transmission to Oracle Support. The diagnostic data includes incident and problem descriptions, trace files, dumps, health monitor reports, alert log entries, and so on.
Oracle Database Utilities for information about using ADRCI
You can use the Data Recovery Advisor to help diagnose and repair corrupted data blocks, corrupted or missing files, and other data failures.
The Data Recovery Advisor is an Oracle Database infrastructure that automatically diagnoses persistent data failures, presents repair options, and repairs problems at your request.
Oracle Database Administrator’s Guide for information about managing diagnostic data
B.3 Using Instance-Specific Alert Files in Oracle RAC
Each instance in an Oracle RAC database has one alert file. The alert file for each instance,
alert.SID.log, contains important information about error messages and exceptions that occur during database operations. Information is appended to the alert file each time you start the instance. All process threads can write to the alert file for the instance.
.log file is in the directory specified by the
DIAGNOSTIC_DEST initialization parameter.
B.4 Enabling Tracing for Java-Based Tools and Utilities in Oracle RAC
All Java-based tools and utilities that are available in Oracle RAC are called by executing scripts of the same name as the tool or utility.
This includes the Cluster Verification Utility (CVU), Database Configuration Assistant (DBCA), the Net Configuration Assistant (NETCA), Server Control Utility (SRVCTL), and the Global Services Daemon (GSD). For example, to run DBCA, enter the command
By default, Oracle Database enables traces for DBCA and the Database Upgrade Assistant (DBUA). For the CVU, GSDCTL, and SRVCTL, you can set the
SRVM_TRACE environment variable to
TRUE to make Oracle Database generate traces. Oracle Database writes traces to log files. For example, Oracle Database writes traces to log files in
Oracle_base/cfgtoollogs/dbua for DBCA and DBUA, respectively.
B.5 Resolving Pending Shutdown Issues
B.6 How to Determine If Oracle RAC Instances Are Using the Private Network
This section describes how to manually determine if Oracle RAC instances are using the private network. However, the best practice for this task is to use the Oracle Enterprise Manager Cloud Control graphical user interface (GUI) to check the interconnect. Also, see the Oracle Database 2 Day + Real Application Clusters Guide for more information about monitoring Oracle RAC using Oracle Enterprise Manager.
oradebug setmypid oradebug ipc
These commands dump a trace file to the location specified by the
DIAGNOSTIC_DEST initialization parameter. The output may look similar to the following:
SSKGXPT 0x1a2932c flags SSKGXPT_READPENDING info for network 0 socket no 10 IP 172.16.193.1 UDP 43749 sflags SSKGXPT_WRITESSKGXPT_UP info for network 1 socket no 0 IP 0.0.0.0 UDP 0...
In the example, you can see the database is using IP 172.16.193.1 with a User Datagram Protocol (UDP) protocol. Also, you can issue the
oradebug tracefile_name command to print the trace location where the output is written.
Additionally, you can query the
V$CLUSTER_INTERCONNECTS view to see information about the private interconnect. For example:
SQL> SELECT * FROM V$CLUSTER_INTERCONNECTS; NAME IP_ADDRESS IS_ SOURCE ----- -------------------------- --- ------------------------------- eth0 184.108.40.206 NO Oracle Cluster Repository
B.7 Database Fails to Start after Private NIC Failure
In a two-node cluster that is not using grid interprocess communication (GIPC) and has only a single private network interface card (NIC), when the NIC fails on the node on which the Oracle Grid Infrastructure Management Repository database (mgmtdb) is running (node A, for example) after the other node (node B) was evicted, then when the private network is reestablished on node A, node B joins the cluster but the database instance on node A is unable to start.
To start the database instance:
Stop the Oracle Clusterware stack on both nodes, as follows:
crsctl stop cluster
Start the Oracle Clusterware stack on both nodes, as follows:
crsctl start cluster
Stop the database instance on node A, on which the NIC failed, as follows:
srvctl stop instance -db db_unique_name -node A
Start the database on both nodes by running the following commands one of the nodes:
srvctl start instance -db db_unique_name -node B srvctl start instance -db db_unique_name -node A
The database instance will fail to start on node A until after the instance starts on node B.