You may want to create an Oracle Listener if any of the following statements are true for your system configuration:
- Multiple Listeners are defined for Multiple Oracle SIDs
- The Oracle Listener is a critical component in your configuration
- A Single Listener is defined for Multiple Oracle SIDs
This process will allow protection of listener(s) within LifeKeeper to accommodate various listener(s) and SIDs combinations.
If you are creating a Listener for multiple resources, follow these procedures.
- 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 Listener from the drop down listing. Click Next to proceed to the next dialog box.
- You will be prompted to enter the following information. 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.
Choose either intelligent or automatic. This dictates how the Listener resource will be switched back to this server when the server comes back up after a failover. If using data replication, choose intelligent as the switchback type.
Note: The switchback type must match that of the dependent resources (IP and volume resources) used by the Listener resource, or else the create will fail.
|Server||Select the server on which you want to create the hierarchy.|
|Listener Configuration File Path||Select the full path to the Oracle listener configuration file.|
|Listener Names(s)||Select the name(s) of the Oracle Listener(s) to provide protection for with this resource instance.|
|Listener Executable(s)||Select the path to the Oracle listener executable. The listener executable is required to start, stop, monitor and recover the specified Oracle listener(s).|
|Listener Protection Level||
Select one of the following levels:
Full Control (Start, Stop, Monitor and Recover)
Intermediate Control (Start, Monitor and Recover)
Minimal Control (Start and Monitor Only)
|Listener Recovery Level||
Select the level of recovery for the specified listener:
Standard (On) – Enable standard LifeKeeper recovery. If Standard (On) is selected, all listener failures will be tried locally, and if necessary, trigger a failover to an available backup server.
Optional (off) – Enable optional LifeKeeper recovery. If Optional (Off) is selected, all listener failures will be tried locally, but will not cause a failover to an available backup server.
|IP Address Name(s)||Select the IP Address resource name that will be protected as dependents of this resource hierarchy. IP Address associated with the selected listener(s) are displayed in the choice list. Select None if no IP resources are required for this configuration,|
|Listener Tag||Enter a unique name for the resource on the server. The valid characters allowed for the name are letters, digits, and the following special characters: – _ . /|
- Select the Create button to start the hierarchy creation. An information box appears and LifeKeeper will validate that you have provided valid data to create your database listener 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.
- The Pre-Extend Wizard dialog will appear stating that you have successfully created the resource hierarchy and you will be prompted to select the following information. If you are unfamiliar with the Extend operation, click Next after making a selection in each dialog box. If you are familiar with the LifeKeeper Extend Resource Hierarchy defaults and want to bypass the prompts for input/confirmation, click Accept Defaults.
|Target Server||Select a Target Server to which the hierarchy will be extended. If you select Cancel before extending the resource hierarchy to at least one other server, LifeKeeper will provide no protection for the applications in the hierarchy.|
|Switchback Type|| This dictates how the Oracle Listener 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. The switchback type can be changed later, if desired, from the General tab of the Resource Properties dialog box.
Note: Remember that the switchback strategy must match that of the dependent resources to be used by the Oracle Listener resource.
|Template Priority|| This field appears only if you did NOT extend directly from the Create function.)
Enter a number between 1 and 999 to specify the template server’s priority in the cascading failover sequence for this resource. A lower number means a higher priority. LifeKeeper assigns the number “1” to the server on which the hierarchy was created. No two servers can have the same priority for a given resource.
|Target Priority||Enter a number between 1 and 999 to specify the target server’s priority in the cascading failover sequence for this resource. A lower number means a higher priority. LifeKeeper offers a default of 10 for the first server to which a hierarchy is extended.|
- After receiving the message that the pre-extend checks were successful, click Next and enter the following information.
|Listener Configuration File Path||Select the full path to the Oracle Listener configuration file.|
|Listener Executable(s) Path||Select the path to the Oracle Listener executables. The listener executables are required to start, stop, monitor and recover the specified Oracle listener(s).|
|Listener Tag||This field is automatically populated with a unique name for the new Oracle Listener resource instance on the primary server. The default naming pattern will be displayed for you. You may type in another unique name. The valid characters allowed for the Listener tag are letters, digits and the following special characters – : . /|
- Click Extend. The Hierarchy Integrity Verification window displays with the following message, Hierarchy Verification Finished. Click Next Server or Finish.