C Log File Locations

A number of log file types are available for diagnostics in the following categories:

• Weblogic logs

• Data and script logs

• ASO Solver logs and dump files

Weblogic Logs

Server logs are available for each administrative or managed server, at the following path:<WLS DOMAIN>/servers/<SERVER NAME>/logs

Some common logs that can contain information relevant to the ORASE applications include:

• <SERVER NAME>.log

• <SERVER NAME>-diagnostic.log

• access.log

Refer to the Oracle WebLogic Support documentation for details on contents of these log files.

Database Logs

Linux script logs are located in these subdirectories of the RSE HOME directory:

• ./common/data/log

• ./common/scripts/log

• ./cdm/cis/scripts/log

• ./cdm/cis/data/log

• ./cdm/mba/data/log

• ./cdm/mba/scripts/log

• ./cdm/dt/data/log

• ./cdm/dt/scripts/log

• ./cdm/cdt/data/log

• ./cdm/cdt/scripts/log

• ./so/data/log

• ./so/scripts/log

The data/log directories will contain logs for any SQL Loader file loading, while the scripts/log directories would contain logs for any .ksh scripts that were run.

Additionally, database logs can be found in the ORASE schema in a table called RSE_LOG_MSG. The database code has an option to log to this table. Any PL/SQL code errors will automatically have their error messages written to this table with a LOG_LEVEL='ERROR'.

It is also possible to enable the database PL/SQL code to write additional levels of messages to this table. The PL/SQL code supports conditional compilation options for the following:

• DEBUG_DATA - This compilation option is not a logging option, but it will make the code retain any transient tables, instead of allowing the code to purge them when the code is complete with the table. This is useful for debugging purposes, but can result in a large amount of used space, and therefore should be used sparingly.

• DEBUG_MODE - This compilation option will trigger logging of additional log messages so the code can report more granular information about the code is doing. This is not necessarily available for all routines, but setting this will not be detrimental. These log messages normally will appear with a LOG_LEVEL='DEBUG'.

• DEBUG_SQL - This compilation option will result in the PL/SQL code to record all dynamic SQL statements to be written to the log table. This can be useful for debugging. These log messages should appear as LOG_LEVEL= 'SQLSTMT'.

• DEBUG_TRACE - This compilation option will result in all procedures, and many functions to record start and end messages, along with a record of any parameters passed to the routines. These log messages should appear with a LOG_LEVEL=' TRACE'. These logging entries can be useful for tracking application performance.

An example to disable all the extra logging information is as follows:

-       alter TYPE RSE_SLS_TXN_ETL_T compile PLSQL_CCFLAGS = 'DEBUG_DATA:FALSE, DEBUG_MODE:FALSE, DEBUG_SQL:FALSE, DEBUG_TRACE:FALSE' ;

An example to enable all the optional debugging logging and data retention is as follows:

-       alter TYPE RSE_SLS_TXN_ETL_T compile PLSQL_CCFLAGS = 'DEBUG_DATA:TRUE, DEBUG_MODE:TRUE, DEBUG_SQL:TRUE, DEBUG_TRACE:TRUE' ;

Any combination of options may be set to TRUE or FALSE as required.

ASO Solver Logs

ASO writes a set of files for all Optimization problems within every Run executed with ASO at the following location:

<WLS_DOMAIN_HOME>/optresults/csv/<RUN_ID>/<opt problem number>_<fixture type>/

For example: <WLS_DOMAIN_HOME>/optresults/csv/1203/2105_shelf

In this directory are a set of directories and files containing all inputs and results for the last successful execution of that optimization problem. Each RUN_ID may contain many optimization problems.

<WLS_DOMAIN_HOME>/optresults/log/opt_problem_<RUN_ID>_<opt problem number>_*.*

For example: <WLS_DOMAIN_HOME>/optresults/log/opt_problem_1204_2113_287_.log

In this directory are a set of log files for each RUN_ID execution. Note a run can be executed many times so there may be multiple files.

The Gurobi solver also writes the following log:

<WLS_DOMAIN_HOME>/Gurobi.log - this file is useful for start & stop time and a summary of solver execution times.