Standard Manager Doesn't Start and Error "The Service Manager has been unable to verify its environment and create its log file." Occurrs Repeatedly in FNDICM Log.
(Doc ID 2158048.1)
Last updated on OCTOBER 30, 2019
Applies to:Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.
When starting concurrent managers using $ADMIN_SCRIPTS_HOME/adcmctl.sh, "Standard Manager" doesn't start though some managers such as "Internal Manager","Conflict Resolution Manager", "PO Document Approval Manager" can start .
We see "Service Manager FNDSM_XXXXX_YYY could not initialize. The Service Manager has been unable to verify its environment and create its log file." in a log file of FNDICM.
But if we do "tnsping FNDSM_XXXXX_YYY", the command can get response as follows.
[oracle]$ tnsping FNDSM_XXXXX_YYY
TNS Ping Utility for Linux: Version 10.1.0.5.0 - Production on 09-JUN-2016 16:35:18
Copyright (c) 1997, 2003, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=<host.domain>)(PORT=1626)) (CONNECT_DATA= (SID=FNDSM)))
OK (0 msec)
There are no changes.
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