Backup controlfile recovery catalog
Hello
If I am using recovery catalog do I still need to backup controlfile with rman ?
or, can I restore controlfile using recovery catalog so that I dont need to backup controlfile explicitly?
How much effort, scripting, time and disk space does it cost to take controlfile backups ? In any case a Full Backup and/or SYSTEM Tablespace backup and/or ControlfileAutoBackupOn would cause controlfile backups.
What if catalog database is unavailable or corrupted ?
Hemant K Chitale
Similar Messages
-
PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST
제품 : RMAN
작성날짜 : 2002-05-30
PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST
===========================================================================
PURPOSE
Recovery Catalog와 Controlfile이 손상되었을 때 Oracle9i의 new feature인
Controlfile Autobackup을 이용하여 full recovery를 수행하는 방법을 알아본다
EXPLANATION
Catalog와 Controlfile이 모두 손상되었을 경우 full recovery를 수행할 수 있도록
하기 위해 oracle9i부터 Controlfile Autobackup이라는 New feature를 제공한다.
이 Feature가 활성화되면 RMAN은 자동으로 특정 형식(specific format)으로
controlfile을 backup한다 나중에 RMAN은 Recovery catalog를 access하지 않고도
이 backup을 인식할 수 있다. 이 형식은 "%F"라는 variable을 포함하는데
이 variable은 중요한 정보인 DATABASE ID를 포함하고 있다.
이것은 다음과 같은 CONFIGURE 명령을 사용하여 Turn-on 될 수 있다.
RMAN> configure controlfile autobackup on;
활성화시킨 후에 controlfile autobackup의 format을 변경할 수 있다. 그러나
이것은 반드시 variable "%F"를 포함해야만 한다. 그렇지 않으면 다음과 같은 Error
를 만나게 된다.
RMAN> configure controlfile autobackup format for
2> device type disk to 'c:\backups\%U';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 01/31/2002 11:57:21
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06492: controlfile autobackup format "c:\backups\%U" must specify a "%F"
format specifier
%F 는 RMAN이 recovery catalog 없이 backup piece를 인식하도록 Key이다.
이 Feature가 활성화 된 후에 RMAN은 BACKUP 명령을 수행할 때마다 controlfile에
대해서 별도의 backup을 수행한다. 이전에는, controlfile 은 오직 system
tablespace가 backup되는 경우에만 자동으로 backup되었다.
Database Backup은 아래와 같은 log를 출력한다.
RMAN> backup database;
Starting backup at 31-JAN-02
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PROD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\PROD\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PROD\EXAMPLE01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PROD\INDX01.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\PROD\USERS01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PROD\CWMLITE01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\PROD\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PROD\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 31-JAN-02
channel ORA_DISK_1: finished piece 1 at 31-JAN-02
piece handle=C:\BACKUPS\01DFKAIH_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:56
Finished backup at 31-JAN-02
Starting Control File Autobackup at 31-JAN-02
piece handle=C:\BACKUPS\C-4159396170-20020131-00 comment=NONE
Finished Control File Autobackup at 31-JAN-02
Note:
Controlfile backup은 backup의 끝에서 수행된다.
그리고 이 backup piece name의 두번째 string은 dbid이다(4159396170)
Current controlfile이 database와 함께 손실되고 Recovery catalog도 손상되어
사용할 수 없게 되었을 때 controlfile autobackup이 controlfile을 restore하기
위해 사용될 수 있다. restore된 controlfile은 db를 mount하고 datafile들을
restore하기 위해 사용될 수 있다.
Controlfile autobackup을 이용하여 full recovery를 수행하기 위해서는 아래와
같은 과정을 수행하면 된다.
1. Target instance를 위한 new init.ora를 생성한다. backup이 있다면 이것을
사용할 수 있다.
2. Startup nomount your new instance.
3. RMAN은 시작하나 어떤 connect statement도 수행하지 않는다.
4. RMAN prompt상에서 DBID를 설정한다. 만약 DBID를 모르면 controlfile autobackup
의 이름으로부터 이것을 알 수 있다.
RMAN> set dbid=4159396170;
5. Dbid를 설정한 후에 nomount로 startup한 target instance에 connect한다.
RMAN> connect target /
6. 만약에 backup이 disk상에 있고 controlfile autobackup을 non-default location
으로 지정하였다면 파일을 다음과 같은 위치로 옮겨 놓는다
ON UNIX : ORACLE_HOME/dbs
ON WINDOWS: ORACLE_HOME/database
RMAN은 controlfile autobackup을 찾기 위해 위 directory를 검색한다.
만약 controlfile autobackup location을 바꾸지 않으면 위 directory안에
backup이 생성되게 된다.
만약에 backup이 tape에 있다면 restore시 channel과 device를 기술하기 위해서
run block을 사용해야 한다. database가 mount되어 있지 않기 때문에
default device와 channel을 설정할 수 없다.
RMAN> run { allocate channel c_1 type 'sbt_tape'
parms "ENV=(NB_ORA_SERV=rm-wgt)";
restore controlfile from autobackup;}
7. Restore the controlfile:
RMAN> restore controlfile from autobackup;
8. Mount the database from the restored controlfile:
RMAN> alter database mount;
9. Restore datafiles:
RMAN> restore database;
10. file들을 restore한 후에 recovery를 수행할 수 있다.
이때 current online redo log가 없고 또한 backup controlfile을 사용하기
때문에 incomplete recovery를 수행해야 한다. 이를 수행하기 위해서는
"UNTIL TIME"을 설정해야 하고 open시에는 resetlogs를 사용해야 한다.
RMAN> set until time=<time stamp>;
RMAN> recover database;
RMAN> alter database open resetlogs;
REFERENCE DOCUMENT
NOTE:174623.1BACKUP Command Behavior
ON
If the backup includes datafile 1, then RMAN does not automatically include the current control file in the datafile backup set. Instead, RMAN writes the control file and server parameter file to a separate autobackup piece.
Note: The autobackup occurs regardless of whether the BACKUP or COPY command explicitly includes the current control file, for example, BACKUP DATABASE INCLUDE CURRENT CONTROLFILE.
OFF
If the backup includes datafile 1, then RMAN automatically includes the current control file and server parameter file in the datafile backup set. RMAN does not create a separate autobackup piece containing the control file and server parameter file.
BUT Dear Mohammed,
It is not working accordingly. what I did is :-
1. I switched off the AUTOBACKUP
2. Then I took whole database backup, that means it included File # 1
3. But according to above it is going to include autobackup of controlfile and spfile in the same backupset .
4. But when I asked it to restore controlfile from autobackup it said NO AUTOBACKUP FOUND.
COULD YOU PLEASE HELP ME ONCE AGAIN DEAR.
If it works accroding to above then it should have my Autobackup.
Regards
Harpreet Singh -
Recommendations for recovery catalog database backup
Hi
We are using IBM Tivoli Storage Manager for our 9i db on AIX 5.2.
I would like us to consider using rman but I am not sure of the best way we would go about backing up the database we would use for our recovery catalog.
This database that hold all the metadata would need to be backed up after every rman backup. The rman backup would go to tape, so I am assuming that the recovery catalog would be backed up on tape also.
What are the common procedures for this in other shops ?Dan A wrote:
Aman. That doc does help, and indeed it does explain
Back up the recovery catalog with the same frequency that you back up the target database.
We would be doing nightly backups, so we would have to back up the catalog with the same frequency.
The doc explains that we would use rman for these backups also, but that it would be in NOCATALOG mode so that the repository is in the control file.
And then what? Just copy this to tape? Seems that with rman there is then a need to do two backups - one of the target db and one of the recovery catalog.
Thanks.I shall suggest to take an export of the underlying schema which is holding the info in the recovery catalog. That's all which is basically required to be safe. In case , everything gets burnt regarding the catalog db,you can immediately create another db, import the user back there and things are in place. This should be a quick and easy way out of the backup of recovery catalog.
Yes if you are going to take backups every night than backup of recovery catalog schema/db nightly will be a good option. Docs are meant to promote people for RMAN so indeed they would talk about it. But its not at all a compulstion to use RMAN for recovery catalog schema's backup. If its a big catalog maintaining lots of database's info than using RMAN with all its features is a good option. If a single db is a part of it than it may not be that much big and export of teh schema alone may serve the purpose too.
HTH
Aman.... -
Switching RMAN from Recovery Catalog DB to target db controlfile
I have a doubt.
Is it possible to make RMAN to use controlfile, from using Recovery Catalog(RC) DB ?
The scenario is like this:
I have a target db and a RC db. The RMAN presently uses RC db for backup and recovery.
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup (That is, controlfile should understand backup sets, which have backed-up using RC )
Is there a way to perform these tasks?Hi,
The rman backup information in the controlfile has a limitation due to space constraints in the controlfile.
Oracle uses the parameter "control_file_record_keep_time" which defaults to 7 days to purge rman backup information from the controlfile. (So if you run rman backups the backup information in the controlfile will be automaticly purged.)
If you run rman using a catalog the controlfile will synchronize new informaton to the catalog at the start of every backup but it won't actively purge information from the catalog. So the catalog (next to other features) has the ability to store information longer than the controlfile. (Delete commands will be needed to purge information from the catalog.)
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?Just skip the connect to the catalog in your script.
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup > (That is, controlfile should understand backup sets, which have backed-up using RC )This is not easy to answer, your restore might work if the backup information is still available in the controlfile (younger than control_file_record_keep_time). Success is not related to the fact the backup was taken with the controlfile and RC at the same time.
Regards,
Tycho -
Backup policy on Grid, using RMAN and Recovery Catalog.
Hello Gurus,
I'm trying to move ahead the new features of Oracle 10g in my company. So I've already created Grid Control and will deploy Agents/Targets during the next week. I also want to switch the backup process from the archaic exp/imp to RMAN with the Recovery Catalog.
My question is such: could anybody suggest the best book or text with solutions and descriptions of backup policy, using the Grid, RMAN and Catalog? What I want to do is to create eventually the powerful and centralized storage of every database in a company and do all daily routine from there. But as long as I'm only in the very beginning I want to gain some knowledge before the bad experience, like crashed recovery catalog and no backups for all databases :-)))
Definitely I'll keep existing imp/exp and hotbackup for a long time. I'm not going to substitute all our backup strategy with one catalog. I just want to understand what will be the best practice in the backup perspective.
And at all, I wonder if you please could give me very brief answer to this question: Let's say I have a huge monster with 5 disks by 500Gb RAD0+1. Is it a bad idea to store all of them in one physical machine before they will tape to backup or it could make sense? For me it sounds a bit scary, but probably if all made with the brain it's not a bad idea?
Please, send me to some valuable and good source (like Tom Kyte or Don Burleson) Unfortunately, I didn't find anything regard the backups itself. Only pretty much general thought.
Thanks a lot in advance.
M.great!
thanks a lot!
this is definitely valuable info and I'll read right away. but as far as understand they suggest to use Data Guard, Standby and RAC which are the best ways to prevent your environment from crash. But in reality (I mean in my company) nobody is going to move to RAC at this point and I'm not sure, that they will have a chance to do in the next year. they just aren't up to it.
what I'm looking for is probably some tips and hints about backups in more or less big environment, but not as big as Oracle itself :-) unfortunately, i'm the only DBA in my surrounding. i mean, i have no friends or mentors DBAs that could seat with me in a pub and pass theirs knowledge from generation to generation :-)))
but anyway, I'll devote this week-end to this link.
thanks a lot! -
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
Hello All,
I have an instance on my LAB server. To explore more avenues in cloning a DB I did the following.
1. On my Oracle 10g Instance I fired an large query which would take atleast an hour to execute.
2. Opened another session and executed shu ABORT to shutdown the above instance abruptly.
3. Took backup of datafiles, archive logs and redologs [ prior to shu abort, I had issued ALTER DATABASE BACKUP CONTROLFILE TO TRACE]
Restoration steps:
NOMOUNT with pfile edited to hold the name of the new DB_NAME
Create control file script edited to reflect the new paths of datafile and redologs.
MOunted succesfully.
ALTER DATABASE OPEN RESETLOGS;
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1:
'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\DATAFILE\DUPLISYSTEM_553LC8QX_.DBF'
SQL> recover datafile 'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\DATAFILE\DUPLISYSTEM_553LC8QX_.DBF';
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile;
ORA-00279: change 2962256 generated at 09/03/2009 12:06:49 needed for thread 1
ORA-00289: suggestion :
F:\ORACLE\COLD_BACKUP_TRIAL\SET2\FLASH_RECOVERY_AREA\DUPLI\ARCHIVELOG\2009_09_23
\O1_MF_1_2_%U_.ARC
ORA-00280: change 2962256 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
F:\oracle\cold_backup_trial\SET2\ONLINELOG_BK\O1_MF_3_553LGCH3_.log
ORA-00342: archived log does not have expected resetlogs SCN 2933995
ORA-00334: archived log:
'F:\ORACLE\COLD_BACKUP_TRIAL\SET2\ONLINELOG_BK\O1_MF_3_553LGCH3_.LOG'
I didn't find the file it was suggesting so I tried many combinations of providing the right recovery file name :-- All the latest Archive logs and Redologs in my backup.
Still the recovery is not successful. Please let me know how can I recover my DATABASE.
Many thanks in advance.
Regards,
ValliGreetings,
If I understood, you basically have a copy of a primary database and the redo log archives of this pretty same database, you have backed up the control file of this primary database, edited it pointing all paths of your datafiles to the new location but renaming the instance name.
I am assuming that you have edited the first line of your control file to something like "CREATE CONTROLFILE SET DATABASE "DB02" RESETLOGS ARCHIVELOG", in this case are you sure that the redolog archives have not loose the sequence? In this case it will ask more and more archives and it will never end, take a look at the date and time of the thread that your instance is asking for recovery. Is your instance a production database? If it is NOT production and you are SURE that the database is completely recovered and is asking for redolog files that does not even exist you can try to add the ALLOWRESETLOGS_CORRUPTION=TRUE to your init.ora and open the db... This solution is not recommended and you should never use it on production instances... take this hint as a LAST effort to bring your db online.
Regards,
Bruno Carvalho -
Recovery using backup controlfile
hai,
can any one explain me on what is the difference between recovering database as,
recover database until cancel using backup controlfile;and
recover database until cancel;regards
ashikHi,
>>Note that you should only use a backup controlfile that was created via 'alter database backup controlfile to /path/to/your/controlfile_backup;'
Not exactly... we can use a control file that was made by a cold backup in order to recover a database.
SQL*Plus: Release 9.2.0.4.0 - Production on Tue Nov 21 21:10:19 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 93394180 bytes
Fixed Size 451844 bytes
Variable Size 67108864 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
Database opened.
SQL> create user SCOTT identified by TIGER default tablespace USERS quota unlimited on USERS;
User created.
SQL> grant connect to SCOTT;
Grant succeeded.
SQL> connect SCOTT/TIGER
Connected.
SQL> create table emp (cod number primary key);
Table created.
SQL> begin
2 for i in 1..10000 loop
3 insert into emp values (i);
4 end loop
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> select count(*) from emp;
COUNT(*)
10000
SQL> connect system/manager
Connected.
SQL> select name from v$archived_log;
NAME
/backup/archive/1_10.dbf
/backup/archive/1_11.dbf
/backup/archive/1_12.dbf
/backup/archive/1_13.dbf
4 rows selected.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 512000 1 NO CURRENT 51849 22-NOV-06
2 1 12 512000 1 YES INACTIVE 51826 22-NOV-06
3 1 13 512000 1 YES ACTIVE 51840 22-NOV-06
SQL> connect / as sysdba
Connected.
Crash Simulation
SQL> shutdown abort
ORACLE instance shut down.
Lost Data files and Control Files Simulation
SQL> host
oracle@linux:/u01> rm oradata/BDRPS/*.dbf
oracle@linux:/u01> rm oradata/BDRPS/*.ctl
oracle@linux:/u01> ls -l oradata/BDRPS/
total 1524
-rw-r----- 1 oracle oinstall 512512 2006-11-22 08:20 redo01.log
-rw-r----- 1 oracle oinstall 512512 2006-11-22 08:18 redo02.log
-rw-r----- 1 oracle oinstall 512512 2006-11-22 08:19 redo03.log
Restore Data Files and Control Files from last cold backup
oracle@linux:/u01> cp -a /backup/oradata/BDRPS/*.dbf oradata/BDRPS/
oracle@linux:/u01> cp -a /backup/oradata/BDRPS/*.ctl oradata/BDRPS/
oracle@linux:/u01> exit
exit
SQL> startup
ORACLE instance started.
Total System Global Area 93394180 bytes
Fixed Size 451844 bytes
Variable Size 67108864 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-00314: log 1 of thread 1, expected sequence# doesn't match
ORA-00312: online log 1 thread 1: '/u01/oradata/BDRPS/redo01.log'
Begin Recovery Process
SQL> recover database using backup controlfile;
ORA-00279: change 51548 generated at 11/07/2006 20:24:21 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_10.dbf
ORA-00280: change 51548 for thread 1 is in sequence #10
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52048 generated at 11/22/2006 08:18:35 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_11.dbf
ORA-00280: change 52048 for thread 1 is in sequence #11
ORA-00278: log file '/backup/archive/1_10.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52056 generated at 11/22/2006 08:18:36 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_12.dbf
ORA-00280: change 52056 for thread 1 is in sequence #12
ORA-00278: log file '/backup/archive/1_11.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52076 generated at 11/22/2006 08:18:37 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_13.dbf
ORA-00280: change 52076 for thread 1 is in sequence #13
ORA-00278: log file '/backup/archive/1_12.dbf' no longer needed for this
recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 52087 generated at 11/22/2006 08:18:37 needed for thread 1
ORA-00289: suggestion : /backup/archive/1_14.dbf
ORA-00280: change 52087 for thread 1 is in sequence #14
ORA-00278: log file '/backup/archive/1_13.dbf' no longer needed for this
recovery
In this moment, I don't have a sequence log 14 archived, then I will use the Current Log File Group for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/oradata/BDRPS/redo01.log
Log applied.
Media recovery complete.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL> connect SCOTT/TIGER
Connected.
SQL> select count(*) from emp;
COUNT(*)
10000Cheers -
RMAN backup multiple database on multiple hosts using recovery catalog
I would like to know if I create one schema called "rman" is enough for repository for backing up multiple database on multiple machines using recovery catalog.
Or is there any better way to handle for reporting peposes.
Quick response is appreciated.
OS Solairs9.
Oracle 9i.
Thanks.
SriniThis worked perfectly fine except for putting sbt in single quotes.
See the reults below.
You are just great Daljith.
Thanks and I do appreciate your help.
Still you did not answe my question.
How come I see backups from June and May even though they are from
diffierent catalog database?
RMAN> allocate channel for maintenance device type 'sbt';
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=9 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: VERITAS NetBackup for Oracle - Release 5.0GA (200)
RMAN> crosscheck backup;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_22_1_628264333 recid=17 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_21_1_628264333 recid=18 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_23_1_628265249 recid=19 stamp=628265249
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-00 recid=20 stamp=628266151
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_26_1_628266195 recid=21 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_25_1_628266195 recid=22 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-01 recid=23 stamp=628266233
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_29_1_628267004 recid=24 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_28_1_628267004 recid=25 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_30_1_628267919 recid=26 stamp=628267920
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-02 recid=27 stamp=628268832
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_32_1_628268875 recid=28 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_33_1_628268875 recid=29 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-03 recid=30 stamp=628268913
Crosschecked 30 objects
RMAN> delete expired backup;
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
11820 11804 1 1 EXPIRED SBT_TAPE bk_2_1_624018818
11821 11805 1 1 EXPIRED SBT_TAPE bk_1_1_624018817
11822 11806 1 1 EXPIRED SBT_TAPE bk_3_1_624019733
11823 11807 1 1 EXPIRED SBT_TAPE al_5_1_624020641
11824 11808 1 1 EXPIRED SBT_TAPE al_4_1_624020641
11825 11809 1 1 EXPIRED SBT_TAPE al_6_1_624020677
11826 11810 1 1 EXPIRED SBT_TAPE bk_8_1_624115253
11827 11811 1 1 EXPIRED SBT_TAPE bk_7_1_624115252
11828 11812 1 1 EXPIRED SBT_TAPE bk_9_1_624116161
11829 11813 1 1 EXPIRED SBT_TAPE al_11_1_624117067
11830 11814 1 1 EXPIRED SBT_TAPE al_10_1_624117067
11831 11815 1 1 EXPIRED SBT_TAPE bk_13_1_624365687
11832 11816 1 1 EXPIRED SBT_TAPE bk_12_1_624365686
11833 11817 1 1 EXPIRED SBT_TAPE bk_14_1_624366605
11834 11818 1 1 EXPIRED SBT_TAPE al_16_1_624367501
11835 11819 1 1 EXPIRED SBT_TAPE al_15_1_624367501
Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
deleted backup piece
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
deleted backup piece
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
deleted backup piece
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
deleted backup piece
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
deleted backup piece
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
deleted backup piece
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
deleted backup piece
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
deleted backup piece
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
deleted backup piece
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
deleted backup piece
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
deleted backup piece
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
deleted backup piece
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
deleted backup piece
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
deleted backup piece
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
deleted backup piece
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
Deleted 16 EXPIRED objects
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
11895 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11896 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11897 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11916 B F A SBT_TAPE 18-JUL-07 1 1
11926 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11927 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11935 B F A SBT_TAPE 18-JUL-07 1 1
11939 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11940 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11941 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11960 B F A SBT_TAPE 18-JUL-07 1 1
11970 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11971 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11977 B F A SBT_TAPE 18-JUL-07 1 1
RMAN>
Message was edited by:
user539835 -
Backup location in recovery catalog...
hi
can any tell me how can i check the backup locatin in recovery catalog?
ThanksBICHO wrote:
hi
can any tell me how can i check the backup locatin in recovery catalog?
It's not going to matter that you are or not using the recovery catalog . The backup location can be checked using the list backup command.
HTH
Aman.... -
Backup and restore to the other database with Recovery Catalog
Dear All,
i need your help about recovery catalog.
I have 3 databases, 2 databases version are 8.1.7.3 (HostA and HostB) and other database is 9.2.0.6 (as Catalog Database)
I want to backup files from HostA with Catalog Database into tape, then restore the backup files into HostB.
Please suggest me how to do this.
Best Regards,
abipyou can achieve this with the rman duplicate command.
if you have the same directory structure then it is a relatively simple task, if the directory structure is different then you need to use the
'set newname' syntax.
regards
Alan -
Backup and Recovery Controlfiles
Hi This is Chaitanyakumar
Dear Sir/Madam please help me how to solve this problem.
I have miss control file in my database.And i have yesterday backup.so today restore control file in specific location and start the database in mount state.
SYS>startup mount
database mounted.
SYS>recover database using backup controlfile until cancel;
ORA-00279:change 787434 generate at 06/26/2012 19:14:15 need for thread 1
ORA-00289:suggestion:/u01/app/oracle/US/archivelog/2012-06-26/01_mf_1_1_7ymhs56x_.arc
ORA-00280:change 787434 for thread 1 is in sequence #1
specify log:{<RET>=suggested|filename|auto|cancel}
i have give redolog file path:/u02/app/oracle/us/redo01.log
ORA-00326:log begins at change 851381, need earlier change 787434
ORA-00334:archived log:'/u02/app/oracle/us/undo01.log'
ORA-10879:error signaled in parallel recover slave
ORA-01547:warning:RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194:file 1 needs more recovery to be consistent
ORA-01110:datafile 1:'/u02/app/oracle/us/system01.dbf'
SYS>recover database using backup controlfile until cancel;
ORA-00275:media recovery has already been startedHi,
Please check ,if archive is its asking and if that archive is present then apply it..else you need need to apply the redo log group and then you can issue the command "alter database open resetlog"
but this command will not success once ur media recovery completed.if its not completed then u can use the one hidden parameter. -
Hi
what is command for backup & recovery recovery catalog ?
yours answer highly appreciated
Regards
kmb>
what is command for backup & recovery recovery catalog ?http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcatdb.htm#CIHFEIIH
HTH
Aman.... -
Resync recovery catalog with controlfile
Oracle :10.2.0.2
os : solaris 5.10
When doing stage refresh with production using RMAN a small pitfall happen.
By mistake i have connected to the stage database and production recovery catalog. This was done after changing the db name for stage database. Recovery catalog has taken this as new incarnation. The stage database opened with resetlogs after refresh. The db id's of both the incarnations are same.
DB_KEY DBID DBINC_KEY NAME CUR
1 3582966461 2 PRD NO
1 3582966461 578463 STG YES
Could anyone help me to resync the recovery catalog with old incarnation with production database.
Help needed ASAP.
ThanksHi,
We are following the rename datafile and then switching and opening the db with resetlogs. In this scenario we are only changing the db name not the dbid.
If it is not for a restore test the duplicate command previously mentioned does everything for you. If you want to proceed manually change the DBID manually after the restore.
Any further suggetions to resolve my issue.
The suggested unregister/register failed ? Catalog is just an optional help, losing data from the catalog does not compromise the possibilities of restorations.
Best regards
Phil -
Recovering lost data from a very old backup (disaster recovery)
Hi all,
I am trying to restore and recover data from an old DAT-72 cassette. All I know is the date when the backup was taken, that is back in November 2006. I do not know the DBID or anything else except for the date.
To recover this, I bought an internal SCSI HP c7438a DAT-72 tape drive on eBay and installed it on a machine running Windows 2003 Server SP2. I made a fresh Oracle 11g Enterprise Edition installation. HP tape drivers have been installed and Windows sees the tape drive without problem. To act as a Media Manager, I have installed Oracle Secure Backup. Oracle Secure Backup sees the HP tape drive without problems as well.
I have to admit my information about Oracle is not very in-depth. I read quite a lot of documents, but the more I read the more confused I become. The closest thing I can find to my situation is the following guide about disaster recovery:
http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmrecov.htm#1007948
I tried the suggestions in this document without success (details below).
My questions are:
1. Is it possible to retrieve data without knowing the DBID?
2. If not, is it possible to figure out the DBID from the tape? I tried to use dd in cygwin, also booted with Knoppix/Debian and Ubuntu CDs to dump the contents of the tape with dd but all of them failed to see the tape device. If there is any way to dump the raw contents of the tape on Windows, I would also welcome input.
3. Is there any way at all to recover this data from the tape given all the unknowns?
Thanks very much in advance,
C:\Program Files>rman target orcl
Recovery Manager: Release 11.2.0.1.0 - Production on Sat Mar 19 15:01:28 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database: ORCL (not mounted)
RMAN> SET DBID 676549873;
executing command: SET DBID
RMAN> STARTUP FORCE NOMOUNT; # rman starts instance with dummy parameter file
Oracle instance started
Total System Global Area 778387456 bytes
Fixed Size 1374808 bytes
Variable Size 268436904 bytes
Database Buffers 503316480 bytes
Redo Buffers 5259264 bytes
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt;
4> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
5> }
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:03:26
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt
4> PARMS 'SBT_LIBRARY=C:\WINDOWS\SYSTEM32\ORASBT.DLL';
5> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
6> }
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:04:56
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
-----------------------------------Hi 845725,
If the backups were created with OSB might be you can query the tape with obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htmTo list pieces you could use <lspiece> within obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htm#BHBBIFFEIf this works you should be able to identify the controlfile autobackup if it has the standard naming < c-dbid-date-xx > and you than know the DBID or you are able to restore a controlfile from a backup piece in the output list.
Might be you have to install 9i or 10g rdbms software as 11g was released a year later in 2007.
Anyway goodluck.
Regards,
Tycho -
RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...
Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AMThis Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.
Maybe you are looking for
-
Screen resolution gone poor in Mac Mini
I cannot get optimum resolution on my Mac Mini. Just a day before I disconnected all the cords, including power and HDMI, just to move my Mac Mini (OS X 10.9.4) to a different room, and connected it back as it was. (Really speaking only two cords) an
-
Sending submitted pdf with notification
Hi we only need to get submitted pdf forms for us to process and it is a real pain to have to go and download them one by one. I have set up the notify me if we have a form. Is there anyway it could send that form directly to me with the notificatio
-
My bridge pause all the time. I have to wait 30 seconds after selecting a picture or click the right button of the mouse. I have installed a new windows 8.1, and a fresh CD6. But still these problems in Bridge. No problems in Photoshop. What to do
-
Nine key not working on macbook pro 2008
Trying to figure out if anone has solved the "Nine" key disfunction. It was intermitent for a while and now I get nada. Any help would be great. I have tried all the reboots and safe mode start-ups. I'm using Lion 10.7.3
-
How can I download a dvd on my mac osx 10.7.4?
How can I download a dvd on my mac osx 10.7.4?