You can test the repository for mistakes by using using the consistency checking choice. Once it is carried out, subsequent step is to load the repository into Oracle BI Server. Then take a look at the repository by means of walking an Oracle BI analysis and verifying the effects.
Go to File → click on Check Global Consistency → You will receive the subsequent message → Click Yes.
Once you click OK → Business model beneath BMM will trade to Green → Click on keep the repository without checking international consistency again.
To improve query overall performance, it is suggested to disable BI server cache choice.
Open a browser and enter the subsequent URL to open Fusion Middleware Control Enterprise Manager: http://<machine name>:7001/em
Enter the consumer call and password. Click Login.
On the left facet, amplify Business Intelligence → coreapplication → Capacity Management tab → Performance.
Enable BI Server Cache phase is by means of default checked → Click on Lock and Edit Configuration → Close.
Now deselect cache enabled option. It is used to enhance question performance. Go to Apply → Activate Changes → Completed Successfully.
Load the Repository
Go to Deployment tab → Repository → Lock and Edit Configuration → Completed Successfully.
Click on Upload BI Server Repository phase → Browse to open the Choose document dialog field → pick the Repository .Rpd document and click on Open → Enter Repository password → Apply → Activate Changes.
Activate Changes → Completed Successfully → Click on Restart to apply current adjustments option on the pinnacle → Click Yes.
Repository is efficiently created and loaded for query analysis.
Enable Query Logging
You can set up query logging stage for man or woman users in OBIEE. Logging stage controls the facts that you will retrieve in log file.
Set Up Query Logging
Open the Administration device → Go to File → Open → Online.
Online mode is used to edit the repository in Oracle BI server. To open a repository in on-line mode, your Oracle BI server have to be going for walks.
Enter the Repository password and consumer name password to login and click on Open to open the repository.
Go to Manage → Identity → Security Manager Window will open. Click BI Repository at the left side and double-click on Administrative consumer → User dialogue field will open.
Click User tab in consumer talk field, you can set logging degrees here.
In normal scenario − The person has a logging degree set to zero and the administrator has a logging level set to two. Logging stage could have values starting from Level 0 to level 5. Level 0 way no logging and Level five approach most logging stage information.
Logging Level Descriptions
|Level 0||No logging|
Logs the SQL statement issued from the client application
Logs elapsed times for query compilation, query execution, query cache processing, and back-end database processing
Logs the query status (success, failure, termination, or timeout). Logs the users ID, session ID, and request ID for each query
Logs everything logged in Level 1
Additionally, for each query, logs the repository name, business model name, presentation catalog (called Subject Area in Answer) name, SQL for the queries issued against physical databases, queries issued against the cache, number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application
Logs everything logged in Level 2
Additionally, adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to udate the exact match hit detector fails
Logs everything logged in Level 3
Additionally, logs the query execution plan.
Logs everything logged in Level 4
Additionally, logs intermediate row counts at various points in the execution plan.
In consumer communicate field, input fee for logging stage.
Once you click OK, it will open the checkout communicate container. Click Checkout. Close the Security Manager.
Go to document → Click on check-in modifications → Save the repository the usage of the Save alternative on the top → To take adjustments in effect → Click OK.
Use Query Log to Verify Queries
You can take a look at question logs once question logging degree is set by way of going to Oracle Enterprise Manager and this facilitates to verify queries.
To take a look at the question logs to confirm queries, visit Oracle Enterprise Manager OEM.
Go to diagnostic tab → click Log messages.
Scroll right down to backside in log messages to peer Server, Scheduler, Action Services and different log info. Click on Server log to open log messages field.
You can pick out various filters − Date Range, Message sorts and message consists of/now not contains fields, and so forth. As proven in the following snapshot −
Once you click on on seek, it will display log messages as according to filters.
Clicking on collapse button lets in you to test info of all log messages for queries.