Understanding the Contents of Exception Logs

If an Essbase Server, an application, or a database shuts down abnormally and cannot restart, Essbase Server generates an exception log to help troubleshoot the problem. The location of the exception log depends on which component shut down abnormally and the amount of information that Essbase Server had available at the time. Table 148, Location of the Exception Log describes the location of the exception log for each type of abnormal shutdown.

Table 147 lists the sections of the exception log and the information included in each section. If Essbase Server could not retrieve all the information before the shutdown finished, some of the later sections may be blank.

Table 147. Contents of the Exception Log (log00001.xcp)

Section of Log

Information Included

General information

  • Date and time

  • Application and database name

  • Location of exception log

  • Process type

Use this information to determine which component shut down abnormally and when it shut down.

Machine registers and stack information

  • General registers

  • Floating point registers

  • Hex registers

  • Stack trace

  • Stack dump

Oracle Support can examine this section of the log to help determine why an abnormal shutdown may have occurred.

Application-wide configuration

  • Server and application name

  • Elapsed application time; that is, how long the application was running

  • List of modules

Use this information to determine whether the application shut down quickly and that all modules are correct. More information about modules is in the system-wide configuration section of the exception log.

Operating system resources

  • System date and time

  • Elapsed operating system time; that is, how long the operating system was running

  • Resource information, including CPU type, memory information, swap information, and drive information

Use this information to see if it is an operating system problem, such as a lack of memory.

System-wide configuration

  • Elapsed Essbase time; that is, how long Essbase was running

  • Essbase release information

  • Network information

  • Environment variables

  • Module information, including module name and release

Use this information to ensure that the release is the same for Essbase and each module, and that environment variables are set correctly.

essbase.cfg values

Values of all settings in the essbase.cfg file.

Use this information to make sure that Essbase Server is configured correctly.

License information

  • Serial number and license expiration date

  • Number of ports purchased and ports in use

  • Essbase options enabled

  • Other Oracle Hyperion products enabled

Use this information to ensure that the correct options of Essbase are installed and that you have purchased enough ports.

Client request activity

  • Server name

  • Application name

  • Thread information, including the number of threads

  • Request information

  • Detailed information about each thread, including the action it is performing, the database, user name, start time, and end time

Use this information to determine how heavy the load on the server was, based on client requests.

File information

  • Page file size

  • Index file size

Use this information to determine whether the page file or the index is too large.

Database information

Use this information to ensure that the database is set up correctly.

Database statistics

Use this information to view dimension information and to see characteristics of data blocks in the database.