Description of the Usage Tracking Data

Table 9–2 describes each column in the usage tracking table. Where appropriate, the data type and length is also included.

Table 9–2 Usage Tracking Data

Column Description

CACHE_IND_FLG Default is N.

Y indicates a cache hit for the query; N indicates a cache miss. COMPILE_TIME_SEC The time in seconds that is required to compile the query. CUM_DB_TIME_SEC The total amount of time in seconds that the BI Server waited for

back-end physical databases on behalf of a logical query. CUM_NUM_DB_ROW The total number of rows that are returned by the back-end

databases.

END_DT The date the logical query was completed.

Description of the Usage Tracking Data

Managing Usage Tracking 9-7

END_TS The date and time the logical query finished. The start and end timestamps also reflect any time that the query spent waiting for resources to become available.

Note: If the user submitting the query navigates away from the page before the query finishes, then the final fetch never happens, and a timeout value of 3600 is recorded. However, if the user navigates back to the page before the timeout, then the fetch completes at that time, and this is recorded as the end_ts time. ERROR_TEXT Default is Null. Varchar(250)

Error message from the back-end database. This column is only applicable if the SUCCESS_FLG (for more information, see entry later in this table) is set to a value other than 0 (zero). Multiple messages are concatenated and are not parsed by the BI Server. NODE_ID The host name of the computer where the BI Server is running. NUM_CACHE_HITS Default is Null. Number(10,0).

For DB2, the data type and length is Decimal(10,0).

Indicates the number of times that the cache result returned for query.

NUM_CACHE_ INSERTED

Default is Null. Number(10,0).

For DB2, the data type and length is Decimal(10,0).

Indicates the number of times that the query generated a cache entry.

NUM_DB_QUERY The number of queries that were submitted to back-end databases to satisfy the logical query request. For successful queries (SuccessFlag = 0) this number is 1 or greater. PRESENTATION_NAME Default is Null. Varchar(128)

The name of the Oracle BI Presentation Catalog.

QUERY_BLOB The data type is ntext when using SQLServer, and is CLOB

when using ORACLE, DB2, or TERRADATA databases.

Contains the entire logical SQL statement without any truncation. QUERY_KEY Default is Null. Varchar(128).

An MD5 hash key that is generated by Oracle Business Intelligence from the logical SQL statement.

QUERY_SRC_CD The source of the request (for example, Drill or Report).

QUERY_TEXT Varchar (1024).

The SQL statement that was submitted for the query. You can change the length of this column (using the ALTER TABLE command), but note that the text that is written into this column is always truncated to the size that is defined in the physical layer. It is the responsibility of the repository administrator not to set the length of this column to a value greater than the maximum query length that is supported by the back-end physical database.

For example, Oracle Databases enable a maximum Varchar of 4000, but Oracle Databases truncate to 4000 bytes, not 4000 characters. Hence, if you use a multibyte character set, the actual maximum string size has a varying number of characters, depending on the character set and characters used. REPOSITORY_NAME The name of the repository that the query accesses. Table 9–2 (Cont.) Usage Tracking Data

Description of the Usage Tracking Data

ROW_COUNT The number of rows that are returned to the query client.

Note: When a large amount of data is returned from a query, this column is not populated until the user displays all of the data. IMPERSONATOR_USER_

NAME

Default is Null. Varchar(128)

The user name of the impersonated user. If the request is not run as an impersonated user, then the value is NULL.

SAW_DASHBOARD The path name of the dashboard. If the query was not submitted through a dashboard, then the value is NULL.

SAW_DASHBOARD_PG Default is Null. Varchar(150)

The page name in the dashboard. If the request is not a dashboard request, then the value is NULL.

SAW_SRC_PATH The path name in the Oracle BI Presentation Catalog for the analysis.

START_DT The date that the logical query was submitted.

START_HOUR_MIN The hour and minute that the logical query was submitted. START_TS The date and time that the logical query was submitted. SUBJECT_AREA_NAME The name of the business model that is being accessed. SUCCESS_FLG The completion status of the query, as defined in the following

list:

■ 0 - The query completed successfully with no errors. ■ 1 - The query timed out.

■ 2 = The query failed because row limits were exceeded. ■ 3 = The query failed due to some other reason.

TOTAL_TIME_SEC The time in seconds that the BI Server spent working on the query while the client waited for responses to its analyses. This setting is the same as the Response time in the nqquery.log file, as described in Section 8.4.1.1, "Setting the Query Logging Level."

USER_NAME The name of the user who submitted the query. Table 9–2 (Cont.) Usage Tracking Data

Part V

Part V

Configuring Oracle Business Intelligence

Although the installer installs Oracle Business Intelligence with a functional sample application, some functionality requires additional configuration changes (for example, the specification of connection details to external systems and e-mail systems). You can also modify default configuration settings to adapt Oracle Business Intelligence to your environment and user needs.

This part includes the following chapters:

■ Chapter 10, "Configuring Repositories"

■ Chapter 11, "Configuring Connections to External Systems" ■ Chapter 12, "Configuring Presentation Setting Defaults" ■ Chapter 13, "Configuring Mapping and Spatial Information" ■ Chapter 14, "Configuring Time Zones"

■ Chapter 15, "Localizing Oracle Business Intelligence" ■ Chapter 16, "Configuring Currency Options"

10

Configuring Repositories 10-1

10

Configuring Repositories

You can use Fusion Middleware Control to upload the Oracle BI metadata repository and to set the location of the Oracle BI Presentation Catalog. This chapter includes the following topics:

■ Section 10.1, "Why Upload a Repository and Set the Catalog Location?"

■ Section 10.2, "Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location"

■ Section 10.3, "Using the System MBeans to Upload the Metadata Repository"