VCS DBG_2 V-16-50-0 Netlsnr:apo_pu_listener1:monitor:stat call failed for proc file (/proc/28101/object/a.out), errno (5) Netlsnr.sun.C:netlsnr_monitor[311]
As part of the Oracle agent's monitor activity it attempts to stat the Oracle binaries to obtain information about the owner user account. This user account is then used for process matching later in the monitor procedure. Without this owner information monitoring may fail.
When the Oracle binaries are located in a Solaris local zone which is NFS mounted, users in the global zone on the NFS client (ie the machine/zone running VCS) do not have permission to stat these file and as a result the stat fails.
Oracle binaries should be NFS mounted into the local zone from the global zone instead of being NFS mounted on the local zone.
For example, given a zone name of 'testzone' and a mount point of '/opt/oracle' within the local zone, rather than mounting Oracle binaries from within the local zone using:
mount server:/filesystem /opt/oracle
the file system should be mounted from the global zone inside of the local zone's zone root, i.e.:
mount server:/filesystem /testzone/root/opt/oracle
Once done agents running in the global zone will then have permissions to stat Oracle binaries within the NFS mount.
This issue was addressed in the 5.1RP2 Oracle agent.