17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Software limitations137# hatype -modify AgentFile/opt/VRTSagents/ha/bin//AgentLimitations related to the VCS database agentsThe Db2udb agent does not support DB2 9.8The Db2udb agent does not support DB2 version 9.8. This is because DB2 9.8 isdesigned especially for DB2 PureScale feature <strong>and</strong> it doesn't support some of thefeatures in DB2 9.7 temporarily.Seehttp://www.ibm.com/developerworks/data/library/techarticle/dm-0909db2whichedition/for more information.DB2 RestartLimit value [1234959]When multiple DB2 resources all start at the same time with no dependencies,they tend to interfere or race with each other. This is a known DB2 issue.The default value for the DB2 agent RestartLimit is 3. This higher value spreadsout the re-start of the DB2 resources (after a resource online failure), which lowersthe chances of DB2 resources all starting simultaneously.Limitation with intentional offline functionality of VCS agent for OracleThe Oracle resource never faults after an intentional offline.Intentional offline functionality of VCS agent for Oracle requires you to enablehealth check monitoring. The agent uses Oracle's Health Check API to find thestate of the database. If the API returns a graceful shutdown for the database,then the agent marks the resource state as INTENTIONAL OFFLINE. Later if theOracle agent's online function does not succeed, the agent does not mark theresource as FAULTED. The state remains as INTENTIONAL OFFLINE because theagent receives the database state from the API as graceful shutdown during eachmonitor cycle. [1805719]Sybase agent does not perform qrmutil based checks if Quorum_dev is notset (2724848)If you do not set the Quorum_dev attribute for Sybase Cluster Edition, the Sybaseagent does not perform the qrmutil-based checks. This error in configuration maylead to undesirable results. For example, if qrmutil returns failure pending, theagent does not panic the system. Thus, the Sybase agent does not performqrmutil-based checks because the Quorum_dev attribute is not set.Therefore, setting Quorum_Dev attribute is m<strong>and</strong>atory for Sybase cluster edition.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!