My Oracle Support Banner

OTBI Analysis Takes A Long Term To Return And Then Gives An Error nQSError: 17001 with ORA-01555 or nQSError: 60009 (Doc ID 1510512.1)

Last updated on SEPTEMBER 18, 2023

Applies to:

Oracle Fusion Transactional Business Intelligence - Version 11.1.4.0.0 and later
Oracle Fusion Application Toolkit - Version 11.1.1.5.1 and later
Oracle Fusion Application Toolkit Cloud Service - Version 11.1.5.0.0 and later
Information in this document applies to any platform.

Symptoms

 You are running an OTBI analysis.  It seems to hang /is slow to complete and, eventually, returns an error.  Here are two examples of errors:

 

[nQSError: 17001] Oracle Error code: 1555, message: ORA-01555: snapshot too old

Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 1555, message: ORA-01555: snapshot too old: rollback segment number <number> with name "<roll back name>" too small at OCI call OCIStmt Fetch. [nQSError: 17012] Bulk fetch failed. (HY000)

 

[nQSError: 60009] The user request exceeded the maximum query governing execution time

Error
View Display Error
Odbc driver returned an error (SQLFetchScroll).
Error Details
Error Codes: OPR40NWY:U9IM8TAC
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 60009] The user request exceeded the maximum query governing execution time. (HY000)

 

Cause

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
Symptoms
 [nQSError: 17001] Oracle Error code: 1555, message: ORA-01555: snapshot too old
 [nQSError: 60009] The user request exceeded the maximum query governing execution time
Cause
Solution
 Do not run such a large/intensive query


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.