Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Issues related to installation and upgrade
Cluster goes into STALE_ADMIN_WAIT state during upgrade from VCS 5.1 to 6.1 or later [2850921]
While performing a manual upgrade from VCS 5.1 to VCS 6.1 or later, cluster goes in STALE_ADMIN_WAIT state if there is an entry of DB2udbTypes.cf in main.cf.
Installation of VRTSvcsea package in VCS 5.1 creates a symbolic link for Db2udbTypes.cf
file inside /etc/VRTSvcs/conf/config
directory which points to /etc/VRTSagents/ha/conf/Db2udb/Db2udbTypes.cf
. During manual upgrade, the VRTSvcsea package for VCS 5.1 gets removed, which in turn removes the symbolic link for file Db2udbTypes.cf
inside /etc/VRTSvcs/conf/config
directory. After the complete installation of VRTSvcsea for VCS 6.1 or later versions, because of absence of file Db2udbTypes.cf
inside /etc/VRTSvcs/conf/config
, cluster goes into STALE ADMIN WAIT state.
Workaround: Manually copy DB2udbTypes.cf
from /etc/VRTSagents/ha/conf/Db2udb
directory to the /etc/VRTSvcs/conf/config
directory after the manual upgrade before starting HAD.