RE: stale ASM alert logs

  • From: Herring Dave - dherri <Dave.Herring@xxxxxxxxxx>
  • To: "Jed_Walker@xxxxxxxxxxxxxxxxx" <Jed_Walker@xxxxxxxxxxxxxxxxx>, Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Sun, 19 Aug 2012 19:19:20 +0000

You could try performing an operation that writes a message to the alert log.  
Issue a rebalance operation on a diskgroup and if you don't want that to 
continue issue it again with "power 0", which will stop the operation.  Both 
commands will get logged to ASM's alert log, along with other ARB status info.

I know there are other commands that may be "safer" to run against production 
but I can't think of any at the moment, at least for ASM.  There are packages 
to write to the alert log but obviously they don't exist for ASM.

Acxiom Corporation
EML   dave.herring@xxxxxxxxxx
TEL    630.944.4762
MBL   630.430.5988 
1501 Opus Pl, Downers Grove, IL 60515, USA

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Walker, Jed S
Sent: Wednesday, August 15, 2012 2:16 PM
To: Guillermo Alan Bort; oracle-l@xxxxxxxxxxxxx
Subject: RE: stale ASM alert logs

Good thinking but that isn't it. I did "show parameter background" and it is 
the directory I'm checking in. It doesn't appear the instance itself thinks it 
is somewhere else.
Anyone have other ideas?

SQL> show parameter background

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
background_core_dump                 string      partial
background_dump_dest                 string      /oracle/grid/diag/asm/+asm/+AS
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release - 
64bit Production With the Real Application Clusters and Automatic Storage 
Management options
(oracle) node-01:+ASM1:/home/oracle
 ->cd /oracle/grid/diag/asm/+asm/+ASM1/trace
(oracle) node-01:+ASM1:/oracle/grid/diag/asm/+asm/+ASM1/trace
 ->ll -rt
total 512
-rw-r----- 1 oracle dba 479574 May 11 05:26 alert_+ASM1.log
-rw-r----- 1 oracle dba   1302 Jul 20 17:07 +ASM1_rbal_27847.trm
-rw-r----- 1 oracle dba  21185 Jul 20 17:07 +ASM1_rbal_27847.trc
-rw-r----- 1 oracle dba     71 Jul 25 16:10 +ASM1_lmon_27827.trm
-rw-r----- 1 oracle dba    934 Jul 25 16:10 +ASM1_lmon_27827.trc

From: alanbort@xxxxxxxxx [mailto:alanbort@xxxxxxxxx] On Behalf Of Guillermo 
Alan Bort
Sent: Wednesday, August 15, 2012 12:38 PM
To: Walker, Jed S
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: stale ASM alert logs

have you checked the background_dump_dest parameter in the ASM instance? are 
you sure you are looking at the correct alert log? sometimes I've seen ASM 
loosing the pfile and going back to default configs, which include the alert 
log location.



The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.


Other related posts: