As part of OBIEE12c two new important columns are added to s_nq_acct tables which will aid in calculating temporary space occupation and to calculate response time.
Few main column details are as follow.
I was keep on waiting for field tota_temp_kb, we are frequently see high disk space usage and we have disabled logs. It was very difficult to identify culprit report. Now with this field we should be able to trace back to the report easily and tune the report.
Table
|
Column
|
Purpose
|
S_NQ_ACCT
|
TOTAL_TEMP_KB
|
Total temp space used by a query during execution of report.
|
S_NQ_ACCT
|
RESP_TIME_SEC
|
To measure time server took before it start fetching records. This is the response time that the end user would experience with few early records being displayed on dashboard, while server continues fetching more
|
S_NQ_ACCT
|
ECID
|
It is corresponds to ECID in biserver-diagnostic.log
|
S_NQ_ACCT
|
TENANT_ID
|
Tenant id used in multitenancy DB
|
S_NQ_ACCT
|
SERVICE_NAME
|
Service name used in multitenancy DB
|
S_NQ_ACCT
|
SESSION_ID
|
Corresponds to biserver session for use in analyzing user behavior by session
|
S_NQ_ACCT
|
HASH_ID
|
logical query hash id, joins to s_nq_db_acct.hash_id.
|
S_NQ_DB_ACCT
|
HASH_ID
|
This attribute to connect with usage tracking main table, joins to s_nq_acct.hash_id
|
S_NQ_DB_ACCT
|
PHYSICAL_HASH_ID
|
To tracing physical queries to the backend database used this attribute.
|
S_NQ_INITBLOCK
|
USER_NAME
|
Name of user for whom init block ran.
|
S_NQ_INITBLOCK
|
BLOCK_NAME
|
The name of the initialization block that was executed.
|
S_NQ_INITBLOCK
|
START_TS
|
The date and time that the initialization block started.
|
S_NQ_INITBLOCK
|
END_TS
|
The date and time that the initialization block finished. The start and end timestamps also reflect any time that the query spent waiting for resources to become available.
|
S_NQ_INITBLOCK
|
DURATION
|
The length of time it took to execute the initialization block.
|
For additional details – take a look at documentation http://docs.oracle.com/
