Details about OM: Debug Level profile in Order Management

OM: Debug Level  -  ONT_DEBUG_LEVEL

This profile option is used to store debug messages to assist in problem identification. The OM: Debug profile option controls which debug messages get written to the debug log based on their assigned level. The directory to be specified for this profile should be available in utl_file_dir parameter of the init.ora file (or check v$parameter) of the application database instance.

Assigning a value greater than 0 or NULL causes debugging to be turned on. The value of this option determines the level of debug messages printed within a log file. For example, if OM: Debug Level has a current value of 3, all debugging messages with a level of 1,2 or 3 will be spooled out to the debug log.

Valid values for this profile option are:

NULL: Do not print any debug messages

1:Level 1; Print a limited subset of debug messages (level 1)

2:Level 2; Print a limited subset of debug messages, including level 1

3:Level 3; Print a limited subset of debug messages, including levels 1,2

4:Level 4; Print a limited subset of debug messages, including levels 1,2 3

5:Level 5; Print all debug messages

If you set this profile option to a value other than NULL, system performance may be affected, because creating and updating a debug log is a task that will consume a lot of system resources as you enter higher debug levels.

Order Management recommends you set this profile option only if you are attempting to gather additional details for unexpected application issues and then reset the value back to NULL once you have gathered the necessary debug details.

The default for this profile option is NULL.