"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:<40e0721c$0$16107$afc38c87_at_news.optusnet.com.au>...
> "Chris" <christian.antognini_at_trivadis.com> wrote in message
> news:c283720b.0406280523.3047cf22_at_posting.google.com...
> > Hi Howard
> >
> > Which name did you use for the ASM instance?
> > Many tools, like DBCA and Grid Control, support only "+ASM". Yes, you
> > should really put the "+" in it :-(
> >
> > Chris
>
> A quick update... it makes no difference.
>
> SQL> startup force
> ASM instance started
>
> Total System Global Area 100663296 bytes
> Fixed Size 787648 bytes
> Variable Size 99875648 bytes
> Database Buffers 0 bytes
> Redo Buffers 0 bytes
> ASM diskgroups mounted
> SQL> create spfile from pfile;
>
> File created.
>
> SQL> select instance_name from v$instance;
>
> INSTANCE_NAME
> ----------------
> +asm
>
> And with all of that running, DBCA still reports: "There are no ASM
> instances running on this machine".
>
> Can I ask where you heard about the naming issue, so I can read around on
> the topic? It certainly sounds like a plausible candidate for the cause of
> my woes, and perhaps there's only a couple of other things I need to change
> to get it working!!
>
> Regards
> HJR
Maybe a stupid remark, but he stated the name should be "+ASM".
the quotes around it suggest it's case-sensitive, and your instance is
in lower-case.
sounds weird, but hey, better then nothing, right?
When I get some free space on my laptop, i'm going to try it myself
too.
(read: when i finally decide to remove my 9i-db and replace it with a
10g one.)
Received on Tue Jun 29 2004 - 06:36:03 CDT
