My Oracle Support Banner

ORA-00020 - Core Database Initialization, SARM server (Doc ID 950077.1)

Last updated on OCTOBER 11, 2023

Applies to:

Oracle Communications ASAP - Version 4.2.0 and later
Information in this document applies to any platform.

Symptoms

This happens when you try to start the SARM but it fails. This is a fatal error that could occur in the SARM server $SARM{ENV_ID}.diag file.

In this case the a SARM server could not connect to the Oracle database (and hence, not start up properly) because of the number of processes has been exceeded. Note that the a rc=20 error, the 'true' error in this case, occurs much sooner in the dialogue file and the other errors that occur as a result of that error are confusing for the user.

...<cut>...


>> 163907.376:367: LOW:Initialization :966 :main.c
Application Server Initialization Wait Complete
>> 163907.376:367:SANE:Thread Start :346 :asc_spawn.c
Startup of Thread [<OCA_SERVER> Unid Mgr], MsqQ [<OCA_SERVER>], MsgQId [80]
>> 163907.376:367:PROG:System Event :353 :unid_mgr.c
ASAP System Event: SYS_INFO
OCA Unid Mgr: Operating in <PRIMARY> Mode
>> 163907.378:367: LOW:ASC_cpalloc :1530:ctlib.c
CS_MAX_CONNECT property set to [40] max connections per context
>> 163907.452:367: LOW:ASC_ociopen :104 :ocilib.c
Open of connection to Oracle Server with user <SARM_USER_NAME> and connection <ASAP_DB_NAME> failed rc = 20
>> 163907.452:367:PROG:System Event :286 :ctlib.c
ASAP System Event: SYS_ERR
Error: Unable to open OCI connection
>> 163907.453:367:PROG:System Event :939 :unid_mgr.c
ASAP System Event: SYS_TERM
Error: Unable to connect to Core database
>> 163907.453:372: LOW:Initialization :966 :main.c
Application Server Initialization Wait Complete
>> 163907.453:372:SANE:Thread Start :346 :asc_spawn.c
Startup of Thread [WO Mgr 1], MsqQ [WO Mgr 1], MsgQId [83]
>> 163907.453:373: LOW:Initialization :966 :main.c

...<cut>...

>> 163908.256:242:SANE:SRP Startup :2380:srp_driver.c
Currently Unable to Connect to <CORBA_SERVER> SRP Server
>> 163908.256:248: LOW:check_socket_fd :2167:asc_io.c
Socket Port Connection is Writable: File Descriptor [159]
>> 163908.256:248:PROG:System Event :1829:asc_io.c
ASAP System Event: UNIX_ERR
Internet Socket Connect: Socket: [159] Can't Connect to Host [xxxxx] Error: [134 Transport endpoint is not connected]
>> 163908.257:248:SANE:SRP Startup :2380:srp_driver.c
Currently Unable to Connect to <CORBA_SERVER> SRP Server
>> 163908.548:20: LOW:ASC_cprpcexec() :1176:ctlib.c
RPC(log_event) Complete in 1076ms, First Result in 1076ms



...<cut>...

RPC(log_event) Complete in 54ms, First Result in 54ms
>> 163909.150:363:SHUT:System Event :939 :unid_mgr.c
Application <SARM_SERVER_NAME> Terminating Due to SYS_TERM Event
Error: Unable to connect to Core database

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
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.