Oracle bi log files

Oracle Analytics Server components control their diagnostic log files by using server-specific settings in their log configuration files, for example:. See Manage the Query Log. Categories and levels for log file messages define the detail and level of importance with which the system writes messages to a log file.

Fusion Middleware Control enables you to control these settings in the logconfig. Each message category in a log file is set to a specific default value between 1 and 32, and only messages with a level less than or equal to the log level is logged. A serious problem caused by unknown reasons has occurred. You can fix the problem only by contacting Oracle Support Services.

An action occurred or a condition was discovered that must be reviewed and might require action before an error occurs. A report of a normal action or event has occurred. This could be a user operation, such as "login completed" or an automatic operation such as a log file rotation.

Low performance impact. You can enable this level broadly in a production environment without having a significant performance impact in the software. A trace or debug message that is used for debugging or performance monitoring has been written. Typically this message contains detailed event data that is clear enough to be understood by someone who does not know internal implementation details.

Small performance impact. This level might be enabled broadly occasionally on a production environment to debug issues with the software. Enabling logging at this level might have a small performance impact, but not to the point of making the software unusable.

A fairly detailed trace or debug message has been written. The message is clear enough to be understood by Oracle Support Services engineers who have a deep knowledge of the product but might not know full details of the internal implementation.

High performance impact. This level mustn't be enabled on a production environment, except on special situations to debug issues with the software.

A highly detailed trace or debug message has been written. The message is intended for an Oracle developer working on the software who knows enough details about the implementation of the subsystem that generates the message. Very high performance impact. In addition to the log file settings that you can change in Fusion Middleware Control , you can change other settings manually.

Use various elements in the log configuration file for a component to change these settings. You can use the Log Viewer in Fusion Middleware Control to find messages that can assist you in resolving issues with the system. The Log Messages page is displayed. The Log Viewer collects lines from all log files and displays them on this page. You can filter the lines to view the ones in which you're interested. To start filtering the list, enter search criteria to locate the messages in which you're interested:.

If you know that an error occurred around a certain date, then set the Date Range to Time Interval. Select the start and end dates for filtering. If the error happens continually, then set the Date Range to Most Recent.

Select Days and specify a number such as 1 or 3. If the number of messages that's returned is too large, then deselect Notification to see only errors and warnings. The advantage of selecting Notification is that you can see what the Oracle Analytics Server system was doing, which can assist you in determining where something went wrong. Click Add Fields , then select Module , and click Add.

Ensure that Module is set to contains , then enter the following value:. That value specifies the name of the Java package from which all log entries for systems management originate. Under Application Deployments, expand bipublisher From the menu, click Logs and then Log Configuration , as shown in the following figure:. By default, the bipublisher-handler log is created. Select bipublisher-handler in the table and click Edit Configuration. You can view log messages using Oracle Fusion Middleware Control or you can view the log files directly.

From the menu, click Logs and then View Log Messages , as shown in the following figure:. Navigate to the directory on your server to view the log file:. Performance monitoring enables you to monitor the performance of queries, reports and document generation and to analyze the provided details. The following table summarizes the beans that are provided:.

Locate the xmlp-server-config. This property enables the integration of performance monitoring and auditing with Oracle Fusion Middleware Control.