Learn how to set up and configure an Oracle rac 10




Download 0.57 Mb.
NameLearn how to set up and configure an Oracle rac 10
page6/9
A typeDocumentation
manual-guide.com > manual > Documentation
1   2   3   4   5   6   7   8   9

The last task in this section it to create the ASM Disks. Creating the ASM disks only needs to be done on one node as the root user account. I will be running these commands on linux1. On the other nodes, you will need to perform a scandisk to recognize the new volumes. When that is complete, you should then run the oracleasm listdisks command on all nodes to verify that all ASM disks were created and available.

$ su -

# /etc/init.d/oracleasm createdisk VOL1 /dev/sda2

Marking disk "/dev/sda2" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL2 /dev/sda3

Marking disk "/dev/sda3" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL3 /dev/sda4

Marking disk "/dev/sda4" as an ASM disk [ OK ]

Note: If you are repeating this guide using the same hardware (actually, the same shared drive), you may get a failure when attempting to create the ASM disks. If you do receive a failure, try listing all ASM disks using:

# /etc/init.d/oracleasm listdisks

VOL1

VOL2

VOL3

As you can see, the results show that I have three volumes already defined. If you have the three volumes already defined from a previous run, go ahead and remove them using the following commands and then creating them again using the above (oracleasm createdisk) commands:

# /etc/init.d/oracleasm deletedisk VOL1

Removing ASM disk "VOL1" [ OK ]

# /etc/init.d/oracleasm deletedisk VOL2

Removing ASM disk "VOL2" [ OK ]

# /etc/init.d/oracleasm deletedisk VOL3

Removing ASM disk "VOL3" [ OK ]

On all other nodes in the cluster, you must perform a scandisk to recognize the new volumes:

# /etc/init.d/oracleasm scandisks

Scanning system for ASM disks [ OK ]

We can now test that the ASM disks were successfully created by using the following command on all nodes as the root user account:

# /etc/init.d/oracleasm listdisks

VOL1

VOL2

VOL3

18. Download Oracle RAC 10g Software

The following download procedures only need to be performed on one node in the cluster!

The next logical step is to install Oracle CRS (10.1.0.3.0) and the Oracle Database 10g (10.1.0.3.0) software. However, we must first download and extract the required Oracle software packages from OTN.

We will be downloading and extracting the required software from Oracle to only one of the Linux nodes in the cluster—namely, linux1. We will perform all installs from this machine. The Oracle installer will copy the required software packages to all other nodes in the RAC configuration we set up in Section 13.

Login to one of the nodes in the Linux RAC cluster as the oracle user account. In this example, we will be downloading the required Oracle software to linux1 and saving them to /u01/app/oracle/orainstall/crs and /u01/app/oracle/orainstall/db.

Downloading and Extracting the Software

First, download the Oracle Database 10g (10.1.0.3 or later) and Oracle CRS (10.1.0.3 or later) software for Linux x86. Both downloads are available from the same page.

As the oracle user account, extract the two packages you downloaded to a temporary directory. In this example, we will use /u01/app/oracle/orainstall/crs and /u01/app/oracle/orainstall/db.

Extract the CRS package as follows:

# su - oracle

$ cd ~oracle/orainstall/crs

$ gunzip ship.crs.lnx32.cpio.gz

$ cpio -idmv < ship.crs.lnx32.cpio

Then extract the Oracle Database Software:

$ cd ~oracle/orainstall/db

$ gunzip ship.db.lnx32.cpio.gz

$ cpio -idmv < ship.db.lnx32.cpio
19. Install Oracle Cluster Ready Services Software

Perform the following installation procedures on only one node in the cluster! The Oracle CRS software will be installed to all other nodes in the cluster by the Oracle Universal Installer.

We are ready to install the "cluster" part of the environment: the CRS software. In the last section, we downloaded and extracted the install files for CRS to linux1 in the directory /u01/app/oracle/orainstall/crs/Disk1. This is the only node we need to perform the install from.

During the installation of CRS, you will be asked for the nodes involved and to configure in the RAC cluster. When the actual installation starts, it will copy the required software to all nodes using the remote access we configured in Section 13.

So, what exactly is the Oracle CRS responsible for?

The Oracle CRS contains all the cluster and database configuration metadata along with several system management features for RAC. It allows the DBA to register and invite an Oracle instance (or instances) to the cluster. During normal operation, CRS will send messages (via a special ping operation) to all nodes configured in the cluster—often called the "heartbeat." If the heartbeat fails for any of the nodes, it checks with the CRS configuration files (on the shared disk) to distinguish between a real node failure and a network failure.

After installing CRS, the Oracle Universal Installer (OUI) used to install the Oracle Database 10g software (next section) will automatically recognize these nodes. Like the CRS install we will be performing in this section, the Oracle 10g database software only needs to be run from one node. The OUI will copy the software packages to all nodes configured in the RAC cluster.

The excellent Metalink Note "CRS and 10g Real Application Clusters - (Note: 259301.1)" provides some key facts about CRS and Oracle RAC 10g to consider before installing both software components:

  • CRS must be installed and running prior to installing RAC 10g.

  • CRS can either run on top of the vendor clusterware (such as Sun Cluster, HP Serviceguard, IBM HACMP, TruCluster, Veritas Cluster, Fujitsu Primecluster, etc.) or without it. (Vendor clusterware was required in Oracle9i RAC.)

  • The CRS HOME and ORACLE_HOME must be installed in different locations.

  • Shared Location(s) or devices for the Voting File and Oracle Configuration Repository (OCR) file must be available prior to installing CRS. The voting file should be at least 20MB and the OCR file should be at least 100MB.

  • CRS and RAC require that the following network interfaces be configured prior to installing CRS or RAC:

    • Public Interface

    • Private Interface

    • Virtual (Public) Interface

    • For more information on this, see Note 264847.1

  • The root.sh script at the end of the CRS installation starts the CRS stack. If your CRS stack does not start, see Note: 240001.1.

  • Only one set of CRS daemons can be running per RAC node.

  • On Unix, the CRS stack is run from entries in /etc/inittab with "respawn".

  • If there is a network split (nodes loose communication with each other), one or more nodes may reboot automatically to prevent data corruption.

  • The supported method to start CRS is booting the machine.

  • The supported method to stop is shutting down the machine or using init.crs stop.

  • Killing CRS daemons is not supported unless you are removing the CRS installation via Note: 239998.1 because flag files can become mismatched.

  • For maintenance, go to single user mode at the OS.

  • When the stack is started, you should be able to see all of the daemon processes with a ps -ef command:

  • $ ps -ef | grep crs

  • root 4661 1 0 14:18 ? 00:00:00 /bin/su -l oracle -c exec /u01/app/oracle/product/10.1.0/crs_1/bin/evmd

  • root 4664 1 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/crsd.bin

  • root 4862 4663 0 14:18 ? 00:00:00 /bin/su -l oracle -c /u01/app/oracle/product/10.1.0/crs_1/bin/ocssd || exit 137

  • oracle 4864 4862 0 14:18 ? 00:00:00 -bash -c /u01/app/oracle/product/10.1.0/crs_1/bin/ocssd || exit 137

  • oracle 4898 4864 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/ocssd.bin

  • oracle 4901 4661 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin

  • root 4908 4664 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/crsd.bin -1

  • oracle 4947 4901 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin



  • oracle 4949 4898 0 14:18 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/ocssd.bin

  • ...

  • oracle 4958 4949 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/ocssd.bin



  • oracle 4959 4947 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin

  • ...

  • oracle 4983 4947 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin



  • oracle 4984 4983 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmlogger.bin \

  • -o /u01/app/oracle/product/10.1.0/crs_1/evm/log/evmlogger.info \

  • -l /u01/app/oracle/product/10.1.0/crs_1/evm/log/evmlogger.log



  • oracle 4985 4947 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin

  • ...

oracle 4990 4947 0 14:19 ? 00:00:00 /u01/app/oracle/product/10.1.0/crs_1/bin/evmd.bin

CRS Shared Files

The two shared files used by CRS will be stored on the OCFS we created earlier. The two shared CRS files are:

  • Oracle Cluster Registry (OCR)

    • Location: /u02/oradata/orcl/OCRFile

    • Size: ~ 100MB

  • CRS Voting Disk

    • Location: /u02/oradata/orcl/CSSFile

    • Size: ~ 20MB

Note: For our installation here, it is not possible to use ASM for the two CRS files, OCR or CRS Voting Disk. These files need to be in place and accessible before any Oracle instances can be started. For ASM to be available, the ASM instance would need to be run first. However, the two shared files could be stored on the OCFS, shared raw devices, or another vendor's clustered filesystem.

Verifying Environment Variables

Before starting the OUI, you should first run the xhost command as root from the console to allow X Server connections. Then unset the ORACLE_HOME variable and verify that each of the nodes in the RAC cluster defines a unique ORACLE_SID. We also should verify that we are logged in as the oracle user account:

Login as oracle

# xhost +

access control disabled, clients can connect from any host
# su - oracle

Unset ORACLE_HOME

$ unset ORA_CRS_HOME

$ unset ORACLE_HOME

$ unset ORA_NLS33

$ unset TNS_ADMIN

Verify Environment Variables on linux1

$ env | grep ORA

ORACLE_SID=orcl1

ORACLE_BASE=/u01/app/oracle

ORACLE_TERM=xterm

Verify Environment Variables on linux2

$ env | grep ORA

ORACLE_SID=orcl2

ORACLE_BASE=/u01/app/oracle

ORACLE_TERM=xterm

Installing Cluster Ready Services

Perform following tasks to install the Oracle CRS:

$ cd ~oracle

$ ./orainstall/crs/Disk1/runInstaller -ignoreSysPrereqs

Screen Name

Response

Welcome Screen

Click Next

Specify Inventory directory and credentials

Accept the default values:
   Inventory directory: /u01/app/oracle/oraInventory
   Operating System group name: dba

Root Script Window - Run orainstRoot.sh

Open a new console window on the node you are performing the install on as the "root" user account.

Navigate to the /u01/app/oracle/oraInventory directory and run orainstRoot.sh.

Go back to the OUI and acknowledge the dialog window.

Specify File Locations

Leave the default value for the Source directory. Set the destination for the ORACLE_HOME name and location as follows:
   Name: OraCrs10g_home1
   Location: /u01/app/oracle/product/10.1.0/crs_1

Language Selection

I accepted the default value:
   Selected Languages: English

Cluster Configuration

Cluster Name: crs
Public Node Name: linux1   Private Node Name: int-linux1
Public Node Name: linux2   Private Node Name: int-linux2

Specify Network Interface Usage

Interface Name: eth0   Subnet: 192.168.1.0   Interface Type: Public
Interface Name: eth1   Subnet: 192.168.2.0   Interface Type: Private

Oracle Cluster Registry

Specify OCR Location: /u02/oradata/orcl/OCRFile

Voting Disk

Enter voting disk file name: /u02/oradata/orcl/CSSFile

Root Script Window - Run orainstRoot.sh

Open a new console window on each node in the RAC cluster as the "root" user account.

Navigate to the /u01/app/oracle/oraInventory directory and run orainstRoot.sh on all nodes in the RAC cluster.

Go back to the OUI and acknowledge the dialog window.

Summary

For some reason, the OUI fails to create a "$ORACLE_HOME/log" for the installation directory before starting the installation. You should manually create this directory before clicking the "Install" button.

For this installation, manually create the file /u01/app/oracle/product/10.1.0/crs_1/log on all nodes in the cluster. The OUI will log all errors to a log file in this directory only if it exists.

Click Install to start the installation!

Root Script Window - Run root.sh

After the installation has completed, you will be prompted to run the root.sh script.

Open a new console window on each node in the RAC cluster as the "root" user account.

Navigate to the /u01/app/oracle/product/10.1.0/crs_1 directory and run root.sh on all nodes in the RAC cluster one at a time.

You will receive several warnings while running the root.sh script on all nodes. These warnings can be safely ignored.

The root.sh may take awhile to run. When running the root.sh on the last node, the output should look like:

...

CSS is active on these nodes.

linux1

linux2

CSS is active on all nodes.

Oracle CRS stack installed and running under init(1M)

Go back to the OUI and acknowledge the dialog window.

End of installation

At the end of the installation, exit from the OUI.
1   2   3   4   5   6   7   8   9

Related:

Learn how to set up and configure an Oracle rac 10 iconSet call options When you first sign in to Lync, you’ll be guided...

Learn how to set up and configure an Oracle rac 10 iconObjectives In this episode you will: Learn about adverbs of frequency....

Learn how to set up and configure an Oracle rac 10 iconPartners in 17 Categories Recognized at Oracle OpenWorld for Excellence...

Learn how to set up and configure an Oracle rac 10 iconFull life cycle development, implementation and support with expertise...

Learn how to set up and configure an Oracle rac 10 iconIdc white Paper sponsored by Oracle Corporation, "Oracle e-business...

Learn how to set up and configure an Oracle rac 10 iconOracle® e-business Suite, Siebel crm, PeopleSoft Enterprise and jd...

Learn how to set up and configure an Oracle rac 10 iconPhp version: 17 set foreign key checks=0; set sql mode="no auto value...

Learn how to set up and configure an Oracle rac 10 iconThe student will learn about reading instruction from birth to secondary...

Learn how to set up and configure an Oracle rac 10 iconDG102sh console Command Set(set coding, set h323, and show)

Learn how to set up and configure an Oracle rac 10 iconResearch into an Intermediate Accounting level practice set was conducted....

Learn how to set up and configure an Oracle rac 10 iconAbstract This integration is a part of Siebel Integrations between...

Learn how to set up and configure an Oracle rac 10 iconTo set up the fw-1884 in Cubase or Nuendo 3 To set up the fw-1884 in Mackie Emulation protocol 3

Learn how to set up and configure an Oracle rac 10 iconDownload and installation: Configure the initial scan

Learn how to set up and configure an Oracle rac 10 iconHow to configure timeGuardian/QuickBooks for direct integration

Learn how to set up and configure an Oracle rac 10 iconConfigure the cics environment for the Debug Tool

Learn how to set up and configure an Oracle rac 10 iconPart 2: Configure ssh access to the Switches

Learn how to set up and configure an Oracle rac 10 iconOracle® SuperCluster T5-8

Learn how to set up and configure an Oracle rac 10 iconOracle® SuperCluster M6-32

Learn how to set up and configure an Oracle rac 10 iconMacBook-Pro-de-Martin-Ortuno: libusb 9 martinortuno$./configure

Learn how to set up and configure an Oracle rac 10 iconLearning to drive -how do you want to learn?




manual




When copying material provide a link © 2017
contacts
manual-guide.com
search