Note: In order to take advantage of Oracle Net remote client access, the IP address used for client connectivity must be under LifeKeeper protection as a dependent of the Oracle hierarchy. (Refer to the section Configuring the Oracle Net Listener for LifeKeeper Protection for details.)
To create a resource instance from the primary server, you should complete the following steps:
- From the LifeKeeper GUI menu, select Edit, then Server. From the drop down menu, select Create Resource Hierarchy.
Important: The Oracle Application must be running when you create the resource.
A dialog box will appear with a drop down list box with all recognized Recovery Kits installed within the cluster. Select Oracle Database from the drop down listing. Click Next to proceed to the next dialog box.
Note: When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is especially helpful should you encounter an error that might require you to correct previously entered information.
If you click Cancel at any time during the sequence of creating your hierarchy, LifeKeeper will cancel the entire creation process.
- Select the Switchback Type. This dictates how the Oracle instance will be switched back to this server when it comes back into service after a failover to the backup server. You can choose either intelligent or automatic. Intelligent switchback requires administrative intervention to switch the instance back to the primary/original server. Automatic switchback means the switchback will occur as soon as the primary server comes back on line and reestablishes LifeKeeper communication paths.
The switchback type can be changed later, if desired, from the General tab of the Resource Properties dialog box. Click Next to proceed to the next dialog box.
- Select the Server where you want to place the Oracle Database (typically this is referred to as the primary or template server). All the servers in your cluster are included in the drop down box. Click Next to proceed to the next dialog box.
- Select the ORACLE_SID for the Database ID. This is the tag name that specifies the Oracle system identifier of the database being configured. An entry for this database must exist in /etc/oratab. Click Next to proceed to the next dialog box.
- Input the Username for ORACLE_SID. This is the Oracle Database Username specified during login to ORACLE_SID. This username must be able to connect as sysdba authority to the database to gain full control. Click Next to proceed to the next dialog box. (This field can be left empty. If left empty, LifeKeeper will not use Username and Password to control the Oracle Database resource, and the next step, Input Password, will be skipped.)
- Input Password. This is the password specified during login to ORACLE_SID. The password will be saved by LifeKeeper with encrypting. Click Next to proceed to the next dialog box.
- Select the tag name of the Listener to be included as a dependency of the Oracle resource. The list displays all the currently protected Listener resource(s) on the server. Select the Listener resource tag that corresponds to the required listener(s) for the Oracle SID. Select None if no Listener resource exists.
- Select or enter the Database Tag. This is a tag name that LifeKeeper gives to the Oracle hierarchy. You can select the default or enter your own tag name.
When you click Create, the Create Resource Wizard will create your Oracle resource.
- At this point, an information box appears and LifeKeeper will validate that you have provided valid data to create your Oracle resource hierarchy. If LifeKeeper detects a problem, an ERROR will appear in the information box. If the validation is successful, your resource will be created.
Click Next to proceed to the Pre-extend dialog box which is explained later in this documentation. You must extend the hierarchy to another server in your cluster in order to place it under LifeKeeper protection.
Post your comment on this topic.