Performing Two or More Operations that Update the Sun StorEdge Availability Suite 3.2.1 Configuration Database Simultaneously Might Corrupt the Configuration Database (6303883)

Problem Summary: You must not perform two or more operations that update the Sun StorEdge Availability Suite 3.2.1 configuration database simultaneously in the Sun Cluster environment.

When the Sun Cluster Geographic Edition software is running, you must not perform two or more of the following commands simultaneously on different protection groups with data replicated by Sun StorEdge Availability Suite 3.2.1:

• geopg add-device-group

• geopg remove-device-group

• geopg get

• geopg delete

• geopg update

• geopg validate

• geopg start

• geopg stop

• geopg switchover

• geopg takeover

For example, running the geopg start pg1 command and geopg switchover pg2 command simultaneously might corrupt the Sun StorEdge Availability Suite 3.2.1 configuration database.

Sun StorEdge Availability Suite 3.2.1 is not supported on Solaris OS 10. If you are running Solaris OS 10, do not install the Sun Cluster Geographic Edition packages for Sun StorEdge Availability Suite 3.2.1 support.

Workaround: For Sun Cluster configurations consisting of two or more nodes, you must enable the Sun StorEdge Availability Suite 3.2.1 dscfglockd daemon process on all of the nodes of both partner clusters. You do not need to enable this daemon for Sun Cluster configurations consisting of only a single node.

To enable the dscfglockd daemon process , complete the following procedure on all nodes of both partner clusters.

How to Enable the Sun StorEdge Availability Suite 3.2.1 dscfglockd Daemon Process

1. Ensure that the Sun StorEdge Availability Suite 3.2.1 product has been installed as instructed in the Sun StorEdge Availability Suite 3.2.1 product documentation.

2. Ensure that the Sun StorEdge Availability Suite 3.2.1 product has been patched with the latest patches available on SunSolve at http://sunsolve.sun.com.

3. Create a copy of the /etc/init.d/scm file.

   # cp /etc/init.d/scm /etc/init.d/scm.original

4. Edit the/etc/init.d/scm file.

   Delete the comment character (#) and the comment “(turned off for 3.2)” from the following lines.

   # do_stopdscfglockd (turned off for 3.2) # do_dscfglockd (turned off for 3.2)

5. Save the edited file.

6. If you do not need to reboot all the Sun Cluster nodes, then a system administrator with superuser privileges must run the following command on each node.

   # /usr/opt/SUNWscm/lib/dscfglockd \ -f /var/opt/SUNWesm/dscfglockd.cf

Next Steps

If you require further assistance, contact your Sun service representative.