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