Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition System Administration Guide

Search Scope:

- This Document
- Entire Library

## How to Recover After a Takeover

1. Allow the MySQL slave threads to be started if the database resource performs a restart or similar action.

   Remove the `skip-slave-start` keyword from the appropriate `my.cnf` file.

2. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC.

   Note - If you use a role with Geo Management RBAC rights, ensure that the `/var/cluster/geo` ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

       # chmod A+user:username:rwx:allow /var/cluster/geo

   The `/var/cluster/geo` directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

3. Log in to MySQL as superuser, then start the slave.

       mysql> start slave;

4. Verify that the slave is running, and wait until it is synchronized with the master.

       mysql> show slave status\G

   If the slave status shows that at least one slave thread is not running, fix the root cause, and retry the operation. As a last resort, you could take a backup from the current master and perform a fresh slave setup.

   Connect to a node of the old primary cluster and update the protection group to change the role from a deactivated primary cluster to a secondary cluster.

5. Log in to a cluster node.
6. Resynchronize the protection group.

        # geopg update protection-group

7. Start the protection group locally.

       # geopg start -scope local protection-group

   For more information, see Resynchronizing a MySQL Protection Group and Activating and Deactivating a MySQL Protection Group.

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |