OBIEE 11g: ORA-01704 Returns and May Not Insert Data into S_NQ_ACCT when Usage Tracking is Used DataDirect Driver
(Doc ID 2528938.1)
Last updated on OCTOBER 23, 2019
Applies to:Business Intelligence Suite Enterprise Edition - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Set up Direct Insertion to collect information for Usage Tracking with DataDirect ODBC drivers.
When using DataDirect drivers, queries with large text may not be captured in the S_NQ_ACCT table. It happened to be a loss of Usage tracking data.
ORA-01704 would be filed in the Oracle Database SQL trace file:
PARSE ERROR #3:len=6097 dep=0 uid=<uid> oct=2 lid=92 tim=1548902905357025 err=1704
INSERT INTO S_NQ_ACCT (USER_NAME, REPOSITORY_NAME, SUBJECT_AREA_NAME, NODE_ID, START_TS, START_DT, START_HOUR_MIN, END_TS, END_DT, END_HOUR_MIN, QUERY_TEXT, QUERY_BLOB,
QUERY_KEY, SUCCESS_FLG, ROW_COUNT, TOTAL_TIME_SEC, COMPILE_TIME_SEC, NUM_DB_QUERY, CUM_DB_TIME_SEC, CUM_NUM_DB_ROW, CACHE_IND_FLG, QUERY_SRC_CD, SAW_SRC_PATH,
SAW_DASHBOARD_PG, PRESENTATION_NAME, ERROR_TEXT, IMPERSONATOR_USER_NAME, NUM_CACHE_INSERTED, NUM_CACHE_HITS, ID)
The issue occurs when all of the following conditions are met:
- Collect Usage Tracking data via DataDirect ODBC drivers.
- the large logical query text less than 4K Characters has been run.
- Some multi-byte(E.g Chinese or Japanese) words included in the logical query text.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document