VCS SAP components resource with SAPSID value other than MDM cannot online and/or monitor cannot find running processes after start

book

Article ID: 100009361

calendar_today

Updated On:

Cause

This issue is tracked via Symantec etrack incident mentioned in the Supplemental Materials section.

If there are SAPComponents resources with SAPSID value other than "MDM" for MDM components,then that SAPComponents resource would not come online. "sapcontrol -function StartService " command is passed "MDM" as SAPSID for MDM components,which prevents the SAPComponents resource with SAPSID value other than than "MDM" from coming online.

Resolution

Veritas has modified the SAPComponents.pm file for VCS SAPComponents agent to handle any valid SAPSID derived from InstProfile attribute of SAPComponents resources.

This fix is available on Solaris platform via VRTSsapcms 5.1.4.1-HF1 patch. Please contact Veritas Technical Support to obtain this patch.
 

The fix will also be included in upcoming 2Q2013 VCS agent pack (ETA July 2013).

 


Applies To

This issue is applicable to all UNIX/Linux platforms running VCS SAPComponents package and when using SAPSID value other than 'MDM' for MDM components.

 

Issue/Introduction

Veritas Cluster Server (VCS) SAPComponents resource does not come online for instances with SAPSID value other than MDM for MDM components. Monitor entry point will also not find running processes after starting the resource outside VCS control. SAPSID value is derived from InstProfile attribute of SAPComponents resources.

Additional Information

ETrack: 3164782
Powered by Wolken Software