This document attempts to answer common questions such as the ones below.
You can let support know if there are additional questions that are not addressed here, in the regular documentation, or elsewhere.
1. How can I turn on debug for components in BSI (Business Service Insight) to get more information in T_LOG?
The logging level for BSI is controlled in the file %OG_HOME%\bin\registry.xml
If you edit the file you can add debugging sections such as shown below:
<LogClient> <ConnectionRecoveryFrequency>10</ConnectionRecoveryFrequency> <SLAExportManager>DEBUG</SLAExportManager> <AllOtherObjects>DEBUG</AllOtherObjects> </LogClient>
Valid components for DEBUG are as follows:
2. Where can I view logging information for BSI?
As long as the logServer service is running on the APP server and the registry.xml file points to this service, all logging information gets put into the system log, or the T_LOG table in the database.
So you can view this through the GUI by going to administration and viewing the system log or by querying the table directly.
For example, you might look for all errors with:
select * from t_log where level_id='E';
or you might find all messages for the past day by running:
select * from t_log where time_stamp > sysdate – 1 order by 1 desc;
3. Are there any physical log files I should be aware of?
There are a couple physical logs you may reference under unusual circumstances.
However, if the logServer service is down (perhaps because it lost connection to the database or the T_LOG tablespace is full) and a legitimate error occurs then this will go into the local logClient.log.
This means there might be cases, such as when you receive an error so large that it does not fit in the Oracle t_log table field, where it makes sense to stop the logServer service and reproduce the problem to get the error in logClient.log.
Thaat physical log would not have the same size constraint the T_LOG table does.
Another case might be where you are trying to debug the logServer service itself (which generally will only have issues if it can't connect to the DB or runs out of tablespace.