The procedures for deleting database instances are different for policy-managed and administrator-managed databases. Deleting a policy-managed database instance involves reducing the number of servers in the server pool in which the database instance resides. Deleting an administrator-managed database instance involves using DBCA to delete the database instance.
To delete a policy-managed database, reduce the number of servers in the server pool in which a database instance resides by relocating the server on which the database instance resides to another server pool. This effectively removes the instance without having to remove the Oracle RAC software from the node or the node from the cluster.
For example, you can delete a policy-managed database by running the following commands on any node in the cluster:
$ srvctl stop instance -d db_unique_name -n node_name $ srvctl relocate server -n node_name -g Free
The first command stops the database instance on a particular node and the second command moves the node out of its current server pool and into the Free server pool.
See Also:
"Removing Oracle RAC" for information about removing the Oracle RAC software from a node
Deleting Instances from Administrator-Managed Databases
Note:
Before deleting an instance from an Oracle RAC database using SRVCTL to do the following:
If you have services configured, then relocate the services
Modify the services so that each service can run on one of the remaining instances
Ensure that the instance to be removed from an administrator-managed database is neither a preferred nor an available instance of any service
See Also:
The procedure in this section explains how to use DBCA in interactive mode to delete an instance from an Oracle RAC database.
See Also:
Oracle Database 2 Day + Real Application Clusters Guide for information about how to delete a database instance from a target node with Oracle Enterprise Manager