Removing an Oracle RAC database
This topic describes how to remove an Oracle RAC database.
Before you begin
- A running Oracle RAC database with exactly one instance currently managed by BMC Database Automation must be available.
NEW IN 8.9.02Starting with version 8.9.02, you can retain or delete the Oracle Home directory when deleting its last associated Oracle database.
ImportantIf the database you are deleting is not the last database associated with the Oracle Home directory, the Oracle Home directory will not be deleted.
To enable the option to retain or delete the Oracle Home directory, you need to add a parameter,
delete_homes_prompt, to the d2500_config file, as follows:
To enable the option to retain or delete the Oracle Home directory
- Log on to the BMC Database Automation Manager server and navigate to the following directory: /app/clarity/dmanager/etc.
Edit the d2500_config file with a text editor and append the following parameter to the file:
Save the file.
After you add the parameter, you can use one of the following methods to retain or delete the Oracle Home directory. If the last database is removed, but the Oracle Home is kept, it is re-discovered and appears in the Pending Approval > Oracle > Oracle Homes Pending Approval section.
Use the Delete Home option: When you set the value of
True, the Delete Home option becomes available on the Remove Oracle Database wizard. By default, this option is already selected. You can clear this option if you do not want to delete the Oracle Home directory.
If you do not insert the
delete_homes_promptparameter in the d2500_config file or set its value to False, the Delete Home option will not be available on the Remove Oracle Database wizard and Oracle Home is removed automatically.
<delete_homes>tag in the template: Modify the template that you want to use while deleting an Oracle Database. Add the XML tag to the template as follows:
XML tag Description
Valid values are:
- True: The Oracle Home directory is automatically deleted when its last associated Oracle database is removed.
- False: The Oracle Home directory is not automatically deleted when its last associated Oracle database is removed.
If you do not insert the
delete_homes_promptparameter in the d2500_config file or set its value to False, value of the
<delete_homes>tag in the template is not considered and Oracle Home is removed automatically.
To remove an Oracle RAC database
- From the Management Console, navigate to the database that you want to remove.
Select Provision > Remove Database.
(Optional) In the General page, select a template from the Template list box.
For more information about templates, see Managing templates for Oracle on Linux and UNIX.
- If you select a template, click Skip Ahead to advance directly to the next step that requires input. An informational message appears on these steps, in green type, listing the fields that require entries before advancing to the next step.
If you do not select a template, go to the next step.
In the Options page, provision the following fields, and click Next.
Fix Inventory Permissions
(Optional) Select to change the permissions on the inventory to 770, so that it is writeable by all users in the install group.
Note: Selecting this option is recommended when the host contains Oracle Homes owned by different users and to avoid pre-verification errors.
(Optional) Select to fix permissions on directories and files that require changes for deployment in a multi-user environment (that is, environments where different Oracle Homes on the same node are owned by different users).
Fix oratab Ownership
(Optional) Select to modify the oratab ownership for the specified oinstall user and bypasses associated verification checks.
NEW IN 8.9.02Delete Home
Select this option to delete the Oracle Home directory when deleting its last associated Oracle RAC database.
Note: This option appears only when you have set the
delete_homes_promptparameter to True, as described in Before you begin.
Ignore Oracle OUI Prerequisite Checks
(Optional) Select to continue with the instance removal if the Oracle prerequisite checks are not met. Specifically, checking this field does the following:
- Uses the -ignoreSysPrereqs flag (for 10gR2) or the -ignorePrereq flag (for 11gR2 and later) during Oracle provisioning operations, thus ignoring any failed Oracle prerequisite checks.
- Ignores the verification checks that verifies whether Oracle media is correctly setup for Red Hat 5.
Do not select this check box. Force removal should only be used as a last resort. The circumstances under which this field should be used are explained in Troubleshooting.
In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows:
Pre-Provisioning Script Directory
(Optional) Select the scripts that you want to run before this event and click Managing pre-provisioning and post-provisioning script files.to move them to the Selected list box. The scripts in Selected are run in the order listed. Use Move Up and Move Down to re-order the scripts when necessary. See also
Post-Provisioning Script Directory
(Optional) Select the scripts that you want to run after this event and click Managing pre-provisioning and post-provisioning script files.to move them to the Selected list box. See also
In the Job Options page, specify any of the following Job options, and click Next.
(Optional) Click Add Email to add email addresses to the notification list.
Cleanup Agent Logs
(Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the Job is complete.
- In the Summary page, review the provisioning information.
To make changes, do the following:
- Click Go to to return to the provisioning step that you want to edit.
- Make your changes.
- Click Save and Review to return to the Summary page.
- Specify your verification preferences.
For additional information, see Understanding pre-verification tests.
- To continue with database creation after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.
The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to the actual provisioning activity.
- Enter Yes when you are prompted to confirm your decision, and click OK.
BMC Database Automation prepares to remove the database. A progress page appears.
Click Continue to remove the database.
This operation permanently removes the RAC database from the node.
When the database is removed, BMC Database Automation removes the resources for the database and the resources for any listeners associated with the Oracle Home if the home is also being removed. The remove database process also performs a re-scan, to ensure the Management Console gets updated.
If this procedure was not successful, see Troubleshooting.
Detailed current and historical information about this action can be viewed in the Jobs section of the Management Console. See Monitoring jobs and viewing job history.