132 high availability case study rac

Oracle Retail 13.2 High-Availability Case Study RAC (Real Application Clusters Environment)

An Oracle Case Study April 2011

Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided

for information purposes only and the contents hereof are subject to change without notice.

This document is not warranted to be error-free, nor subject to any other warranties or

conditions, whether expressed orally or implied in law, including implied warranties and

conditions of merchantability or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document and no contractual obligations are formed either

directly or indirectly by this document. This document may not be reproduced or transmitted

in any form or by any means, electronic or mechanical, for any purpose, without our prior

written permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names

may be trademarks of their respective owners.

Note: The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are

subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed

orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be

reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Contents Case Study: Creating a High-Availability RAC Environment for Oracle Retail 13.2 .........1

Installation Overview.......................................................................................................................1

Oracle 11gR2 CRS Installation on Linux x86-64...................................................................2 Node Configuration .........................................................................................................................2 Oracle Clusterware Installation ......................................................................................................6

Installing the Oracle Database 11g Release 2 (11.2.0.1) on Linux....................................20 Installing RDBMS 11.2.0.1 Database Software............................................................................20

Installing Oracle Examples for Oracle Database 11g Release 2 (11.2.0.1) ......................28 Apply Required One-Off Patches.................................................................................................30

Create ASM Instances and Diskgroups...............................................................................31 Create the Raw File Systems .........................................................................................................31 Create the ASM Instances..............................................................................................................31

Configuring SPFILES on Shared Devices with Raw File Systems ...................................38 Create Database.....................................................................................................................39

Create a Single Instance Database using a Template via the Database Configuration Assistant...........................................................................................................................................39

Prerequisites .................................................................................................................................39 Editing and Defining Datafile Locations ..................................................................................40 Instance Creation .........................................................................................................................40 Install Interactively Using the Database Configuration Assistant........................................40

Create the RMS Tablespaces .........................................................................................................66 Convert Single Instance Database to a RAC ...............................................................................66

Configure a shared spfile............................................................................................................66 Prepare Database for RAC..........................................................................................................67 Prepare Host 2 for the second instance.....................................................................................68 Startup Instance 2.........................................................................................................................69 Configure SRVCTL ......................................................................................................................69 Configure TNSNAMES.ora ........................................................................................................70 Configure LISTENER.ora ...........................................................................................................71

Appendix A – Create the RMS Tablespace..........................................................................73

Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are

subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed

orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be

reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Case Study: Creating a High-Availability RAC Environment for Oracle Retail 13.2

This document describes the case study for creating high-availability RAC Environment for Oracle Retail 13.2.

Installation Overview Oracle Retail applications can be deployed in a grid computing environment, utilizing Oracle Fusion Middleware Active-Active clustering and Oracle Real Application Cluster (RAC) databases to provide high availability and scalability. This configuration allows lower-cost commodity systems to be combined into a single scalable, fault-tolerant computing environment.

There are many options for configuring an Oracle grid computing environment and these options can have a significant impact on the way that the environment is configured and built. The intent of this case study is not to provide exhaustive documentation on all possible ways to configure a suitable grid computing environment for Oracle Retail, but rather to document a specific configuration that was used for verification purposes. As such, the specific installation steps documented in this case study will only apply in their entirety to the exact hardware and software configuration described here.

This Case Study details the steps used to create the high-availability RAC database used for Oracle Retail development:

1. Install Oracle Database RAC environment

a. Install Oracle Cluster Ready Services Software.

b. Install Oracle Database Software.

c. Install Example CD.

d. Create ASM instance and the Diskgroups.

e. Create single-instance database for Oracle Retail products.

f. Convert single-instance database to RAC.

Note: This Case Study uses the hostnames dbserver1 and dbserver2 for the different systems in the db cluster. You should substitute the appropriate names of the hosts for your installation. In some screenshots, you may see the names mspdev53 and mspdev54, which are the equivalent of dbserver1 and dbserver2, respectively.

Oracle Retail 13.2 High-Availability Case Study RAC (Real Application Clusters Environment) 1 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle 11gR2 CRS Installation on Linux x86-64

This section describes the Oracle 11gR2 CRS installation on Linux x86-64.

Node Configuration To configure the node:

1. Verify that the RPMs and System Settings have been set up correctly using the My Oracle Support Note ID 169706.1.

a. Download the Remote Diagnostic Agent (RDA) from My Oracle Support Web site using the links displayed in the My Oracle Support Note ID 314422.1.

b. Extract the RDA on each system of the cluster.

c. Run ./rda.sh –T hcve on each node.

d. Choose the Oracle Database 11g R2 (11.2.0) PreInstall (linux-amd64) option for validation.

e. Enter the Oracle Home path you will be using.

f. Review the output file and resolve any failures that are found:

i. If your version of binutils is newer then 2.15.92.0.2-13.0.0.0.2, RDA may incorrectly claim that you fail verification.

ii. For some packages, both 64-bit and 32-bit RPMs are required, having only one or the other will cause RDA to complain.

iii. Use rpm -qa --qf %{NAME}_%{ARCH}-%{VERSION}-%{RELEASE}\n to list installed RPM names and their architectures (x86-64 or i386).

2. Have your System Administrators configure two gigabit interfaces, one for the public network (for example, eth0), and one for the cluster interconnect (for example, eth1). The virtual IP address should not be assigned to an interface at this point.

3. Have the System Administrators specify the following IP addresses for eth0, and eth1 interfaces for the two cluster nodes. The interconnect IP addresses should be on a separate private subnet that is not registered with DNS. These should be defined in the /etc/hosts file on each node. The public and private interface names must be the same on each node.

Example: dbserver1 (mspdev53) eth0 – ip: 10.141.29.73, netmask: 255.255.252.0 eth1 – ip: 192.168.1.3, netmask: 255.255.255.0 dbserver2 (mspdev54) eth0 – ip: 10.141.29.74, netmask: 255.255.252.0 eth1 – ip: 192.168.1.4, netmask: 255.255.255.0

2 Oracle Retail 13.2 High-Availability Case Study RAC (Real Application Clusters Environment) Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

4. Have the System Administrator request for a SCAN name (Single Client Access Name) that is resolvable to a minimum of 2 IP addresses and can be up to 3 IP addresses in a round robin fashion. The SCAN should be setup in the DNS server, not in the host file. SCAN is the single point of access for all applications connecting to the database and is responsible for failover and load balancing. This is a new Oracle Database 11g Release 2 feature. VIPs are still used internally but the initial connection is made through the SCAN, via the remote_listener. You will be prompted for the name during the installation. Once the SCAN is setup, it can be verified using nslookup and ping.

--> nslookup mspdvcl4 Server: 10.141.28.50 Address: 10.141.28.50#53 Non-authoritative answer: Name: mspdvcl4.us.oracle.com Address: 10.141.30.123 Name: mspdvcl4.us.oracle.com Address: 10.141.30.124 --> ping mspdvcl4.us.oracle.com PING mspdvcl4.us.oracle.com (10.141.30.124) 56(84) bytes of data. 64 bytes from mspdvcl4.us.oracle.com (10.141.30.124): icmp_seq=1 ttl=64 time=1.63 ms 64 bytes from mspdvcl4.us.oracle.com (10.141.30.124): icmp_seq=2 ttl=64 time=0.198 ms --> ping mspdvcl4.us.oracle.com PING mspdvcl4.us.oracle.com (10.141.30.123) 56(84) bytes of data. 64 bytes from mspdvcl4.us.oracle.com (10.141.30.123): icmp_seq=1 ttl=64 time=0.021 ms 64 bytes from mspdvcl4.us.oracle.com (10.141.30.123): icmp_seq=2 ttl=64 time=0.031 ms

5. Have your System Administrators update the /etc/hosts file on the cluster nodes. All virtual IP addresses should be listed in the hosts file.

Example /etc/host file: # # Internet Hosts Table # 127.0.0.1 localhost.localdomain localhost 10.141.29.74 dbserver2 10.141.30.73 dbvip1 10.141.30.74 dbvip2 192.168.1.4 dbserver1p 192.168.1.3 dbserver2p

6. Verify the eth0 interface is connected to the switch and can communicate with the ZFS Storage Appliance. Use the /usr/sbin/ping command to verify connectivity to the ZFS Storage Appliance over the gigabit network from both of the cluster nodes.

Example: $ /usr/sbin/ping sunnas01 Note: run df –k to see what is being used for the mounted filesystems.

7. The other interface, eth1 on dbserver1, should be able to communicate with its counterpart, eth1 on dbserver2. Use the /usr/sbin/ping command to verify the cluster interconnect from both the cluster nodes, using the private names (for example, dbserver1p and dbserver2p).

Oracle Retail 13.2 High-Availability Case Study RAC (Real Application Clusters Environment) 3

Example: $ /usr/sbin/ping dbserver1p $ /usr/sbin/ping dbserver2p

8. Verify network configuration by pinging dbserver1 from dbserver2 and vice versa. Example: ping dbserver1 ping dbserver2

Note: It is not possible to ping the virtual IP’s (dbvip1 and dbvip2) until after the clusterware is installed, up and running.

9. Determine where Oracle software will be installed. Oracle Base (ORACLE_BASE) Oracle CRS Home (ORA_CRS_HOME) Oracle Home (ORACLE_HOME)

This particular installation used the following local directories on each node:

ORACLE_BASE /u00/oracle

ORA_CRS_HOME /u00/crs/oracle/product/11.2.0

ORACLE_HOME /u00/oracle/product/11.2.0.1

Oracle Inventory /u00/oraInventory

Oracle User’s home directory /u00/oracle

Create the directories:

a. Oracle Base mkdir /u00/oracle

b. Oracle CRS Home mkdir –p /u00/crs/oracle/product/11.2.0

c. Oracle Software Home mkdir –p /u00/oracle/product/11.2.0.1

10. Verify the Oracle user and dba group have been created on each host.


11. Verify the following mount options in the /etc/fstab file. Mount the exported file systems from sunnas01, i.e. /u02/ocr1, /u02/ocr2, /u02/arch, /u03, and /u04.

Example /etc/fstab entries: sunnas01:/vol/dbdevgrp/ocr1 /u02/ocr1 nfs hard,nointr,rsize=32768,wsize=32768,tcp,noac,timeo=600 sunnas01:/vol/dbdevgrp/ocr2 /u02/ocr2 nfs hard,nointr,rsize=32768,wsize=32768,tcp,noac,timeo=600 sunnas01:/vol/dbdevgrp/arch /arch nfs hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,timeo=600 sunnas01:/vol/dbdevgrp/u03 /u03 nfs hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,timeo=600 sunnas01:/vol/dbdevgrp/u04 /u04 nfs hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,timeo=600 Where: sunnas01 is the name of the ZFS Storage Appliance. /u02/ocr1, /u02/ocr2, /u03 and /u04 are the mount points on the cluster nodes.

12. Create mount points for the Oracle Cluster Registry (OCR) and Voting Disks as root user on the ZFS Storage Appliance.

# mkdir /u02/ocr1/oracle # mkdir /u02/ocr2/oracle

13. After mounting the OCR and Voting Disk directories, grant ownership and read/write permissions to the Oracle user on those mounted directories.

# chown –R oracle:dba /u02/ocr1/oracle # chmod –R 775 /u02/ocr1/oracle # chown –R oracle:dba /u02/ocr2/oracle # chmod –R 775 /u02/ocr2/oracle

14. Change the ownership of the directories above the CRS installation directory so that root owns them.

# chown root:dba /u00/crs # chown root:dba /u00/crs/oracle # chown root:dba /u00/crs/oracle/product # chown root:dba /u00/crs/oracle/product/11.2.0

15. Configure SSH access between systems. The Oracle Universal Installer uses SSH to copy binaries between RAC hosts during installation. Execute the following steps when logged in directly as oracle.

a. Create private key on dbserver1. $ ssh-keygen –t dsa

i. Accept the default location for the key.

ii. Hit the return key twice when prompted for a passphrase.

b. Create private key on dbserver2. $ ssh-keygen –t dsa

i. Accept the default location for the key.

ii. Hit the return key twice when prompted for a passphrase.


c. Create authorized keys file on dbserver1. $ cd ~/.ssh $ scp dbserver2:/u00/oracle/.ssh/id_dsa.pub id_dsa.pub2 $ cat id_dsa.pub id_dsa.pub2 > authorized_keys

d. Create authorized keys file on dbserver2. $ cd ~/.ssh $ scp dbserver1:/u00/oracle/.ssh/id_dsa.pub id_dsa.pub2 $ cat id_dsa.pub id_dsa.pub2 > authorized_keys

e. Make sure /u00/oracle has permissions of 755 instead of 775.

f. Verify SSH access between systems. None of these commands should prompt for a password. Prompting for addition to a known_hosts file is OK, just accept the prompt.

i. From dbserver1 $ ssh dbserver2 $ ssh dbserver1

ii. From dbserver2

$ ssh dbserver1 $ ssh dbserver2

Oracle Clusterware Installation To install the Oracle Clusterware:

1. Modify the user profile in oracle home on both nodes adding the following parameters: export ORA_CRS_HOME=<CRS_HOME location> export NODE_LIST=<Hostnames in cluster, separated by a comma>

a. Example: export ORA_CRS_HOME=/u00/crs/oracle/product/11.2.0 export NODE_LIST=dbserver1,dbserver2

2. As the oracle UNIX user who will own clusterware installation, navigate to the location where the clusterware media is stored

3. Run clusterware pre-install checks. Any problems identified must be resolved before continuing with clusterware installation.

Navigate into the directory where the CRS software is and run the runcluvfy.sh to perform pre-installation check.

a. Execute the following command to perform post-checks for hardware/operating system setup:

./runcluvfy.sh stage -pre crsinst -n $NODE_LIST

b. Execute the following command to check peer compatibility: ./runcluvfy.sh comp peer –n all –orainv dba –verbose

c. Execute the following command to verify node connectivity: ./runcluvfy.sh comp nodecon -n $NODE_LIST –verbose


d. Execute the following command to check system requirements for CRS: ./runcluvfy.sh comp sys –n $NODE_LIST –p crs –orainv dba –verbose

Note: Investigate and resolve any error messages before continuing.

4. Set DISPLAY to IP address.

a. export DISPLAY=<ip address>:0.0.

5. Setup environment variables.

a. unset LD_LIBRARY_PATH.

b. export ORACLE_HOME=$ORA_CRS_HOME.

6. Execute the installer.

a. ./runInstaller

Note: This will be done only on 1 node. The CRS software will complete the install on the 2nd node in the cluster all by itself.

7. The Select Installation Option window opens.

Click Next.


8. The Select Installation Type window opens.

Select Advanced Installation.

Click Next.

9. The Select Product Languages window opens.

Click >> button to install all languages.


Click Next.

10. The Grid Plug and Play Information window opens.

Ensure the information in the Cluster name, SCAN Name, and SCAN port are correct.

Click Next.


11. The Cluster Node Information Validation window opens.

Once the validation completes, all nodes for this cluster will be detected and displayed. Place the cursor on of the entries and right click to examine the details.

12. The Add Cluster Node Information window opens.

Edit the cluster node detail. Clicking on one of the node entries will display the details and enable editing if necessary.

Click OK.


13. The Specify Network Interface Usage window opens.

a. Ensure that the 10.141 subnet is public. If not, click Edit to modify it.

b. Ensure that the 192.160 subnet is private. If not, click Edit to modify it.

c. For any other interface names, highlight the interface click Edit. Choose Do Not Use as the interface type. Those will always be set to Do Not Use.

Click Next.


14. The Storage Option Information window opens.

Select the storage option.

Click Next.

15. The OCR Storage Option window opens.

Enter the locations of OCR.

Click Next.


16. The Voting Disk Storage Option window opens.

Enter the locations of the voting disks.

Click Next.


17. The Failure Isolation Support window opens.

Select Do not use Intelligent Platform Management Interface if you do not intend to configure it.

Click Next.

18. The Privileged Operating System Groups window opens.

Click Next if the Operating System Groups shown are correct, otherwise click on the down-arrow to choose a different group.


19. The Specify Installation Location window opens.

Enter the paths for ORACLE_BASE and home of CRS.

Click Next.


20. The Perform Prerequisite Checks window opens.

Click Fix & Check Again to generate a fixup script for the Sysadmin to execute and to fix the settings. Alternatively, click on Ignore All to continue.

21. The Summary window opens.

Click Finish to start the installation.


22. The Setup window opens.

The installation begins.

23. The Execute Configuration Scripts window opens.


On each node, navigate to CRS_HOME/bin and run root.sh. It is important not to run root.sh on all nodes at the same time. After the script has been run on each node successfully, check the crs services by running crs_stat: --> crs_stat -t Name Type Target State Host ------------------------------------------------------------ ora....ER.lsnr ora....er.type ONLINE ONLINE mspdev53 ora....N1.lsnr ora....er.type ONLINE ONLINE mspdev54 ora....N2.lsnr ora....er.type ONLINE ONLINE mspdev53 ora.asm ora.asm.type OFFLINE OFFLINE ora.eons ora.eons.type ONLINE ONLINE mspdev53 ora.gsd ora.gsd.type OFFLINE OFFLINE ora....SM1.asm application OFFLINE OFFLINE ora....53.lsnr application ONLINE ONLINE mspdev53 ora....v53.gsd application OFFLINE OFFLINE ora....v53.ons application ONLINE ONLINE mspdev53 ora....v53.vip ora....t1.type ONLINE ONLINE mspdev53 ora....SM2.asm application OFFLINE OFFLINE ora....54.lsnr application ONLINE ONLINE mspdev54 ora....v54.gsd application OFFLINE OFFLINE ora....v54.ons application ONLINE ONLINE mspdev54 ora....v54.vip ora....t1.type ONLINE ONLINE mspdev54 ora....network ora....rk.type ONLINE ONLINE mspdev53 ora.oc4j ora.oc4j.type OFFLINE OFFLINE ora.ons ora.ons.type ONLINE ONLINE mspdev53 ora....ry.acfs ora....fs.type OFFLINE OFFLINE ora.scan1.vip ora....ip.type ONLINE ONLINE mspdev54 ora.scan2.vip ora....ip.type ONLINE ONLINE mspdev53

Verify SCAN configuration using cluvfy on either node: --> cluvfy comp scan -verbose Verifying scan Checking Single Client Access Name (SCAN)... SCAN VIP name Node Running? ListenerName Port Running? ---------------- ------------ ------------ ------------ ------------ ------------ mspdvcl4 mspdev53 true LISTENER 1521 true Checking name resolution setup for mspdvcl4... SCAN Name IP Address Status Comment ------------ ------------------------ ------------------------ ---------- mspdvcl4 10.141.30.124 passed mspdvcl4 10.141.30.123 passed Verification of SCAN VIP and Listener setup passed Verification of scan was successful.


The CRS installation also configures a SCAN listener on each node. It can also be verified:

srvctl config scan_listener SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521 SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1521

Note: If there will be a 10g database on the same RAC, the nodes need to be pinned using the following command, otherwise you will receive ORA-29702 error when trying to start the 10g database. As root, execute:

$ORACLE_HOME/bin/crsctl pin css –n dbserver1 dbserver2


Installing the Oracle Database 11g Release 2 (11.2.0.1) on Linux

This section describes how to install Oracle Database 11g Release 2 (11.2.0.1) software on Linux.

Installing RDBMS 11.2.0.1 Database Software To install RDBMS 11.2.0.1 database software:

1. As the Oracle user, on Dbserver1, change to the directory where the Oracle Database 11.2.0.1 software is located.

2. Set your environment to point to the desired Oracle Database Home.

a. export ORACLE_HOME=/u00/oracle/product/11.2.0.1

b. export ORACLE_BASE=/u00/oracle

3. cd into the software location and start the installer ./runInstaller

The Configure Security Updates window opens.

If you don’t wish to receive security update emails, uncheck the option.

Click Next.


4. An Email Address Not Specified error message may appear.

If you have unchecked the Receive Security Updates checkbox, this screen will appear.

Click Yes to acknowledge and continue.

5. The Select Installation Options window opens.

Select Install database software only.

Click Next.


6. The Node Selection window opens.

If the nodes shown are correct, click Next.

7. The Select Product Languages window opens.

Click >> to install all languages.

Click Next.


8. The Select Database Edition window opens.

Select Enterprise Edition.

Click Select Options.

9. The Choose Components window opens.

Select the components.

The above options have been checked by default.

Click OK to close the window.



Ensure the locations are correct.

Click Next.

11. The Oracle Base Location verification window opens.

If the location of ORACLE_BASE is within the ORACLE user’s UNIX home directory, the Oracle Database 11g Release 2 Installer window opens.

Click the appropriate response.


12. The Privileged Operating System Group window opens.

If dba is the correct group, click Next. Otherwise, select a different group by clicking on the down arrow.

13. The Perform Prerequisite Checks window opens.

Ensure that all the failed pre-requisites have been acknowledged accordingly.

Click Next.


14. The Summary of Installation window opens.


15. The Install Product window opens.

The installation begins.


16. The Execute Configuration Scripts window opens.

After copying the files, the installer will prompt you to run the root.sh script. You can run the script via pseudo like: sudo /u00/oracle/product/11.2.0.1/root.sh on all nodes of the RAC.

Note: It is important to not run root.sh on all nodes simultaneously.

Click OK when the root.sh has been run on both nodes.

17. The Finish window opens.

The installation of RDBMS binary completes on all nodes.


Installing Oracle Examples for Oracle Database 11g Release 2 (11.2.0.1)

This section describes the Oracle Database 11g Release 2 examples: 1. As Oracle, change to the directory where the Oracle Database Companion software is

located.

2. Run the installer. ./runInstaller


If the locations shown are correct, click Next.

4. The Oracle Examples Installer window opens.

Click Yes if Oracle Base shares the same location as Oracle Home.


5. The Summary window—Steps 3 of 5 opens.


6. The Install Product window – Step 4 of 5 opens.

The Installer will extract the files and send them to the remote nodes. This will take a few minutes. Refrain from clicking the Cancel button.


7. When complete, the Finish window opens.

Click Close to exit.

Apply Required One-Off Patches To apply the required one-off patches:

1. Set your environment to point to the database home.

a. export ORACLE_HOME=/u00/oracle/product/11.2.0.1.

2. Change to the directory containing the one-off patches.

3. Apply the following patches using the OPatch utility: 9582272: ORA-600kkdlReadOnDiskDefVal: error occurs when ALTER TRIGGER is executed. 9100882: SOA: ORA-600KGHFRE3 SIGNALLED. 9010222: APPS ST 11G ORA-00600 KKSFBC-REPARSE-INFINITE-LOOP 9932143: CTS 3 FAILURES IN JMS/AQ RUN DIDN'T GET EXPECTED MSG BACK AND REDELIVERED FLAG 9130054: MASSIVE ORA-2051 SIGNALLED DURING SOA TEST AGAINST AN 11.2.0.1 DATABASE. 9367425: PROCESS CRASHED WHEN USING 11GR2 JDBC/OCI. 9495959: HANG WHEN TWO THREADS TRY TO CREATE THE ENV HANDLE AT THE SAME.

Note: Patches 9367425 and 9495959 work together to correct a JDBC issue.

4. Apply any other one-off patches documented in the installation guides for the application you are installing.


Create ASM Instances and Diskgroups This section describes how to create ASM instances and diskgroups.

Create the Raw File Systems To create the raw file systems:

As Oracle, on one of the servers, create the raw partitions that will be used for the ASM diskgroup. dd if=/dev/zero of=/u03/oradata/data1 bs=8192 count=1000000 dd if=/dev/zero of=/u03/oradata/data2 bs=8192 count=1000000 dd if=/dev/zero of=/u04/oradata/data1 bs=8192 count=1000000 dd if=/dev/zero of=/u04/oradata/data2 bs=8192 count=1000000

Create the ASM Instances To create the ASM instances:

Navigate into the home of Oracle Database CRS to start the creation of the ASM instances: export DISPLAY=<ip address:0.0> export ORA_CRS_HOME=<home_of_crs> export TMP=<dir_has_enough_space>/install_temp export TMPDIR=$TMP $ORA_CRS_HOME/bin/asmca


1. The Create ASM window opens.

Enter the passwords for sys and asmsnmp.

Click Specify Disk Group.

2. The Create Disk Group window opens.

Click Change Disk Discovery Path to open the window to start configuring the disk groups.


3. The Change Disk Discovery Path window opens.

Enter the paths of the diskgroups to be discovered.

Click OK. All of the raw partitions on the specified paths will be located.

4. The Create Disk Group window opens.

Enter the diskgroup name.

Assign the disks that should make up the diskgroup.

Click OK to return to the previous screen.


5. The Create ASM Instances window opens.

Click Create ASM to initiate the creation of the first diskgroup and the ASM instance.

6. The ASMNMP Password window opens.

Click the appropriate button to acknowledge the password accordingly.


7. The Create ASM window opens.

The creation of the ASM instance in progress.

8. When complete, the Create ASM window opens.

9. Click OK.


The ASM Configuration Assistant: Configure ASM Diskgroups window opens where additional diskgroup can be created.

Click Create to create additional diskgroups.

10. The Create Disk Groups window opens.

Enter the second diskgroup name and its members.

Click OK.


11. The DiskGroups Creation window opens.

The new diskgroup will be created when complete.

12. When complete, the DiskGroup: Creation window opens.

Click OK to return to the previous screen.

13. The ASM Configuration Assistant: Configure ASM Diskgroups window opens.

The diskgroups created will display.

Click Exit to finish the ASM installation.


Configuring SPFILES on Shared Devices with Raw File Systems

The ASM configuration assistant creates a default spfile. You will create a pfile from the spfile and create an alias for the spfile which resides on the shared device with a raw file system.

1. Create an alias for the default SPFILE created in the device with the raw file system.

With the SID pointing to the ASM instance, find the location of the default SPFILE created by ASM. sqlplus /as sysdba SQL> show parameter spfile NAME TYPE VALUE ------------------- ---------------- ------------------------------------------ spfile string +DATA2/rnd_rac-cluster/asmpara

meterfile/registry.253.719417353

Create an alias for the SPFILE using the ASM command line language: --> asmcmd ASMCMD> mkalias +data2/RND_RAC-cluster/ASMPARAMETERFILE/REGISTRY.253.719417353 spfileasm.ora

Check the alias by issuing ‘ls –l’ while in asmcmd prompt. It should show: spfileasm.ora => +DATA2/RND_RAC-cluster/ASMPARAMETERFILE/REGISTRY.253.719417353 Exit

2. Log on as the sysdba user, and prepare a pfile with the necessary parameters for the instances:

-> create pfile=’/u00/crs/oracle/product/11.2.0/dbs/init$ORACLE_SID.ora’ from spfile’;

Ensure the pfile has values for:

asm_diskgroups=’diskgroup names separated by comma’

asm_disstraing=’disk_string_names separated by comma’

instance_type=’asm’

Rename this file as a backup pfile. -> mv init$ORACLE_SID.ora init$ORACLE_SID.ora.bak

3. Create another PFILE for the instance that contains one line pointing to the SPFILE on the raw device as shown below:

--> cat /u00/crs/oracle/product/11.2.0/dbs/init+ASM1.ora spfile=+DATA2/RND_RAC-cluster/ASMPARAMETERFILE/spfileasm.ora

Note: Instead of pointing to the name REGISTRY.253.719417353, it points to a more readible alias filename.


Log on as a sysasm user, and then restart the first instance to ensure the correct spfile is being used: shutdown immediate startup show parameter diskgroup show paramter instance

4. Repeat the same steps to create spfile for the remaining instances.

Create Database This section assumes the following environment will be used for the RAC database:

Database Name: retaildb

Datafile paths: +data1/*.dbf, +data2 /*.dbf

Archivelog path: /arch/retaildb

Host1 Name: dbserver1

Instance1 Name: retaildb1

Instance1 Undo TS: UNDO_TS01

Host2 Name: dbserver2

Instance2 Name: retaildb2

Instance 2 Undo TS: UNDO_TS02

Create a Single Instance Database using a Template via the Database Configuration Assistant

If a single instance of the Oracle Database 11g Release 2 does not already exist, create one as per the following instructions.

Prerequisites A set of retail database creation template files for 4 supported platforms are included with the 13.2 RMS instllation media. You can find them in the directory rms/dbschema/create_db. Copy the file of your platform into directory $ORACLE_HOME/ assistants/dbca/templates, then unzip and untar it. . gzip –d Retail_DB_Template_13.2_ OS_Platform _Release.tar.gz . tar –xvf Retail_DB_Template_13.2_ OS_Platform _Release.tar


Once the file has been untarred, four files will be extracted: Retail_DB_Template_13.2_OS_Platform_Release.dfb Retail_DB_Template_13.2_ OS_Platform _Release.ctl Retail_DB_Template_13.2_ OS_Platform _Release_variables.txt Retail_DB_Template_13.2_ OS_Platform _Release.dbc

Editing and Defining Datafile Locations When creating a database on regular file system, put the values of the datafile paths in the file Retail_DB_Template_13.2_ OS_Platform _Release_variables.txt. For example, if the datafiles are going to be created in /u02/oradata and /u03/oradata, the following 2 entries should be in the file Retail_DB_Template_13.2_ OS_Platform _Release_variables.txt. ORA_DATA1=/u02/oradata ORA_DATA2=/u03/oradata

However, when creating a database on ASM devices, the locations are defined in the file Retail_DB_Template_13.2_OS_Platform_Release.dbc instead. Replace the occurrence of ORA_DATA1 and ORA_DATA2 with +DATA1 and +DATA2 in this file, or the equivalent disksgroup names.

Instance Creation Log into UNIX server as the oracle user or whichever account that owns the Oracle Database software at your site.

Install Interactively Using the Database Configuration Assistant To install interactively using DBCA:

Launch the Database Configuration Assistant using the following commands: $> cd $ORACLE_HOME/bin $> . export DISPLAY=<set DISPLAY> $>./dbca


The Database Configuration Assistant Welcome window opens.

Select the Oracle single instance database.

Click Next.


The Operations window opens.

Select the Create a Database option.

Click Next.


The Database Templates window opens.

Select the Retail DB Tebmplate 13.2 Linux x86_64 Release option.

Click Next.


The Database Identification window opens.

Enter the new database name, the SID in Global Database Name, and SID fields.

Click Next.


The Management Options window opens.

Clear Configure Enterprise Manager.

Click Next.


The Database Credentials window opens.

Determine to either use the same passwords for both the SYS and the SYSTEM accounts or not. Enter the passwords for both accounts accordingly.

Click Next.


The Database File Location window opens.

Select Automatic Storage Management (ASM).

Select Use Database File Locations from Templates to ensure the correct template file is used.


The Remote Desktop window opens.

A window prompting for the ASMMNP password will open.

Enter a password.

Click OK to exit.

Click File Location Variables.


The File Locations Variables window opens.

Validate the values of ORACLE_BASE, ORACLE_HOME, DB_NAME, DB_UNIQUE_NAME, and SID are set correctly.

Click OK to exit this screen.

Click Next.


The Recovery Configuration window opens.

If you use a flash recovery area, select Specify Flash Recovery Area.

Enter values in Flash Recovery Area.

Enter values in Flash Recovery Area Size.

Select Enable Archiving if the database is going to be in archived mode.

Click Next.


The Database Content window opens.

If there are any scripts to run during the database creation process, select Run the following scripts and enter the names of the scripts. If no script is to be run, check No scripts to run.

Click Next.


The Initialization Parameters window opens.

If the setting of Typical is acceptable, select the option. If not, select the Custom option and adjust the values in the SGA Size and PGA Size accordingly.


Select the Sizing tab.

Validate that Processes is set as desired.


Select the Character Sets tab.

Select Choose from the list of character sets.

Clear Show recommended character sets only to expand the list of available character sets, and then enter UTF8 to open that option.


Select UTF8 to accept that option.


Verify that UTF8 is shown as the chosen character set.


Select the Connection Mode tab.

Select the Dedicated Server Mode option.

Click Next.


The Database Storage window opens.

Validate each branch in the Storage option.


Expand the Datafile option.


If you wish to change the directory paths, select the File Directory field and change +DATA1 to +DATA2.

Validate the Redo Log Groups branch by selecting on each one. Change the File Directory path, if necessary.

Click Next.


The Creation Options window opens.

Select Create Database.

Select Generate Database Creation Scripts.

Click Finish.


The Confirmation window opens.

The create database summary is shown, displaying all settings for the instance about to be created.

Validate the values one last time.

Click OK.


The Database Configuration Assistant window opens.

Click OK.

The database creation script runs.

A progress window opens.


When complete, the database creation complete window opens.

Click Password Management.


The Password Management window opens.

Set the passwords and unlock accounts selectively.

Click OK.


The completion window opens.

Click Exit to exit DBCA.

Create the RMS Tablespaces Continue the database creation process by creating the RMS tablespaces as per Appendix A.

Convert Single Instance Database to a RAC To convert single instance database to RAC:

Configure a shared spfile To configure a shared spfile:

1. Create a temporary pfile in the multi-instance format for editing.

Execute these commands using sqlplus against instance 1: create spfile='/tmp/spfileretaildb.ora' from pfile; create pfile='/tmp/initretaildb.ora' from spfile='/tmp/spfileretaildb.ora';

2. Edit the temporary pfile and change parameters for instance 1.

Change these parameters: *.instance_name='retaildb1' *.audit_file_dest='/u00/oracle/admin/retaildb1/adump' *.local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))' *. log_archive_dest_1=’/u00/oracle/admin/retaildb/arch’ *.undo_tablespace='undo_ts01'


To these values: retaildb1.audit_file_dest='/u00/oracle/admin/retaildb1/adump' retaildb1.instance_name='retaildb1' retaildb1.local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbvip1)(PORT=1521)))' retaildb1.log_archive_dest_1=’/u00/oracle/admin/retaildb/arch’ retaildb1.undo_tablespace='undo_ts01'

3. Edit the temporary pfile and add new parameters for instance 2.

Add these parameters: *.cluster_database=TRUE *.cluster_database_instances=2 *.remote_listener= mspdvcl4.us.oracle.com:1521 # SCAN name retaildb1.instance_number=1 retaildb2.instance_number=2 retaildb2.local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbvip2)(PORT=1521)))' retaildb2.undo_tablespace='undo_ts02' retaildb2.audit_file_dest='/u00/oracle/admin/retaildb2/adump' retaildb2.instance_name='retaildb2'

4. Create the spfile on the shared device.

Execute these commands using sqlplus against instance 1: create spfile='+data2/retaildb/spfile.ora' from pfile='/tmp/initretaildb.ora';

5. Create a pfile on dbserver1 that points to the spfile on the shared device.

First backup the pfile: mv initretaildb1.ora initretaildb1.ora.orig

Create another pfile initretaildb1.ora with only the following one line pointing to the spfile on the ASM disk. spfile=’+data2/retaildb/spfile.ora’

Prepare Database for RAC To prepare the database for RAC:

1. Restart instance 1 and ensure parameters changed above are in effect.

Execute the following commands from sqlplus against instance 1: shutdown immediate startup show parameter cluster show parameter instance show parameter undo


2. Add and enable a second thread of redo.

Execute the following command from sqlplus against instance 1: alter database add logfile thread 2 group 4 ('+data1/retaildb/redo04a.log', '+data2/retaildb/redo04b.log') size 100M, group 5 ('+data1/retaildb/redo05a.log', '+data2/retaildb/redo05b.log') size 100M, group 6 ('+data1/retaildb/redo06a.log', '+data2/retaildb/redo06b.log') size 100M; alter database enable public thread 2;

3. Create a second undo tablespace.

Execute the following command from sqlplus against instance 1: create undo tablespace undo_ts02 datafile '+data2/retaildb/undo_ts0201.dbf' size 500M;

Prepare Host 2 for the second instance To prepare Host 2 for the second instance:

1. Add Instance 2 to the oratab on dbserver2. retaildb2:/u00/oracle/product/11.2.0.1:Y

2. Create an $ORACLE_BASE/admin structure for Instance 2

Execute the following commands as ‘oracle’ on host 2: mkdir –p $ORACLE_BASE/admin/retaildb2/adump

Note: Instance 1 should be switched to a similar arch link, if it doesn’t already use one.

ln –s /arch/retaildb $ORACLE_BASE/admin/retaildb2/arch

3. Create a pfile as the Oracle user, that points to the spfile on the shared device on dbserver2.

Create the pfile initretaildb2.ora that contains the one line below: spfile=’+data2/retaildb/spfile.ora’


Startup Instance 2 To startup instance 2:

1. Start up instance 2 and ensure parameters are in effect.

Execute the following commands from sqlplus against instance 2: startup show parameter cluster show parameter instance show parameter undo

2. Verify v$active_instances shows both instances.

Execute the following query in sqlplus against each instance: select * from v$active_instances;

Configure SRVCTL To configure SRVCTL:

1. Add the database and both instances to the srvctl registry.

Execute the following commands as ‘oracle’ on either host: srvctl add database -d retaildb -o /u00/oracle/product/11.2.0.1 srvctl add instance -d retaildb -i retaildb1 -n dbserver1 srvctl add instance -d retaildb -i retaildb2 -n dbserver2

2. Verify the database have been added as CRS resources.

Execute the following command as ‘oracle’ on either host: export ORA_CRS_HOME=/u00/crs/oracle/product/11.2.0 $ORA_CRS_HOME/bin/crs_stat ora.retaildb.retaildb1.inst .crs_stat should show output similar to this: NAME=ora.retaildb.retaildb1.inst TYPE=application TARGET=ONLINE STATE=ONLINE on dbserver1

If the output doesn’t state that the target & state are online, then shutdown the instance manually, and restart the database using srvctl: Example: srvctl start database –d retaildb

If after the restart all targets aren’t online, wait a minute. Sometimes it takes a couple of minutes for the target to reflect it is online status.


Configure TNSNAMES.ora To configure TNSNAMES.ora:

1. The following example tnsnames entries can be used to connect to the RAC database (load-balanced across both instances).

retaildb = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = scan.domain)(PORT = 1521)) ) (CONNECT_DATA =(SERVICE_NAME = retaildb)) )

2. The following example tnsnames entries can be used to connect to a specific instance. retaildb1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = scan.domain)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = retaildb) (INSTANCE_NAME=retaildb1) ) ) retaildb2 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = scan.domain)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = retaildb) (INSTANCE_NAME=retaildb2) ) )


Configure LISTENER.ora To configure LISTENER.ora:

For Oracle Database 11g Release 2, there are two listener files: listener.ora and endpoints_listener.ora. They are located in $ORA_CRS_HOME/network/admin.

1. The following example entries are setup in the listener.ora file of one node. LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN2)))) # line added by Agent SID_LIST_LISTENER= (SID_LIST = (SID_DESC = (PROGRAM = extproc) (SID_NAME = extproc_agent_1521) (ENVS='EXTPROC_DLLS=ANY') ) ) LISTENER= (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = dbvip1)(PORT = 1521)(IP = FIRST)) (ADDRESS = (PROTOCOL = TCP)(HOST = dbserver1)(PORT = 1521)(IP = FIRST)) (ADDRESS = (PROTOCOL = IPC)(KEY = extproc_key_1521))) ) ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON # line added by Agent

2. The following example shows the setup in the endpoints_listener.ora file of one node. The file is created during CRS installation.

LISTENER_dbserver1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= dbvip1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST= dbserver1_IP)(PORT=1521)(IP=FIRST)))) # line added by Agent


Appendix A – Create the RMS Tablespace This section lists the contents of the create_rms_tablespaces.sql SQL script file that enables you to create the RMS Tablespace. ------------------------------------------------------------------------------------- --- Script: create_rms_tablespaces.sql --- Execute as: sysdba --- Note: Before running this script: --- Modify <datafile_path> values. --- Modify datafile storage parameters and sizes based on partitioning strategy. ---------------------------------------------------------------------------------- spool create_rms_tablespaces.log CREATE TABLESPACE RETEK_INDEX DATAFILE '<datafile_path>/retek_index01.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ; CREATE TABLESPACE RETEK_DATA DATAFILE '<datafile_path>/retek_data01.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ; CREATE TABLESPACE LOB_DATA DATAFILE '<datafile_path>/lob_data01.dbf' SIZE 50M AUTOEXTEND ON NEXT 100M MAXSIZE 2000M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ; CREATE TABLESPACE USERS DATAFILE '<datafile_path>/users01.dbf' SIZE 100M AUTOEXTEND ON NEXT 100M MAXSIZE 2000M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ; ALTER TABLESPACE RETEK_INDEX ADD DATAFILE '<datafile_path>/retek_index02.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; ALTER TABLESPACE RETEK_INDEX ADD DATAFILE '<datafile_path>/retek_index03.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; ALTER TABLESPACE RETEK_INDEX ADD DATAFILE '<datafile_path>/retek_index04.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; ALTER TABLESPACE RETEK_INDEX ADD DATAFILE '<datafile_path>/retek_index05.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; ALTER TABLESPACE RETEK_INDEX ADD DATAFILE '<datafile_path>/retek_index06.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ;

Oracle Retail 13.2 High-Availability Case Study RAC (Real Application Clusters Environment) 73 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

ALTER TABLESPACE RETEK_DATA ADD DATAFILE '<datafile_path>/retek_data02.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; ALTER TABLESPACE RETEK_DATA ADD DATAFILE '<datafile_path>/retek_data03.dbf' SIZE 500M AUTOEXTEND ON NEXT 500M MAXSIZE 2000M ; spool off exit


Author: Tiffany Szeto Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright © 2011, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

132 high availability case study rac

Documents

2 osplatform

2 osplatform

flash recovery

prior written

zfs storage

500m maxsize

icmpseq2 ttl64

asm configuration