RE: Does ocssd.bin started from 11gASM home support diskgroups mounted by 10g ASM instance
- From: "Matthew Zito" <mzito@xxxxxxxxxxx>
- To: "Martin Berger" <martin.a.berger@xxxxxxxxx>
- Date: Mon, 3 Aug 2009 18:02:30 -0400
That was going to be my question, if I have multiple ASM instances, how does
your Oracle instance know which one to talk to? Also, what happens if I have
my diskstring set to /dev/sd* in both instances? Do they both try to mount the
diskgroups? Does Oracle have any sane sort of fencing to prevent that? If so,
is it just a race to acquire a lock?
It seems like bad mojo, even if technically it is possible.
Matt
-----Original Message-----
From: Martin Berger [mailto:martin.a.berger@xxxxxxxxx]
Sent: Mon 8/3/2009 4:34 PM
To: Matthew Zito
Cc: sanjeevorcle@xxxxxxxxx; John Hallas; oracle-l@xxxxxxxxxxxxx
Subject: Re: Does ocssd.bin started from 11gASM home support diskgroups
mounted by 10g ASM instance
I run some tests and it's really possible to run different ASMs on one
machine. I also didn't found some evidence multiple ASMs are not _supported_
(even all documents I red only mentioned one ASM per node). - Only in RACs,
only one ASM is _supported_.
So I could not find any reason not to run multiple ASMs on one node (even it's
very complicated).
Just note, one Instance can only use all DiskGroups from one ASM; I didn't
found any method to use DGs from different ASMs in one Instance.
I didn't analyse this fact to the end, but it seems to be based on the way an
Instance gets the DG-metadata from the first ASM it asks, and therefore cannot
merge this information with the one of any other ASMs. But this is just a
guess(!)
br
Martin
Am 03.08.2009 um 20:17 schrieb Matthew Zito:
Uhhh, that is probably not a supported configuration. One ASM
instance per machine is the rule, AFAIK.
Matt
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of sanjeev m
Sent: Monday, August 03, 2009 2:13 PM
To: John Hallas
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Does ocssd.bin started from 11gASM home support diskgroups
mounted by 10g ASM instance
Since we can have only ONE ocssd.bin per host and there is a need to
use 10gASM instance to keep things in sync with PRD env we brought up 10gASM
instance. There are other 11g RDBMS on this host making use of 11g ASM instance.
Regards,
Sanjeev.
On Mon, Aug 3, 2009 at 4:13 AM, John Hallas
<John.Hallas@xxxxxxxxxxxxxxxxxx> wrote:
I am a bit confused.
11g ASM supports 10G RDBMS
If I was running an 11g ASM instance I would start the occsd using the
11G binaries whether or not the 10G occsd binary worked
Remember to get you compatibility settings correct
col COMPATIBILITY form a10
col DATABASE_COMPATIBILITY form a10
col NAME form a20
col VALUE form a10
select group_number, name, compatibility, database_compatibility
from v$asm_diskgroup;
alter diskgroup data set attribute 'compatible.rdbms'='10.2';
alter diskgroup data set attribute 'compatible.asm'='11.1';
(or whatever is appropriate)
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of sanjeev m
Sent: 03 August 2009 05:53
To: oracle-l@xxxxxxxxxxxxx
Subject: Does ocssd.bin started from 11gASM home support diskgroups
mounted by 10g ASM instance
Listers,
On our non-rac environment we have upgraded 10g ASM home to 11g ASM
home.Can we mount diskgroup belonging to 10g RDMS from 10g ASM home even
though the ocssd.bin process is running out of 11g ASM home. In our testing it
looks like it is working. I would like to know from support and configuration
point of view whether this i ok.
In other words does ocssd.bin started from 11gASM home support
diskgroups mounted by 10g ASM instance.
Regards,
Sanjeev.
______________________________________________________________________
Wm Morrison Supermarkets Plc is registered in England with number
358949. The registered office of the company is situated at Gain Lane,
Bradford, West Yorkshire BD3 7DL. This email and any attachments are intended
for the addressee(s) only and may be confidential.
If you are not the intended recipient, please inform the sender by
replying to the email that you have received in error and then destroy the
email.
If you are not the intended recipient, you must not use, disclose, copy
or rely on the email or its attachments in any way.
Wm Morrison Supermarkets PLC accepts no liability or responsibility for
anything said in the email or its attachments and gives no warranty as to
accuracy. It is the policy of Wm Morrison Supermarkets PLC not to enter into
any contractual or other obligations by email.
Although we have taken steps to ensure the email and its attachments
are virus-free, we cannot guarantee this or accept any responsibility,
and it is the responsibility of recipients to carry out their own virus
checks.
______________________________________________________________________
Other related posts:
