Re: Unexpected behavior from ASM (?)
- From: Martin Berger <martin.a.berger@xxxxxxxxx>
- To: daniel.hubler@xxxxxxxxxx
- Date: Wed, 19 Mar 2014 14:44:58 +0100
Hi Daniel,
it can be a quite complex setup.
please check: as which user is your ASM instance running?
at which user is your DB running? what are the Groups those 2 belong to?
what's the owner/group of the raw devices?
what's the user/group of the oracle binaries involved?
all of those can affect the symptoms and there are a LOT of combinations
which can create your suggested incident pattern.
(I'm working with linux-only setup at the moment, but I hope posix group &
permissions are similar on AIX)
Martin
On Wed, Mar 19, 2014 at 2:03 PM, Hubler, Daniel <daniel.hubler@xxxxxxxxxx>wrote:
> Oracle DBMS v11.2.0.3
>
> 2-node RAC
>
> ASM on raw devices
>
> AIX v6.1
>
> (a TEST environment !)
>
>
>
>
>
>
>
> Added a bunch of raw devices into ASM using the following:
>
> ===
>
> SQL> alter diskgroup data
>
> add disk
> '/dev/rhdisk35','/dev/rhdisk36','/dev/rhdisk37','/dev/rhdisk38','/dev/rhdisk39','/dev/rhdisk40','/dev/rhdisk41'
>
> rebalance power 8;
>
>
>
> Diskgroup altered.
>
> ===
>
>
>
> Shortly (minutes) after this completed,
>
> both database instances crashed.
>
> ASM survived.
>
>
>
> Immediately started looking at the details on these raw devices.
>
> Discovered that the permissions on some of them were incorrect; missing
> various r-w permissions.
>
>
>
> Changed those permissions.
>
> Restarted the DBMS instances successfully; no issues since.
>
>
>
> I guess my question is, how did this get past ASM ?
>
> Does it not check for this?
>
>
>
> (the coincidence is that the AIX-admin who built the raw devices was doing
> this for the first time)
>
>
>
> Thanks for any input.
>
Other related posts:
