Symantec High Availability

Agent Pack Release Notes

3Q 2014

September 2014

Symantec High Availability Agent Pack Release

Notes
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Product Version: 3Q2014
Document version: 3Q2014 Rev 0

Legal Notice
Copyright 2014 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, Veritas, Veritas Storage Foundation,
CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered
trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other
names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations, whether delivered by Symantec as on premises
or hosted services. Any use, modification, reproduction release, performance, display or
disclosure of the Licensed Software and Documentation by the U.S. Government shall be
solely in accordance with the terms of this Agreement.

Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com

Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantecs support offerings include the following:

A range of support options that give you the flexibility to select the right amount
of service for any size organization

Telephone and/or Web-based support that provides rapid response and

up-to-the-minute information

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis

Premium service offerings that include Account Management Services

For information about Symantecs support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/index.jsp
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
www.symantec.com/business/support/contact_techsupp_static.jsp
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at
the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:

Product release level

Hardware information

Available memory, disk space, and NIC information

Operating system

Version and patch level

Network topology

Router, gateway, and IP address information

Problem description:

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/business/support/

Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs or manuals

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan

customercare_apac@symantec.com

Europe, Middle-East, and Africa

semea@symantec.com

North America and Latin America

supportsolutions@symantec.com

Documentation
Your feedback on product documentation is important to us. Send suggestions for
improvements and reports on errors or omissions. Include the title and document
version (located on the second page), and chapter and section titles of the text on
which you are reporting. Send feedback to:
doc_feedback@symantec.com
For information regarding the latest HOWTO articles, documentation updates, or
to ask a question regarding product documentation, visit the Storage and Clustering
Documentation forum on Symantec Connect.
https://www-secure.symantec.com/connect/storage-management/
forums/storage-and-clustering-documentation

About Symantec Connect

Symantec Connect is the peer-to-peer technical community site for Symantecs
enterprise customers. Participants can connect and share information with other
product users, including creating forum posts, articles, videos, downloads, blogs
and suggesting ideas, as well as interact with Symantec product teams and
Technical Support. Content is rated by the community, and members receive reward
points for their contributions.
http://www.symantec.com/connect/storage-management

Release Notes
This document includes the following topics:

Introduction

Changes introduced in this release

Fixed issues

Known issues

Documentation

Introduction
This document provides important information about this Symantec High Availability
Agent Pack release. Review this entire document before installing and configuring
the agents.
For more information about Symantec High Availability Agent Pack, refer to the
Getting Started Guide, which is available on the Symantec Operations Readiness
Tools (SORT) site: https://sort.symantec.com/agents.
For important updates regarding this release, see the Late-Breaking News TechNote
on the Symantec Technical Support website:
http://www.symantec.com/business/support/index?page=content&id=TECH46455
Note: This document does not contain information about the Symantec High
Availability agents for Microsoft applications on Windows. For information about
these agents, see the Symantec Cluster Server Agent Pack Readme. The Readme
is available on the VCS Agent Details page on SORT and also in the agent ZIP file.

Release Notes
Changes introduced in this release

Note: For information about ApplicationHA agents on Windows, see the Symantec
Application HA Agent Pack Readme. The Readme is available on the ApplicationHA
Agent Details page on SORT and also in the agent ZIP file.

Changes introduced in this release

This section lists the new features and enhancements in this Agent Pack release.

Application agents
Table 1-1 lists the changes in the VCS Application agents in this Agent Pack release.
Table 1-1

Application agents

Application

New feature or enhancement

Application Agent
Builder

Added support for VCS 6.1 and later. By default, the tool generates
the agent for VCS 5.1 and later.

IBM WebSphere MQ

Added support for IBM WebSphere MQ version 8.0.

IBM WebSphere
Message Broker

Added support for IBM WebSphere Message Broker V8.0 and IBM
Integration Bus (IIB) V9.0.

Informatica

Added support for Informatica Powercenter V9.6.

Added support for Solaris 10 and Solaris 11.

The agent Image Packaging System (IPS) package

VRTSinformatica.p5p is now available for installation on a
Solaris 11 system.

Oracle E-Business
Components 11i, R12

The agent Image Packaging System (IPS) package

VRTSvcsoc11.p5p is now available for installation on a Solaris
11 system.

SAP NetWeaver with

HA-API support

Added HA-API support to use the new instance type

SAPSTARTSRV instead of the Application agent to monitor the
sapstartsrv process.

Symantec High
Availability Agent for
Cisco UCS

Symantec has developed a new CiscoUCS agent, which supports

high availability of service profiles in Cisco UCS datacenter
architecture.
This agent is provided with VRTSucsutil package.

Release Notes
Changes introduced in this release

Database agents
Table 1-2 lists the changes in the VCS Database agents in this Agent Pack release.
Table 1-2

Database agents

Application

New feature or enhancement

MySQL

A new script MySQLTypes.cmd is provided to import the agent type

definition from the command line.

Replication agents
Table 1-3 lists the changes in the VCS Replication agents in this Agent Pack release.
Table 1-3

Replication agents

Application

New feature or enhancement

HP 3PAR Remotecopy Added CLI support in the agent to connect to 3PAR array. Updated
the agent for AIX, HP-UX, Linux, Solaris, and Windows.
Oracle Data Guard
Broker

Added support for database username/password to login to

DataGuard broker in single instance and RAC. Updated the agent
for AIX, Linux, and Solaris.

Symantec ApplicationHA agents

Note: This Agent Pack release contains Symantec High Availability agents for
ApplicationHA 6.0 and ApplicationHA 6.1.
The Symantec ApplicationHA for Linux agents include the following changes in this
Agent Pack release:
Table 1-4

Symantec ApplicationHA for Linux agents

Application

New feature or enhancement

IBM WebSphere MQ

Added support for IBM WebSphere MQ version 8.0 on

ApplicationHA 6.1.

SAP NetWeaver with

HA-API support

Added support for SAP HANA SPS 08 on ApplicationHA 6.1.

The Symantec ApplicationHA for Windows agents include the following changes
in this Agent Pack release:

Release Notes
Fixed issues

Table 1-5

Symantec ApplicationHA for Windows agents

Application

New feature or enhancement

Microsoft SQL Server

2014

Added support for Microsoft SQL Server 2014 (for VMware and
Hyper-V) on ApplicationHA 6.1.

Siebel CRM

Added support for Siebel CRM (for Hyper-V) on ApplicationHA 6.1.

SAP Web Application

server

Added support for SAP Web Application server (for Hyper-V) on

ApplicationHA 6.1.

Fixed issues
This section describes the incidents that are fixed in this Agent Pack release.
Table 1-6 lists the issues that are fixed in the VCS Application agents.

10

Release Notes
Fixed issues

Table 1-6

VCS Application agents fixed issues

Incident

Description

3548876

SAP NetWeaver
Operating system: AIX, Linux, and Solaris
Symptoms: The VCS agent for SAP NetWeaver executes the
cleanipc command during the offline and clean operation, although
the sapstartsrv process is still running. The SAP NetWeaver resource
for the SAP instance calls the cleanipc command, while the
sapstartsrv process of the SAP instance is monitored using a child
Application resource, which is in the online state.
Description: For the SAP instance, the shared memory persists on
the system until it is explicitly removed using the cleanipc
command. With the current design to enable HA-API integration, the
sapstartsrv process is managed by a separate VCS resource of the
Application type. The sapstatsrv process keeps running even after
the resource for the SAP instance is stopped. As per the SAP
recommendation, the shared memory must not be removed when
the sapstartsrv process is running.
Resolution: Symantec has enhanced the VCS agent for SAP
NetWeaver by introducing a new instance type, SAPSTARTSRV.
The SAPSTARTSRV instance type should be used to monitor the
sapstartsrv process instead of the Application resource. A resource
with the SAPSTARTSRV instance type runs the cleanipc command
in the offline and clean operation for the SAP instance after the
sapstartsrv process is stopped. The SAP NetWeaver VCS resources
with instance types other than SAPSTARTSRV will not run the
cleanipc command during the agent operations.

3538282

IBM WebSphere MQ
Operating System: AIX, HP-UX, Linux, and Solaris
Symptoms: Symantec High Availability Agent for WebSphereMQ
fails to get the details for the MQ user.
Description: The agent code does not handles the call to
getpwnam() for failure.
Resolution: Symantec has modified the Symantec High Availability
Agent for WebSphereMQ to fix this issue. Now the agent reports
resource as unknown, if the user details on the target system are
not retrieved.

Table 1-7 lists the issues that are fixed in the VCS Database agents.

11

Release Notes
Fixed issues

Table 1-7

VCS Database agents fixed issues

Incident

Description

3520427

MySQL
Symptoms: The VCS agent for MySQL is unable to bring the MySQL
resource online if the MySQL application is installed in a non-default
location. The following error message appears in the engine log:
2014/02/21 20:14:03 VCS INFO V-16-2-13716 (vrtp2a)
Resource (mysql_cvmysql):
Output of the completed operation (online)
140221 20:09:22 mysqld_safe Logging to
'/appmysqlrtp/logs/mysql-bin.err'. 140221 20:09:22
mysqld_safe The file /usr/local/mysql/bin/mysqld does
not exist or is not executable. Please cd to the mysql
installation directory and restart this script from
there as follows: ./bin/mysqld_safe&
See: http://dev.mysql.com/doc/mysql/en/mysqld-safe.html
Description: In the VCS agent for MySQL, the BaseDir attribute specifies
the MySQL installation directory. If the MySQL application is installed in a
non-default location, the VCS agent for MySQL does not execute the startup
command from the BaseDir directory and the agent is unable to bring the
MySQL resource online.
Resolution: Symantec has modified the VCS agent for MySQL to change
the working directory to BaseDir before executing the MySQL startup
command.

3517498

SAP MaxDB
Symptoms: SFHA6.0.3 SAP MaxDB agent does not clean IPC resources
and the MaxDB database cannot start on the previous primary node.
Description: Directory for IPC is changed from /sapdb/SDP/data/ipc
to /var/lib/sdb/dbm/ipc from versions: 7.6.04.17, 7.6.05.12, 7.6.06
and newer patches 7.7.02.22, 7.7.03.26, 7.7.04.30, 7.7.06.07, and 7.7.07.
Resolution: This issue has been resolved by using
/sapdb/QAS/db/pgm/dbmshm DELETE /var/lib/sdb/dbm/ipc
QAS to delete the IPC resources.

Table 1-8 lists the issues that are fixed in the VCS Replication agents.

12

Release Notes
Known issues

Table 1-8

VCS Replication agents fixed issues

Incident

Description

3584600

EMC SRDF
Operating system: Windows
Symptom: The operation to configure the Symm heartbeat fails.
Description: This issue occurs while configuring the Symm heartbeat on a
cluster. The operation fails with the following error: Can't exec /bin/sh at
C:\Program Files\Veritas\Cluster Server\bin\hb\Symm\aya.pl line 1. This
happens because a perl file defined for a UNIX system was incorrectly
shipped with SFW HA 6.1.
Resolution: This issue has been resolved by adding the correct file to the
SRDF agent that will replace the UNIX version of the file.

3574918

HP 3PAR Remote Copy

Operating systems: AIX, HP-UX, Linux, Solaris, and Windows
Symptom: startrcopygroup command on 3PAR agent fails when array
refuses to execute the command.
Description: After the role reversal, 3PAR array appears to be busy in doing
some internal tasks and it refuses the next command to start the 3PAR
group.
Resolution: The issue has been fixed by introducing the retry logic which
parses the output of startrcopygroup command in case if the array
refuses to execute the command.

Known issues
This section lists the known issues that are applicable in this agent pack release.

VCS application agents

SAP liveCache
On SAP liveCache 7.7, the intentional offline functionality might not work because
the lcinit and lccluster scripts do not get executed.

13

Release Notes
Known issues

IBM WebSphere MQ

The VRTSmq6 package on Solaris 11 contains two agents the WebSphereMQ

agent and the WebSphereMQFTE agent. Only the WebSphereMQ agent is
supported on Solaris 11 in this release.

Queue Managers that have the same resource dependencies must not be
configured using multiple runs of the Symantec High Availability Configuration
wizard.
When you configure queue managers that have the same resource dependencies
such as, shared mount points and IP addresses, using multiple runs of the
wizard, the queue managers are configured separately and not merged with the
existing configuration.
This issue occurs on the Windows and Linux operating systems.
Resolution: To resolve this issue, configure multiple queue managers that have
the same resource dependencies in a single run of the Symantec High Availability
Configuration wizard.

On the Queue Manager selection panel, if you click Next without selecting the
Monitor Listener for the Queue Manager checkbox, you might not be able to
return to that panel to configuring monitoring for a queue manager listener.
This issue occurs on the Windows and Linux operating systems.
Resolution: To configure monitoring for a queue manager listener, ensure that
you select the Monitor Listener for the Queue Manager checkbox on the
Queue Manager selection panel before you click Next.

The Symantec High Availability Configuration wizard supports only one listener
associated with each queue manager.
This limitation is applicable to the Windows and Linux operating systems.

When upgrading the Symantec High Availability Configuration wizard, the

installation of the Agent Pack using the ./installagpack -upgrade command
might cause the following error message to appear:
Starting WebSphereMQ_Agent...
Failed Symantec High Availability Wizards Agent Pack Startup
did not complete successfully
WebSphereMQ_Agent failed to start on system_name

Resolution: It is safe to ignore this message.

14

Release Notes
Known issues

VCS replication agents

Multiple replication agents

A user's attempt to add a disk to a VxVM disk group, after the replication roles
have changed from Secondary to Primary, might fail.
This issue occurs because of a stale VxVM cache and a VxVM rule that does
not permit a user to add a primary disk to a disk group that contains secondary
disks.
Resolution: To resolve this issue, use the Symantec preonline trigger; contact
Symantec Technical Support to obtain the Symantec preonline trigger.

On the Windows operating system with SFW HA versions 6.0 or 6.0.1, fire drill
might fail with the following error message:
ERROR: Disk group : No Disk found with matching tag SIRemote-*
Incident number: 3123099
Resolution: To resolve this issue, follow the instructions given in the Symantec
TechNote: http://www.symantec.com/docs/TECH206237.

In Silver configurations, fire drill might fail with the error: 'Cannot import disk
group DiskGroup in pitc silver; exiting'. A mismatch in the parameters sent to
the diskgroup import command causes this error to occur. This problem occurs
on the AIX, HP-UX, Linux, and Solaris operating systems.
Resolution: To resolve this issue, upgrade to VCS 5.1 Service Pack 1 RP2.

On AIX 6.1 or later with VxVM 5.1 SP1 or later, the service group containing a
replication resource might fail and display the following error: Could not import
Diskgroup.
Resolution: To resolve this issue, perform the following steps:

Run the vxdisk rm vxdisk names command to delete any VxVM subdisks
that are participating in the concerned VxVM DiskGroup.

Run the vxdisk scandisks to rescan the VxVM subsystem.

Import the concerned VxVM DiskGroup.

The replication agents currently ship action entry points on the CVMVolDg
resource which is part of the VRTScavf package. This package is part of the
SFCFS package set. The VRTScavf package also ships the same action entry
points. As a result, while installing the replication agent package in an SFCFS
environment, the installer might display file conflict error messages. This problem
occurs on the AIX, HP-UX, Linux, and Solaris operating systems.
Resolution: Symantec recommends installing the replication agent package with
the appropriate force option so as to overwrite the conflicting files installed by
the VRTScavf package.

15

Release Notes
Known issues

Agentsmight not compute the RPO correctly if snapshot devices are attached
to the replication luns at the DR site and are mapped to the same DR site hosts.
When you invoke the GetCurrentRPO action, the agent might display an error
message or report incorrect RPO.
Resolution: Unmap the snapshot devices that are attached to the replication
luns from the DR site hosts and then enable RPO computation on the resource.

EMC MirrorView
The MirrorviewSnap resource might fail to come online.
VxVM does not assign the _1 suffix to the MirrorView snapshot LUN. As a result,
the LUN is not identified as a snapshot LUN and the VCS MirrorViewSnap agent
cannot proceed to tag this Snapshot LUN and import the diskgroup.
Resolution: To address this issue, run the vxconfigd -kr reset command.
If the disk access records are not refreshed on running this command, contact
Symantec Technical Support.

EMC SRDF

Silver fire drill configuration may fail with SFHA 6.1 and SFCFS HA 6.1
The Diskgroup agent resource in the fire drill service group may not be able to
import the fire drill diskgroup. This is due to a change in the VxVM semantics
for importing a clone DiskGroup. The import command may fail with the error:
VxVM vxdg ERROR V-5-1-16514 Disk group mera_dg_fd: import failed:
DG import duplicate clone detected.
Please refer to system log for details.

Resolution: For the fire drill to succeed, perform the following steps:

1. Bring the SRDFSnap resource(s) online

/opt/VRTSvcs/bin/hares -online <SRDFSnapResource> -sys <system>

where, SRDFSnapResource is the name of the SRDFSnap resource in the

fire drill service group, and system is the system on which the fire drill service
group must be brought online.

2. Run the following script to clear the clone_disk flag on the fire drill devices:
/usr/sbin/vxdisk listtag |grep <DeviceGroup> |while read x y;
do echo disk: [$x]; vxdisk set $x clone=off; done

where, DeviceGroup is the name of the Symmetrix device group.

3. Bring the rest of the fire drill service group online

hagrp -online <FiredrilSG> -sys <system>

16

Release Notes
Known issues

where FiredrillSG is the name of the fire drill service group, and system is
the system on which the fire drill service group must be brought online.

The SRDFSnap resource might not come online if the host is rebooted while
the fire drill luns are in sync with their corresponding source luns.
This issue occurs on the AIX operating system.
Resolution: To resolve this issue, bring the devices back to their normal (online)
state. To do this, perform the following steps:

1. Find the disks that correspond to the fire drill luns, and run the vxdisk
path command to find the corresponding VxVM disks.

2. Run the command vxdisk rm disk1 disk2 ... to delete the vmdisks
corresponding to the fire drill luns.

3. Run the appropriate SYMCLI command to split the devices from their
sources and to make the fire drill luns read-write enabled.

4. Use the vxdisk scandisks command to rescan the VxVM disks.

5. Run the appropriate SYMCLI establish command to resynchronize the

fire drill luns with their corresponding sources.

When a service group has multiple SRDFSnap resources, some of the resources
might not come online.
The symcfg discover command locks the Symmetrix configuration database,
causing this command to fail for other agents.
Resolution: To resolve this issue, run the following command to set the
NumThreads attribute of the SRDFSnap agent to 1:
$hatype -modify SRDFSnap NumThreads 1

The DiskGroup resource may not come online on an AIX LPAR with SYMAPI
servers configured.
If the host on which the SRDF agent is running is an AIX LPAR, then
SymapiServer is required for managing the replication since the Gatekeeper
devices cannot be mapped to the LPARs. If the LPAR is rebooted while the
underlying SRDF devices are in R2 (secondary) mode, and the VCS service
group is subsequently switched to go online on the same LPAR, the DiskGroup
resource may not go online. This problem occurs only on the AIX operating
system.
Resolution: To resolve this issue, perform the following steps:

1. After the reboot, log on to the AIX LPAR.

2. Find the disks that correspond to the SRDF R2 luns, and run the vxdisk
path command to find the corresponding VxVM disks.

17

Release Notes
Known issues

3. Run the vxdisk rm disk1 disk2command to delete the selected

vmdisks.

4. Use the vxdisk scandisks command to rescan VxVM disks.

EMC RecoverPoint
If you stop HAD on a system that has configured RecoverPoint resources and then
uninstall the RecoverPoint agent, HAD might not start on that system. In such a
case, the system transitions to the state of STALE_ADMIN_WAIT. This issue is
applicable only to the Windows operating system.
Resolution: Unconfigure RecoverPoint resources before you uninstall the
RecoverPoint agent.

IBM Global Mirror

VxVM disk groups might not get imported after a failover to the DR site in the
following conditions:

If VxVM disk groups are configured using IBM GlobalMirror volumes.

If FlashCopy and Global Copy volumes are attached to the same host.

Resolution: To resolve this issue, use the Symantec preonline trigger; contact
Symantec Technical Support to obtain the Symantec preonline trigger.

IBM SVCCopyServices

In some cases,the recreatevg command fails to create a volume group on the

IBM FlashCopy target disks. As a result, the SVCCopyServicesSnap resource
fails to come online.
Resolution: None

After you run the Silver fire drill, the application service group fails to come online
at the disaster recovery site.
Resolution: After running the Silver fire drill for SVCCopyServices at the disaster
recovery site, the replication target is resynchronized from the primary when
the fire drill service group is taken offline. If a disaster happens before the
resynchronization is complete, restore the replication target from the snapshot.
After the resynchronization from the primary or restore from the snapshot is
complete, you must discard the snapshot to bring the application service group
online at the disaster recovery site.

18

Release Notes
Known issues

IBM XIV Mirror

When you use the Symantec High Availability agent for IBM XIV Mirror with IBM
XCLI version 3.1.1, the XCLI script fails to run. This issue is observed on AIX and
Solaris operating systems.
This error is a result of a known issue in the IBM XIV XCLI.
For more details about the issue and the resolution, see the release notes for IBM
XIV Storage System Management Tools version 3.1.1.

Oracle Data Guard

In an Oracle RAC configuration, the Oracle Data Guard Broker resource comes
online on the first RAC node, but might fail to come online on the remaining RAC
nodes. This issue occurs when the DGMGRL status on the primary database is
ERROR.
Resolution: To resolve this issue, run the show configuration DGMGRL command
and resolve the error. You can then bring the resource online.

Oracle GoldenGate

The GetCurrentRPO action function is likely to time out when the application is
writing continuously to the database.
Resolution: To resolve this issue, consider increasing the timeout value of the
GetCurrentRPO action function for the GoldenGate type.

When a system on which the GoldenGate resource is online faults and fails over
to another system in the same cluster, data that is written to the database after
the fault occurs might not be replicated.
Resolution: When the GoldenGate resource comes online on another system
in the same cluster, perform the following tasks:

In the remote cluster, remove the lock on the trail file on the remote system.
To do this, temporarily rename the file and then revert to the original file
name.

Restart the Replicat process in the remote cluster. To do this, run the
StopReplicat action function and then run the StartReplicat action function.

NetAppSnapMirror
If the schedule for QSM or VSM is not present in the \etc\snapmirror.conf file
at the destination filer, then the remote failover of NetApp resource fails.

19

Release Notes
Known issues

Resolution: To resolve this issue, you have to manually add schedule entry to
\etc\snapmirror.conf file of the destination filer and then perform remote failover
operation.

VCS One replication agents

Oracle Data Guard
While bringing the Composite Service Group (CSG) online, if the primary cluster is
not available, then the online operation of the CSG fails.
Resolution: To avoid this problem, follow the below procedure after the Oracle Data
Guard resource has been configured. Oracle Data Guard resource is a part of the
CSG. Assign an additional role for the VCSOne client user to view the cluster objects
and for proper working of the Oracle Data Guard resource.
To assign an additional role for the VCS One client user:

Log on to the Policy Master (PM) server. Run the following command to list
the system users that are configured on the PM:
Policy_Master# hauser -list sys

Run the following command to display the object roles assigned to the VCS
One client user:
Policy_Master#hauser -value -sys
<vcsone_client_hostname>@VCSONE_USERS@<cluster_name> ObjectRoles

If the output is blank, then run the following command to set the object role
(ServerFarmObjectGuest) for the user:
Policy_Master# hauser -addrole
<vcsone_client_hostname>@VCSONE_USERS@<cluster_name>
ServerFarmObjectGuest

Run the following command to verify that the role is set:

Policy_Master# hauser -value -sys
<vcsone_client_hostname>@VCSONE_USERS@<cluster_name> ObjectRoles

Note: vcsone_client_hostname is the hostname of the VCS One client and

cluster_name is the cluster name to which the VCS One client belongs.

20

Release Notes
Known issues

Symantec ApplicationHA agents

Heartbeat agent

When upgrading the Symantec High Availability Configuration wizard, the

installation of the Agent Pack using the ./installagpack -upgrade command
might cause the following error message to appear:
Starting Heartbeat_Agent...
Failed Symantec High Availability Wizards Agent Pack Startup
did not complete successfully
Heartbeat_Agent failed to start on system_name

Resolution: It is safe to ignore this message.

IBM WebSphere MQ

When upgrading the Symantec High Availability Configuration wizard, the

installation of the Agent Pack using the ./installagpack -upgrade command
might cause the following error message to appear:
Starting WebSphereMQ_Agent...
Failed Symantec High Availability Wizards Agent Pack Startup
did not complete successfully
WebSphereMQ_Agent failed to start on system_name

Resolution: It is safe to ignore this message.

Documentation errata
This section provides a list of errors found in the documentation of the application
and database agents.

In the Installing, upgrading, and removing the agent chapter, a section name is
incorrect. The name of the section Installing the agent in a non-global zone on
Solaris 11 should be Installing the agent in a Solaris 10 brand zone. This error
is present in the documents of the following applications:

JBoss Application Server

PostgreSQL

Tibco EMS

The documentation for the following section is missing in the Installing, upgrading,
and removing the agent chapter of a few agents.
Installing the agent in a Solaris 10 brand zone

21

Release Notes
Documentation

To install the <agent name> in a brand zone on Solaris 10:

Ensure that the ACClibrary package, VRTSacclib, is installed in the non-global

zone.
To install VRTSacclib in the non-global zone, run the following command
from the global zone:
# pkgadd -R /zones/zone1/root -d VRTSacclib.pkg

To install the agent package in the non-global zone, run the following
command from the global zone:
# pkgadd -R zone-root/root -d . <agent package name>

Documentation
The following sections contain useful information about the Symantec High
Availability Agent Pack documentation.

Locating and displaying documentation

The latest version of the Agent Pack documentation is available in PDF format on
the Symantec Operations Readiness Tools (SORT) Web site here:
https://sort.symantec.com/agents.
If you download and uncompress the complete Agent Pack tar file or ZIP file, you
can find the documentation in the following directories.

For VCS agents:

platform/dist_arch/vcs/category/agent/vcs_ver/ag_ver/docs, where,

category is application, database, or replication.

For VCS One agents: platform/dist_arch/vcsone/vcsone_ver/docs

Getting help
Visit http://www.symantec.com/business/support/assistance_care.jsp for product
assistance. Use the Knowledge Base search feature to access resources such as
TechNotes, product alerts, software downloads, hardware compatibility lists, and
our customer email notification service. If you encounter an error when using a
product, include the error number preceding the message when contacting Technical
Services. You can also use the error number to search for information in TechNotes
or documents on the Web site.

22