B
Troubleshooting Appendix

This appendix describes different ways of troubleshooting problems that may occur when you are using Oracle Change Management Pack applications.

You may decide to contact an Oracle Worldwide Customer Support representative regarding a problem with Oracle Change Management Pack. If so, you may be asked to use one of the approaches described in this appendix to obtain information that will help the representative determine the source of the problem.

Using Environment Variables When Running Change Manager from the Command Line

You can set environment variables in the MS-DOS or UNIX command line before you run the Change Manager application from the command line. The following environment variables may provide information that is useful for troubleshooting and debugging Oracle Change Management Pack problems:

• set ORACLE_OEM_JAVAMX=-mx<number>m

  The default is -mx128m. This environment variable specifies the maximum amount of virtual memory to be used by the Java Virtual Machine (in megabytes). This memory is not used unless needed. If the amount is exceeded, execution will be terminated. This environment variable can be used to increase the amount of memory for large script generations and other purposes.

• set ORACLE_OEM_CLIENTTRACE=true

  This environment variable, which is for Windows NT only, displays troubleshooting information in an MS-DOS window. Before you set this environment variable, the OCM_TRACE.ENABLED property in the ORACLE_HOME/sysman/config/ClientConfig.properties file (described in Table B-1) must be set to true, otherwise troubleshooting information is not displayed in the MS-DOS window. Note that ORACLE_HOME is the directory in which Oracle Enterprise Manager is installed.

• set ORACLE_OEM_JAVARUNTIME=<directory where bin/java.exe is located>

  You can specify this environment variable if you have a Java development environment. This environment variable can be useful when the system is hanging and you want to get a thread dump.

Enabling Tracing and Debugging for Oracle Change Management Pack

You can turn on tracing and debugging facilities for the Oracle Change Management Pack applications to help troubleshoot problems.

You can enter different properties in the ClientConfig.properties file in the ORACLE_HOME/sysman/config directory for Oracle Enterprise Manager to obtain more tracing and debugging information about Oracle Change Management Pack applications. Table B-1 displays the properties and a description of each property.

By default, the trace files for Oracle Change Management Pack applications are written to the ORACLE_HOME/sysman/log directory for Oracle Enterprise Manager.

Note: The OCM_TRACE.ENABLED property in the ClientConfig.properties file must be set to true for the other properties whose names begin with OCM_TRACE in the ClientConfig.properties file to be meaningful.

Table B-1 Using ClientConfig.properties to Enable Tracing and Debugging  

Property and Settings	Description
OCM_TRACE.ENABLED={true|false}	If true, enables output of informational and problem trace messages.
OCM_TRACE_FILE.ENABLED={true|false}	If true, enables output of trace information to a file. The setting of the OCM_TRACE_VERSIONING.ENABLED property determines the name of the trace file.
OCM_TRACE_VERSIONING.ENABLED={true|false}	The OCM_TRACE_FILE.ENABLED property must be true for the OCM_TRACE_VERSIONING.ENABLED property to be meaningful. If the OCM_TRACE_VERSIONING.ENABLED property is true, a new version of the trace file is created for each run of the application. The file has a name in the format Oracle Change Manager_nnnnnn.log, where nnnnnn represents a series of numbers. If an Oracle Change Management Pack application is running in more than one session on your machine, examine the timestamp of each trace file to determine the trace file that is associated with each session. The trace file with the earliest timestamp is the trace file for the session that started first, and so on. If the OCM_TRACE_VERSIONING.ENABLED property is false or not used, the trace file has the name Oracle Change Manager.log, and the file is overwritten for each run of the application.
OCM_TRACE_DEBUG.ENABLED={true|false}	If the OCM_TRACE_DEBUG.ENABLED property is true, general debugging information (such as property values) is output to the trace file while Change Manager runs.
OCM_TRACE_DEBUG_VERBOSE.ENABLED={true|false}	If the OCM_TRACE_DEBUG_VERBOSE.ENABLED property is true, more detailed debugging information, including class names and line numbers, is output to the trace file while Change Manager runs.
VDB_DEBUG={true|false}	If the VDB_DEBUG property is true, database calls are output to the trace file. This property is not specific to Change Management Pack applications. It can be used with other Oracle Enterprise Manager applications. Use this property in the ClientConfig.properties file to capture database calls in the trace file when you are running Change Manager standalone. Use this property in the omsconfig.properties file in the $ORACLE_HOME/sysman/config directory to capture database calls in the trace file when you are running Change Manager connected to an Oracle Management Server. Use this property in both the ClientConfig.properties file and the omsconfig.properties file if you want to capture database calls in the trace file regardless of how you are running Change Manager.
VDB_VERBOSE_DEBUG={true|false}	If the VDB_VERBOSE_DEBUG property is true, more detailed information about database calls, including SQL statement issued and return values, is output to the trace file. This property is not specific to Change Management Pack applications. It can be used with other Oracle Enterprise Manager applications. Use this property in the ClientConfig.properties file to capture database calls in the trace file when you are running Change Manager standalone. Use this property in the omsconfig.properties file in the $ORACLE_HOME/sysman/config directory to capture database calls in the trace file when you are running Change Manager connected to an Oracle Management Server. Use this property in both the ClientConfig.properties file and the omsconfig.properties file if you want to capture database calls in the trace file regardless of how you are running Change Manager.