Re: New ASM diskgroups not registered as a service in Grid Infrastructure
- From: Fuad Arshad <fuadar@xxxxxxxxx>
- To: usn@xxxxxxxxx
- Date: Mon, 15 Oct 2012 06:04:05 -0700 (PDT)
Martin,
You are right its early in the morning its ASM_DIskgroups not asm_diskstring
i believe once you create the database that uses the new diskgroup
if using dbca it should automatically add the resources
if using manually you will need to add the database using srvctl and the
discovery process will create the dependencies
----- Original Message ----
From: Martin Klier <usn@xxxxxxxxx>
To: Fuad Arshad <fuadar@xxxxxxxxx>
Cc: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
Sent: Mon, October 15, 2012 7:05:58 AM
Subject: Re: New ASM diskgroups not registered as a service in Grid
Infrastructure
Hi Fuad,
we are talking about GI 11gR2 here.
Usually, each existing diskgroup is represented as, for example, a GI
service ora.ORADATA.dg. On 6 of my other systems, it works this way.
This entry is created, as soon as I create the DG with asmca or SQL*PLUS.
But on this particular box, it does not work this way, instead, the new
DG is added to ASM_DISKGROUPS parameter. But I want to install a 11gR2
database, which has to establish dependencies to diskgroups. Obviously,
I have continous problems with such an incomplete setup.
IMO, the ASM_DISKSTRING parameter is the pattern for scanning devices,
not managing diskgroups.
Thank you
Martin
Fuad Arshad schrieb:
> Martin GI only needs to register the diskgroup that it stores the spfile in
> In case of cluster the place where voting disks are at the rest if the
>diskgroups are managed by the ASM disk string
>
>
> Fuad
>
>
> On Oct 15, 2012, at 4:15, Martin Klier <usn@xxxxxxxxx> wrote:
>
>> Hi list,
>>
>> how should ASM register new diskgroups with Grid Infrastructure? I was
>> under the impression that the services like ora.ORADATA.dg are created
>> as soon as I mount the DG for the first time. But in my new system, it
>> doesn't do that - and there is no SRVCTL command to add a diskgroup.
>>
>> Does somebody know how this mechanism works, and where to start looking
>> up the issue?
>>
>> Facts:
>> * Interestingly, the diskgroup created initially by runInstaller (named
>> +OCW) in fact IS registered as ora.OCW.dg
>> * I don't have created a database/instance yet, so it's no DB issue.
>> * My Oracle-Grid-Home Version is 11.2.0.3.3
>>
>> Thanks
>> Martin
>> --
>> Usn's IT Blog for Linux, Oracle, Asterisk
>> http://www.usn-it.de
>>
>> --
>> //www.freelists.org/webpage/oracle-l
>>
>>
>
--
Usn's IT Blog for Linux, Oracle, Asterisk
http://www.usn-it.de
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
