This content has been marked as final. Show 9 replies
Thank you. That is the doc I have been following and it does not answer my questions. However, I was able to test my theory - by shutting down the existing 126.96.36.199 env and then running ./deinstall from the 188.8.131.52 path. It got past the previous error now it wants me to run :
/tmp/deinstall2011-03-23_05-29-02-PM/perl/bin/perl -I/tmp/deinstall2011-03-23_05-29-02-PM/perl/lib -I/tmp/deinstall2011-03-23_05-29-02-PM/crs/install /tmp/deinstall2011-03-23_05-29-02-PM/crs/install/roothas.pl -force -delete -paramfile "/tmp/deinstall2011-03-23_05-29-02-PM/response/deinstall_noHomeName.rsp"
I'm afraid to run this because I don't want to deinstall the 184.108.40.206 home from CRS. The documentation is not clear to me on this.
Please check below notes:
11gR2 RAC: How to re-install the Grid Infrastructure without disturbing the RDBMS installations. [ID 1276975.1]
Oracle De-install Utility - 11g R2 [ID 886184.1]
How to Proceed from Failed 11gR2 Grid Infrastructure (CRS) Installation [ID 942166.1]
11gR2 Grid Infrastructure - Deinstall script rootcrs.pl failed [ID 1174384.1]
We are having the same issue with the 220.127.116.11 deinstall utility, using the -checkonly parameter. Found note 883743.1, that I am reviewing and will try to download the tool from OTN. The error is:
ERROR: Can't deconfigure Oracle Restart before removing or downgrading managed Oracle databases.
We are using Oracle Restart from the 18.104.22.168 Grid Infrastructure home.
I downloaded the deinstall tool and tried to run from another location. Same Error =
PRKU-01039: Can't deconfigure Oracle Restart before removing or downgrading managed Oracle databases.
Cause: A request to deconfigure Oracle Restart found one or more managed Oracle database homes, so the request was rejected.
Action: Run the Oracle deconfiguration tool from Oracle database homes to delete, deconfigure or downgrade Oracle database and then run the same tool from Oracle Restart home to deconfigure the Oracle Restart stack.
Anyone have a fix for this? Not sure I trust this tool yet. We have working ASM and database instances running from 22.214.171.124_ORACLE_HOME
I ran into the same issue. But I solved the problem.
The issue here is OHAS and CSS services are still running in background, and need to shut them down before run deinstall script:
1) shutdown ASM instance;
2) shutdown OHAS and CSS services by using the following script as root user:
$ORACLE_HOME/crs/install/roothas.pl -deconfig -force
3) make sure OHAS and CSS is down:
crsctl check has
crsctl check css
Edited by: 865548 on Nov 4, 2011 9:11 AM
On all cluster nodes except the last, run the following command as the "root" user.
# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force
On the last cluster node, run the following command as the "root" user.
# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force -lastnode
This final command will blank the OCR configuration and voting disk.
You should be in a position to rerun the "root.sh" file now, but if you are using ASM, you will need to prepare your ASM disks before doing so.
Once you attempt an installation, your ASM disks are marked as being used, so they can no longer be used as candidate disks. To revert them to candidate disk do the following.
Overwrite the header for the relevant partitions using the "dd" command.
# dd if=/dev/zero of=/dev/sdb1 bs=1024 count=100
Remove and create the ASM disk for each partition.
# /etc/init.d/oracleasm deletedisk DATA /dev/sdb1
# /etc/init.d/oracleasm createdisk DATA /dev/sdb1