Debugging Various Utilities in Oracle RAC

Prior to Oracle Database 10g, you had to modify the srvconfig file located in the $ORACLE_ HOME/bin directory to enable the advance tracing by changing the JRE options. Beginning with Oracle 10g, special environment variable SRVM_TRACE can be used to trace the SRVM files and various Java-based utilities, such as DBCA, ASMCA, CLUVFY, DBUA, and SRVCTL. Oracle displays trace data on the standard output while tracing the SRVCTL utility, whereas trace files for others are written into the file system.

By default, tracing is enabled for the Database Configuration and Database Upgrade Assistants, and their trace files are located under $ORACLE_HOME/cfgtools/dbca and $ORACLE_ HOME/cfgtools/dbua, respectively. The trace file for CLUVFY is stored under the $GRID_HOME/ cv/log directory. There are situations where you enable this trace file for debugging. For example, if you are unable to start a database or database instance using the SRVCTL utility and the standard error reported by the SRVCTL utility is not providing enough information, setting the SRVM_TRACE environment variable to TRUE provides more information that is helpful in debugging the problem. Here is an example of enabling a Java trace for the SRVCTL utility, which is unable to ....