Unable To Start NEP_<ENV_ID> When Using Customized NEP
(Doc ID 2298466.1)
Last updated on MAY 05, 2023
Applies to:
Oracle Communications ASAP - Version 7.2.0 and laterInformation in this document applies to any platform.
Symptoms
We are unable to start NEP_<ENV_ID> when using a customized NEP. The following errors were received:
ERROR
-----------------------
>> 104215.809:72:PROG:checkerr :1830:-Ocilib.c
Error - ORA-01005: null password given; logon denied
errcode[1005]
>> 104215.809:72:SANE:DBLogon_oci8 :1635:-Ocilib.c
Error: Failed OCISessionBegin,status[0]
>> 104215.809:72:PROG:System Event :83 :-Ocilib.c
ASAP System Event: SYS_ERR
Error: Unable to open OCI connection
>> 104215.809:72:SANE:Queues :355 :asc_msgs.c
Putting message into queue [Control Agent] [369].
>> 104215.809:72:PROG:System Event :309 :ctlib.c
ASAP System Event: SYS_ERR
Error: Unable to open OCI connection
>> 104215.809:72:SANE:Queues :355 :asc_msgs.c
15:30
>> 104215.809:72:PROG:checkerr :1830:ocil...
Error: Unable to open OCI connection
>> 104215.809:72:SANE:Queues :355 :asc_msgs.c
Putting message into queue [Control Agent] [369].
>> 104215.810:72:PROG:System Event :2461:main.c
ASAP System Event: SYS_ERR
Initialization Function [Client Proc. Init] Failed, Terminating Server
>> 104215.810:72:SANE:Queues :355 :asc_msgs.c
Putting message into queue [Control Agent] [369].
Changes
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 |
References |