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 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=<any text>

  This environment variable causes an MS-DOS window to be displayed. Sometimes, useful troubleshooting information will be displayed in this window. Note that you must type some text after the equal sign for this environment variable to work properly. The environment variable works properly as long as you enter some text.

  Note: The OCM_TRACE property described in Table B-1 must be set to true for the troubleshooting information to be displayed in the MS-DOS window.

• 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.

You can run the Change Manager application from the MS-DOS command line. To do so:

1. From the Windows Start menu, point to Programs, then click Command Prompt to display an MS-DOS window.

2. Set the working directory to the bin subdirectory of the Oracle installation directory (ORACLE_HOME) for Oracle Enterprise Manager, for example: \OEM_21\bin.

3. Start the Oracle Management Server if it is not already started, or make sure your system has access to an Oracle Management Server running on a different system.

4. Run the Change Manager application by typing the following in the MS-DOS window:

   oemapp ocm
       
   
            

5. After Change Manager starts, you can start any of the other Oracle Change Management Pack applications from Change Manager in the usual manner.

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.

The ocm.properties file in the ORACLE_HOME\sysman\ocm\bin directory for Oracle Enterprise Manager contains a number of properties that you can set to provide more information about Oracle Change Management Pack applications. Table B-1 displays the properties and a description of each property.

Note: The other properties in the ocm.properties file whose names begin with OCM_TRACE are meaningful only when the OCM_TRACE property is set to true.

Table B-1 Using the ocm.properties File to Enable Tracing and Debugging

Property	Description
OCM_TRACE	If true, enables output of informational and problem trace messages.
OCM_TRACE_FILE	If true, enables output of trace information to a file. The setting of the OCM_TRACE_VERSIONING property determines the name of the trace file.
OCM_TRACE_VERSIONING	The OCM_TRACE_FILE property must be true for the OCM_TRACE_VERSIONING property to be meaningful. If the OCM_TRACE_VERSIONING property is true, a new version of the trace file is created for each run of the application. The file has a name of the format Oracle Change Manager_nnnnnn.log. 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 property is false, the trace file has the name Oracle Change Manager.log, and the file is overwritten for each run of the application.
OCM_TRACE_DEBUG	If the OCM_TRACE_DEBUG property is true, general debugging information (such as property values) is output to the trace file at application startup time.
OCM_TRACE_DEBUG_VERBOSE	If the OCM_TRACE_DEBUG_VERBOSE property is true, more detailed debugging information, including class names and line numbers, is output to the trace file at application startup time.
VDB_DEBUG	If the VDB_DEBUG property is true, database calls are output to the trace file.
VDB_VERBOSE_DEBUG	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.

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

---