Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 3.3 3/13 |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
4. Administering Access and Security
5. Administering Cluster Partnerships
How to Create Heartbeat Plug-in
Modifying a Heartbeat Plug-in Property
How to Modify the Properties of a Heartbeat Plug-in
Displaying Heartbeat Configuration Information
How to Display Heartbeat Configuration Information
Tuning the Heartbeat Properties
How to Modify the Heartbeat Properties
Creating a Heartbeat That Uses a Custom Heartbeat Plug-in
Overview of Creating a Custom Heartbeat Plug-in
How to Add a Custom Heartbeat Plug-in to an Existing Default Heartbeat
How to Create a Custom Heartbeat Plug-in and Add It to a Custom Heartbeat
Configuring Heartbeat-Loss Notification
Configuring the Heartbeat-Loss Notification Properties
Creating an Action Shell Script for Heartbeat-Loss
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
This section describes procedures for deleting heartbeats and heartbeat plug-ins.
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.
# geohb delete heartbeatname
Specifies an identifier for the heartbeat settings.
For more information about the geohb command, refer to the geohb(1M) man page.
Example 6-4 Deleting a Heartbeat
This example deletes a heartbeat that is named paris-to-newyork.
# geohb delete paris-to-newyork
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.
# geohb remove-plugin pluginname heartbeatname
Caution - Do not delete the default heartbeat plug-ins tcp_upd_plugin and ping_plugin. |
Specifies the name of the custom heartbeat plug-in
Specifies an identifier for the heartbeat that contains this plug-in
For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities.
For more information about the geohb command, refer to the geohb(1M) man page.
Example 6-5 Deleting a Plug-in From a Heartbeat
This example removes the plug-in that is named command1 from the heartbeat that is named paris-to-newyork.
# geohb remove-plugin command1 paris-to-newyork