Removing a single instance Oracle database on Windows

This topic describes how to remove a single-instance Oracle database on Windows.

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.

Important

If 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

  1. Log on to the BMC Database Automation Manager server and navigate to the following directory: /app/clarity/dmanager/etc.
  2. Edit the d2500_config file with a text editor and append the following parameter to the file:
    delete_homes_prompt=True

  3. 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 delete_homes_prompt to 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.

    Note

    If you do not insert the delete_homes_prompt parameter 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.

  • Use the <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 tagDescription
    <delete_homes> </delete_homes>

    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.

    Note

    If you do not insert the delete_homes_prompt parameter 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 Windows

  1. From the Management Console, navigate to the domain that contains the Oracle database that you want to remove, and click the database name.
  2. Select Provision > Remove Database.
  3. In the Remove Oracle Database page, populate the following fields, and click Next.

    Field

    Description

    Domain

    Displays the name of the domain of the database you are about remove.

    Host

    Displays the node on which the instance resides.

    Database

    Displays the name of the database that you are about to remove.

    Template

    (Optional) Select a template that contains any optional or mandatory parameters for this operation. See Managing templates for Oracle on Windows. 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.

  4. If the Custom Fields page appears, update the custom fields as necessary, 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.
  5. In the Options page, populate the following fields, and click Next.

    Field

    Description

    Ignore Oracle OUI Prerequisite Checks

    (Optional) Select to continue with the instance removal if the Oracle prerequisite checks are not met.

    Force Removal

    (Optional) 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.

    Upload Oracle Media

    (Optional) Select to upload Oracle media to the Agent.

    Cleanup Oracle Media When Completed

    (Optional) Select to remove Oracle media from Agent after the remove operation is complete.

    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_prompt parameter to True, as described in Before you begin.

    Database Installation Domain

    Type the domain of the OS user that should own this Oracle installation.

    Database Installation User

    Type the OS user that should own this Oracle installation.

    Database Installation Password

    Type the password of the OS user that should own this Oracle installation.

  6. In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.

    Field

    Description

    Pre-Provisioning Script Directory

    (Optional) Select the scripts that you want to run before this event and click 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 Managing pre-provisioning and post-provisioning script files.

    Post-Provisioning Script Directory

    (Optional) Select the scripts that you want to run after this event and click to move them to the Selected list box. See also Managing pre-provisioning and post-provisioning script files.

  7. In the Job Options page, specify any of the following Job options, and click Next.

    Type

    Option

    Description

    Notification Emails

    Email List

    (Optional) Click Add Email to add email addresses to the notification list.

    Job Administration

    Cleanup Agent Logs

    (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the Job is complete.

  8. If the Change Control page displays, populate the following fields, and click Next.

    Section

    Field

    Description

    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

    Change Type

    Assign the type of change for the new BMC Remedy ITSM change ticket.

    Change Impact

    Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.

    Change Urgency

    Assign the urgency level for the new BMC Remedy ITSM change ticket.

    Change Risk-Level

    Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.

    Change Class

    Assign the change class for the new BMC Remedy ITSM change ticket.

    Change Summary

    Type a summary of the change process.

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring change control.

  9. In the Summary page, review the provisioning information.
    To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  10. 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.

      Note

      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.

  11. Click Remove Database.
  12. Click OK when you are prompted to confirm that you want to remove the database.

    Warning

    This operation permanently deletes the database files from the node.

    Note

    If you select the Automatically Continue If All Tests Succeed option, the removal process continues automatically after the tests have been completed successfully.

    After verification, the job is performed and the results appear.
    A confirmation message indicates the database has been removed.

  13. If this procedure was not successful, see Troubleshooting.

    Note

    You can always return to a Job's Information page by using the Jobs section of the Management Console. See Monitoring jobs and viewing job history for details.

Was this page helpful? Yes No Submitting... Thank you

Comments