SPAM: [suse-sles-e] SPAM: Re: [suse-oracle] Re: [suse-sles-e] Re: [suse-oracle] Re: [suse-sles-e] Re: [suse-oracle] Raw Devices

From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Sat Oct 14 2006 - 04:43:00 CEST


Message-ID: <005e01c6ef3a$76b71750$6f31a8c0@sjc.exigengroup.com>
From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com>
Date: Fri, 13 Oct 2006 19:43:00 -0700
Subject: SPAM: [suse-sles-e] SPAM: Re: [suse-oracle] Re: [suse-sles-e] Re: [suse-oracle] Re: [suse-sles-e] Re: [suse-oracle] Raw Devices

CHECKLIST:

After changing LVM object, abd before reconfiguring Oracle, check, if:
- does all nodes see new object?
- does Oracle see new object parameters (such as volume size) on all nodes?
/it is not the same as prev. question/
- does system see new object correctly after node restarts.

PS. I can imagine problems with archive logs @ ASM or stability of ASM in
case of
   * rac
   * asm reconfiguration
   * node failure

but I can't image any problems with tablespace resizing @ ASM at all. There
is nothing worst then resizing tablespace on raw devices.
But you can try - it have it's own benefits - simplicity (you have 2 things
only - raw and lvm - instead of, for example, ASM + raw + OCFSv2).

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com



This archive was generated by hypermail 2.1.7 : Sat Oct 14 2006 - 04:38:25 CEST