ASAP Servers Terminated Due to Database Failover (Doc ID 1909911.1)

Last updated on JANUARY 06, 2017

Applies to:

Oracle Communications ASAP - Version 7.0.0 and later
Information in this document applies to any platform.
***Check on Currency on Jan-06-2017***

Symptoms

ASAP crashed constantly.

On CTRLAS7.diag:

>> 130044.313:14: LOW:ASC_ociclose :325 :control/libasc/ocilib.c
OCI8 Session closed
>> 130048.272:32:PROG:ORACLE ERROR :1556:control/libasc/ocilib.c

-- ORACLE error OOPEN

>> 130048.274:32:PROG:ORACLE ERROR :1564:control/libasc/ocilib.c
error message ORA-25408: can not safely replay call


>> 130048.274:32: LOW:ASC_ociopen_cursor :450 :control/libasc/ocilib.c
Failed to open cursor
>> 130048.274:32:PROG:ASC_oci8_to_lda :2022:control/libasc/ocilib.c
Error: Open of cursor to Oracle Server ASAPUAT failed rc = 0
>> 130048.274:32:SANE:ASC_cprpcexec() :3895:control/libasc/ctlib.c
Error: DB Connection re-established by TAF. Warning recieved:[25408]
>> 130048.274:32:PROG:System Event :1032:sarm/sarm/sarm/unid_mgr.c
ASAP System Event: SYS_TERM
Error: Failed to update Max Unid

...

>> 130052.335:23: LOW:Reg Proc Param :355 :control/libcontrol/reg_proc.c
Reg Proc [log_event] Received with 6 Parameters
1 : appl_cd = CTRLAS7
2 : file = control/control/ctrl_svr/process.c
3 : reason = Error: Abnormal Termination of SARMAS7 (Generic SARMAS7), Pid 1596
4 : line = 1321
5 : event = ABNORMAL
6 : event_log = 1

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms