VCS Netlsnr and Oracle agent reports "VCS ERROR V-16-20002-204" error "Invalid owner <user name> for Oracle executables was specified" during monitor cycle
book
Article ID: 100023240
calendar_today
Updated On:
Resolution
ISSUE:
VCS Netlsnr and Oracle Agent reports error "Invalid owner for Oracle executables was specified" during monitor.
VCS engine log is flooded with following messages for Oracle and Netlsnr resources during monitor cycle.
2009/09/22 15:34:35 VCS ERROR V-16-20002-204 (node1)Netlsnr:LSNR_gc0_bs:monitor:Invalid owner oraclec0 for Oracle executables was specified
2009/09/22 15:34:35 VCS ERROR V-16-20002-204 (node1)Netlsnr:LSNR_gd0_bs:monitor:Invalid owner oracled0 for Oracle executables was specified
2009/09/22 15:38:14 VCS ERROR V-16-20002-204 (node1)Oracle:ORA_gm0_bs:monitor:Invalid owner oraclem0 for Oracle executables was specified
ERROR CODE/ MESSAGE:
With VCS agent debugging enabled, Oracle_A.log shows:
2009/09/22 15:38:13 VCSDBG_AGINFO V-16-50-0 Thread(7) Resource ORA_gm0_bs transitioning from Online to Monitoring
VCSAgRes.C:internal_state[3879]
[...]
2009/09/2215:38:13 VCS DBG_3 V-16-50-0 Oracle:ORA_gm0_bs:monitor:Starting monitor....
Oracle.sun.C:oracle_monitor[584]
2009/09/22 15:38:13VCS DBG_3 V-16-50-0 Oracle:ORA_gm0_bs:monitor:Zone id is4
Oracle.sun.C:oracle_monitor[635]
2009/09/22 15:38:14 VCSDBG_1 V-16-50-0 Oracle:ORA_gm0_bs:monitor:User String:stat failed: Value toolarge for defined datatype <== NOTE
Oracle.sun.C:getZoneUserId[98]
2009/09/22 15:38:14 VCSDBG_AGINFO V-16-50-0 Thread(7) Resource(ORA_gm0_bs) - monitor entry point exitedwith a confidence value0.
VCSAgType.C:call_monitor[1383]
2009/09/22 15:38:14 VCSDBG_AGINFO V-16-50-0 Thread(7) ORA_gm0_bs reported state (Unknown) &conf_level (0)
VCSAgRes.C:call_entry_point[1276]
2009/09/2215:38:14 VCS DBG_AGINFO V-16-50-0 Thread(7) Resource ORA_gm0_bs transitioningfrom Monitoring to Online
VCSAgRes.C:internal_state[3879]
CAUSE:
VCS Oracle and Netlsnr agents relies onthe user information of the Oracle resource owner in VCS configuration to successfully monitor VCS resources. VCS Application agent's monitor entry point runs '/usr/bin/id' command as resource owner in Solaris zone context, i.e, runs"zlogin /usr/bin/id " command from global zone as root. In one situation, this command was failing occasionally due to SUN bug (doc # 6815860 - zlogin(1) needs to be largefile safe). If the'/usr/bin/id' command fails to complete, VCS would return the resource state as UNKNOWN but would continue to work normally.
SOLUTION:
Please contact SUN/Oracle support to address the SUN bug (doc # 6815860 - zlogin(1) needs to be largefilesafe) issue. No changes is required from VCS side.
Issue/Introduction
VCS Netlsnr and Oracle agent reports "VCS ERROR V-16-20002-204" error "Invalid owner for Oracle executables was specified" during monitor cycle
Was this article helpful?
thumb_up
Yes
thumb_down
No