ASAP SARM - Receiving Oracle Errors On Large Order
(Doc ID 1328077.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Communications ASAP - Version 4.7.1 to 5.2.4 [Release 4.7 to 5.2]
Information in this document applies to any platform.
***Check for Relevance on APR-7-2017***
When submitting a large Work Order, ASAP does not seem to be able to load it from SARM database to memory.
>> 220745.131:14:PROG:ORACLE ERROR :1452:ocilib.c
-- ORACLE error OFETCH, OFEN
>> 220745.137:14:PROG:ORACLE ERROR :1456:ocilib.c
error message ORA-01002: fetch out of sequence
>> 220745.137:14:PROG:ASC_ocifetch :1317:ocilib.c
>> 220745.137:14:SANE:WO Handler :881 :fetch_wo.c
Fetch failed - rows fetched = 0
>> 220745.137:14:PROG:ASC_cprpcexec() :975 :ctlib.c
Error while performing handler
>> 220745.145:14:PROG:System Event :322 :fetch_wo.c
ASAP System Event: SYS_TERM
Error: SSP_get_csdl_parm Failed for WO <WO_ID>, SRQ 11991498
And the SARM subsequently terminated.
The typical WO that can cause the problem is:
40,000 CSDLs with 300,000 Parameters.
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