Problems and workarounds for installing Oracle_rac

Source: Internet
Author: User

While running:

/u01/app/oracle/product/10.2.0/db_1/root.sh

Checking to see if the Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting Up NS Directories
Prot-1:failedtoinitializeocrconfig
Failedto upgrade Oracle Cluster Registry configuration

DD If=/dev/zero f=/dev/rdsk/v1064_vote_01_20m.dbf bs=8192 count=2560
DD If=/dev/zero F=/dev/rdsk/ocrv1064_100m.ora bs=8192 count=12800

Workaround 1
Failedto upgrade Oracle Cluster Registry configuration
When CRS is installed, when the second node executes the./root.sh, the following prompt appears, and I perform normally on the first node. Please give some advice on prawns, thank you!
[Email protected] crs]#./root.sh
Warning:directory '/app/oracle/product/10.2.0 ' isn't owned by root
Warning:directory '/app/oracle/product ' isn't owned by root
Warning:directory '/app/oracle ' isn't owned by root
Warning:directory '/app ' isn't owned by root
Checking to see if the Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting Up NS Directories
Prot-1:failedtoinitializeocrconfig
Failedto upgrade Oracle Cluster Registry configuration
Cause of Error:
Because of the problem of installing CRS device permissions, such as my device using raw to place OCR and vote, to set up these hardware devices and the permissions of the attached files, here is my environment:
[Email protected] oracrs]#
lrwxrwxrwx 1 root root 12:49 Ocr.crs-/dev/raw/raw1
lrwxrwxrwx 1 root root 13:31 Vote.crs-/dev/raw/raw2
Chown ROOT:OINSTALL/DEV/RAW/RAW1
Chown ROOT:OINSTALL/DEV/RAW/RAW2
chmod 660/DEV/RAW/RAW1
chmod 660/DEV/RAW/RAW2
Where/DEV/SDB1 placed Ocr,/dev/sdb2 place vote.
[Email protected] oracrs]# service rawdevices Reload
Assigning devices:
/DEV/RAW/RAW1-/DEV/SDB1
/dev/raw/raw1:bound to Major 8, minor 17
/DEV/RAW/RAW2-/DEV/SDB2
/dev/raw/raw2:bound to Major 8, minor 18
Done
Then the execution is OK again.
[Email protected] oracrs]#/oracle/app/oracle/product/crs/root.sh
Warning:directory '/oracle/app/oracle/product ' isn't owned by root
Warning:directory '/oracle/app/oracle ' isn't owned by root
Checking to see if the Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting Up NS Directories
Oracle Cluster Registry Configuration upgraded successfully
Warning:directory '/oracle/app/oracle/product ' isn't owned by root
Warning:directory '/oracle/app/oracle ' isn't owned by root
Clscfg:existing configuration version 3 detected.
Clscfg:version 3 is 10G Release 2.
Assigning default hostname Rac1 for node 1.
Assigning default hostname RAC2 for node 2.
Successfully accumulated necessary OCR keys.
Using ports:css=49895 crs=49896 evmc=49898 and evmr=49897.
Node <nodenumber>: <nodename> <private interconnect name> Node 1:rac1 priv1 Rac1
Node 2:rac2 priv2 RAC2
Clscfg:arguments Check out successfully.

Oracle gave me a patch that allowed us to format the OCR and voting disk. Now the problem may just is I need to run root.sh on Node1 or wipe both clean and start fresh.
Devices formatted, now we need to get the CRS daemon up and running on both nodes.
[[email protected] ~]# dd If=/dev/zero f=/dev/raw/raw2 bs=1048576 count=1000
1000+0 Records in
1000+0 Records out
[Email protected] ~]#/orahome/app/oracle/product/10.1.2.0.2/crs/root.sh
Warning:directory '/orahome/app/oracle/product/10.1.2.0.2 ' isn't owned by root
Warning:directory '/orahome/app/oracle/product ' isn't owned by root
Warning:directory '/orahome/app/oracle ' isn't owned by root
Warning:directory '/orahome/app ' isn't owned by root
Checking to see if the Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting Up NS Directories
Oracle Cluster Registry Configuration upgraded successfully
Warning:directory '/orahome/app/oracle/product/10.1.2.0.2 ' isn't owned by root
Warning:directory '/orahome/app/oracle/product ' isn't owned by root
Warning:directory '/orahome/app/oracle ' isn't owned by root
Warning:directory '/orahome/app ' isn't owned by root
Successfully accumulated necessary OCR keys.
Using ports:css=49895 crs=49896 evmc=49898 and evmr=49897.
Node <nodenumber>: <nodename> <private interconnect name> Node 1:DR2DB2 dr2db2-eth2 dr2db2
Node 2:DR2DB1 dr2db1-eth2 dr2db1
Creating OCR keys for user ' root ', privgrp ' root '.
Operation successful.
Now formatting voting device:/DEV/RAW/RAW6
Format of 1 voting devices complete.
Startup'll is queued to init within seconds.
Adding daemons to Inittab
Expecting the CRS daemons to being up within-seconds.
CSS is active on these nodes.
Dr2db2
CSS is inactive on these nodes.
Dr2db1
Local node checking complete.
Run root.sh on remaining nodes to start CRS daemons.
[Email protected] ~]# Ps-ef | grep ora
Root 6572 2526 0 13:39? 00:00:00 sshd:oracle [Priv]
Oracle 6574 6572 0 13:39? 00:00:00 sshd: [Email PROTECTED]/1
Oracle 6575 6574 0 13:39 pts/1 00:00:00-bash
Root 14172 2526 0 17:54? 00:00:00 sshd:oracle [Priv]
Oracle 14176 14172 0 17:55? 00:00:00 sshd: [Email PROTECTED]/2
Oracle 14177 14176 0 17:55 pts/2 00:00:00-bash
Root 14682 1 0 17:57? 00:00:00/bin/su-l oracle-c sh-c ' Ulimit-c Unlimited; CD/ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/LOG/DR2DB2/EVMD; EXEC/ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/BIN/EVMD '
Root 14686 1 0 17:57? 00:00:00/orahome/app/oracle/product/10.1.2.0.2/crs/bin/crsd.bin reboot
Oracle 14959 14682 0 17:58? 00:00:00/orahome/app/oracle/product/10.1.2.0.2/crs/bin/evmd.bin
Root 15018 14942 0 17:58? 00:00:00/bin/su-l oracle-c/bin/sh-c ' Ulimit-c Unlimited; CD/ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/LOG/DR2DB2/CSSD; /ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/BIN/OCSSD | | Exit $? '
Oracle 15021 15018 0 17:58? 00:00:00/bin/sh-c Ulimit-c Unlimited; CD/ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/LOG/DR2DB2/CSSD; /ORAHOME/APP/ORACLE/PRODUCT/10.1.2.0.2/CRS/BIN/OCSSD | | Exit $?
Oracle 15057 15021 0 17:58? 00:00:00/orahome/app/oracle/product/10.1.2.0.2/crs/bin/ocssd.bin
Root 15996 14206 0 17:59 pts/2 00:00:00 grep ora
Crs_setperm crs_setperm.bin crs_start crs_start.bin crs_stat crs_stat.bin crs_stop crs_stop.bin
[Email protected] ~]#/orahome/app/oracle/product/10.1.2.0.2/crs/bin/crs_stat-t
Crs-0184:cannot communicate with the CRS daemon.
On next node
[Email protected] ~]#/orahome/app/oracle/product/10.1.2.0.2/crs/root.sh
Warning:directory '/orahome/app/oracle/product/10.1.2.0.2 ' isn't owned by root
Warning:directory '/orahome/app/oracle/product ' isn't owned by root
Warning:directory '/orahome/app/oracle ' isn't owned by root
Warning:directory '/orahome/app ' isn't owned by root
Checking to see if the Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting Up NS Directories
Oracle Cluster Registry Configuration upgraded successfully
Warning:directory '/orahome/app/oracle/product/10.1.2.0.2 ' isn't owned by root
Warning:directory '/orahome/app/oracle/product ' isn't owned by root
Warning:directory '/orahome/app/oracle ' isn't owned by root
Warning:directory '/orahome/app ' isn't owned by root
/orahome/app/oracle/product/10.1.2.0.2/crs/bin/crsctl.bin:error while loading shared libraries:libstdc++.so.5: Cannot open shared object File:no such file or directory
Failure Initializing entries in/etc/oracle/scls_scr/dr2db1.
I think whats needed is a clean install.

Http://www.puschitz.com/InstallingOracle10gRAC.shtml#CreatingPartitionsForRawDevices

Performed on Node1:/opt/ora10g/product/10.2.0/crs_1/root.sh; Performed on Node2:/opt/ora10g/product/10.2.0/crs_1/root.sh;

Usually, when the last node executes root.sh, it encounters an error, and in our case of course it is node2~~

Tip: There are three common errors:

a). If you run into this error:
/opt/ora10g/product/10.2.0/crs_1/jdk/jre//bin/java:error while loading shared libraries:libpthread.so.0:cannot open Shared object File:no such file or directory
Can be resolved as follows:
===============================
Modify the VIPCA file
[Email protected] opt]# VI/OPT/ORA10G/PRODUCT/10.2.0/CRS_1/BIN/VIPCA
Find the following:
Remove This workaround if the bug 3937317 is fixed
Arch= ' Uname-m '
If ["$arch" = "i686"-o "$arch" = "ia64"]
Then
ld_assume_kernel=2.4.19
Export Ld_assume_kernel
Fi
#End Workaround
Add a new line after FI:
Unset Ld_assume_kernel
and Srvctl file
[Email protected] opt]# Vi/opt/ora10g/product/10.2.0/crs_1/bin/srvctl
Find the following:
ld_assume_kernel=2.4.19
Export Ld_assume_kernel
Also add a new line later:
Unset Ld_assume_kernel
Save exit, and then re-execute root.sh in Node2
Of course, since we already know the problem, it is advisable to first modify VIPCA before Node2 executes root.sh.
In fact, you also need to change the $oracle_home/bin/srvctl file, or after loading the database, Srvctl command will also report this error. To know that srvctl is so common, if it performs the old error, it is very deadly ah. But you are now installed to CRS, from the Create DB is still far away, you can wait until the database is created, and then modify the file when you need to manage it.

b). If you run into this error:
The given interface (s),  "eth0"  is not  public. Public interfaces should  be used to configure virtual  ips. The
resolves as follows:
Run $CRS_HOME/BIN/VIPCA on the ==============================
graphical interface, manually reconfigure RAC1-VIP and RAC2-VIP.
[[email protected] opt]# xhost +
[[email protected] opt]# /opt/ ORA10G/PRODUCT/10.2.0/CRS_1/BIN/VIPCA
Follow the prompts to click Next
Click Finish to VIPCA start automatic configuration
When all configuration is complete, click Exit to quit the action window.

C). If you run into this error:
Error 0 (Native:listnetinterfaces:[3])
[Error 0 (native:listnetinterfaces:[3])]
The solution is as follows:
===============================
[Email protected] bin]#/oifcfg iflist
Eth1 10.10.17.0
Virbr0 192.168.122.0
Eth0 192.168.100.0
[Email protected] bin]#/oifcfg setif-global eth0/192.168.100.0:public[[email protected] bin]#./oifcfg Setif-global E Th1/10.10.10.0:cluster_ Interconnect
[Email protected] bin]#/oifcfg getif
Eth0 192.168.100.0 Global Public
eth1 10.10.10.0 Global Cluster_interconnect
You can then re-execute the VIPCA in the Windows interface, as shown in the previous B example.

Problems and workarounds for installing Oracle_rac

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.