Host Job Using Global Named Credential Fails With ERROR: Execution failed due to binary missing or permission issues
(Doc ID 2018524.1)
Last updated on FEBRUARY 12, 2019
Applies to:Enterprise Manager Base Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
A host job using global Host Named Credential (NC) fails with:
ERROR: Execution failed due to binary missing or permission issues
This is a global named credential that is used by other hosts, and all of them work fine except for a single host.
Doing a "test / save" for the NC and select the problem host, it fails.
There is no problem accessing the binaries in the <Agent_BASE>/sbin directory, and "nmo" test completes successfully.
The settings in the file /etc/security/limits.conf include the soft process (nproc) settings at 16384.
However when logged in as the user who owns the Agent Binaries (oracle for example), the result of the "ulimit -a" command displays a lower value.
Although the Soft Processes in /etc/security/limits.conf has the Global Setting:
* soft nproc 16384
when executing the ulimit -a command, the result for the 'oracle' user show a lesser value:
[oracle@problematichost sbin]$ ulimit -a
max user processes (-u) 1024 <<<<< The actual value is: 1024, not 16384...
The log file <AGENT_INST>/sysman/log/gcagent.log may include:
A new PAM (Pluggable Authentication Module) package has been installed on the host.
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