Re: Rman Duplicating Error--Strange Though
- From: Peter McLarty <peter.mclarty@xxxxxxxxxxxxxxxxxx>
- To: avadhanimys@xxxxxxxxx
- Date: Fri, 21 Dec 2007 23:17:06 +1000
Hi
Some time when you have a chance run rman with the the debug on and you
will see all what happens,
RMAN communicates with the production to find out what was the last
archivelog written, as it duplicates right up to the last completed
archivelog, and the only true source is that, If you clone across
systems you always need to make available to the server where the clone
is going the archivelogs past the backup you are using to clone from.
Cheers
Peter McLarty
Consultant, Pacific DBMS Pty Ltd
peter.mclarty@xxxxxxxxxxxxxxxxxx
Database Consultants across Asia Pacific
15 Barron Road
Margate, QLD 4019 Australia
work: 61 7 3883 1086
mobile: 61 4 0209 4238
fax: 61 7 3883 1016
Want a signature like this?
On Fri, 2007-12-21 at 18:25 +0530, Avadhani mys wrote:
> Hi All,
>
> There was a request to refresh production database to Test database
> and the version is 10gR1, Now we are getting the following strange
> error in Production database Alertlog, I searched in google and
> Metalink no help, If any one knows please help, But our Production
> system is up and running..fine
>
> My question is why the error is popping up in production database when
> we are no way connected to Prod database and we when we are Restoring
> from Catalog database.Please help me to understand from your
> expertise.
>
>
> Alert
>
> =======================
>
> alter database recover datafile list clear
> Thu Dec 20 20:47:03 2007
> Completed: alter database recover datafile list clear
> Thu Dec 20 20:47:03 2007
> alter database recover datafile list
> 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12
> Completed: alter database recover datafile list
> 1 , 2 , 3 ,
> Thu Dec 20 20:47:03 2007
> alter database recover if needed
> start until time 'DEC 17 2007 22:09:50'
> Media Recovery Start
> Thu Dec 20 20:47:03 2007
> Media Recovery failed with error 1124
> ORA-283 signalled during: alter database recover if needed
> ============================================
>
>
> Script
>
> =========================================
> connect catalog rman/manager@Catalog
> connect target sys/xxxxxx@Prod
> connect auxiliary /
> run {
> set until time "to_date('Dec 17 2007 22:09:50','Mon DD YYYY
> HH24:MI:SS')";
> set newname for datafile 1 to '/u01/oradata/DBID/system01.dbf';
> set newname for datafile 2 to '/u02/oradata/DBID/sie_idx02.dbf';
> set newname for datafile 3 to '/u01/oradata/DBID/sysaux01.dbf';
> set newname for datafile 4 to '/u01/oradata/DBID/achi_data01.dbf';
> set newname for datafile 5 to '/u02/oradata/DBID/achi_idx01.dbf';
> set newname for datafile 6 to '/u01/oradata/DBID/users01.dbf';
> set newname for datafile 7 to '/u01/oradata/DBID/siedata01.dbf';
> set newname for datafile 8 to '/u02/oradata/DBID/undotbs01.dbf';
> set newname for datafile 9 to '/u02/oradata/DBID/tools01.dbf';
> set newname for datafile 10 to '/u01/oradata/DBID/sie02.dbf';
set newname for datafile 11 to '/u02/oradata/DBID/ddata01.dbf';
duplicate target database to DBID logfile
group 1 ('/u01/oradata/DBID/log01a.dbf','/u02/oradata/DBID/log1b.dbf') size
250m reuse,
group 2 ('/u01/oradata/DBID/log02a.dbf','/u02/oradata/DBID/log2b.dbf') size
250m reuse,
group 3 ('/u01/oradata/DBID/log03a.dbf','/u02/oradata/DBID/log3b.dbf') size
250m reuse;
recover clone database until time "to_date('Dec 2007 22:09:50','Mon DD YYYY
HH24:MI:SS')";
alter clone database open resetlogs;
}
========================================
Other related posts:
