Installing Oracle

Once you have installed LifeKeeper and configured the volume and communication resources, you are ready to install Oracle to the protected volume(s).

Oracle 12c Installation: Oracle12c introduces some new installation options. The following options for software and sample database installation are recommended.

• Oracle Services Account – Select the “Windows Built-In Account”. This is referring to the Local System Account.

• Container Database – Uncheck the “Container Database” checkbox option for the sample database.

*If you are installing Oracle 12c R2 go to Advanced Options to change the passwords for SYS and SYSTEM usernames.

• Password Management – After the sample database is installed the “Password Management” button is presented. Select it and set the password for the SYS and SYSTEM administrator accounts. One of these accounts (your choice) will be needed for creating the Oracle resource hierarchy.

On the Primary Server

1. Install the Oracle software to the protected shared volume. This creates the Oracle SID. Note that all files related to this Oracle SID (including log,trace, control, and data files) must be located on protected volumes.

2. Stop the default TNSListener service OracleTNSListener and set the startup mode to Manual. (You will create a new Listener for the SID to be protected in a later step.)

3. Using Oracle Net Manager, configure Oracle to use the LifeKeeper-protected communication resource(s) as follows:

   1. Create a new TNSListener Service using the SID name. Configure Listening Locations designating the LifeKeeper-protected IP address and/or named pipe (LAN Manager alias name). Then configure the Database Services specifying the Oracle Home directory and SID.

   2. Modify the Oracle Service for your SID. For TCP/IP, change the host name to the protected IP address. For Named Pipes, change the machine name to the LAN Manager alias.

4. Create a separate TNSListener Service instance for the SID to be protected under LifeKeeper. The service should be created using the lsnrctl Start <SID> command. This will create a service with the name OracleTNSListener<SID>.

5. Use the Services tool to test your Oracle services as follows:

   1. Verify that the new TNSListener service can be stopped and started successfully.

   2. Ensure that the OracleService<SID> service has been created by Oracle.

   3. Stop all Oracle services.

On the Backup Server

1. In LifeKeeper, bring the protected volume in service on the backup server.

2. Remove the Oracle inventory directory and rename the directory or directories that contain the Oracle data files. If this is a new installation you can delete the data files.

3. Install the Oracle software to the protected volume. Use EXACTLY the same installation options as on the primary server (the Oracle Home, SID name and paths must be identical). If prompted, choose to overwrite the existing Oracle configuration. Note: Ignore errors regarding moving files to *.bak.

4. Stop the default TNSListener service Oracle<OraHome>TNSListener, and set the startup mode to Manual.

5. Using Oracle Net Manager, configure Oracle to use the LifeKeeper-protected communication resource(s) as follows, if required:

   1. Create a new TNSListener Service using the SID name. Configure Listening Locations, designating the LifeKeeper-protected IP address and/or named pipe (LAN Manager alias name). Then configure the Database Services, specifying the Oracle Home directory and SID.

   2. Modify the Oracle Service for your SID. For TCP/IP, change the host name to the protected IP address. For Named Pipes, change the machine name to the LAN Manager alias.

6. Create a separate TNSListener Service instance for the SID to be protected under LifeKeeper. The service should be created using the lsnrctl Start <SID> command. This will create service with the name Oracle<OraHome>TNSListener<SID>.

7. Use the Services tool to test your Oracle services as follows:

   1. Verify that the new TNSListener Service can be stopped and started successfully.

   2. Ensure that the OracleService<SID> service has been created by Oracle.

   3. Stop all Oracle services on the backup server.

On the Primary Server

1. Bring the volume resource back in service on the primary server.

2. Start the OracleService<SID> service on the primary server.

3. Create the Oracle hierarchy on the primary server and extend it to the backup server. See Creating an Oracle Hierarchy for details.

4. Test the new Oracle hierarchy by performing a manual failover.