Essbase Server and Application Logs

Essbase Server log

Essbase Server writes, or logs, activities that occur in Essbase Server and applications in text files with a .log extension.
The Essbase Server log, named ESSBASE.LOG, is located in this directory in a standard Essbase installation:

• HYPERION_HOME/logs/essbase/ESSBASE.LOG

Application log

Each application on Essbase Server has its own application log, named after the application. For example, the log file for the Sample application is named sample.log. In a standard Essbase installation, application logs are located in one of these directories, depending on the value of the DEFAULTLOGLOCATION configuration parameter:

• HYPERION_HOME/logs/essbase/app/appname
• ARBORPATH/app/appname

Information in application logs can help you pinpoint where and why an error occurred.

Contents of the Essbase Server Log

The information in the ESSBASE.LOG file can help you assess:

• Who performed an operation
• When an operation was performed
• Errors that occurred when an operation was performed or attempted

Table 77 lists the types of actions logged and the information included in the log message. For information about specific error messages, see Oracle Essbase Error Message Reference.

Table 77. Contents of the Essbase Server Log

Type of Action	Information Included
Actions performed at the Essbase Server level, such as logging on Essbase Server or setting security	User name Date and time If changing permissions—User and group information and IP address of user If logging on—Time and date the user last logged on If logging off—Length of time the user was logged on If creating or changing an application or database—Request to create or open the artifact; load, connect, and start the application or database to be created; and lock of the artifact to be created or changed If creating, changing, or viewing an application or database—Requests to list applications and databases and requests to retrieve access information Shutdown or startup requests Requests to retrieve and delete the Essbase Server log
Actions performed at the application level, such as viewing application settings or viewing and changing custom-defined macros, custom-defined functions, and substitution variables	User name Date and time Requests to retrieve operating system resources, license information, and systemwide configuration Retrieving and setting global values If altering substitution variables—Request to list and set substitution variables If altering custom-defined macros—Request to list and delete custom-defined macros Requests to retrieve and delete the application log
Actions performed at the database level, such as creating rules files, outlines, reports, or calculation scripts	User name Date and time Requests to retrieve client settings, user, and group information Requests to list applications and databases Requests to retrieve access information Requests to lock artifacts Returning artifacts

Essbase Server Log Example

The following essbase.log example shows entries written when Essbase Server starts. First, the Sample application and the Basic database are loaded. The log includes information about the time the application and database are loaded, the process ID assigned to the application by the operating system, and the startup of the security authentication module.

Note:

You can use the process ID to stop the application improperly if you are unable to perform a normal shutdown. 

[Tue Nov 06 07:54:16 2001]Local/ESSBASE0///Info(1054014)
Database Basic loaded

[Tue Nov 06 07:54:16 2001]Local/ESSBASE0///Info(1051061)
Application Sample loaded - connection established

[Tue Nov 06 07:54:16 2001]Local/ESSBASE0///Info(1054027)
Application [Sample] started with process id [1300]

[Tue Nov 06 07:54:18 2001]Local/ESSBASE0///Info(1054014)
Database Basic loaded

[Tue Nov 06 07:54:23 2001]Local/ESSBASE0///Info(1051134)
External Authentication Module: [LDAP] enabled

[Tue Nov 06 07:54:23 2001]Local/ESSBASE0///Info(1051051)
Essbase Server - started

The following log shows a single error. The admin user tried to rename an application using a name that already exists on Essbase Server. The log includes information about the user name, the time of the error, and the operation that failed and caused the error.

[Tue Nov 06 08:00:04 2001]Local/ESSBASE0///Info(1051001)
Received client request: Rename Application (from user admin)

[Tue Nov 06 08:00:04 2001]Local/ESSBASE0///Error(1051031)
Application Testing already exists

[Tue Nov 06 08:00:04 2001]Local/ESSBASE0///Warning(1051003)
Error 1051031 processing request [Rename Application] - disconnecting

The next log shows a shutdown. The log includes information about the name of the application shutdown and the time of the shutdown.

[Tue Nov 06 08:00:46 2001]Local/ESSBASE0///Info(1054005)
Shutting down application Sample

[Tue Nov 06 08:00:52 2001]Local/ESSBASE0///Info(1051052)
Essbase Server - finished

Contents of the Application Log

The information in the appname.log file can help you assess:


Who performed a specific operation
When an operation was performed
Errors that occurred when an operation was performed or attempted
Information about dimensions and members to aid in optimization
The name of an artifact used to execute an operation (such as a calc script or load file used to perform a calculation or a data load) if the artifact resides on an instance of Essbase



Table 78 lists the types of actions logged and the information included in the log message.




Table 78. Contents of the Application Log

Type of Action
Information Included

Actions performed at the database level, such as loading data, clearing data, or calculating data


User name
Date and time
Application and database name and time
If starting application—Loading Java modules, and reading and writing database and application information
If loading databases—Information about dimension sizes, dynamic calculation members, blocks, cache sizes, index page size, and I/O information
If starting databases—Application and database setup information, including reading free space information, writing database parameters, retrieving state information, writing application and database definition information, retrieving database volumes, and writing database mapping
If loading—Load command, parallel data load information, cells updated, elapsed load time, and the name of the rules file and data file



Note:

Essbase supplies the load rule name only if the client making the request (for example, Administration Services) is at the same release level as Essbase; for example, Release 7.0.


If calculating—the name of the calculation script used to perform the calculation
If reporting—the name of the report script



Actions performed at the outline level, such as restructuring


User name
Date and time
Information about dimension sizes, dynamic calculation members, blocks, cache sizes, index page size, I/O information, and restructure elapsed time



Actions performed at the spreadsheet level, such as lock and send


User name
Date and time
Action performed









Example of an Application Log


The following topics show example entries in the application log, including a standard startup and shutdown, and an example of the messages logged when an error occurs.



Example 1: Startup Messages in the Application Log


The following log example shows all the entries written to appname.log when Essbase Server starts. The log includes information such as the time the application starts, when application and database information is read and written, when the application is ready for login requests, and when the database is loaded.



[Tue Nov 06 08:47:14 2001]Local/Sample///Info(1002035)
Starting Essbase Server - Application [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1200480)
Loaded and initialized JVM module




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019008)
Reading Application Definition For [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019009)
Reading Database Definition For [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019021)
Reading Database Mapping For [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019010)
Writing Application Definition For [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019011)
Writing Database Definition For [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019022)
Writing Database Mapping For [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013202)
Waiting for Login Requests




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [Load Database]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019018)
Writing Parameters For Database [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019017)
Reading Parameters For Database [Basic]


After Essbase Server starts, it writes information about the dimensions and members in the outline, such as the dimension sizes and dynamic calculation information, to the application log, as shown in the following example:


[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019012)
Reading Outline For Database [Basic]



[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1007043)
Declared Dimension Sizes = [20 17 23 25 5 3 5 3 15 8 6 ]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1007042)
Actual Dimension Sizes = [20 14 20 25 4 3 5 3 15 8 5 ]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1007125)
The number of Dynamic Calc Non-Store Members = [8 6 0 0 2 ]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1007126)
The number of Dynamic Calc Store Members = [0 0 0 0 0 ]


Next, Essbase Server writes information about the blocks in the database, including the block size, the number of declared and possible blocks, and the number of blocks needed to perform calculations (you can use this information to estimate the retrieval performance for members of sparse dimensions tagged as Dynamic Calc) to the application log:



[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1007127)
The logical block size is [1120]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1010008)
Maximum Declared Blocks is [575] with data block size of [1700]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1010007)
Maximum Actual Possible Blocks is [500] with data block size of [192]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1200481)
Formula for member [Opening Inventory] will be executed in [CELL] mode




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1012710)
Essbase needs to retrieve [1] Essbase Kernel blocks in order to calculate the top dynamically calculated block.


Next, Essbase Server writes information about the caches set for each database to the application log:



[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1012736)
The Dyn.Calc.Cache for database [Basic] can hold a maximum of [2340] blocks.




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1012737)
The Dyn.Calc.Cache for database [Basic], when full, will result in [allocation from non-Dyn.Calc.Cache memory].




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019018)
Writing Parameters For Database [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019017)
Reading Parameters For Database [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1070013)
Index cache size ==> [1048576] bytes, [1024] index pages.




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1070014)
Index page size ==> [8192] bytes.




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1070081)
Using buffered I/O for the index and data files.




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1070083)
Using waited I/O for the index and data files.




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019019)
Reading Data File Free Space Information For Database [Basic]...




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1006025)
Data cache size ==> [3145728] bytes, [2048] data pages




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1006026)
Data file cache size ==> [0] bytes, [0] data file pages


The final messages logged at startup refer to general database information:



[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [Get Database Volumes]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [Set Database State]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019018)
Writing Parameters For Database [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019018)
Writing Parameters For Database [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [Get Database State]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [Get Database Info]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1013205)
Received Command [SetApplicationState]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019010)
Writing Application Definition For [Sample]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019011)
Writing Database Definition For [Basic]




[Tue Nov 06 08:47:15 2001]Local/Sample///Info(1019022)
Writing Database Mapping For [Sample]





Example 2: Errors in the Application Log


The following example shows a single error. An unknown member was found in the data load file; the presence of an unknown member caused the load to fail. First, you see the request for the data load, then the error message, and, finally, information messages describing the data values changed by the data load and the data load elapsed time.


[Tue Nov 06 08:49:52 2001]Local/Sample///Info(1013210)
User [admin] set active on database [Basic]

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Info(1013091)
Received Command [DataLoad] from user [admin]

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Info(1003040)
Parallel dataload enabled: [1] block prepare threads,
[1] block write threads.

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Error(1003000)
Unknown Item [500-10] in Data Load, [0] Records Completed

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Warning(1003035)
No data values modified by load of this data file

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Info(1003024)
Data Load Elapsed Time : [0.11] seconds

[Tue Nov 06 08:49:52 2001]Local/Sample/Basic/admin/Info(1019018)
Writing Parameters For Database [Basic]




Example 3: Shutdown Messages in the Application Log


The following messages are logged when Essbase Server performs a normal shutdown. First, information about the database is retrieved. Then the database is unloaded, free space information is written, and the server shuts down.


[Tue Nov 06 08:50:26 2001]Local/Sample///Info(1013214)
Clear Active on User [admin] Instance [1]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Get Database Info]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Get Database State]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Get Database Volumes]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Get Database State]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Get Database Volumes]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013205)
Received Command [Unload Database]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1019018)
Writing Parameters For Database [Basic]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1019020)
Writing Free Space Information For Database [Basic]

[Tue Nov 06 08:50:34 2001]Local/Sample///Info(1013207)
RECEIVED SHUTDOWN COMMAND - SERVER TERMINATING