The following log example shows all the entries written to appname.log when Essbase Server starts. The log file 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]
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(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(1070013) Index cache size ==> [1048576] bytes, [1024] index pages.
[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: