My Oracle Support Banner

Increasing the OPMN Log Level in Versions 9.0.2 to 10.1.2 (Doc ID 217128.1)

Last updated on JULY 31, 2020

Applies to:

Oracle Fusion Middleware - Version to [Release 9iAS to AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: to
Checked for relevance on 11-Oct-2010


This document describes how to configure the Oracle Application Server Process Manager (OPMN) to produce an increased level diagnostic output.

It can be useful to temporarily adopt this configuration while troubleshooting startup difficulties for those Application Server components which are started by OPMN, such as Oracle HTTP Server (OHS) and Oracle Containers for J2EE (OC4J).

Examples provided within the document are given for a UNIX environment but the steps are believed to be generic enough that they can be applied to an Application Server installation on a Windows platform.

This steps provided in this document are specific to the implementation of OPMN present within Application Server versions 9.0.2.x through 10.1.2.x. For additional information relevant when troubleshooting the OPMN implementation within Application Server 10g 10.1.3.x versions, please also see:

How to Enable OPMN Logging in OracleAS 10g Rel 3 (10.1.3)?

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 Ensure that the Enterprise Manager (EM) web site is not running
 Backup the current OPMN configuration file
 Edit "opmn.xml" and increase the "level" attribute
 Propagate the changes
 Stop OPMN and use "ps -ef" to confirm that all OPMN processes have terminated
 Backup and/or clear down the current "ipm.log" file
 Restart opmn using "opmnctl start"
 Start each component individually

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.