So here is the logic - you ASM is up but dbca doesn't see it. If I recall correctly, it contacts ASM via listener so you want to make sure that your ASM instances are registered with listeners and have password file set/created. Perhaps, you could find sqlnet.log file created with connection error. Check that you have listener running and etc. On 7/23/07, Ravi Gaur <ravigaur1@xxxxxxxxx> wrote:
Hi all, We've a 2-node RAC cluster with a database up and running using ASM and we're trying to add another database to the cluster via DBCA. It shows up a popup with the following message at the "storage options" screen in dbca -- DBCA could not start ASM instance configured on this node. To proceed with database creation using ASM you need the ASM instance to be up and running. Do you want to recreate the ASM instance on this node? The OS is Linux4 and the database is 10.2.0.3. ASM is seen OK from sqlplus and EM finds it healthy. I've an SR open with Oracle but I suspect it will take longer to diagnose the issue and thought if anyone had any tips etc to check. We're not getting any hits on Google and/or metalink. TIA, - Ravi Gaur Lead Systems DBA Univ of IL.
-- Alex Gorbachev, Oracle DBA Brewer, The Pythian Group http://www.pythian.com/blogs/author/alex http://www.oracloid.com BAAG party - www.BattleAgainstAnyGuess.com