Using the Oracle BI Presentation Services Logging Facility Structure for the Oracle BI Presentation Services Configuration File
8.5.3 Examples of the Formats of Logged Messages
The fmtName attribute of the Writer element formats logged messages in one of three formats: default 10g style, ODL-TEXT, and ODL-XML. The following entries are examples of these formats. Example 8–5 shows the default format. Example 8–5 Default Format The default format generates messages with identifying headings, such as: Type: Information Severity: 30 Time: Wed Jul 26 11:22:20 2006 File: project\sawserver\sawserver.cpp Line: 399 Properties: ThreadID-2552 Location: saw.sawserver saw.sawserver.initializesawserver saw.sawserver Oracle BI Presentation Services has started successfully. Example 8–6 shows the ODL-TEXT format. Example 8–6 ODL-TEXT Format The short format generates messages in a shortened form without identifying headings, such as: [timestamp] [component id] [messagetype:level] [message-id] [module id] [field-name: field-value] message-text [[ supplemental-detail ]] [2010-05-27T10:51:20.000-07:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: 1243446680218334471555761] [tid: 2552] Oracle BI Presentation Services OBIPS FilterRecord warning Contains an integer that specifies the severity of the corresponding message type. Only messages with a severity index less than the provided number are logged. FilterRecord error Contains an integer that specifies the severity of the corresponding message type. Only messages with a severity index less than the provided number are logged. FilterRecord trace Contains an integer that specifies the severity of the corresponding message type. Only messages with a severity index less than the provided number are logged. FilterRecord incident_error Contains an integer that specifies the severity of the corresponding message type. Only messages with a severity index less than the provided number are logged. Table 8–3 Cont. Oracle BI Presentation Services Log Configuration File Elements Element Attribute Description 8-20 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 11.1.1.2 Build 0 are starting up.[[ File:sawserver.cpp Line:432 Location: saw.sawserver saw.sawserver.initializesawserver saw.sawserver ecid: 1243446680218334471555761 ]] Example 8–7 shows the ODL-XML format. Example 8–7 ODL-XML Format The xml format generates messages in XML format, such as: msg time=2010-05-08T18:41:05.000+00:00 comp_id=OBIPS type=NOTIFICATION level=1 msg_id= module=saw.sawserver ecid=124180446517874242628761 tid=127c txt Oracle BI Presentation Services has started successfullytxt suppl_detail msg8.5.4 Oracle BI Presentation Services Message Structure
Each message that is logged by Presentation Services has several components, as described in Table 8–4 .8.5.5 Oracle BI Presentation Services Log Filters
FilterRecords customize logging details. Use FilterRecords to specify the implementation output type and logging levels for categories of Web logs: Incident Error, Error, Trace, Warnings, and Information. In the following example, the first two FilterRecords contain the following string: path=saw This string logs the informational events at level 1, the error messages at level 31, and so on: FilterRecord writerClassGroup=Console path=saw information=1 warning=31 error=31 trace=0 incident_error=32 Table 8–4 Components of Presentation Services Log Message Message Component Description Message Text The text of the log message to the user. Message Type One of five types: information, warning, error, incident_error or trace. For information, see Table 8–1 . Severity The severity is represented as a positive integer. The lower the value, the more important the message. A message with severity of 0 is the most important type of message, whereas a message with a severity of 32 is not important at all. Message Properties Properties indicate other kinds of information. The kind varies among messages and might include user name, the IP address of the client browser, the thread ID, and so on. Diagnosing and Resolving Issues in Oracle Business Intelligence 8-21 FilterRecord writerClassGroup=File path=saw information=1 warning=31 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw.mktgsqlsubsystem.joblog information=1 warning=2 error=31 trace=0 incident_error=32 This high-level path applies to every event. You can customize FilterRecords by adding new FilterRecords, such as the third one shown in the preceding example, with finer-grain specification of log levels for events of various types. In this example, information is being logged to a disk file from saw.mktgsqlsubsystem.log, which generates Marketing job events. You can disable logging of job details by changing the information level from 1 to 0, as shown in the following example, or by commenting out the lines: FilterRecord writerClassGroup=Console path=saw information=1 warning=31 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw information=1 warning=31 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw.mktgsqlsubsystem.joblog information=1 warning=2 error=31 trace=0 incident_error=328.5.6 Diagnosing Issues with Agents
If an agent fails to execute fully or if debugging is turned on in Oracle BI Scheduler, then a log file is generated for the agent. You manually turn on debugging by setting the Debug element to True in the Oracle BI Scheduler instanceconfig.xml file. For information, see Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located? The location for agent log files is specified in the instanceconfig.xml file for the Oracle BI Scheduler. For information, see Section 19.3.3.3, Agent Scheduler Configuration Settings. The default location for log files is the Log directory in the Oracle Business Intelligence installation directory on the computer where the Oracle BI Scheduler is installed. The log file name has the following format: Agent-JobID-InstanceID.xxx In this file name: ■ Agent is the prefix for all agent log files. ■ JobID is the Oracle BI Scheduler job identifier for the agent. ■ InstanceID is the Oracle BI Scheduler instance identifier for the agent. ■ xxx is the file extension: – .err for agent error log files. – .log for debug log files. The agent error and debug log files are written as separate files for each agent instance that fails to execute. You can use a text editor to view the files. Entries are generally self-explanatory. The presence of an error log does not necessarily mean that an agent failed completely. For example, suppose an agent delivers content to multiple e-mail addresses. If some addresses are invalid or the mail server is down, then an error log is generated for the agent. 8-22 System Administrators Guide for Oracle Business Intelligence Enterprise Edition You can also view error messages and exit codes for job instances in Job Manager. For information, see Instance Properties in Job Manager in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition. Exit status shows the number of deliveries successfully completed. 9 Managing Usage Tracking 9-1 9 Managing Usage Tracking The Oracle BI Server supports the collection of usage tracking data. When usage tracking is enabled, the Oracle BI Server collects usage tracking data for each query and writes statistics to a usage tracking log file or inserts them directly to a database table. It is strongly recommended that you use direct insertion instead of writing to a log file. If you are upgrading from previous versions of Usage Tracking, then see the usage tracking topics in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. This chapter includes the following topics: ■ Section 9.1, Setting Up Usage Tracking ■ Section 9.2, Description of the Usage Tracking Data9.1 Setting Up Usage Tracking
The Oracle BI Server supports the accumulation of usage tracking statistics that can be used in a variety of ways such as database optimization, aggregation strategies, or billing users or departments based on the resources that they consume. The BI Server tracks usage at the detailed query level. When you enable usage tracking, statistics for every query are inserted into a database table or are written to a usage tracking log file. If you use direct insertion, then the BI Server directly inserts the usage tracking data into a relational database table. It is recommended that you use direct insertion to write statistics to a database table. When the BI Server starts, it validates the column names in the metadata against the list of valid columns in the usage tracking table. The following events occur: ■ Column names. If there is a mismatch between the columns in the database table and the columns in the metadata, then it results in a database error on insert. ■ Varchar length. If the length in the metadata and the set length in the table do not match, then an error is written to the nqserver.log file and usage tracking is disabled. Note: A sample usage tracking implementation is provided with the Oracle Business Intelligence installation at: ORACLE_ INSTANCE\bifoundation\OracleBIServerComponent\coreapplicatio n_obisn\sample\usagetrackingParts
» Oracle Fusion Middleware Online Documentation Library
» What Are the Oracle Business Intelligence System Administration Tasks?
» Getting Started with Managing Oracle Business Intelligence
» A Single Host and Enterprise Install
» A Single Host and Simple Install
» Oracle Business Intelligence on Multiple Hosts
» About Java Components About Java Components and System Components for Oracle Business Intelligence
» What Is the Administration Server?
» Fusion Middleware Control What System Administration Tools Manage Oracle Business Intelligence?
» Oracle WebLogic Server Administration Console
» Oracle Process Manager and Notification Server OPMN Tool
» Oracle Weblogic Scripting Tool WLST
» Oracle BI Administration Tool
» Job Manager What System Administration Tools Manage Oracle Business Intelligence?
» Working with the Sample Application
» Oracle BI Publisher Integration
» Topics of Interest in Other Guides
» System Requirements and Certification
» Why Use Fusion Middleware Control and WebLogic Server Administration Console?
» Logging into Fusion Middleware Control to Manage Oracle Business Intelligence
» Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components
» About the Navigation Tree in Fusion Middleware Control
» Configuring Oracle Business Intelligence
» Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings
» Using the Oracle BI Systems Management API to Update Configuration Settings
» Using a Text Editor to Update Configuration Settings
» Where Are Configuration Files Located?
» About Starting and Stopping Oracle Business Intelligence
» Starting Oracle Business Intelligence on Windows Platforms
» Starting Oracle Business Intelligence on UNIX Platforms
» Using Oracle WebLogic Server Administration Console to Start and Stop Java Components
» Using the OPMN Command Line to Start, Stop, Restart, and View the Status of System Components
» Using a Windows Service to Start and Stop System Components
» Confirming Whether the Administration Server Is Running
» Click Start. Oracle Fusion Middleware Online Documentation Library
» Administration Server Fails to Start When the Database Is Not Running
» Oracle BI Server Fails to Start
» Oracle BI Presentation Services Fails to Start
» Cannot Log In Troubleshooting System Startup
» How Do I Know When to Scale Out Processes?
» What Processes Should I Scale?
» Vertically Scaling Oracle Business Intelligence Horizontally Scaling Oracle Business Intelligence
» Uploading and Sharing the Oracle BI Repository
» Using Fusion Middleware Control to Identify Single Points of Failure
» Achieving High Availability Using an Active-Passive Model
» Using Fusion Middleware Control to Configure Primary and Secondary Instances
» Setting Optional Cluster Controller Parameters
» Setting Optional Presentation Services Parameters
» Setting Optional Oracle BI Presentation Services Plug-in Parameters
» Status Information Viewing and Managing Cluster Information
» Cache Information Viewing and Managing Cluster Information
» Select Action, and then select an option.
» Server Information Viewing and Managing Cluster Information
» Using Fusion Middleware Control to View Common Performance Metrics
» Using Fusion Middleware Control to View All Oracle Business Intelligence Metrics
» Using the Administration Console to View Metrics for Java Components
» About Query Performance Tuning
» Using Fusion Middleware Control to Disallow RPD Updates
» Using Fusion Middleware Control to Set the User Session Log-Off Period
» Using Fusion Middleware Control to Set the Maximum Number of Rows Processed to Render a Table
» Query Cache Architecture About the Oracle BI Server Query Cache
» Advantages of Caching About the Oracle BI Server Query Cache
» Administrative Tasks Costs of Caching
» Keeping the Cache Up To Date
» About the Refresh Interval for XML Data Sources
» Using Fusion Middleware Control to Enable and Disable Query Caching
» Using Fusion Middleware Control to Set Query Cache Parameters
» Manually Editing Additional Query Cache Parameters
» Using Fusion Middleware Control to Set Global Cache Parameters
» Manually Editing Additional Global Cache Parameters
» Disable Caching for the System
» In the Physical Table properties dialog, in the General tab, make one of the
» To set a cache expiration time, specify a Cache persistence time and specify a unit
» Click OK. Caching and Cache Persistence Timing for Specified Physical Tables
» Configure Oracle BI Server Event Polling Tables
» Storing and Purging Cache for SAPBW Data Sources
» Online Mode How Repository Changes Affect the Query Cache
» Offline Mode How Repository Changes Affect the Query Cache
» Switching Between Repositories How Repository Changes Affect the Query Cache
» Changes to Dynamic Repository Variables
» Ensuring Correct Cache Results When Using Row-Level Database Security
» Running a Suite of Queries to Populate the Cache
» Using Agents to Seed the Oracle BI Server Cache
» Displaying Global Cache Information in the Cache Manager
» Select Manage, then Cache to open the Cache Manager dialog.
» Select Cache or Physical mode by selecting the appropriate tab in the left pane.
» Select the cache entries to purge, and then select Edit, then Purge to remove them.
» Polling Table Structure Setting Up Event Polling Tables on the Physical Databases
» Sample Event Polling Table CREATE TABLE Statements
» Making the Event Polling Table Active
» Populating the Oracle BI Server Event Polling Table
» Troubleshooting Problems with Event Polling Tables
» Managing the Oracle BI Presentation Services Cache Settings
» Using Fusion Middleware Control to View Log Information, Error Messages, and Alerts
» Click Lock and Edit Configuration to enable changes to be made.
» Click Apply, then click Activate Changes.
» Return to the Business Intelligence Overview page and click Restart.
» Locate the section in which you must add the Format element, which specifies the
» Include the element and its ancestor elements as appropriate, as shown in the
» What Are Diagnostic Log Files and Where Are They Located?
» What Are Diagnostic Log Configuration Files and Where Are They Located?
» What Are Log File Message Categories and Levels?
» What Messages Are Included in the System Log?
» Setting the Query Logging Level
» Double-click the name of the user for which you want to set the query logging
» Set the logging level by clicking the Up or Down arrows next to the Logging Level
» Click OK. Setting the Query Logging Level for a User
» Running the Log Viewer Utility
» Interpreting the Log Records
» Examples of the Formats of Logged Messages
» Oracle BI Presentation Services Message Structure
» Oracle BI Presentation Services Log Filters
» Diagnosing Issues with Agents
» Setting Up Direct Insertion to Collect Information for Usage Tracking
» Selecting an Output Location
» File Naming Conventions Output File Format
» Performance Considerations Setting Up a Log File to Collect Information for Usage Tracking
» Description of the Usage Tracking Data
» Understanding Modes Why Upload a Repository and Set the Catalog Location?
» Understanding Repository Version Numbers
» Using the System MBeans to Upload the Metadata Repository
» Click OK. Configuring E-Mail and Agents
» Using Fusion Middleware Control to Configure the Connection to the Marketing Content Server
» Configuring to Download Oracle Hyperion Smart View for Office
» Using Fusion Middleware Control to Change Presentation Setting Defaults
» What Are the System Requirements for Map Views?
» Associating Layers with Columns
» Changes to Spatial Metadata Require Restart
» Administration Page Functions Administering Maps
» Administering Maps Using Administration Pages
» Hardware Sizing and Deployment Strategy for Maps Why and Where are Time Zones Used?
» Setting Time Zones Oracle Fusion Middleware Online Documentation Library
» Description of Time Zone Settings
» Example: Configuration File Settings for Specifying the Time Zone
» What Components Are Translated?
» Tasks for Localizing Oracle Business Intelligence Components
» Understanding the Directory Structure for Localizing Presentation Services
» Click Languages. Specifying the Default Language for the Sign-In Page
» Use the Move Up and Move Down buttons to position the desired language at the
» Locate the ServerInstance section, in which you must add the following elements:
» Specifying the Language in the URL
» From the Tools menu, select Export Captions.
» Click Browse to select the location in which to write the output file, then click OK.
» To exclude the Description properties from the export, select Exclude
» Click OK. Step 2: Exporting Text Strings in the Catalog
» Step 1: Understanding the Export Process Step 3: Editing Exported Strings in XML Files
» Click OK. Step 4: Handling Duplicate Exported Text Strings
» The export process not only generates new XML files, but the process also
» Sign into Oracle Business Intelligence and select the appropriate language, such as
» Display the translated content.
» Tip for Arabic and Hebrew in Mozilla Firefox Browsers
» Setting the Current Locale in Catalog Manager
» Setting the Locale on UNIX Systems
» Handling the NLS Locale Not Supported Error Message
» Setting the Japanese Locale on AIX Systems
» Localizing Metadata Names in the Repository
» What is Multilingual Data Support?
» What is Lookup? Supporting Multilingual Data
» What is Double Column Support?
» A Lookup Table for Each Base Table
» A Lookup Table for Each Translated Field
» Creating Logical Lookup Tables
» Designating a Logical Table as a Lookup Table About the LOOKUP Function Syntax
» Creating Logical Lookup Columns
» Creating Physical Lookup Tables and Physical Lookup Columns
» Supporting Multilingual Data in Essbase Through Alias Tables Enabling Lexicographical Sorting
» Defining User-Preferred Currency Options Using a Dynamic Mapping
» Example: Dynamic Mapping to Define User-Preferred Currency Options
» Handling Users of the Catalog
» Handling Heterogeneous Nodes File System Guidelines for Catalogs
» Handling Catalog Files on Various Platforms Known Issues with Catalog Files
» Manually Changing Additional Configuration Settings for the Catalog
» Manually Creating a New Oracle BI Presentation Catalog
» Deploying Catalogs to Production
» Performing a Basic Validation of the Catalog
» Locate the Catalog section in which you must add the elements that are described
» Include the elements and their ancestor element as appropriate, as shown in the
» Save your changes and close the file.
» Guidelines for Working with Catalog Manager
» Tips for Working with Catalog Manager
» Starting Catalog Manager Starting Catalog Manager and Opening Catalogs
» Online Mode Understanding the Two Catalog Modes
» Take Presentation Services on each computer in the cluster out of Maintenance
» Operations Available in Online Mode and Offline Mode
» Opening an Oracle BI Presentation Catalog
» What Does the Catalog Manager Workspace Do?
» What Does the Catalog Manager Workspace Look Like?
» Managing the View of the Catalog Manager Workspace
» Searching for Catalog Objects Using Catalog Manager
» In the source catalog, right-click the source object and select Copy.
» Advanced Options for Pasting Objects
» Renaming Catalog Objects Working with the Properties of Catalog Objects
» Setting Permissions of Catalog Objects
» Previewing Objects from Catalog Manager
» What Happens When Tenants are Provisioned?
» What Options are Available for Provisioning?
» Locate the section in which you must add the EnableMultiTenancy element.
» Viewing and Editing Catalog Objects in XML
» Searching for and Replacing a Simple Catalog Text String
» XML File Format for Searching for and Replacing Text Strings
» Example XML File for Searching for and Replacing Text Strings
» Searching for and Replacing Multiple Catalog Text Strings
» Creating Reports to Display Catalog Data Using Catalog Manager
» Archiving a Folder Using Catalog Manager
» Unarchiving a Folder Using Catalog Manager
» What is a Full-Text Catalog Search?
» Deployment of Oracle Full-Text Catalog Search
» How is Security Handled in the Full-Text Catalog Search?
» Click Administration in the global header.
» On the Administration tab, click Manage Privileges.
» Step 2: Ensuring that Secure Enterprise Search is Available
» Display the Identity Management Setup page using steps such as the following:
» Click Finish. Step 3: Configuring Identity Management for Full-Text Catalog Search
» In the Source Type list, select Oracle Fusion, then click Create.
» If you clicked Create and Customize, then on the Documents tab, add the RTF
» Click Apply. Step 4: Creating the Data Source for Full-Text Catalog Search
» Step 5: Editing the Schedule for Full-Text Catalog Search
» Select Global Settings, then Configure Search Result List in the Out-of-Box
» Enable the replication of the Oracle BI Presentation Catalog.
» Perform a full crawl on the catalog.
» Locate the section in which you must add the Replication element.
» Restart Oracle Business Intelligence.
» Step 8: Configuring Properties for Full-Text Catalog Search Manually
» Step 9: Allowing Users to Access the Full-Text Catalog Search
» Replication Log File Records
» Configuring to Replicate an Oracle BI Presentation Catalog
» Copying Oracle BI Presentation Catalog Files
» mark Using the Oracle BI Presentation Services Replication Agent
» remotecopy Using the Oracle BI Presentation Services Replication Agent
» run Using the Oracle BI Presentation Services Replication Agent
» Structure of the Configuration File
» Elements of the Configuration File
» Editing the instanceconfig.xml File for Replication
» Resuming Replication if Replication Log Files Are Unavailable
» Managing Dashboards Oracle Fusion Middleware Online Documentation Library
» Providing Access to Metadata Dictionary Information
» Supporting Nested Folders, Navigation, and Drill-Down
» Manually Configuring Cube Settings for Pivot Tables and Graphs
» Manually Configuring Settings for Data in Views
» Configuring Fonts for Graphs
» Manually Changing Alternating Bar Color
» Manually Changing Presentation Setting Defaults
» Configuring Links to Dashboard Pages
» Configuring an Alternate Toolbar for Oracle BI Publisher
» Modifying the Table of Contents for PDF Versions of Briefing Books
» Storing JavaScript Files Blocking Analyses in Answers
» Blocking Analyses Based on Criteria
» Blocking Analyses Based on Formula
» Validation Helper Functions Blocking Analyses in Answers
» XML Message Files for View Defaults
» Adding a Default Header or Footer to New Analyses Preventing Auto-Previewing of Results
» Setting Defaults for Analyses in the Compound Layout Changing Dashboards Section Defaults
» Specifying Dashboard Page Defaults Including Headers and Footers
» Write-Back Limitations Configuring for Write Back in Analyses and Dashboards
» Locate the ServerInstance section in which you must add the LightWriteback
» Requirements for the Write-Back Template
» Example: Write-Back Template About the Write-Back Template
» How Does Antivirus Software Affect Agents?
» What Privileges Affect Agents?
» Manually Configuring Presentation Services Settings That Affect Agents
» Manually Changing Additional Scheduler Settings That Affect Agents
» General Scheduler Configuration Settings That Affect Agents
» E-Mail Scheduler Configuration Settings That Affect Agents
» Agent Scheduler Configuration Settings
» Controlling Delivery Options for Agents
» Managing Device Types for Agents
» Monitoring Active Agent Sessions
» Configuring MapViewer to Support Map Views
» Manually Configuring for Map Views
» Inserting Text on a Map Configuring Maps for External Consumption
» What Is the Oracle BI Systems Management API?
» Accessing Oracle BI Systems Management API Methods
» Example: Using a Java Program to Display the Status of Oracle Business Intelligence
» Example: Using WLST Commands to Stop and Start Oracle Business Intelligence
» Example: Using WLST to Edit the E-Mail Sender Display Name Configuration Setting
» Example: Using a Java Program to Edit the E-Mail Sender Display Name Configuration Setting
» Example: Using WLST to Scale Out to Servers
» Example: Using a Java Program to Scale Out to Servers
» Using the Dynamic Monitoring Service for Metrics
» Verify that you are in online mode by viewing the following prompt:
» Descriptions of JMX Admin MBeans and Methods for the Oracle BI Systems Management API
» Step 1: Stop System Component Processes for Oracle BI EE
» Step 2: Invoke OPatch with -rollback Option
» Step 3: Start System Component Processes for Oracle BI EE
» Step 4: Redeploy J2EE Applications
Show more