Hi Martin,
thanks again for the valuable suggestions!
No, there's neither UAT nor DR environment for this database ...
Assuming no changes to the oracleasm configuration,
could the following operations still break/have an impact on the live
database?
1. Add new disks to the servers.
2. Create disks using the oracleasm createdisk command (using the
first path found, in this case one of the two physical paths).
3. Create new diskgroup using the new disks.
I don't know if running scandisks, in order to make the newly created
disks visible to the other nodes,
could have a negative impact on the rest of the system.
I'm only looking for information and suggestions,
I realize these operations could be destructive and most probably we
will call Oracle for this.
The library shows as:
ASM Library - Generic Linux, version 2.0.4 (KABI_V2)
Best regards
Dimitre
On 08/04/2011 10:20, Martin Bach wrote:
Hi Dimitre,
As you're live with production such a change shouldn't be made
without proper testing-is your UAT environment a suitable candidate
for this? You might create situation where not only the new disks
aren't visible, but worse: the old ones won't be either creating the
"perfect outage". I usually do such changes in DR first, or
alternatively ensure that DR can be activated and stakeholders are
aware of the risk. You'd then hope that you followed change
management correctly and kept production and DR in sync .... But that
keeps the job interesting!
Also, out of curiosity, what's the output of v$asm_disk.library -
does it show system or asmlib?
Best regards,
Martin
Martin Bach
Martin Bach Consulting Ltd
http://www.linkedin.com/in/martincarstenbach
http://martincarstenbach.wordpress.com
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
....
