Disclaimer!

FatDBA or Oracle ‘Ant’ is an independent web-blog/site.The experiences, Test cases, views, and opinions expressed in this website are my own and does not reflect the views or opinions of my employer.

This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content.
Product and company names mentioned in this website may be the trademarks of their respective owners.

While ‘Linking Libraries’ step received an error message which says about which i skipped and soon after that got many different errors related to linking, which i again skipped.

Same has happened during ‘Net Configuration Step’ and ‘DB Configuration Assistant’, which i again skipped (Otherwise the message keeps on coming on screen)

After that I’ve executed root.sh and related scripts from root account.

But now after this installation has completed (With many errors related to linking and Configuration files), I’m not able to launch the sqlplus executable. Even after setting the ORACLE_BASE, ORACLE_HOME.

I’ve recently created an ASM instance on one of my Test DB Machine which has 10g R2 installed on Red Hat Linux 5 platform . It was absolutely good until a recent system issue which forced us to reboot machine and soon after the machine is up and we tried starting ASM instance it’s prompting following errors on the terminal which reads:

SQL> startupORA-15032: not all alterations performedORA-15063: ASM discovered an insufficient number of disks for diskgroup “‘+TESTDB_DATA1′”

OR Sometimes

ORA-29701: unable to connect to Cluster Manager
Then i tried to check the status of raw disks I’ve made during the Failgroup creation and found the permissions has somehow reverted back to root:root which should be oracle:oinstall in place for all raw disks.

(There are four raw disks and raw 1 and raw 2 part of Failgroup 1 and raw 3 and raw 4 is Failgroup 2)

so, i manually changed the permissions again to oracle:oinstall and modified the mode to 660 and then tried to start the ASM instance and as per my expectations it started working good.
But to test i rebooted machine again after this permissions and mode change and it’s started doing the same and permissions and ownership rolled back to root:root

Below are the contents of boot up script– /etc/rc.d/rc.local

[root@localhost raw]# vi /etc/rc.d/rc.local

#!/bin/sh
#
# This script will be executed after all the other init scripts.
# You can put your own initialization stuff in here if you don’t
# want to do the full Sys V style init stuff.