Oracle BI Presentation Services Log Filters

9-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition This section contains the following topics: ■ Section 9.1.1, Setting Up Direct Insertion to Collect Information for Usage Tracking ■ Section 9.1.2, Setting Up a Log File to Collect Information for Usage Tracking

9.1.1 Setting Up Direct Insertion to Collect Information for Usage Tracking

Direct insertion is the recommended method for setting up usage tracking. To set up direct insertion, update the following parameters in the Usage Tracking section of the NQSConfig.INI file: ■ ENABLE. Set this parameter to YES to enable usage tracking. ■ DIRECT_INSERT. This parameter determines whether the query statistics are inserted directly into a database table or are written to a file for subsequent loading. Set this parameter to YES to enable direct insertion. ■ PHYSICAL_TABLE_NAME. To insert query statistic information into a table, you must provide the name of the table and the connection pool that is used to access the table see the CONNECTION_POOL parameter. The fully qualified physical table name consists of as many as four components database name, catalog name, schema name, and table name. Each component is surrounded by double quotation marks and separated by a period .. The physical table name must be fully qualified. This fully qualified physical table name must match a table name in the physical layer of the loaded repository. The following is an example of a physical table name for the Usage Tracking table in the Oracle Business Intelligence repository: PHYSICAL_TABLE_NAME = Oracle BI Usage.Catalog.dbo.S_NQ_ACCT ; In this example, Oracle BI Usage represents the database component, Catalog represents the catalog component, dbo represents the schema component, and S_NQ_ACCT represents the table name. ■ CONNECTION_POOL. The fully specified connection pool name has two parts: database name and connection pool name. Each part is surrounded by double quotation marks and separated by a period .. The fully qualified connection pool name should match a connection pool name in the physical layer of the loaded repository. For an example, see the following connection pool name in the Oracle Business Intelligence repository: CONNECTION_POOL = Oracle BI Usage.Connection Pool ; In this example, Oracle BI Usage represents the database component and Connection Pool represents the actual connection pool name. For Usage Tracking insertions to succeed, the connection pool must be configured with a user ID that has write access to the back-end database. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information about configuring connection pools. Note: It is recommended that the connectivity type supports international data. Managing Usage Tracking 9-3 ■ BUFFER_SIZE. This parameter indicates how much memory the BI Server should allocate for buffering the insert statements. Such a buffer lets the BI Server submit multiple insert statements as part of a single transaction, improving Usage Tracking insert throughput. It also means that ordinary analyses do not have to wait on Usage Tracking insertions, which improves average query response time. You might want to adjust this value based on available memory and memory utilization on the server computer. ■ BUFFER_TIME_LIMIT_SECONDS. This parameter indicates the maximum amount of time that an insert statement remains in the buffer before the Usage Tracking subsystem attempts to issue it. This time limit ensures that the BI Server issues the insert statements quickly, even during periods of extended quiescence. ■ NUM_INSERT_THREADS. This parameter indicates the number of threads that remove insert statements from the buffer and issue them to the Usage Tracking database. Assuming separate connection pools for readers and inserters, the number of insert threads should typically equal the Maximum Connections setting in the connection pool. ■ MAX_INSERTS_PER_TRANSACTION. This parameter indicates the maximum number of insert statements that the Usage Tracking subsystem attempts to issue as part of a single transaction. The larger this number, the greater potential throughput for UsageMarathon Tracking inserts. However, a larger number also increases the likelihood of transactions failing due to deadlocks. A small value for BUFFER_TIME_LIMIT_SECONDS can limit the number of inserts per transaction. See Appendix A, NQSConfig.INI File Configuration Settings for additional information about the usage tracking configuration parameters.

9.1.2 Setting Up a Log File to Collect Information for Usage Tracking

Log file collection is an alternate method for configuring usage tracking. Although this feature is supported, it is recommended that you use direct insertion to collect information for usage tracking. See Section 9.1.1, Setting Up Direct Insertion to Collect Information for Usage Tracking for details. The following sections explain how to configure log file collection for usage tracking. Before you configure the log file parameters, you must set the ENABLE parameter in the Usage Tracking section of the NQSConfig.INI file to YES to enable usage tracking. See Appendix A, NQSConfig.INI File Configuration Settings for more information about the usage tracking configuration parameters. This section contains the following topics: ■ Section 9.1.2.1, Selecting an Output Location ■ Section 9.1.2.2, File Naming Conventions ■ Section 9.1.2.3, Output File Format ■ Section 9.1.2.4, Performance Considerations

9.1.2.1 Selecting an Output Location

The STORAGE_DIRECTORY parameter in the Usage Tracking section of the NQSConfig.INI file determines the location of usage tracking log files. If usage tracking is enabled, but no storage folder is specified, then the files are written in the logs folder in the software installation folder for example, in \OBI11g\logs.