Removing a single instance Oracle database on Linux and UNIX
This topic describes how to remove a single instance Oracle database on Linux/UNIX.
Before you begin
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.
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 a single-instance Oracle database on Linux/UNIX
If the database is running on a VCS cluster, ensure that resources for the group are online on one of the cluster nodes before attempting to remove the database in BMC Database Automation.
- From the Management Console, navigate to the domain that contains the Oracle database that you want to remove, and click the database name.
- In the right pane, under Database Configuration, select Provision > Remove Database.
In the Remove Oracle Database page, update the fields as follows, and click Next.
Displays the name of the domain of the database you are about remove.
Displays the node on which the instance resides.
Displays the name of the database that you are about to remove.
(Optional) Select a BMC Database Automation template that contains any optional or mandatory parameters for this operation. 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 information message appears in the step, in green type, listing the fields that require entries before advancing to the next step.
- If the Custom Fields page appears, update fields as desired, and click Next.
The Custom Fields page appears only when custom fields are defined in the BMC Database Automation XML template used for this provisioning activity. See Adding custom fields to a template.
In the Options page, update the following fields, and click Next.
Fix Inventory Permissions
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.
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
Select to modify the oratab ownership for the specified oinstall user and bypasses associated init-verify checks.
NEW IN 8.9.02Delete Home
Select this option to delete the Oracle Home directory when deleting its last associated Oracle 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
If the Oracle prerequisite checks are not met, enable this option to continue with the database removal.
Leave this field unchecked. 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, and click Next.
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.
If the Change Control page displays, populate the following fields, and click Next.
Bypass Change Control
(Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page.
Change Control Options
Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.
- Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page.
- Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.
Use Existing Change Ticket
ITSM Change ID
Specify the BMC Remedy ITSM change ticket number to associate with this change process.
ITSM Task ID
Specify the BMC Remedy ITSM task ID number to associate with this change process.
Create New Change Ticket
Assign the type of change for the new BMC Remedy ITSM change ticket.
Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.
Assign the urgency level for the new BMC Remedy ITSM change ticket.
Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.
Assign the change class for the new BMC Remedy ITSM change ticket.
Type a summary of the change process.
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
- 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.
Click Remove Database. You are prompted to confirm that you want to remove the database.
This operation permanently deletes the database files from the node.
A status page appears, and a confirmation message appears when the database has been removed.
If you select the Automatically Continue If All Tests Succeed option while the removal is in progress, the removal process continues automatically after the tests have been completed successfully.
- Click Continue to complete this step and return to the Contents view of this domain.
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.