Log File Characteristics Accessing the Log Files

Managing System Processes 3-39 Information is also captured in logs controlled by the Oracle WebLogic Server Administration Console using Oracle log APIs. The Oracle UCM interface provides access to these logs. For details, see Section 2.6, Viewing Log Information for Oracle Content Server. This section covers the following topics: ■ Section 3.7.1.1, Log File Characteristics ■ Section 3.7.1.2, Accessing the Log Files ■ Section 3.7.1.3, Using Oracle Content Server Logs ■ Section 3.7.1.4, Using Archiver Logs

3.7.1.1 Log File Characteristics

The log files associated with the Oracle Content Server instance have the following characteristics: ■ They are created only once each day at the time the first status, error, or irrecoverable error occurs. ■ No empty log files are generated. Each log file contains the following columns: ■ Type: Specifies the kind of incident that prompted the log entry: Information, Error, or Fatal. ■ Time: Lists the date and time the log entry occurred. ■ Description: Describes the incident that occurred. The log files are standard HTML pages and are maintained for each Oracle Content Server instance. Logs are kept in revolving file name format for a maximum of 30 files. When the 31st file is created, the oldest one is deleted. Therefore, log file names in Oracle Content Server bear no relation to the date they were generated. To find a certain day in the log file, view the index file in a browser and select that days link. The file name is displayed in the browsers status bar if it is enabled.

3.7.1.2 Accessing the Log Files

The log files of the Oracle Content Server instance are normally accessed from the Log Files folder in the Administration tray. Note: When applied to process log output, verbose logging can quickly increase the size of a log file and possibly cause the Oracle Content Server instance to slow down. It is recommended that for process logs, verbose logging is only used when troubleshooting a specific issue. Regular Oracle Content Server logs do not have this issue with verbose logging. Tip: Bookmark your log file pages. This will help you to troubleshoot problems, even if the Oracle Content Server instance is unavailable. Also, know where your configuration files are so you can find them if the Oracle Content Server instance is unavailable. 3-40 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server If, for whatever reason, you cannot view the log files from the Administration tray, you can also access them on the file system of the Oracle Content Server computer. The log files are located in the following locations:

3.7.1.3 Using Oracle Content Server Logs