關(guān)于Clusterware卸載的問題？

lyh303

正在實施一套Solaris10+Sun Cluster3.2+Oracle Clusterware+Oracle10g RAC的項目，已經(jīng)配置完Sun Cluster3.2和SVM，在安裝完Oracle Clusterware后（安裝沒問題、VIP已經(jīng)生效、crs_stat顯示狀態(tài)正常，但還未安裝Oracle RAC）發(fā)現(xiàn)其安裝目錄指定在默認的$ORACLE_BASE/db_1目錄下了（應該為$ORACLE_BASE/crs），為規(guī)范起見，準備卸載Clusterware軟件，并重新安裝指定到正確目錄，但重新運行安裝程序時，在安裝完軟件包后，提示以root用戶執(zhí)行下面的腳步（/opt/oracle/product/10.2.0/crs/root.sh），只提示了以root執(zhí)行這一個腳本，在一個節(jié)點上執(zhí)行這個腳本時就停在“Startup will be queued to init within 30 seconds”不動了，不知道什么原因？？？是不是卸載Clusterware不徹底呀？還需要做什么呢？

root@ecdb1 # /opt/oracle/product/10.2.0/crs/root.sh
WARNING: directory '/opt/oracle/product/10.2.0' is not owned by root
WARNING: directory '/opt/oracle/product' is not owned by root
WARNING: directory '/opt/oracle' is not owned by root
Checking to see if Oracle CRS stack is already configured
Checking to see if any 9i GSD is up

Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/opt/oracle/product/10.2.0' is not owned by root
WARNING: directory '/opt/oracle/product' is not owned by root
WARNING: directory '/opt/oracle' is not owned by root
clscfg: EXISTING configuration version 3 detected.
clscfg: version 3 is 10G Release 2.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 0: ecdb1 clusternode1-priv ecdb1
node 1: ecdb3 clusternode2-priv ecdb3
clscfg: Arguments check out successfully.

NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 30 seconds.



備注，卸載Clusterware的步驟如下：
1. Run the command CRS_home/install/rootdelete.sh to disable the Oracle Clusterware applications that are running on the cluster node.
2. Start OUI. In the Welcome page, click Deinstall Products to display the list of installed products. Select the Oracle Clusterware home to de-install.

山野村夫

不記得卸載時還有運行root.sh呀

guyeh

需要在RAC的每個節(jié)點上都運行CRS_home/install/rootdelete.sh和CRS_home/install/rootdeinstall.sh

lyh303

問題解決了，的確是卸載的不徹底導致，后來在metalink上找到一篇文檔，安裝文檔做了一遍reboot系統(tǒng)后，問題解決。感謝樓上幾位的支持！

lyh303

對了，把那個文檔貼出來，供大家參考：

Subject: How to Clean Up After a Failed Oracle Clusterware (CRS) Installation
  Doc ID: 239998.1 Type:  BULLETIN
  Modified Date:  18-MAR-2009 Status:  PUBLISHED


PURPOSE
-------

The purpose of this document is to help DBA's and support analysts understand how
to clean up a failed CRS (Cluster Ready Services) install for 10g RAC.


SCOPE & APPLICATION
-------------------

DBA's and Support Analysts


10g RAC: How to Clean Up After a Failed CRS Install
---------------------------------------------------

Not cleaning up a failed CRS install can cause problems like node reboots.
Follow these steps to clean up a failed CRS install:

1. Run the rootdelete.sh script then the rootdeinstall.sh script from the
$ORA_CRS_HOME/install directory on any nodes you are removing CRS from.  Running
these scripts should be sufficent to clean up your CRS install.  Rootdelete.sh
accepts options like nosharedvar/sharedvar, and nosharedhome/sharedhome. Make
yourself familiar with these options by reading the Oracle Clusterware and
Oracle Real Application Clusters Administration and Deployment Guide.
If you have any problems with these scripts please open a service request.  

If for some reason you have to manually remove the install due to problems
with the scripts, continue to step 2:

2. Stop the Nodeapps on all nodes:

        srvctl stop nodeapps -n <node name>

3. Prevent CRS from starting when the node boots.  To do this issue the following
as root:

Sun:

        rm /etc/init.d/init.cssd
        rm /etc/init.d/init.crs
        rm /etc/init.d/init.crsd
        rm /etc/init.d/init.evmd
        rm /etc/rc3.d/K96init.crs
        rm /etc/rc3.d/S96init.crs
        rm -Rf /var/opt/oracle/scls_scr
        rm -Rf /var/opt/oracle/oprocd
        rm /etc/inittab.crs
        cp /etc/inittab.orig /etc/inittab

Linux:

        rm /etc/oracle/*
        rm -f /etc/init.d/init.cssd
        rm -f /etc/init.d/init.crs
        rm -f /etc/init.d/init.crsd
        rm -f /etc/init.d/init.evmd
        rm -f /etc/rc2.d/K96init.crs
        rm -f /etc/rc2.d/S96init.crs
        rm -f /etc/rc3.d/K96init.crs
        rm -f /etc/rc3.d/S96init.crs
        rm -f /etc/rc5.d/K96init.crs
        rm -f /etc/rc5.d/S96init.crs
        rm -Rf /etc/oracle/scls_scr
        rm -f /etc/inittab.crs
        cp /etc/inittab.orig /etc/inittab

HP-UX:

        rm /sbin/init.d/init.cssd
        rm /sbin/init.d/init.crs
        rm /sbin/init.d/init.crsd
        rm /sbin/init.d/init.evmd
        rm /sbin/rc2.d/K960init.crs
        rm /sbin/rc2.d/K001init.crs
        rm /sbin/rc3.d/K960init.crs
        rm /sbin/rc3.d/S960init.crs
        rm -Rf /var/opt/oracle/scls_scr
        rm -Rf /var/opt/oracle/oprocd
        rm /etc/inittab.crs
        cp /etc/inittab.orig /etc/inittab

HP Tru64:

        rm /sbin/init.d/init.cssd
        rm /sbin/init.d/init.crs
        rm /sbin/init.d/init.crsd
        rm /sbin/init.d/init.evmd
        rm /sbin/rc3.d/K96init.crs
        rm /sbin/rc3.d/S96init.crs
        rm -Rf /var/opt/oracle/scls_scr
        rm -Rf /var/opt/oracle/oprocd
        rm /etc/inittab.crs
        cp /etc/inittab.orig /etc/inittab

IBM AIX:

        rm /etc/init.cssd
        rm /etc/init.crs
        rm /etc/init.crsd
        rm /etc/init.evmd
        rm /etc/rc.d/rc2.d/K96init.crs
        rm /etc/rc.d/rc2.d/S96init.crs
        rm -Rf /etc/oracle/scls_scr
        rm -Rf /etc/oracle/oprocd
        rm /etc/inittab.crs
        cp /etc/inittab.orig /etc/inittab

4. If they are not already down, kill off EVM, CRS, and CSS processes or reboot
   the node:

        ps -ef | grep crs       
        kill <crs pid>
        ps -ef | grep evm
        kill <evm pid>
        ps -ef | grep css       
        kill <css pid>

   Do not kill any OS processes, for example icssvr_daemon process !

5. If there is no other Oracle software running (like listeners, DB's, etc...),
   you can remove the files in /var/tmp/.oracle or /tmp/.oracle.  Example:

        rm -f /var/tmp/.oracle/*

        or

        rm -f /tmp/.oracle/*

6. Remove the ocr.loc
   Usually the ocr.loc can be found at /etc/oracle

7. De-install the CRS home in the Oracle Universal Installer

8. Remove the CRS install location:

          rm -Rf <CRS Install Location>/*

9. Clean out the OCR and Voting Files with dd commands.  Example:

        dd if=/dev/zero of=/dev/rdsk/V1064_vote_01_20m.dbf bs=1M count=256
        dd if=/dev/zero of=/dev/rdsk/ocrV1064_100m.ora bs=1M count=256

   See the Clusterware Installation Guide for sizing requirements...  

   If you placed the OCR and voting disk on a shared filesystem, remove them.

   If you are removing the RDBMS installation, also clean out any ASM disks if
   they have already been used.

10. It is good practice to reboot the node before starting the next install.

11.If you would like to re-install CRS, follow the steps in the RAC Installation manual.

山野村夫

不錯，收藏了

dingning239

感謝樓主的分享

rickcafe

請教一下？

suncluster與clusterware的作用是不是重疊？只用一種群集管理軟件是不是也可以實現(xiàn)RAC？

blue_stone

原帖由 rickcafe 于 2009-7-18 07:14 發(fā)表
請教一下？

suncluster與clusterware的作用是不是重疊？只用一種群集管理軟件是不是也可以實現(xiàn)RAC？

不重疊, Oracle clusterware可以使用suncluster的某些功能, 比如集群管理, 比如裸設備管理.

10g RAC必須安裝Oracle clusterware, suncluster可以裝, 也可以不裝

koolji

我郁悶了2天asm，最后更換硬盤才解決。