Mladen Gogala wrote:
I have a RAC database with a standby. Both RAC and standby are on ASM.
On standby,
I used the flashback recovery area located on the DGFRA diskgroup to
create standby redo
logs. There aren't any problems but I am perplexed by entries like this:

RFS[1]: Successfully opened standby log 30:
'+DGFRA/adprd/onlinelog/group_30.265.614877861'
SUCCESS: diskgroup DGFRA was dismounted
SUCCESS: diskgroup DGFRA was mounted
SUCCESS: diskgroup DGFRA was dismounted
Sun Feb 18 17:51:50 2007
SUCCESS: diskgroup DGFRA was mounted
SUCCESS: diskgroup DGFRA was dismounted
SUCCESS: diskgroup DGFRA was mounted
SUCCESS: diskgroup DGFRA was dismounted
Sun Feb 18 17:51:52 2007
Media Recovery Log /BACKUP/archives/archADPRD_1_514_614435904.dbf
Media Recovery Log /BACKUP/archives/archADPRD_1_515_614435904.dbf
Media Recovery Log /BACKUP/archives/archADPRD_2_863_614435904.dbf
Media Recovery Log /BACKUP/archives/archADPRD_1_516_614435904.dbf
Media Recovery Log /BACKUP/archives/archADPRD_2_864_614435904.dbf
Media Recovery Waiting for thread 1 sequence 517

Why in the world is it unmounting/mounting the diskgroup? What useful
purpose does it serve and why
doesn't the instance just leave it mounted?
--

Malden,

I think this could be the same issue discussed in ML note 361173.1
Asm Diskgroup success Mount And Umount messages in alert.log during Rman
Backup

Thanks
Fairlie
---------------------------

Mladen,

Ignore the messages. They are just informal ones and will be removed
from future(!)versions. Basically ASM close (or dismount) those groups
when it closes the file descriptors on that DG and mounts when it
opens first file on that DG.

-Gopal

-------------------------

Hello Malden,

We keep a (multiplexed) copy of the controlfile in the disk group used
for FRA, it's a good practice anyway and as a side effect it keeps the
FRA diskgroup always mounted.

Cheers,
Luca  
--------------------------
Luca Canali schrieb:
> 
> We keep a (multiplexed) copy of the controlfile in the disk group used
> for FRA, it's a good practice anyway and as a side effect it keeps the
> FRA diskgroup always mounted.

i second that. i haven't seen these messages anymore after putting a
controlfile copy in the FRA and i agree storing a controlfile copy in
the FRA is really a good practice.

regards,
-ap
-----------------------------
Hi,

There is a metalink Note:361173.1 which states that this is an expected behavior. So you can ignore these messages.

-Amithttp://askoracledba.wordpress.com
-----------------------------