Trying to restore RMAN backup in new server, got error RMAN-06172 [message #512718] |
Tue, 21 June 2011 15:43 |
jbetetayahoocom
Messages: 6 Registered: October 2010
|
Junior Member |
|
|
Hello,
We are using Oracle 10g R2 in Windows Server 2003. I'm trying to
restore a database in a new server, using RMAN backups.
Our external consultant configured RMAN scripts for full and
incremental backups but never tested them . Since he just doesn't show up, I'm forced to tested them, restoring the whole database in a new server.
My instance is named MTDPROD, and I will create all from scratch.
At current server, RMAN files are generated in:
//192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/RMAN
At new server, I run all these commands:
C:\>oradim -new -sid MTDPROD -intpwd mtdprod
Instance created
-- I created the relevant folder hierarchy under <ORACLE_BASE>
directory
-- Then, I created the relevant directories for Oracle Database, as
follows:
--a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>
\admin'
-- directory,
-- b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata'
directory; in my
-- case MTDPROD
C:\> set oracle_sid=MTDPROD
C:\> rman
RMAN> connect target sys
connected to target database (not started)
-- My DBID is 2169285856
RMAN> set dbid=2169285856
RMAN> startup force nomount;
RMAN> restore spfile from autobackup db_recovery_file_dest='//
192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/RMAN' db_name='MTDPROD';
Messages:
Starting restore at 21-JUN-11
using channel ORA_DISK_1
recovery area destination: //192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/
RMAN
database name (or database unique name) used for search: MTDPROD
channel ORA_DISK_1: no autobackups found in the recovery area
channel ORA_DISK_1: looking for autobackup on day: 20110621
channel ORA_DISK_1: looking for autobackup on day: 20110620
channel ORA_DISK_1: looking for autobackup on day: 20110619
channel ORA_DISK_1: looking for autobackup on day: 20110618
channel ORA_DISK_1: looking for autobackup on day: 20110617
channel ORA_DISK_1: looking for autobackup on day: 20110616
channel ORA_DISK_1: looking for autobackup on day: 20110615
channel ORA_DISK_1: no autobackup in 7 days found
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of restore command at 06/21/2011 12:50:28
RMAN-06172: no autobackup found or specified handle is not a valid
copy or piece
The RMAN backups are generating in //192.168.1.149/g$/XXXSRV4-ArcLogs/
MTDPROD/RMAN.
By instance, I see a lot of this kind of files:
- FULL_MTDPROD_20110529_386_1.BAK
- INCR_MTDPROD_20110621_480_7.BAK
And only see these two files:
- C-2169285856-20110527-03
- C-2169285856-20110527-04
It seems that this C-2169285856-.... files only were on 27/05/2011 and
then no more.
However, the FULL_... and INCR_.. files are generated every day.
The FULL is generated at the end of each month and INCR is generated
every day.
This is the backfull.sql:
run {
allocate channel c1 type disk maxpiecesize=4G;
CROSSCHECK archivelog all;
backup
incremental level 0
format '\\192.168.1.149\g$\XXXSRV4-arclogs\MTDPROD\RMAN\FULL_
%d_%T_%s_%p.bak'
filesperset 8
database include current controlfile;
SQL 'alter system archive log current';
backup
format '\\192.168.1.149\g$\XXXSRV4-arclogs\MTDPROD\RMAN\ARC_
%d_%T_%s_%p.bak'
archivelog all delete all input;
}
This is the backincr.sql:
run {
allocate channel c1 type disk maxpiecesize=4G;
CROSSCHECK archivelog all;
backup
incremental level 1 cumulative
format '\\192.168.1.149\g$\XXXSRV4-arclogs\MTDPROD\RMAN\INCR_
%d_%T_%s_%p.bak'
filesperset 8
database include current controlfile;
SQL 'alter system archive log current';
backup
format '\\192.168.1.149\g$\XXXSRV4-arclogs\MTDPROD\RMAN\ARC_
%d_%T_%s_%p.bak'
archivelog all delete all input;
}
[Updated on: Tue, 21 June 2011 23:43] by Moderator Report message to a moderator
|
|
|
Re: Trying to restore RMAN backup in new server, got error RMAN-06172 [message #512726 is a reply to message #512718] |
Tue, 21 June 2011 18:28 |
|
Mahesh Rajendran
Messages: 10707 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
>>RMAN-06172: no autobackup found or specified handle is not a valid
that is expected.
By default, RMAN will look for only 7 days with autobackup.
Either you specify the specific file to restore or
Try something like this. Specify the maxdays option that will include the old file.
For example, following will ask RMAN to search for last 90 days in its default location.
restore spfile from autobackup maxdays=90;
restore controlfile from autobackup maxdays=90;
[Updated on: Tue, 21 June 2011 18:29] Report message to a moderator
|
|
|
|
Re: Trying to restore RMAN backup in new server, got error RMAN-06172 [message #512729 is a reply to message #512726] |
Tue, 21 June 2011 19:00 |
jbetetayahoocom
Messages: 6 Registered: October 2010
|
Junior Member |
|
|
I tried with maxdays 90. No success.
RMAN> restore spfile from autobackup db_recovery_file_dest='//
192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/RMAN' db_name='MTDPROD'maxdays 90;
What is RMAN looking for? Incremental bkp files? The full bkp file? The files like: C-2169285856-20110527-03 or C-2169285856-20110527-04 ?
As I noted, there are only two files of this kind:
- C-2169285856-20110527-03
and
- C-2169285856-20110527-04
Maybe there is the error. These files seem to have been created 27/05/2011 and there are no more.
External consultant started to RMAN backup on 16/05/2011.
My RMAN parameters in Source Server:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\192.168.1.149
\g$\XXXSRV4-arclogs\MTDPROD\RMAN\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '\\192.168.1.149\G$\XXXSRV4-ARCLOGS\MTDPROD\RMAN\CTRLSHOT.CTL';
[Updated on: Tue, 21 June 2011 23:43] by Moderator Report message to a moderator
|
|
|
|
Re: Trying to restore RMAN backup in new server, got error RMAN-06172 [message #512854 is a reply to message #512751] |
Wed, 22 June 2011 08:55 |
jbetetayahoocom
Messages: 6 Registered: October 2010
|
Junior Member |
|
|
Thank you Mahesh, for rewieng my question.
I tried restore command with path:
\\192.168.1.149\g$\XXXSRV4-ArcLogs\MTDPROD\RMAN
or
//192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/RMAN
Same results:
RMAN> restore spfile from autobackup db_recovery_file_dest='\\192.168.1.149\g$\XXXSRV4-ArcLogs\MTDPROD\RMAN' db_name='MTDPROD' maxdays 90;
Starting restore at 22-JUN-11
using channel ORA_DISK_1
recovery area destination: \\192.168.1.149\g$\XXXSRV4-ArcLogs\MTDPROD\RMAN
database name (or database unique name) used for search: MTDPROD
channel ORA_DISK_1: no autobackups found in the recovery area
channel ORA_DISK_1: looking for autobackup on day: 20110622
channel ORA_DISK_1: looking for autobackup on day: 20110621
channel ORA_DISK_1: looking for autobackup on day: 20110620
channel ORA_DISK_1: looking for autobackup on day: 20110619
channel ORA_DISK_1: looking for autobackup on day: 20110618
channel ORA_DISK_1: looking for autobackup on day: 20110617
channel ORA_DISK_1: looking for autobackup on day: 20110616
channel ORA_DISK_1: looking for autobackup on day: 20110615
channel ORA_DISK_1: looking for autobackup on day: 20110614
channel ORA_DISK_1: looking for autobackup on day: 20110613
channel ORA_DISK_1: looking for autobackup on day: 20110612
channel ORA_DISK_1: looking for autobackup on day: 20110611
channel ORA_DISK_1: looking for autobackup on day: 20110610
channel ORA_DISK_1: looking for autobackup on day: 20110609
channel ORA_DISK_1: looking for autobackup on day: 20110608
channel ORA_DISK_1: looking for autobackup on day: 20110607
channel ORA_DISK_1: looking for autobackup on day: 20110606
channel ORA_DISK_1: looking for autobackup on day: 20110605
channel ORA_DISK_1: looking for autobackup on day: 20110604
channel ORA_DISK_1: looking for autobackup on day: 20110603
channel ORA_DISK_1: looking for autobackup on day: 20110602
channel ORA_DISK_1: looking for autobackup on day: 20110601
channel ORA_DISK_1: looking for autobackup on day: 20110531
channel ORA_DISK_1: looking for autobackup on day: 20110530
channel ORA_DISK_1: looking for autobackup on day: 20110529
channel ORA_DISK_1: looking for autobackup on day: 20110528
channel ORA_DISK_1: looking for autobackup on day: 20110527
channel ORA_DISK_1: looking for autobackup on day: 20110526
channel ORA_DISK_1: looking for autobackup on day: 20110525
channel ORA_DISK_1: looking for autobackup on day: 20110524
channel ORA_DISK_1: looking for autobackup on day: 20110523
channel ORA_DISK_1: looking for autobackup on day: 20110522
channel ORA_DISK_1: looking for autobackup on day: 20110521
channel ORA_DISK_1: looking for autobackup on day: 20110520
channel ORA_DISK_1: looking for autobackup on day: 20110519
channel ORA_DISK_1: looking for autobackup on day: 20110518
channel ORA_DISK_1: looking for autobackup on day: 20110517
channel ORA_DISK_1: looking for autobackup on day: 20110516
channel ORA_DISK_1: looking for autobackup on day: 20110515
channel ORA_DISK_1: looking for autobackup on day: 20110514
channel ORA_DISK_1: looking for autobackup on day: 20110513
channel ORA_DISK_1: looking for autobackup on day: 20110512
channel ORA_DISK_1: looking for autobackup on day: 20110511
channel ORA_DISK_1: looking for autobackup on day: 20110510
channel ORA_DISK_1: looking for autobackup on day: 20110509
channel ORA_DISK_1: looking for autobackup on day: 20110508
channel ORA_DISK_1: looking for autobackup on day: 20110507
channel ORA_DISK_1: looking for autobackup on day: 20110506
channel ORA_DISK_1: looking for autobackup on day: 20110505
channel ORA_DISK_1: looking for autobackup on day: 20110504
channel ORA_DISK_1: looking for autobackup on day: 20110503
channel ORA_DISK_1: looking for autobackup on day: 20110502
channel ORA_DISK_1: looking for autobackup on day: 20110501
channel ORA_DISK_1: looking for autobackup on day: 20110430
channel ORA_DISK_1: looking for autobackup on day: 20110429
channel ORA_DISK_1: looking for autobackup on day: 20110428
channel ORA_DISK_1: looking for autobackup on day: 20110427
channel ORA_DISK_1: looking for autobackup on day: 20110426
channel ORA_DISK_1: looking for autobackup on day: 20110425
channel ORA_DISK_1: looking for autobackup on day: 20110424
channel ORA_DISK_1: looking for autobackup on day: 20110423
channel ORA_DISK_1: looking for autobackup on day: 20110422
channel ORA_DISK_1: looking for autobackup on day: 20110421
channel ORA_DISK_1: looking for autobackup on day: 20110420
channel ORA_DISK_1: looking for autobackup on day: 20110419
channel ORA_DISK_1: looking for autobackup on day: 20110418
channel ORA_DISK_1: looking for autobackup on day: 20110417
channel ORA_DISK_1: looking for autobackup on day: 20110416
channel ORA_DISK_1: looking for autobackup on day: 20110415
channel ORA_DISK_1: looking for autobackup on day: 20110414
channel ORA_DISK_1: looking for autobackup on day: 20110413
channel ORA_DISK_1: looking for autobackup on day: 20110412
channel ORA_DISK_1: looking for autobackup on day: 20110411
channel ORA_DISK_1: looking for autobackup on day: 20110410
channel ORA_DISK_1: looking for autobackup on day: 20110409
channel ORA_DISK_1: looking for autobackup on day: 20110408
channel ORA_DISK_1: looking for autobackup on day: 20110407
channel ORA_DISK_1: looking for autobackup on day: 20110406
channel ORA_DISK_1: looking for autobackup on day: 20110405
channel ORA_DISK_1: looking for autobackup on day: 20110404
channel ORA_DISK_1: looking for autobackup on day: 20110403
channel ORA_DISK_1: looking for autobackup on day: 20110402
channel ORA_DISK_1: looking for autobackup on day: 20110401
channel ORA_DISK_1: looking for autobackup on day: 20110331
channel ORA_DISK_1: looking for autobackup on day: 20110330
channel ORA_DISK_1: looking for autobackup on day: 20110329
channel ORA_DISK_1: looking for autobackup on day: 20110328
channel ORA_DISK_1: looking for autobackup on day: 20110327
channel ORA_DISK_1: looking for autobackup on day: 20110326
channel ORA_DISK_1: looking for autobackup on day: 20110325
channel ORA_DISK_1: no autobackup in 90 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/22/2011 06:20:54
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
I attach in one file log full and incrmental rman backup.
|
|
|
Re: Trying to restore RMAN backup in new server, got error RMAN-06172 [message #512913 is a reply to message #512854] |
Wed, 22 June 2011 16:21 |
|
Mahesh Rajendran
Messages: 10707 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
Your backup has issues.
From your logfile.
channel c1: specifying datafile(s) in backupset
including current controlfile in backupset
channel c1: starting piece 1 at 22-JUN-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 06/22/2011 00:37:49
RMAN-10038: database session for channel c1 terminated unexpectedly
Edit:
Check the alert_sid.log for the primary database.
There should be some relevant errors.
[Updated on: Wed, 22 June 2011 17:29] Report message to a moderator
|
|
|