This section describes how to use ODBC/JDBC procedures to obtain diagnostic information for the Oracle BI Server.
This section contains the following topics:
You can use ODBC/JDBC procedures to obtain diagnostic information for the Oracle BI Server.
These procedures are especially useful on non-Windows platforms where you cannot run the Administration Tool.
Use the nqcmd utility to run the procedures using ODBC. See Using nqcmd to Test and Refine the Repository in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition .
You can also run the procedures using JDBC. For more information about using JDBC to connect to the Oracle BI Server, see the README.TXT file contained in the bijdbc.jar file in ORACLE_HOME/bi/bifoundation/jdbc.
You can first run OBISAvailableDiagnostics() to get a list and description of the diagnostic categories that are available.
See the following example:
call OBISAvailableDiagnostics()
The results appear similar to the following:
| Category | Description |
|---|---|
|
General |
General overview of the OBIS instance you are connected to. |
|
DBInstance:DBNAME1 |
All of the statistics related to the DB instance named in DBNAME1 |
|
DBInstance:DBNAMEn |
All of the statistics related to the DB instance named in DBNAMEn |
|
LDAP:Instance1 |
All of the statistics related to the LDAP instance named in Instance1 |
|
LDAP:Instancen |
All of the statistics related to the LDAP instance named in Instancen |
|
DBConnectionPool:Instance1 |
All of the statistics related to the DB connection pool named in Instance1 |
|
DBConnectionPool:Instancen |
All of the statistics related to the DB connection pool named in Instancen |
|
ThreadPool:Instance1 |
All of the statistics related to the Thread pool named in Instance1 |
|
ThreadPool:Instancen |
All of the statistics related to the Thread pool named in Instancen |
|
Cache:Instance1 |
All of the statistics related to the Cache named in Instance1 |
|
Cache:Instancen |
All of the statistics related to the Cache named in Instancen |
All categories, except for the General category, are Instance categories. Instance categories are statistics related to a particular instance object (like a specific physical database). If multiple instances of an object are initialized, separate categories exist for each instance, in the format category_name:instance_name. See the preceding table for examples.
Note the following about the ODBC/JDBC categories:
The ThreadPool category only displays statistics from threads created and managed by the DbConnection PoolMgr.
The Cache category displays statistics from the Compiler Cache and the LDAP Internal Cache.
Running diagnostics for specific categories helps troubleshoot issues and ensures the system is optimized.
After you obtain the available diagnostic categories, you can call OBISDiagnostics(string) to obtain diagnostics for individual categories, where string is a category name. For example:
call OBISDiagnostics('ThreadPool:orcldb_pool')
The results appear similar to the following:
| Parameter Name | Value |
|---|---|
|
CAPACITY |
1000 |
|
THREAD COUNT |
20 |
|
BUSY THREAD COUNT |
15 |
|
ACCUMULATED REQUESTS |
5 |
|
MAX STACK SIZE |
100 |
The spelling of the category must be correct, or no rows are returned.
Another example might be:
call OBISDiagnostics('General')
The results appear similar to the following:
| Parameter Name | Value |
|---|---|
|
TOTAL SESSIONS |
10 |
|
QUERIES PER SEC |
5 |
|
NEW LOGINS |
10 |
|
ACTIVE LOGINS |
7 |
|
NEW REQUESTS |
30 |
|
DATA CACHE HIT PER SEC |
5 |
|
NEW INIT BLOCKS |
10 |
The following tables provide parameter reference information for each category type.
| Parameter Name | Description |
|---|---|
|
TOTAL SESSIONS |
The total number of sessions connecting clients to the Oracle BI Server. |
|
QUERIES PER SEC |
The number of queries completed each second by the Oracle BI Server. |
|
NEW LOGINS |
The total number of new login requests received by the Oracle BI Server. |
|
ACTIVE LOGINS |
The total number of active logins within the Oracle BI Server. |
|
NEW REQUESTS |
The number of new execute requests received by the Oracle BI Server. |
|
DATA CACHE HIT PER SEC |
The percentage of data cache hits for each second. |
|
NEW INIT BLOCKS |
The total number of new initialization block requests received by the Oracle BI Server. |
| Parameter Name | Description |
|---|---|
|
QUERIES PER SEC |
The number of queries completed each second by the back-end database. |
|
FAILED QUERIES PER SEC |
The number of queries that failed each second in the back-end database. |
|
NEW PREPARES |
The number of prepares sent to the back-end database. |
|
ROWS PER SEC |
The number of rows retrieved each second from the back-end database. |
|
KB PER SEC |
The number of kilobytes retrieved each second from the back-end database. |
| Parameter Name | Description |
|---|---|
|
NEW REQUESTS |
The total number of new LDAP authentication requests received. |
|
NEW IMPERSONATED REQUESTS |
The total number of new impersonated LDAP authentication requests received. |
|
ACTIVE REQUESTS |
The number of LDAP authentication requests active within the Oracle BI Server. |
| Parameter Name | Description |
|---|---|
|
CAPACITY |
The maximum number of connections that the database connection pool allows. |
|
CONNECTION COUNT |
The current number of open connections in the thread pool. |
|
BUSY CONNECTION COUNT |
The number of connections that have been assigned to process a query, or that are currently processing a query, in the database connection pool. |
|
AVG REQUESTS PER SEC |
The average number of requests each second that have been submitted to the database connection pool. |
|
AVG OPEN REQUESTS PER SEC |
The average number of connections that are opened each second. Connections might be opened for new connections, because other connections timed out, or because of problems with a connection. |
| Parameter Name | Description |
|---|---|
|
CAPACITY |
The maximum number of threads allowed by the thread pool. |
|
THREAD COUNT |
The current number of threads in the thread pool. |
|
BUSY THREAD COUNT |
The current number of threads that have been assigned work. The thread might be blocked waiting for a resource or data, or it could be actively running on a CPU. |
|
ACCUMULATED REQUESTS |
The total number of requests that have been submitted to the thread pool. |
|
MAX STACK SIZE |
The maximum number of stack bytes consumed for all threads in the thread pool. |
| Parameter Name | Description |
|---|---|
|
CAPACITY |
The total capacity of the specified cache object. |
|
TOTAL REQUESTS |
The total number of requests each second against the specified cache object. |
|
AVG REQUESTS |
The average number of requests each second against the specified cache object. |
|
AVG HITS |
The average number of hits each second for the specified cache object. |
|
AVG MISS |
The average number of misses each second for the specified cache object. |