Relocating an Oracle RAC One Node active instance
You can create a RAC One node database on all the nodes that are part of a cluster. For a planned migration, a RAC One Node environment works effectively because it enables you to continue work without impacting the business by relocating the instance from one node to another while moving the sessions along with it. Oracle RAC One Node instance relocation provides a transparent workaround for issues such as the instance being down or the node not having enough resources to handle the incoming workload.
This topic describes how to relocate an Oracle RAC One Node instance to another node/instance.
Before you begin
Download the ORA-Relocate-RON-DB Action, available as a zipkit on the BDA Community (https://communities.bmc.com/docs/DOC-36130) and import it into your Action Repository.
- Ensure that an Oracle RAC One Node database with at least one instance that is online and one or more available candidate servers are currently available and being managed by BDA. For more information, see Adding-a-candidate-server-to-an-Oracle-RAC-One-Node-database.
To relocate an Oracle RAC One Node active instance
- From the Management Console, navigate to the RAC One Node database and select the active node/instance under that database.
- Select Management > Relocate Instance.
In the Action page, populate the following fields, and click Next.
In the Custom Fields page, populate the following fields and any other custom fields you have defined in the template, and click Next.
In the Job Options page, specify any of the following Job options, and click Next.
In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
New in 8.9.03If you choose to run the job now or at a future time, optionally, you can use the Set Maintenance Window option to specify the Maintenance Window Start Time and the Maintenance Window End Time during which the job should be scheduled and running.If the Change Control page displays, populate the following fields, and click Next.
- 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.
- If you have uploaded custom verification checks for this Action, specify your verification preferences.
- To run the Action after the custom verification checks have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
To run the Action without having first run the custom verification checks, select Skip Pre-Verification Tests.
Click Execute Job or Schedule Job (depending on your selection in the Scheduling step).
If the Action is running, a progress page appears.The Instances section of Database Configuration page for the RAC One Node database in the Context Frame will show the active and passive instances switched.
When you schedule an Action, it is added to the Jobs list. You can view scheduled Jobs by selecting Jobs from the Context Frame, specifying a start and end date, and filtering the Jobs list for a Scheduled status. After you schedule a job, the start date and time cannot be modified. If you need to change the schedule for a Job, you must cancel the Action and recreate it. See Cancelling an Action. After a Job has started running, it cannot be cancelled by using the Management Console.
If a target for an Action is in a Down state, or is no longer in the environment when the associated Job starts, the Job will stop due to the unavailability of the target, and the status of the Job changes to Failed.
If you have uploaded custom verification checks, the Verification page displays. If all of the checks pass, click Continue to run the Action. If checks fail, resolve the identified issues and click Repeat Verification.