5/26/2018 Consistency Check & Logging Level

1/3

http://deliverbi.wordpress.com/category/obiee-11g-query-log-levels/

http://gerardnico.com/wiki/dat/obiee/loglevel

http://santoshbidw.wordpress.com/category/obiee-10g/obiee-10g-rpd/consistency-check/

Consistency check is one of the process to check whether a repository is yieldin

g proper results in Answer reports. It checks whether;

All logical columns are mapped correctly to physical columns.

All logical dimension tables have a logical key.

There are at least two logical tables in the business model; one is a logical fact table, the other is logical dimension table with join condition.

There are no circular logical join relationships.

A presentation catalog exists for the business model.

Types of ChecksThere are mainly three types of checks performed

1. Errors: Must be fixed to make the repository consistent.2. Warnings: Condition that may or may not be an error.3. Best Practice: Does not indicate an inconsistency.

Disable or Enable Consistency CheckNavigate to File menu -> Check Global Consistency > Option Tab.Select any object in the list type of check and click on enable or disable.

-----------------------------------------------------------------

Query Logging set in the RPD .Goto Identity Menu in RPD and Filter a User Type in Username wanted and set thelogging level

Query Logging LevelsLogging LevelInformation That Is Logged

Level 0No logging.

Level 1

Logs the SQL statement issued from the client application. Also logs the following:

Physical Query Response Time The time for a query to be processed in the back-end database.Number of physical queries The number of queries that are processed by the back-end database.Cumulative time The sum of time for all physical queries for a request (that is,the sum of all back-end database processing times and DB-connect times).DB-Connect time The time taken to connect to the back-end database.

5/26/2018 Consistency Check & Logging Level

2/3

Query cache processing The time taken to process the logical query from the cache.Elapsed time The time that has elapsed from when the logical query is presentedto the BI Server until the result is returned to the user. Elapsed time can never be less than response time, because elapsed time takes into account the smallextra time between the logical query being presented to the BI Server to the start of preparation of the query. In cases where this delta time is negligible, the elapsed time equals the response time.Response time The time taken for the logical query to prepare, execute, and fetch the last record.Compilation time The time taken to compile the logical query.

For each query, logs the query status (success, failure, termination, or timeout), and the user ID, session ID, and request

Level 2Logs everything logged in Level 1.Additionally, for each query, logs the repository name, business model name, subject area name, SQL statement issued against the physical database, queries issued against the cache, number of rows returned from each query against a physicaldatabase and from queries issued against the cache, and the number of rows returned to the client application.

Level 3Logs everything logged in Level 2.

Additionally, adds a log entry for the logical query plan, when a query that wassupposed to seed the cache was not inserted into the cache, when existing cacheentries are purged to make room for the current query, and when the attempt toupdate the exact match hit detector fails.

Level 4Logs everything logged in Level 3.Additionally, logs the query execution plan.

Level 5Logs everything logged in Level 4.Additionally, logs intermediate row counts at various points in the execution plan.

Level 6 and 7Not used.

5/26/2018 Consistency Check & Logging Level

3/3