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-ch eck/

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 fa ct 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 Checks There 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 Check Navigate 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 logging level Query Logging Levels Logging Level Information That Is Logged Level 0 No logging. Level 1 Logs the SQL statement issued from the client application. Also logs the followi ng: Physical Query Response Time The time for a query to be processed in the back-en d database. Number of physical queries The number of queries that are processed by the backend 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. Type in Username wanted and set the

Query cache processing The time taken to process the logical query from the cach e. Elapsed time The time that has elapsed from when the logical query is presented to the BI Server until the result is returned to the user. Elapsed time can neve r be less than response time, because elapsed time takes into account the small extra time between the logical query being presented to the BI Server to the sta rt of preparation of the query. In cases where this delta time is negligible, th e elapsed time equals the response time. Response time The time taken for the logical query to prepare, execute, and fetc h 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 2 Logs everything logged in Level 1. Additionally, for each query, logs the repository name, business model name, sub ject area name, SQL statement issued against the physical database, queries issu ed 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 retu rned to the client application. Level 3 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 update the exact match hit detector fails. Level 4 Logs everything logged in Level 3. Additionally, logs the query execution plan. Level 5 Logs everything logged in Level 4. Additionally, logs intermediate row counts at various points in the execution pl an. Level 6 and 7 Not used.