RE: Standby Log corruption -- in Recover phase

From: <Laimutis.Nedzinskas_at_seb.lt>
Date: Thu, 5 Jul 2012 10:56:44 +0300
Message-ID: <OFF5B73323.6F1510A7-ONC2257A32.002B03C9-C2257A32.002BA5CD_at_seb.lt>



Looks like the recovery area is used.

Just had a similar situation today. Archiver on primary (LGWR in my case) was complaining about archive issues. The errors messages were not conclusive in the primary logs at least. On the standby site some of the errors were strange too (online redo log related, etc)

The solution was to free space in recovery area on the standby site: for me it was enough to RMAN> delete archivelog [all] But watch out the archive log deletion policy. Actually it is better to stay on the safe side and use delete archivelog until the last applied log.


Please consider the environment before printing this e-mail

                                                                                                                                                  
  From:       "Mark W. Farnham" <mwf_at_rsiz.com>                                                                                                    
                                                                                                                                                  
  To:         <krishna.setwin_at_gmail.com>, "'Li Li'" <litanli_at_gmail.com>                                                                           
                                                                                                                                                  
  Cc:         "'Oracle List'" <oracle-l_at_freelists.org>                                                                                            
                                                                                                                                                  
  Date:       2012.07.03 16:23                                                                                                                    
                                                                                                                                                  
  Subject:    RE: Standby Log corruption -- in Recover phase                                                                                      
                                                                                                                                                  





error creating

classic reasons to check: process permissions, broken destination device (broken or offline), file already exists, failure to connect.

If you can trace the process trying to write the file at the OS level, you should be able to see exactly what is failing in terms of system calls, which would eliminate the heuristic process of narrowing it down.

Good luck. (I didn't decode your parameter string - has it been working in the past? Were there any recent changes?)

regards,

mwf

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [?mailto:oracle-l-bounce_at_freelists.org ]
On Behalf Of Krishna
Sent: Monday, July 02, 2012 11:50 PM
To: Li Li
Cc: Mark W. Farnham; Oracle List
Subject: Re: Standby Log corruption -- in Recover phase

hi,
Thanks Mark and Li Li.
I validated the archivelogs on primary. They are fine.

Now, I am having this error.

Redo transport problem detected: redo transport for database drdb has the following error:
  ORA-00270: error creating archive log
07/02/2012 23:41:26
Redo transport problem detected: redo transport for database drdb has the following error:
  ORA-00270: error creating archive log
07/02/2012 23:42:26
Redo transport problem detected: redo transport for database drdb has the following error:
  ORA-00270: error creating archive log

FRA sizes on both DR & Primary are less than 50%.(i am checking V$FLASH_RECOVERY_AREA_USAGE) i have the following parameter:
log_archive_dest_2='SERVICE=drdb LGWR ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=drdb' scope=both sid='*' ;

Any inputs strongly appreciated.

Thanks
krishna.

On Mon, Jul 2, 2012 at 1:03 PM, Li Li <litanli_at_gmail.com> wrote:

> I have had this issue and oracle has logged bug 14227837 for it.
> Currently I manually copy the logs over to standby, then rman catalog
> it to get through this situation.
>
> On Mon, Jul 2, 2012 at 8:05 AM, Krishna <krishna.setwin_at_gmail.com> wrote:
> > Mark,
> > Thanks for your reply.
> > I dont see any corruption errors on primary nodes.
> >
> > I see the following errors on primary..
> >
> > FAL[server, ARC2]: FAL archive failed, see trace file.
> > ARCH: FAL archive failed. Archiver continuing ORACLE Instance
> > primdb1 - Archival Error. Archiver continuing.
> >
> >
> >
> >
> > On Mon, Jul 2, 2012 at 8:49 AM, Mark W. Farnham <mwf_at_rsiz.com> wrote:
> >
> >> I would start by validating the archived redo log on the primary.
> >> That should help determine a direction for the solution and
> >> establish whether the corruption is primary or a network artifact.
> >>
> >> -----Original Message-----
> >> From: oracle-l-bounce_at_freelists.org [mailto:
> oracle-l-bounce_at_freelists.org]
> >> On Behalf Of Krishna
> >> Sent: Monday, July 02, 2012 6:57 AM
> >> To: Oracle List
> >> Subject: Standby Log corruption -- in Recover phase
> >>
> >> Hi All,
> >> I am trying to set up RAC to RAC dataguard between 2 databases in
> different
> >> data centers.
> >> I am able to ship archivelogs from primary to DR. The logs are not
> getting
> >> applied.
> >>
> >>
> >> In the standby alert log -- I see the following errors (several of
> >> these CORRUPTION DETECTED Errors)
> >>
> >> *CORRUPTION DETECTED: In redo blocks starting at block 4097count
> >> 2048
> for
> >> thread 4 sequence 15019*
> >> RFS[1185]: Possible network disconnect with primary database
> >> *Deleted Oracle managed file
> >> +FR1/drdb/archivelog/2012_07_02/thread_4_seq_15019.578.787560321*
> >> RFS[1186]: Possible network disconnect with primary database Mon
> >> Jul 02
> >> 06:45:36 2012
> >> RFS[1189]: Assigned to RFS process 5016
> >> RFS[1189]: Opened log for thread 2 sequence 12872 dbid 832151255
> >> branch
> >> 782279895
> >> *CORRUPTION DETECTED: In redo blocks starting at block 1count 2048
> >> for thread 2 sequence 12872 Deleted Oracle managed file
> >> +FR1/drdb/archivelog/2012_07_02/thread_2_seq_12872.578.787560337*
> >> Mon Jul 02 06:45:38 2012
> >>
> >>
> >> another thing is -- I have any another application, where there is
> >> dataguard from RAC to single instance. For this I dont see any
problem..
> >>
> >> can anybody throw some light on this problem?
> >>
> >> Thanks in advance..
> >>
> >> Krishna
> >>
> >>
> >> --
> >> http://www.freelists.org/webpage/oracle-l
> >>
> >>
> >>
> >
> >
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
>

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l





--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jul 05 2012 - 02:56:44 CDT

Original text of this message