Once i verify that ASM is working and that it's hooked into EM Grid Control, I cd to my Oracle 10gR2 home, setup my environment by using oraenv, and then run dbca.
Everything is going great until I get to the storage page, where I select "ASM" and click Next. Within a couple of seconds, I see this gem of an error message:
"DBCA could not startup the ASM instance configured on this node. To proceed with the database creation using ASM, ASM instance needs to be up and running. Do you want to recreate ASM instance on this node?"Hmm. Not what I wanted to see, that's for sure. :-(
So it's off to Metalink to see what Oracle has to say. In no short order, I find about 6 separate issues (some with their own accompanying bug numbers) all reporting the exact same issue, and all with existing ASM
instances.
The only note that had a real work-around involved changing some OAS (Oracle Advanced Security) settings as ODBC did not work well with them. That's all well-and-good, but i'm not using OAS. My sqlnet.ora file has one line!
Next, I did what all good DBA's do when faced with this type of situation: go to Google. Unfortunately, I was still unable to find a solution. The OTN forums were not much help either. Oddly enough, some of my searches even resulted in googlewhacks.
The one interesting result I found on Metalink said something like, "I managed to use dbca to setup a database with ASM before, but now that I try it a second time, it does not work!" Interesting. To me, that meant there HAD TO BE a solution here. There's just no way that dbca is unable to create a database with ASM. Common!!
Here's what i'm doing: I have 2 terminal windows open - one was running dbca, the other was my working terminal. The working one being the terminal I used to change listener settings, tnsping, etc.
After 2 hours of a hapless tango between clicking Next> and seeing the same error, then changing settings ...
Just for fun, I run dbca from the OTHER term window where i've been continually futzing with settings. I get to Storage, select ASM and click Next... NOW IT WORKS!!! WTF?!
That's why it works for some people sometimes and then stops the next time. We've got some env variable or something set wrong!
SOLUTION: If you get this error, check your settings, open another window, re-run oraenv, keep trying!
As soon as dbca completed, I catpured my 'env' output - here's the items of interest:
- ORACLE_SID=+ASM
- ORACLE_HOME=/orabase/product/ora10g
- LIBPATH=/orabase/product/ora10g/lib:/orabase/product/ora10g/lib32:/usr/lib:/lib
- JAVA_HOME=/usr/java5/bin
3 comments:
I'm having (had) the same problem install 10gR2 on a Solaris x86 cluster using CRS. I have CRS, ASM and DB all in seperate oracle homes. For the DB install to recognize ASM I had to have the ORACLE_SID set to the ASM instance and the ORACLE_HOME and PATH pointing at the ASM HOME. Then I ran DBCA from the DB Oracle home (confused yet?). Oracle installs are great fun.
I've found the solution:
http://rdbland.blogspot.com/2007/10/dbca-non-sente-asm.html
Sorry it's in italian but I think you can get it :-)
Thanks to this blog, the reference to Rudy's DBland, and Google Translator I was able to put an end to a sleepness night wondering why this wasn't working. My experience was that I forgot to add CRS_HOME/bin to my PATH, following ORACLE_HOME/bin of course, and to link my ASM_HOME/network/admin directory into my ORACLE_HOME/network directory. I haven't narrowed down the exact network/admin files/settings required yet but that worked for me.
Post a Comment