Skip to Content

OLAP Data Access Logging: Part 1 – Introduction and basic settings – Introduction and basic settings
OLAP Data Access Logging: Part 2 – Modules and Components – Modules and Components
OLAP Data Access Logging: Part 3 – API call timings – API call timings
OLAP Data Access Logging: Part 4 – Query logging – Query logging
OLAP Data Access Logging: Part 5 – Log Formatting – Log Formatting
OLAP Data Access Logging: Part 6 – Assertions, Unix and 64 bit Windows – Assertions, Unix and 64 bit Windows
Part 7 – Choosing the correct settings and example defaults

Full article also available in SDN’s Article section here.

Choosing the correct settings

When thinking about what level to set logging at the situation is very important to consider. Just running with all logging turned on at full verbosity is rarely what is required. It will also generate huge amounts (gigabytes) of information quite quickly and introduce a performance overhead to the software. The following are possible situations and suggested registry settings to match the situation.

Logging in concurrent environment

If it is expected that multiple users will be using the system concurrently at the same time then it is advisable to add the thread ID into the log format. This will help separate out individual user’s activities in a situation where consecutive lines in the log file may be from two separate users doing totally separate things. The concurrent user case would be the expected situation for most deployments except if the tool being used is a desktop client tool like the Crystal Reports designer or the Web Intelligence rich client.

Monitoring a successfully running production system

If a system has been up and running successfully for a while it can be tempting to run the system with no logging at all, but it is useful to turn on minimal logging so that if an incident should happen there is at least some information available. Therefore it might be prudent to turn logging on at a verbosity of critical or serious for all modules and components. This can be done by deleting the MODULES folder and everything beneath it and just having a single Verbosity value set to 1 or 2 in the root Log folder. For example

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALog]

“Verbosity”=dword:00000002

Monitoring a system with intermittent problems

If a system is suffering intermittent problems such as users experiences errors or performance problems it might be advisable to turn up the logging to see if the source of the problems can be narrowed down. So if the problems are errors then the verbosity set in the above example could be raised to Warning or even Info. If there performance problems are being experienced, the API call timing logging could be turned on with a threshold set sufficiently high to only capture extremely long running API calls.

Narrowing down a critical issue on a production system and trouble shooting on a development environment

If critical but undiagnosed issues are occurring on a production system, or a system is under development and in need of regular trouble shooting then a rather more aggressive selection of logging may be advisable. It is still not advisable to turn everything on at the highest level but there are targeted segments of logging that generally give a good initial picture when troubleshooting.

The modules to turn on to full verbosity are APIMODULE or COMWRAP depending on the version in use. This gives an indication of what is being asked of the OLAP Data Access component by the layer above. The other module to turn on is the one associated with the particular data source being used. The modules are ODBOMODULE, ESSBASEMODULE or SAPMODULE. The next section gives some examples of good default registry settings for such a situation.

Example default settings

XI R2

Web Intelligence, Crystal Reports and OLAP Intelligence

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)Asserts]

“Model”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)Log]

“Location”=”C:Program FilesBusiness ObjectsOLAP Intelligence 11.5Bin”

“LogFile”=”C:Program FilesBusiness ObjectsOLAP Intelligence 11.5Binsofa.log”

“Overwrite”=”Yes”

“AppendPID”=”Yes”

“Verbosity”=”2”

“LogFormat”=”%T: %I: %X: %C: %m” 

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModules]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesCOMWRAP]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesCOUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesRORFLATTENER]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesODBOMODULE]

“Verbosity”=dword:0000000a

“MDX Query Log”=”C:Program FilesBusiness ObjectsOLAP Intelligence 11.5Binodbomdx.log”

“MDX Query Clock”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesSAPMODULE]

“Verbosity”=dword:0000000a

“MDX Query Log”=”C:Program FilesBusiness ObjectsOLAP Intelligence 11.5Binsapmdx.log”

“MDX Query Clock”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesESSBASEMODULE]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5OLAP IntelligenceOCCA(o)LogModulesASSERTION]

“Verbosity”=dword:00000001

Voyager

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDAAsserts]

“Model”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALog]

“LogFile”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 11.5LoggingMDA.log”

“Location”=”C:Program FilesBusiness Objectscommon3.5 in”

“Overwrite”=”Yes”

“AppendPID”=”Yes”

“Verbosity”=”2”

“LogFormat”=”%T: %I: %X: %C: %m”

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULES]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESAPIMODULE]

“Verbosity”=dword:0000000a

“Timer Threshold”=dword:00000000

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESAPIMODULEComponents]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESAPIMODULEComponentsINFO]

“Verbosity”=dword:00000000

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESODBOMODULE]

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 11.5Loggingodbomdx.log”

“MDX Query Clock”=dword:00000001

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESODBOSHAREDUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESSAPMODULE]

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 11.5Loggingsapmdx.log”

“MDX Query Clock”=dword:00000001

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogMODULESESSBASEMODULE]

“Verbosity”=dword:0000000a

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.5VoyagerMDALogModulesASSERTION]

“Verbosity”=dword:00000001

XI 3.0 and XI 3.1

Crystal Reports

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)Asserts]

“Model”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)Log]

“LogFile”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0LoggingSOFA.log”

“Location”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86”

“Overwrite”=”Yes”

“AppendPID”=”Yes”

“Verbosity”=”2”

“LogFormat”=”%T: %I: %X: %C: %m”

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModules]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesCOMWRAP]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesCOUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesODBOMODULE]

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0Loggingodbomdx.log”

“MDX Query Clock”=dword:00000001

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesSAPMODULE]

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0Loggingsapmdx.log”

“MDX Query Clock”=dword:00000001

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesESSBASEMODULE]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesODBOSHAREDUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0OLAP IntelligenceOCCA(o)LogModulesASSERTION]

“Verbosity”=dword:00000001

Voyager and Web Intelligence

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDAAsserts]

“Model”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALog]

“LogFile”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0LoggingMDA.log”

“Location”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86”

“Overwrite”=”Yes”

“AppendPID”=”Yes”

“Verbosity”=”2”

“LogFormat”=”%T: %I: %X: %C: %m”

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModules]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesAPIMODULE]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesAPIMODULEComponents]

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesAPIMODULEComponentsINFO]

“Verbosity”=dword:00000000

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesASSERTION]

“Verbosity”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesESSBASEMODULE]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesODBOMODULE]

“Verbosity”=dword:0000000a

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0LoggingODBOMDX.log”

“MDX Query Clock”=dword:00000001

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesODBOSHAREDUTILITIES]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesRORMODULE]

“Verbosity”=dword:0000000a

 

[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesSAPMODULE]

“Verbosity”=dword:0000000a

“MDX Query Log”=”C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0LoggingSAPMDX.log”

“MDX Query Clock”=dword:00000001

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply