HP StorageWorks Storage Mirroring application notes High availability for Oracle 10g Part number: T2558–88088 Fourth edition: May 2008
Legal and notice information © Copyright 2005-2008 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Document overview This document is a Storage Mirroring application note. An application note provides guidelines on the use of Storage Mirroring in a specific environment. This document contains: • Document overview—Explains what an application note contains, how it should be used, what you need to know before trying to use the application note, and where you can go for more information.
Solution overview Oracle is a scalable, reliable, flexible, and high-performance relational database management system for many server-based operating systems. Storage Mirroring provides real-time enterprise data protection and replication. Storage Mirroring can be used to provide high availability for Oracle. This document describes the steps necessary to configure Storage Mirroring to provide high availability for Windows® servers running Oracle 10g.
Modifying the sample script files After you modify the sample scripts, save them with a new name to remove the SAMPLE_ prefix. Copy the scripts to the directory where Storage Mirroring is installed. The sample batch files provided are only examples. Because no two environments or configurations are exactly the same, you MUST modify the sample scripts in order to make the solution work in your environment.
Sample implementation This section described an example of how to configure Storage Mirroring and Oracle. Use these procedures as a guideline for creating your own implementation. Because no two environments or configurations are exactly the same, you will probably need to implement additional or different steps than what is documented in order to Install software on the source. Install software on the source 1. Install Oracle on the source, if it is not already installed. 2.
• File Name—This column lists each file name you need to select for replication. These files are assigned names during your initial Oracle installation and configuration causing some of these files to be unique to your environment. For example, if you used the default Oracle installation, your instance parameter file will be init.ora and located in the \oracle\admin\instance_name\pfile folder in the destination drive. If you supplied an instance name of prod, your init.
NOTE: There is a unique numeric identifier at the end of the init.ora file (xxxxx) that uniquely identifies initialization files when there is more than one installed. Besides the initialization parameter file (init.ora), which is stored in a text format, administrators can choose to maintain the initialization parameters in a binary server parameter file (spfile.ora). This is installed by default The Listener service will not start on the target if listener.
Sample_postover.bat rem ## ***SAMPLE*** Oracle post-failover script rem ## This sample batch file is provided as an example only. Because no two rem ## environments or configurations are exactly the same, you MUST modify rem ## this script in order to make the solution work in your environment. rem ## This script makes the following two assumptions: rem ## 1. You have created a directory c:\oracle_fo rem ## 2. The dbx_start.
rem ## The following line starts the Oracle Listener service. The outcome is redirected to rem ## the failover directory where a log file is created. Check this log file for errors. NET START OracleOraHomeTNSListener >>%ORACLE_FO%\start_services.log NOTE: After failover is complete, users will need to log back into the Oracle database. You may want to devise an automatic process to notify the users of this information and include it at the end of the post-failover script.
Sample_preback.bat rem ## ***SAMPLE*** Oracle pre-failback script rem ## This sample batch file is provided as an example only. Because no two rem ## environments or configurations are exactly the same, you MUST modify rem ## this script in order to make the solution work in your environment. rem ## This script makes the following two assumptions: rem ## 1. You have created a directory c:\oracle_fo rem ## 2. The db_stop.
3. Select Start, Programs, Storage Mirroring, Failover Control Center. 4. Select the target machine from the list of available machines. If the target you need is not displayed, click Add Target, enter the machine name, and click OK. 5. To add a monitor for the selected target, click Add Monitor. Type the name of the source machine and click OK. The Monitor Settings window will open. 6. In the Monitor Settings window, mark the IP address that is going to failover. 7.
8. You will be prompted to determine if you want to continue monitoring the source server. Do not choose Continue or Stop at this time. 9. Connect the source machine to the network. 10. After the source is back online, select whether or not you want to continue monitoring this source machine (Continue or Stop). NOTE: Verify that the Storage Mirroring connection on the source has been disconnected. If it is not right-click the connection in the Storage Mirroring Management Console and select Disconnect. 11.
