File Naming Conventions Output File Format

9-8 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 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. Varchar128 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. Varchar150 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 Column Description 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 ■ Chapter 17, Configuring and Managing the Oracle BI Presentation Catalog 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 10.1 Why Upload a Repository and Set the Catalog Location? As the administrator, you must ensure that users can access the metadata repositories and Oracle BI Presentation Catalogs that contain the information that they require. The following list describes the importance of uploading the repository and setting the catalog location: ■ Upload Repository — Uploading a repository enables the Oracle BI Server to load the repository into memory upon startup and makes the repository available for queries. When you upload a repository file, you provide the name and location of the repository file and the current repository password. The uploaded repository is available to clients of Oracle BI Server, including to Oracle BI Presentation Services. ■ Set Catalog Location — Setting the location of the Oracle BI Presentation Catalog ensures that its objects are available to users of Oracle Business Intelligence. The catalog is never uploaded. Instead, you copy the catalog files manually to either a local or shared location, then you set the location in Fusion Middleware Control.

10.1.1 Understanding Modes

You can upload the repository in either shared mode, which is recommended, or in distributed mode, as described in the following list: ■ In shared mode, each Oracle BI Server instance loads the repository from the shared network location designated as the repository upload directory. You typically upload the repository in the recommended mode of shared when you have multiple Oracle BI Server components in the deployment. Repositories that are uploaded through Fusion Middleware Control are uploaded to both the shared location and the default local directory for each Oracle BI Server.