| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Geographic Edition System Administration Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Cluster Geographic Edition System Administration Guide |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
4. Administering Access and Security
5. Administering Cluster Partnerships
7. Administering Protection Groups
8. Monitoring and Validating the Geographic Edition Software
9. Customizing Switchover and Takeover Actions
A. Standard Geographic Edition Properties
B. Legal Names and Values of Geographic Edition Entities
C. Disaster Recovery Administration Example
E. Troubleshooting Geographic Edition Software
F. Deployment Example: Replicating Data With MySQL
MySQL Replication Resource Group
MySQL Application Resource Group
Initial Configuration of MySQL Replication
Installing MySQL and Configuring the MySQL Database Resource Group
How to Configure the MySQL Replication
Configuring the MySQL Application Resource Group
Administering MySQL Protection Groups
Planning for Your MySQL Protection Group
Creating, Modifying, Validating, and Deleting a MySQL Protection Group
How to Create the MySQL Configuration
Modifying a MySQL Protection Group
Validating a MySQL Protection Group
How to Delete a MySQL Protection Group
Administering MySQL Application Resource Groups
How to Add an Application Resource Group to a MySQL Protection Group
How to Delete an Application Resource Group From a MySQL Protection Group
Administering MySQL Data-Replicated Components
How to Add a Data-Replicated Component to a MySQL Protection Group
Data Replication Subsystem Process for Verifying the Replicated Component
How to Modify a MySQL Data-Replicated Component
Replicating a MySQL Protection Group Configuration to a Partner Cluster
Activating and Deactivating a MySQL Protection Group
Activating a MySQL Protection Group
Deactivating a MySQL Protection Group
Resynchronizing a MySQL Protection Group
Recovery Strategy After a Takeover of a MySQL Protection Group
How to Recover After a Takeover
You might need to delete a data-replicated component from a protection group if you previously added a data-replicated component to that protection group. Normally, after an application is configured to connect to the database, you would not change the database.
Before You Begin
Before you delete a data-replicated component, ensure that the following conditions are met:
The protection group is defined on the local cluster.
The protection group is offline on the local cluster and the partner cluster, if the partner cluster can be reached.
The device group is managed by the protection group.
For information about deleting protection groups, refer to How to Delete a MySQL Protection Group.
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.
# geopg remove-replication-component MySQL-replicated-component protection-group
In this syntax, MySQL-replicated-component specifies the name of the data-replicated component, and protection-group specifies the name of the protection group.
Example F-6 Deleting a Replicated Component From a MySQL Protection Group
In the following example, a data-replicated device group is deleted from a MySQLprotection group:
# geopg remove-replication-component mysql-dg mysql-pg
|