Re: ASM and EMC PowerPath

  • From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
  • To: cichomitiko@xxxxxxxxx
  • Date: Fri, 8 Apr 2011 15:22:24 -0500

I believe there are options with kfod to do some of this.  The
asm_diskstring parameter should show you how it is finding the disks
currently.  As I recall, if you try and change asm_diskstring, and current
disks arent listed it wont let you.

On Fri, Apr 8, 2011 at 4:04 AM, Radoulov, Dimitre <cichomitiko@xxxxxxxxx>wrote:

>
> One more question:
>
> - oracleasm querydisk -p shows correctly all paths (physical and logical)
> to the devices.
> - oracleasm querydisk -d shows the first one found during discovery
>
> How can we know which path was used originally, when the disk was created?
>
>
>
> Best regards
> Dimitre
>
>
>
> On 08/04/2011 10:42, Radoulov, Dimitre wrote:
>
>>
>> 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]
>>>>
>>> ....
>>>
>>>
>>>
>>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>


-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 04-2011