Orders Failing In SARM With Hard ASDL Failure
(Doc ID 2334530.1)
Last updated on DECEMBER 15, 2017
Applies to:Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
We are trying to place a bulk order on some 60 exchanges, out of which it failed on around 15 exchanges, the reason is the same for all 15 exchanges, which is that it is not moving from SARM to NEP for further processing.
NE Avail Timestamp '1510658665', ASDL Timestamp '1510658665'
>> 112648.719:37: LOW:Hard ASDL Failure :6071:sarm/sarm/sarm/nep_driver.c
CSAM00199504-043: Incrementing Hard Error Counter for ASDL [A-FILE_TRANSFER], NE [MA-SCT]
>> 112648.719:37: LOW:Delete in Progress ASDL :4965:sarm/sarm/sarm/nep_driver.c
CSAM00199504-043: Deleting from 'MA-SCT' In Progress Queue, ASDL = A-FILE_TRANSFER (3890)
>> 112648.719:37:SANE:ASDL Dispatch :3997:sarm/sarm/sarm/nep_driver.c
'MA-SCT': State: 0 Pending 0 In Proc 0 Connect 1 Prime 1, Aux 0, NE Avail 1
>> 112648.720:37: LOW:ASDL Dispatch :4091:sarm/sarm/sarm/nep_driver.c
Checking for connections and nothing in progress.
>> 112648.720:37: LOW:ASDL Dispatch :4153:sarm/sarm/sarm/nep_driver.c
'MA-SCT' Idle, Setting Disconnect Alarm for 300 Seconds
>> 112648.720:37: LOW:RPC Param :1689:control/libasc/ctlib.c
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!