Hi Robert, Here is the scenario: server A --> shadow copied and mounted to server B ---> RMAN--->tape The shadow copy is done by Hitachi and the platform for all these is Solaris. The first LO backup from server B to tape always works. Subsequent incremental backups from server B works only at times; and prior to this subsequent daily backup from server B there is always a daily shadow copy from server A. Backing up the control file on day 2 will work, but what about new ctl file from day 3's shadow copy? There is a disconnect between raman catlog and the new control files from server A. Here is the crux of the problem; the second day/third day's control file from server A when it is copied to Server B after a shadow copy does not contain info that it an earlier LO backup has taken place from server B to tape; is there anyway RMAN catalog can pusth that info into the new control file from day 2. Hope I could convey the issue clearly. Thanks a lot. -Suresh On Tue, Jun 8, 2010 at 9:05 AM, Robert Freeman <robertgfreeman@xxxxxxxxx> wrote: > I'm not finding the first part of this thread with the details but is this a > case where the DBID did not get changed on the non-RMAN cloned database? > > RF > > > Look Ma! It's a shorter Sig!! > > Robert G. Freeman > Master Principal Consultant, Oracle Corporation, Oracle ACE > Author of various books on RMAN, New Features and this shorter signature > line. > Blog: http://robertgfreeman.blogspot.com > > ________________________________ > From: Suresh P <suresh.gm@xxxxxxxxx> > To: Jared Still <jkstill@xxxxxxxxx> > Cc: oracle-l@xxxxxxxxxxxxx > Sent: Tue, June 8, 2010 9:29:24 AM > Subject: Re: RMAN-20036: invalid record order > > Sorry about that, here are the versions: > > - target database: 11.1.0.7.0 > - catalog database: 11.1.0.7.0 > - RMAN executable : 11.1.0.7.0 > - catalog schema : rman_11g > > Here is the scenario: > > server A --> shadow copied and mounted to server B ---> tape > > First, second and subsequent backups *always* works from server A to tape. > > But they work only at times from server B to tape. > > > We are in the process of resyncing and de-registering and registering > the databases in RMAN; will let you know if it works consistently > after doing this. Would love to hear other suggestions. > > Thanks a lot, > -Suresh > > On Mon, Jun 7, 2010 at 12:17 PM, Jared Still <jkstill@xxxxxxxxx> wrote: >> On Mon, Jun 7, 2010 at 12:03 PM, Suresh P <suresh.gm@xxxxxxxxx> wrote: >>> >>> Hi team, >>> >>> We are getting RMAN errors on Day 2 while backing up DB to tape( for >>> both L0 or L1). Day 1's L0 full backup is always fine.. Below is the >>> error description >>> >>> >>> Recovery Manager: Release 11.1.0.7.0 - Production on Mon Jun 7 11:23:57 >>> 2010 >>> >> >> It would be helpful to know the versions and platforms of all the >> components >> involved, >> as well as the version of the Catalog Schema. >> >> Jared Still >> Certifiable Oracle DBA and Part Time Perl Evangelist >> Oracle Blog: http://jkstill.blogspot.com >> Home Page: http://jaredstill.com >> >> > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l