This content has been marked as final. Show 10 replies
Your spfile not exists On ASM , Hope you have Pfile
TRY THE FOLLOWING :
SQL> CREATE SPFILE='+RACDB_DATA/RACDB/spfileRACDB.ora' from pfile='<path>/sid.ora'; sHUTDOWN IMMEDIATE ; STARTUP MOUNT ;
Status Level: Newbie (10)
Registered: Aug 10, 2007
Total Posts: 244
Total Questions: 51 (36 unresolved)
Location Hyderabad ( India )
Occupation Oracle Database Administrator
Try to close your thread please
Change owner of partition to user “oracle” and group “oinstall”.
# chown oracle:oinstall /../disk1
# chown oracle:oinstall /../disk2
# chown oracle:oinstall /../disk3
# chmod 600 /.../disk1
# chmod 600 /.../disk2
# chmod 600 /.../disk3
try again to startup
Have you set the group ownership of the oracle executable to the ASMDBA group? The $ORACLE_HOME/bin/setasmgid utility does this for you.
The ownership of Oracle executables is oracle:oinstall, but for oracle, it is oracle:asmadmin. This is same for both the nodes:
[oracle@racnode2 bin]$ pwd /u01/app/oracle/product/11.2.0/dbhome_1/bin -r-sr-s--x 1 oracle asmadmin 173515905 Nov 17 15:29 oracle* [oracle@racnode2 bin]$
Any clue on this ?
did you check if your spfile exists on ASM or not ?
Yep, everything is in place. Its in shared drive and there is only 1 spfile, with instance specific parameters. So, its not the question of presence of spfile, but permission is screwed up somewhere...
I think you have many permission errors. This is clearly wrong:
-r-sr-s--x 1 oracle asmadmin 173515905 Nov 17 15:29 oracle*
If I were you, I wouldn't waste more time trying to fix it, just remove your DB home and install again. Doesn't take long.
I totally agree with you and it striked my mind as well. But, we are missing an opportunity to debug. Anyway, I took your suggesion seriously. I'll spend a couple to hours more to debug and then, I'll remove and create.