My Oracle Support Banner

OAS: Few Timed Out Analyses Does Not Get Registered in Usage Tracking Tables (Doc ID 2957437.1)

Last updated on JULY 03, 2023

Applies to:

Oracle Analytics Server - Version 5.9.0 and later
Information in this document applies to any platform.

Symptoms

Few analyses fails after hitting the query limits(Max Time=60 Mins) defined in RPD which is expected, but it randomly fails with two different errors once the 60 mins limit is reached. Where one error gets registered in Usage Tracking(UT) tables and the other doesn’t.

1) Error which gets registered in UT tables:

[nQSError: 17001] Oracle Error code: 1013, message: ORA-01013: user requested cancel of current operation
[nQSError: 60009] The user request exceeded the maximum query governing execution time

2) Error which doesn’t get registered in UT tables:

[nQSError: 60016] The user cancelled the query with request id 2434072590.\n[nQSError: 17001] Oracle Error code: 1013, message: ORA-01013: user requested cancel of current operation\n at OCI call OCIStmtFetch.

Changes

 Upgraded from OBIEE 11.1.1.9 to OAS 5.9

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
Changes
Cause
Solution


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