16
Monitoring Procedures

The log files, found in the $ORACLE_HOME/ocal/log directory, are a useful starting point for troubleshooting problems related to the calendar server's operations or performance.

This chapter covers the following topics:

• Viewing Log Files
• Interpreting Log Files

Viewing Log Files

To view a log file, go to the $ORACLE_HOME/ocal/log directory and open the file using a text editor. Note that log files for utilities are created the first time the utility is run.

Table 16-1 Calendar server log files

Filename	Description
act.log	Tracks calendar usage and monitors possible security violations. To track all signons and signoffs, set the [ENG] activity parameter in unison.ini to TRUE. The size of the act.log file should be closely monitored, since it can increase quickly.
csm.log	For the Oracle Calendar Server Manager.
cws.log	For the Corporate-Wide Services. Set the [CWS] trace parameter in unison.ini to TRUE to log each transaction performed by the CWS. This will cause the size of the cws.log file to increase quickly, and should only be used for a short time for testing or debugging purposes.
das.log	For the Directory Access Service.
dasstats.log	For Directory Access Service statistics.
dbi.log	For node (database) initialization.
dbv.log	Database operation file. Created only if there is a problem.
dsstats.log	For directory server (LDAP) calls.
eng.log	For the Engine.
lck.log	For the Lock Manager.
ocad.log +	For the Oracle Calendar Administrator.
script.log	For all UNIX utilities.
snc.log	For the Synchronous Network Connections.
stats.log	Tracks CPU consumption, user wait times, and network traffic for calendar server user sessions. Session statistics are output once a client session is terminated normally. To enable this logging, set the [ENG] stats parameter in unison.ini to TRUE. The size of the stats.log file should be closely monitored since it can increase quickly.
<utility>.log	For various utilities that create and update self-named log files when they are run.
+ The ocad.log file is located in the $ORACLE_HOME/ocad/bin directory.

Interpreting Log Files

Much of the content of the calendar server log files is self-explanatory, namely the sections referring to the status of the various daemons/servers. Interpreting other sections may require the knowledge and resources of a qualified support representative. If you are uncertain about the content of a log file, use Oracle MetaLink to search for log file information or to log a Technical Assistance Request (TAR) online.