How to trace Essbase errors and check logs - Part2

Essbase logs, we need to check for any issues.

ESSBASE.LOG                                        —    Essbase Server activities and errors

ESSBASE_ODL.log                                 —    Essbase Server activities and errors

dataload_ODL.err                                     —    Data load and dimension build errors

log0000x.xcp                                            —    Errors that result when Essbase Server stops abnormally

leasemanager_server_HOSTNAME.log  —    Essbase Server Lease Manager information

leasemanager_essbase_HOSTNAME.log—    Essbase Agent Lease Manager information

log00001.xcp                                            —    Errors that result when the agent stops unexpectedly

easserver.log                                             —    Administration Services Server activity

EssbaseAdminServices0.log                    —    Administration Services Java web application activity

opmn.log                                                  —    Information about when Essbase starts, stops, and how                                                                                 many stop and start retry attempts are made

console~ESSBASE_CLUSTER_NAME~ESSBASE_PROCESS_TYPE~AGENT~1.LOG — All console messages are directed to a file that is called the "console" output file for a managed process, in this case, Essbase.

Note: ESSBASE.LOG and ESSBASE_ODL.log contain the same information in different formats.

Thanks,

Mady

How to trace Essbase errors and check logs - Part1

     While working with Essbase, we may face lot of issues in our day to day activities. Here, I am going to update how to check errors and validate connections of Essbase. Why because, Essbase runs with OPMN in most of the deployments.

Frist of all, Essbase is an multi-dimensional database, so we will have all data saved into the Essbase Arbor path only. Most of the issues, will be with data only. Example as blow:

1. Error while loading data

2. Error while Retrieving data

3. Error while updating or loading Metadata.

4. smartview data validations etc.

Along with those, lot of admin issues will be happening in our daily activities. Like, connectivity, user access, space getting full, compression not happening, cache setting errors, Restructuring errors etc.

So, whatever issue if our work will get impact, then only It is issue. 😄

You will find errors in below logs:

Fist of all, Essbase log. Navigate to the Essbase.log Path, to find the Essbase.log.

Along with Essbase.log, in the same folder, we can find Essbase_ODL.log files, which log will be rotating and will be created as multiple files.

You can search with error, login name, process key words.

If you find xcp file in application folder, then application may corrupted/recovered from corruption.

If you find xcp file in Database folder, Then Database may corrupted either data or entire database.

(you can try renaming .apb as .app for applications or .dbb as .db for database as initial step. If itwon't work, try to contact with Infra team to restore database/application. You can contact Oracle also to find RootCause for generaing xcp files.)

Will continue in next part about analysis and tracing logs...!! 👍

How to trace Essbase errors and check logs - Part2

Thanks,

Mady