BACKUP RMAN LIST COMMAND
I am using the following commands.RMAN > sql ' alter session set nls_date_format = "HH24:MI:SS mon-dd-yyyy";
2 > database reports sunk;
3 > report need backup days database 2.
4 > list backup;
5 > "exit";
BS key Type LV size device Type time elapsed time.
6249525 complete 68G SBT_TAPE 01:38:05 * 25 October 2010 *.
BP key: 6249547 status: AVAILABLE Tag: TAG20101025T040741
Even after setting nls_date_format, deadline list backup command does not return exact time... He is back just the date...
How to get completion times in the RMAN BACKUP COMMAND LIST with hour, minute and second details... Please let me know
I use the catalog database... database version 9i and catalog db target version is 10 g.
Thank you
DB
Try with double quotes:
export NLS_DATE_FORMAT="DD-MON-YYYY HH24:MI:SS"
Tags: Database
Similar Questions
-
Relationship between current incarnation & backup / RMAN-20011
Hello
I have
the following situation in RMAN:
Incarnations:
>
RMAN > list incarnation;
List of Incarnations of the database
DB key Inc key STATE ID DB name DB reset reset time SNA
------- ------- -------- ---------------- --- ---------- ----------
133 146 TESTDB 2528045035 PARENT 05-SEPT 1.-10
133 134 TESTDB 2528045035 CURRENT 972274 2 MARCH 11
133 548 TESTDB 2528045035 ORPHAN 996374 MARCH 2, 11
133 646 TESTDB 2528045035 ORPHAN 996490 4 MARCH 11
133 460 TESTDB 2528045035 ORPHAN 997986 MARCH 2, 11
>
Backups:
>
RMAN > list backup;
List of backup sets
===================
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
56,57 M 176 00:00 DRIVE: 42 MARCH 2, 11
BP key: 177 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100444
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
List of newspapers archived in defined backup 176
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 2 977121 2 MARCH 11 988286 MARCH 2, 11
1 3 988286 2 MARCH 11 994189 MARCH 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
Incr 187 0 M DISK 00:15:42 999,72 2 March 11
BP key: 190 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100531
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of defined backup data files 187
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
1 0 incr 994637 /CDATA/TESTDB/system01.dbf March 2, 11
2 0 994637 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
3 0 incr 994637 /CDATA/TESTDB/undotbs01.dbf March 2, 11
4 0 incr 994637 /CDATA/TESTDB/users01.dbf March 2, 11
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
DISK 4,48 M 201 00:00: 01 MARCH 2, 11
BP key: 206 location: AVAILABLE Tablet: NO Tag: TAG20110302T102124
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
List of newspapers archived on backup the value 201
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 4 994189 2 MARCH 11 996336 MARCH 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
214 full 9.36 M DISK 00:00:10 March 2, 11
BP key: 216 situation: AVAILABLE Tablet: NO Tag: TAG20110302T102129
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996373 cash time: March 2, 11
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
244 757,50 K DISK 00:00:01 MARCH 2, 11
BP key: 247 Situation: AVAILABLE Tablet: NO Tag: TAG20110302T103137
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
List of newspapers archived in backup set 244
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 5 996336 2 MARCH 11 997210 MARCH 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
261 incr 0 M DISK 00:13:29 1001,02 March 2, 11
BP key: 263 situation: AVAILABLE Tablet: NO Tag: TAG20110302T103138
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of defined backup data files 261
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
1 0 incr 997238 /CDATA/TESTDB/system01.dbf March 2, 11
2 0 997238 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
3 0 incr 997238 /CDATA/TESTDB/undotbs01.dbf March 2, 11
4 0 incr 997238 /CDATA/TESTDB/users01.dbf March 2, 11
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
279 742,00 K DISK 00:00:01 MARCH 2, 11
BP key: 284 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104517
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
List of newspapers archived on backup worth 279
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 6 997210 2 MARCH 11 997953 MARCH 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
297 full 9.36 M DISK 00:00:10 March 2, 11
BP key: 299 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104519
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 997985 cash time: March 2, 11
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
* 342 438,00 K DISK 00:00:00 MARCH 2, 11 *.
BP key: 345 location: AVAILABLE Tablet: NO Tag: TAG20110302T104935
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
List of newspapers archived on backup worth 342
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
* 1 7 997953 2 MARCH 11 998260 2 MARCH 11 *.
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* 364 incr 0 M DISK 00:14:34 1001,65 2 March 11 *.
BP key: 366 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104937
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of defined backup data files 364
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
* 1 0 incr 998289 /CDATA/TESTDB/system01.dbf* March 2, 11
* 2 0 998289 /CDATA/TESTDB/sysaux01.dbf* incr 2 March 11
* 3 0 incr 998289 /CDATA/TESTDB/undotbs01.dbf* March 2, 11
* 4 0 incr 998289 /CDATA/TESTDB/users01.dbf* March 2, 11
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
* 7,58 M 387 00:00 DISK: 02 MARCH 2, 11 *.
BP key: 392 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110421
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
List of newspapers archived in backup set 387
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
* 1 8 998260 2 MARCH 11 1000465 2 MARCH 11 *.
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* 410 full 9.36 M DISK 00:00:10 March 2, 11 *.
BP key: 412 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110425
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 1000507 cash time: March 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
483 full 9.36 M DISK 00:00:05 March 2, 11
BP key: 484 situation: AVAILABLE Tablet: NO Tag: TAG20110302T113759
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 998081 cash time: March 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
571 full 9.36 M 04:00:00 disc 2 March 11
BP key: 572 situation: AVAILABLE Tablet: NO Tag: TAG20110302T121754
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996489 cash time: March 2, 11
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
667 full 9.36 M DISK 00:00:18 March 4, 11
BP key: situation 668: AVAILABLE Tablet: NO Tag: TAG20110304T132050
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE included: Modification Date: March 4, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996596 cash time: March 4, 11
RMAN >
>
I want to rebuild the database with the backup (bold text).
And I get the error after you run the following script:
>
RMAN > RUN
2 > {}
3 > # STARTUP NOMOUNT;
4 > # RESTORE SPFILE to ' / u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' tag "TAG20110302T063849".
5 > # SHUTDOWN IMMEDIATE;
6 > STARTUP NOMOUNT;
7 > RESTORE CONTROLFILE tag "TAG20110302T110425".
8 > STARTUP MOUNT;
9 > SET up to this THAT SNA 1000507.
10 > RESTORE database;
11 > RECOVER DATABASE;
12 > ALTER DATABASE OPEN RESETLOGS;
{13 >}
database is already started
From restoration to March 4, 11
using channel ORA_DISK_1
channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 piece reading
channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag = TAG20110302T110425
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:00:15
output file name=/CDATA/TESTDB/control01.ctl
output file name=/CFLASH/TESTDB/control02.ctl
Restoration finished in March 4, 11
database is already started
mounted database
output channel: ORA_DISK_1
executing command: SET until clause
From restoration to March 4, 11
From implicit overlapping backup 4 March 11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 136 type of device = DISK
Cut 11 objects
Backup of implicit overlap finished March 4, 11
Starting copy of implicit intersection to March 4, 11
using channel ORA_DISK_1
Copy of implicit cross ended up at March 4, 11
the search for all files in the recovery area
cataloging files...
cataloging done
List of cataloged files
=======================
File name: /CFLASH/TESTDB/archivelog/2011_03_04/o1_mf_1_1_6q1k25xs_.arc
using channel ORA_DISK_1
channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_DISK_1: restore datafile 00001 to /CDATA/TESTDB/system01.dbf
channel ORA_DISK_1: restore datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
channel ORA_DISK_1: restore datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
channel ORA_DISK_1: restore datafile 00004 in /CDATA/TESTDB/users01.dbf
channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 piece reading
channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag = TAG20110302T104937
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:13:45
Restoration finished in March 4, 11
From back to March 4, 11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 04/03/2011 13:47:17
RMAN-06004: error ORACLE recovery catalog database: RMAN-20011: target database incarnation is not common in the recovery catalog
>
How will I know the right embodiment to restore power?
Help, please
Reagards
hqr200475
Edited by: hqt200475 the 04.03.2011 06:19To verify valid backups in the current version number:
recoverable backup list;
Definition of this statement:
/*
Specifies the data backups or copies file whose status in the repository is AVAILABLE and which can be used for restoration and recovery in the course of the incarnation target database. This list includes all backups and copies except the incremental backups that have no valid parent to which the differential can be applied.
*/Werner
-
Oracle 10.2.0.4
I assigned a band unit that has a drawn backupset of another data base and trying to backup from the list. Am I missing syntax here?
RMAN > run
2 > {allocate channel sbt type ch01
3 > format = '% d_data_set % s_piece % p_ T_ %U '.
4 > PARMS 'ENV=(TDPO_OPTFILE=/a0167/oracle/tivoli/ndk8oasu181.opt) ';
5 > list backup;
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-00558: error occurred during parsing of order entry
RMAN-01009: syntax error: found 'list': expected an of: "{assign, modify, save, beginline, blockrecover, catalog, edit, copy, convert, duplication, configure, duplicate, debug, delete, run, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restoration, resync,}, together, setlimit, sql, switch, start, stop, send, display, transport, post.
RMAN-01007: column 1 row 5 file: entry standard
Thank you!!Hi, you can not use "backup list" command in block execution (run {}). You can only use it outside block 'run '.
-
Backups RMAN does not match its retention policy
Hello
I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.
For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.
DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.
I have clear and defined retention to 14 days over policy but doesn't seem to work.
I would be grateful suggestion (s) about the strange.
Thank you very much.
Best regards
John-MK wrote:
Hello
I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.
For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.
DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.
I have clear and defined retention to 14 days over policy but doesn't seem to work.
I would be grateful suggestion (s) about the strange.
Thank you very much.
Best regards
We would need to know what kind of backups and where they were taken. Imagine this scenario:
7-day retention strategy.
Level 0 incremental backup taken on Sunday
Backup incremental level 1 taken Monday at Sam.
Let's say that October 1 is a Sunday, so we take an Inc.-0 backup on October 1 and again on Oct. 8.
Now let's say that we are at 10 Oct. Our 7-day retention policy dicatates that we can recover any day of return to 3 Oct.
The only way we can find to 3 Oct is to start with this backup Inc.-0 Oct. 1.
Recovery all starts with last Inc.-0 backup before the point in time to be recovered. In a normal life, regularly cycling calendar of backups, actually will end you with backups 1 day far twice also older than your retention period.
A more extreme example. Same period of retention of 7 days, but after a single backup Inc. - 0, you don't take any backups of 3 months. That only a backup is always necessary to apply your window of recovery and therefore is not obsolete, despite the fact it is 3 months old and your recovery window is 7 days.
Also, you mention "expiration". Regarding backups oracle, 'expired' isn't the same as "obsolete".
"Obsolète" means "is more necessary to apply the principle of recovery."
"Expired" is a little more complex.
When a backup is performed, or an archivelog is written, an account of which is written in the repository. When you do a 'crossover' rman, these repository records are compared to reality - to see if the archivelog or saved backup file actually exists. Maybe someone used an OS command to delete them. Any file found "go walkabout" have their directory of files marked as "expired". An rman "expiration to delete" then delete the records in the repository.
-
The front last backup RMAN delete file even if redundancy on 3 days
Dear Oracle gurus
My environment
Node 2 11g R2 Cluster with ASM
Database 11.2.0.3.0
I got to know that file below is delete by RMAN even if redundancy on 3 days
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed
can you please provide a reason or recommendations to correct the backup configuration
=========Before Backup========================================
917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
* 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
===========================================================================
===================After Backup========================================================
-rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
==================================================================================
Configuration of RMAN
bash-$3.2 rman target /.
Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID = 3171721304)
RMAN > show all.
using the control file of the target instead of recovery catalog database
RMAN settings for database with db_unique_name ORCLDR are:
CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default
RMAN > exit
=========================================================================================
RMAN Full Backup Script
RMAN level 0
#! / bin/bash
. /Home/Oracle/.bash_profile
logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
run
{
allocate channels ch1 type disk maxpiecesize = 1024 M;
allocate channel ch2 type disk maxpiecesize = 1024M;
database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
include current controlfile more archivelog delete all entries
tag 'datafile_full ';
}
delete noprompt obsolete;
EXIT;
EXPRESSIONS OF FOLKLORE
=========================================================================================
Backup logs
-bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log
Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID = 3171721304)
RMAN >
RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
using the control file of the target instead of recovery catalog database
allocated channel: ch1
channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type
allocated channel: ch2
channel ch2: SID = 5 = device type ORCLdr2 = DISK instance
From backup may 19, 13
Current archived log
archived journal of wire 1 to jump with sequence 84; already saved
skip the journal archived thread 2 with sequence 79; already saved
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from 3 to 19 May 13 piece
channel ch2: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:01:10
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
channel ch1: finished part 3 to 19 May 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:01:25
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
Backup finished on 19 May 13
From backup may 19, 13
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
channel ch1: from room 1 to May 19, 13
channel ch2: start the incremental level 0 datafile backup set
channel ch2: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:22
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
channel ch2: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: complete set of backups, time: 00:00:22
including the current control in the backup set file
channel ch1: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:01
Backup finished on 19 May 13
From backup may 19, 13
Current archived log
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:00:01
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:00:01
channel ch2: archived deletion or newspapers
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
Backup finished on 19 May 13
From control file and SPFILE Autobackup 19 May 13
room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
File control finished and Autobackup SPFILE to 19 May 13
output channel: ch1
output channel: ch2
RMAN >
RMAN >
RMAN retention policy apply to the order
RMAN retention policy is set to 3 redundancy
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
Remove the following obsolete backups and copies:
Making key time filename/handle type
-------------------- ------ ------------------ --------------------
8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
Game save 40 9 May 13
Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Save game 39 may 9, 13
Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Backs up the entire 42 9 May 13
Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
Backs up the entire 43 9 May 13
Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
Save game 46 may 10, 13
Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
Game backup 45 may 10, 13
Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
Save game 47 10 May 13
Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 48 may 10, 13
Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 50 10 May 13
Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
Backs up the entire 51 may 10, 13
Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
Backs up the entire 54 may 11, 13
Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
Save game 53 may 11, 13
Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
Save game 55 may 11, 13
Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 56 may 11, 13
Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 58 may 11, 13
Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
Save game 59 may 11, 13
Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
Backs up the entire 62 12 May 13
Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
Save game 61 12 May 13
Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
Save game 77 14 May 13
Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
Game backup 101 16 May 13
Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
Backs up the entire 114 18 May 13
Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
20 objects deleted
RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
RMAN-06208: status do not match. Use the OVERLAP command to set status
RMAN-06210: list of relevant objects
RMAN-06211: =.
RMAN-06212: filename/Type object Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup
RMAN >
RMAN >
Complete recovery manager.
-bash - $3.2
Concerning
Hitgon
Published by: hitgon on May 20, 2013 02:09
Published by: hitgon on May 20, 2013 02:15It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.
Hemant K Collette
-
Oracle 11.2.0.2
Question: Via TSM I need to copy a backup rman since a TSM server to the disk.
I have rman backups who have written on tape SBT (TSM server). I can get the handle with the backup from the list, but how to find the path where it is written. Looking at the tdpo.opt file has a value for TDPO_FS, which is a virtual drive. I can't use backup because rman backup set which works only from disk to tape and NO tape on the disc. So I have to try to get this backupset through TSM commands.
Any help would be appreciated!If you want to copy the TSM backups on disk, you can simulate a scenario to "restore to a new host. The TSM API knows where to find the tape backup.
http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmadvre.htm#i1007814
Otherwise, you have tom consult TSM staff, I am sure that 'somewhere' in the TSM environment that real places are stored. But who does not directly to RMAN/Oracle.
Werner
-
last available retention policy backup RMAN
Hi all
I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 22 days see below
Published by: user8363520 on September 28, 2011 15:08RMAN> show all; RMAN configuration parameters for database with db_unique_name TEST are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1; CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default List of Backup Sets ===
Published by: user8363520 on September 28, 2011 15:09user8363520 wrote:
Hi allI'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 8 days see below
RMAN> show all; RMAN configuration parameters for database with db_unique_name TRGT are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/cont_spfile_%F'; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_ctl_spfile_%F'; CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1; CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/%d_%t_%s_%p_%T'; CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE'; CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/112_64/dbs/snapcf_TRGT.f'; # default RMAN>but when I login and backup list... back were taken log time back still shows as AVAILABLE... I thought that it would be marked obsolete or expired... any reason why his does not like that? I had to change my couple of time format is why it dose not match the above... but just that I do not understand why his watch available?
They are not 'marked' as outdated. They are "evaluated" as obsolete when necessary to meet demand for obsolete series. Notice what happens when I take three backups with a REDUNDANCY 2 retention policy
RMAN> show retention policy; using target database control file instead of recovery catalog RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; RMAN> backup database; Starting backup at 27-SEP-11channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25 Finished backup at 27-SEP-11 Starting Control File and SPFILE Autobackup at 27-SEP-11 piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 27-SEP-11 RMAN> backup database; Starting backup at 27-SEP-11 channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45 Finished backup at 27-SEP-11 Starting Control File and SPFILE Autobackup at 27-SEP-11 piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 27-SEP-11 RMAN> backup database; Starting backup at 27-SEP-11 channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55 Finished backup at 27-SEP-11 Starting Control File and SPFILE Autobackup at 27-SEP-11 piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 27-SEP-11 RMAN> list backup; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 113 Full 94.59M DISK 00:01:18 27-SEP-11 BP Key: 113 Status: AVAILABLE Compressed: YES Tag: TAG20110927T194613 Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp List of Datafiles in backup set 113 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 114 Full 6.89M DISK 00:00:01 27-SEP-11 BP Key: 114 Status: AVAILABLE Compressed: NO Tag: TAG20110927T194739 Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp Control File Included: Ckp SCN: 1185229 Ckp time: 27-SEP-11 SPFILE Included: Modification time: 27-SEP-11 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 115 Full 94.59M DISK 00:01:38 27-SEP-11 BP Key: 115 Status: AVAILABLE Compressed: YES Tag: TAG20110927T194931 Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 116 Full 6.89M DISK 00:00:02 27-SEP-11 BP Key: 116 Status: AVAILABLE Compressed: NO Tag: TAG20110927T195116 Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp Control File Included: Ckp SCN: 1185400 Ckp time: 27-SEP-11 SPFILE Included: Modification time: 27-SEP-11 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 117 Full 94.59M DISK 00:01:50 27-SEP-11 BP Key: 117 Status: AVAILABLE Compressed: YES Tag: TAG20110927T195228 Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 118 Full 6.89M DISK 00:00:02 27-SEP-11 BP Key: 118 Status: AVAILABLE Compressed: NO Tag: TAG20110927T195423 Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp Control File Included: Ckp SCN: 1185555 Ckp time: 27-SEP-11 SPFILE Included: Modification time: 27-SEP-11 RMAN> report obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 2 Report of obsolete backups and copies Type Key Completion Time Filename/Handle -------------------- ------ ------------------ -------------------- Backup Set 113 27-SEP-11 Backup Piece 113 27-SEP-11 /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp Backup Set 114 27-SEP-11 Backup Piece 114 27-SEP-11 /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp RMAN> delete obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 2 using channel ORA_DISK_1 Deleting the following obsolete backups and copies: Type Key Completion Time Filename/Handle -------------------- ------ ------------------ -------------------- Backup Set 113 27-SEP-11 Backup Piece 113 27-SEP-11 /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp Backup Set 114 27-SEP-11 Backup Piece 114 27-SEP-11 /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp Do you really want to delete the above objects (enter YES or NO)? y deleted backup piece backup piece handle=/orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp recid=113 stamp=762983174 deleted backup piece backup piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp recid=114 stamp=762983260 Deleted 2 objects RMAN> exit or note this:
RMAN> report obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 2 Report of obsolete backups and copies Type Key Completion Time Filename/Handle -------------------- ------ ------------------ -------------------- Backup Set 115 27-SEP-11 Backup Piece 115 27-SEP-11 /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp Backup Set 116 27-SEP-11 Backup Piece 116 27-SEP-11 /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp RMAN> CONFIGURE RETENTION POLICY TO REdundancy 6; old RMAN configuration parameters: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; new RMAN configuration parameters: CONFIGURE RETENTION POLICY TO REDUNDANCY 6; new RMAN configuration parameters are successfully stored RMAN> report obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 6 no obsolete backups found RMAN> CONFIGURE RETENTION POLICY TO REdundancy 1; old RMAN configuration parameters: CONFIGURE RETENTION POLICY TO REDUNDANCY 6; new RMAN configuration parameters: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; new RMAN configuration parameters are successfully stored RMAN> report obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 1 Report of obsolete backups and copies Type Key Completion Time Filename/Handle -------------------- ------ ------------------ -------------------- Backup Set 115 27-SEP-11 Backup Piece 115 27-SEP-11 /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp Backup Set 116 27-SEP-11 Backup Piece 116 27-SEP-11 /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp Backup Set 117 27-SEP-11 Backup Piece 117 27-SEP-11 /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp Backup Set 118 27-SEP-11 Backup Piece 118 27-SEP-11 /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp RMAN> exit -
Backup RMAN when FRA is configured
I configured on a db Flash recovery area 11.2.0.4; I want RMAN full backup to a different location of FRA.
I ran the full backup of rman with specified format...
backup in the database format compressed more archivelog backupset ' / backup/BKPD15/%U';
I see, some files will FRA and a few other small files are there in /backup/BKPD15 location as well.
What is the right way to take backup to any location of fra.
Hello
1. According to my knowledge, you must use two format, since the format applies to only backup of database archives goes for fra (see demo below)
Demo:
SYS@demo1 December 27, 15 > db_rec setting sho
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string/u04/temp_data/demo1
whole large db_recovery_file_dest_size 10G
db_recycle_cache_size large integer 0
[oracle@host1 test_backup] $ pwd
u04 / / test_backup
[oracle@host1 test_backup] $ ls - tl
Total 0
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string/u04/temp_data/demo1
whole large db_recovery_file_dest_size 10G
db_recycle_cache_size large integer 0
[oracle@host1 test_backup] $ pwd
u04 / / test_backup
[oracle@host1 test_backup] $ ls - tl
Total 0
RMAN > backup as database format compressed more archivelog backupset ' / u04/test_backup/%U';
From December 27, 15 backup
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying the newspapers archived in the backup set
archived journal thread = 1 = 3 sequence entry RECID = STAMP 3 = 899558724
channel ORA_DISK_1: from room 1 to 27 December 15
channel ORA_DISK_1: finished piece 1 to December 27, 15
total, handle = / u04/test_backup/01qpsba4_1_1 tag = TAG20151227T132524 comment = NONE - location no fra
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
From December 27, 15 backup
using channel ORA_DISK_1
channel ORA_DISK_1: from complete compressed datafile backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
Enter a number of file datafile = 00005 name=/u02/demo1/oradata/demo1/example01.dbf
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/mssm_tbs.dbf 00002
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/assm_tbs.dbf 00007
Enter a number of file datafile = 00001 name=/u02/demo1/oradata/demo1/system01.dbf
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/sysaux01.dbf 00003
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/undotbs01.dbf 00004
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/users01.dbf 00006
channel ORA_DISK_1: from room 1 to 27 December 15
channel ORA_DISK_1: finished piece 1 to December 27, 15
piece handle=/u04/temp_data/demo1/DEMO1/backupset/2015_12_27/o1_mf_nnndf_TAG20151227T132526_c7z6cgf1_.bkp tag = TAG20151227T132526 comment = NONE - fra position control file
channel ORA_DISK_1: complete set of backups, time: 00:01:05
channel ORA_DISK_1: from complete compressed datafile backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
including the current control in the backup set file
including current SPFILE in the backup set
channel ORA_DISK_1: from room 1 to 27 December 15
channel ORA_DISK_1: finished piece 1 to December 27, 15
piece handle=/u04/temp_data/demo1/DEMO1/backupset/2015_12_27/o1_mf_ncsnf_TAG20151227T132526_c7z6fjyk_.bkp tag = TAG20151227T132526 comment = NONE - fra location spfile
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup over at December 27, 15
From December 27, 15 backup
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying the newspapers archived in the backup set
archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794
channel ORA_DISK_1: from room 1 to 27 December 15
channel ORA_DISK_1: finished piece 1 to December 27, 15
total, handle = / u04/test_backup/04qpsbca_1_1 tag = TAG20151227T132634 comment = NONE - location no fra
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup over at December 27, 15
From December 27, 15 backup
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying the newspapers archived in the backup set
archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794
channel ORA_DISK_1: from room 1 to 27 December 15
channel ORA_DISK_1: finished piece 1 to December 27, 15
total, handle = / u04/test_backup/04qpsbca_1_1 tag = comment TAG20151227T132634 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
Correct way:
RMAN > run {}
2 > allocate channel backup_disk1 type disk;
3 > backup format COMPRESSED BACKUPSET DATABASE TAG 'DB' ' / u04/test_backup/%U.db'
4 > format PLUS ARCHIVELOG ' / u04/test_backup/%U.arc';
{5 >}
output channel: ORA_DISK_1
allocated channel: backup_disk1
channel backup_disk1: SID = 48 type device = DISK
From December 27, 15 backup
Current archived log
channel backup_disk1: compressed boot archived log backup set
channel backup_disk1: specifying the newspapers archived in the backup set
archived journal thread = 1 = 3 sequence entry RECID = STAMP 3 = 899558724
archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794
archived journal entry thread = 1 sequence = RECID 5 = 5 STAMP = 899559573
channel backup_disk1: from room 1 to 27 December 15
channel backup_disk1: finished piece 1 to December 27, 15
piece handle=/u04/test_backup/05qpsc4l_1_1.arc tag = TAG20151227T133933 comment = NONE
channel backup_disk1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
From December 27, 15 backup
channel backup_disk1: from complete compressed datafile backup set
channel backup_disk1: specifying datafile (s) in the backup set
Enter a number of file datafile = 00005 name=/u02/demo1/oradata/demo1/example01.dbf
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/mssm_tbs.dbf 00002
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/assm_tbs.dbf 00007
Enter a number of file datafile = 00001 name=/u02/demo1/oradata/demo1/system01.dbf
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/sysaux01.dbf 00003
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/undotbs01.dbf 00004
Enter a number of file datafile = name=/u02/demo1/oradata/demo1/users01.dbf 00006
channel backup_disk1: from room 1 to 27 December 15
channel backup_disk1: finished piece 1 to December 27, 15
piece handle=/u04/test_backup/06qpsc4m_1_1.db tag = comment DB = NONE
channel backup_disk1: complete set of backups, time: 00:00:55
channel backup_disk1: from complete compressed datafile backup set
channel backup_disk1: specifying datafile (s) in the backup set
including the current control in the backup set file
including current SPFILE in the backup set
channel backup_disk1: from room 1 to 27 December 15
channel backup_disk1: finished piece 1 to December 27, 15
piece handle=/u04/test_backup/07qpsc6d_1_1.db tag = comment DB = NONE
channel backup_disk1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
From December 27, 15 backup
Current archived log
channel backup_disk1: compressed boot archived log backup set
channel backup_disk1: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = RECID 6 = 6 STAMP = 899559632
channel backup_disk1: from room 1 to 27 December 15
channel backup_disk1: finished piece 1 to December 27, 15
piece handle=/u04/test_backup/08qpsc6g_1_1.arc tag = TAG20151227T134032 comment = NONE
channel backup_disk1: complete set of backups, time: 00:00:01
Backup over at December 27, 15
output channel: backup_disk1
RMAN >
RMAN > list backupset;
List of backup sets
===================
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
5.89 5 M DISK 00:00:00 DECEMBER 27, 15
BP key: 5 location: AVAILABLE Tablet: YES Tag: TAG20151227T133933
Part name: /u04/test_backup/05qpsc4l_1_1.arc
List of newspapers archived on backup the value 5
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 3 2871101 DECEMBER 27, 15 2875107 27 DECEMBER 15
1 4 2875107 27 DECEMBER 15 2875234 27 DECEMBER 15
1 5 2875234 27 DECEMBER 15 2875749 27 DECEMBER 15
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
6 integer M DISK 00:00:55 360,54 27 December 15
BP key: 6 location: AVAILABLE Tablet: YES Tag: DB
Part name: /u04/test_backup/06qpsc4m_1_1.db
List of files of backup data the value 6
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
2875757 full 1 /u02/demo1/oradata/demo1/system01.dbf December 27, 15
2 full 2875757 /u02/demo1/oradata/demo1/mssm_tbs.dbf 27 December 15
3 full 2875757 /u02/demo1/oradata/demo1/sysaux01.dbf 27 December 15
4 integer 2875757 /u02/demo1/oradata/demo1/undotbs01.dbf 27 December 15
5 integer 2875757 /u02/demo1/oradata/demo1/example01.dbf 27 December 15
6 integer 2875757 /u02/demo1/oradata/demo1/users01.dbf 27 December 15
7 full 2875757 /u02/demo1/oradata/demo1/assm_tbs.dbf 27 December 15
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
7 full 1.03 M DISK 00:00:02 27 December 15
BP key: 7 location: AVAILABLE Tablet: YES Tag: DB
Part name: /u04/test_backup/07qpsc6d_1_1.db
SPFILE included: Change Date: 27 December 15
SPFILE db_unique_name: DEMO1
Control file included: cash SNA: 2875780 cash time: 27 December 15
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
13.50 8 K DISK 00:00:00 DECEMBER 27, 15
BP key: situation 8: AVAILABLE Tablet: YES Tag: TAG20151227T134032
Part name: /u04/test_backup/08qpsc6g_1_1.arc
List of newspapers archived in backup set of 8
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 6 2875749 DECEMBER 27, 15 2875786 27 DECEMBER 15
It may be useful
-Pavan Kumar N
-
Do not lock - automate the deletion of backups RMAN old day after a success
Hi all
Admin: Do not lock this thread. I moved here the database instance based on the suggestion of another Member, and the question to this forum. If you want to lock a thread, lock one in the forum of the database, not this one.
I am looking for a way to automate the deletion of backups RMAN old days only after the occurrence of a success. At the present time, I have daily backups of L0 via crontab, and I need to create a script that can tell if a successful backup is done, then delete the old L0 if it has. Any suggestions on how to start? I'm stuck in code to see if a successful backup has been performed.
Oracle 11.2.0.3
Exadata (4 nodes)
Linux 5.10
* a from database forum
A backup is completed when the backup command is complete.
You have two 'blocks execution' in your rman script.
Put the DELETE OBSOLETE between the end of the last execution block and EXIT:
OUTPUT CHANNEL fs1b;
OUTPUT CHANNEL fs2b;
OUTPUT CHANNEL fs3b;
CHANNEL fs4b;
CHANNEL fs5b;
CHANNEL fs6b;
CHANNEL fs7b;
CHANNEL fs8b;}
remove the backup noprompt obsolete;
"exit";You also want to do some other household:
cross-checking of backup;
delete expired backup noprompt.
overlap archivelog all;
delete noprompt expired archivelog all;
-
case of disaster with backup rman and archivelogs
Salvation;
When the disk failure comes and drop everything on disks, if we have a cold backup and logs archiving ONLY after a cold backup up to disk failure, we can restore files (datafiles, controlfile and everything) and apply to these cold backup archive logs and make the database updated up to the failure of disks.
I had this case in real life, and it works.
but
What happens if you don't have backup rman online that was taken before the failure of disk instead of cold backup and archive logs that was created after the backup online up to the failure of the drive.
We can restore the online of rman backup files, but can we apply archive logs to these restored files to update the database to the disk failure?
Best regardsUse the SET clause UNTIL - for example the VALUE up to TIME - before running the command RECOVER the DATABASE.
See http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsubcl019.htm#i1000331
and example 4-38 on the same page.
Hemant K Collette
-
Create database pending active using the RMAN Duplicate command
Hello guys,.
I created the database before using the RMAN Duplicate command, but here I am stuck.
Please help me to overcome this >
RMAN > run {}
2 > allocate channel prmy1 type disk;
3 > allocate channel prmy2 type disk;
4 > allocate channel prmy3 type disk;
5 > allocate channel prmy4 type disk;
6 > allocate auxiliary channel stby type disk;
7 > duplicate target database for the eve of the active database
8 > spfile
9 > parameter_value_convert "orcl", "orclstd".
10 > set db_unique_name = "orclstd".
11 > set db_file_name_convert = "/ orcl / ', ' / orclstd / '.
12 > set log_file_name_convert = "/ orcl / ', ' / orclstd / '.
"13 > set control_files="D:\app\employee3\oradata\ORCLSTD\control01.ctl ', 'D:\app\employee3\flash_recovery_area\ORCLSTD\control02.ctl '.
14 > set log_archive_max_processes = '5'
15 > set fal_client = "orclstd."
16 > set fal_server = "orcl".
17 > set diagnostic_dest =: \app\employee3'
18 > set db_recovery_file_dest = a: \app\employee3\flash_recovery_area'
19 > set standby_file_management = 'AUTO '.
"20 > set log_archive_config ='dg_config = (orcl, orclstd)"
21 > set log_archive_dest_2 = 'service = orcl ASYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd';
{22 >}
allocated channel: prmy1
channel prmy1: SID = 70 type device = DISK
allocated channel: prmy2
channel prmy2: SID = 135 type device = DISK
allocated channel: prmy3
channel prmy3: SID = 191 type device = DISK
allocated channel: prmy4
channel prmy4: SID = 7 type of device = DISK
allocated canal: stby
channel stby: SID = 129 type device = DISK
From 7 November 12 Db double
content of Script memory:
{
backup that copy reuse
TargetFile "E:\app\RAJKUMAR\product\11.2.0\dbhome_1\DATABASE\PWDorcl.ORA" auxiliary format
"D:\app\employee3\product\11gr2\DATABASE\PWDorclstd.ORA" targetfile
' E:\APP\RAJKUMAR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL. ORA' auxiliary format
' D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD. ORA';
clone of SQL ' alter system set spfile = "D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD." ORA "«;»
}
execution of Script memory
From backup 7 November 12
Backup finished in 7 November 12
SQL statement: alter system set spfile = "D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD. ORA "
content of Script memory:
{
clone of SQL 'alter system set audit_file_dest =
"E:\app\RAJKUMAR\admin\orclstd\adump" comment =
' ' scope = spfile;
clone of SQL 'alter system set dispatchers =
''(Protocol=TCP) (SERVICE = orclstdXDB) "comment =
' ' scope = spfile;
clone of SQL 'alter system set db_unique_name =
"Orclstd" comment =
' ' scope = spfile;
clone of SQL 'alter system set db_file_name_convert =
"/orcl/", "/orclstd/" comment is
' ' scope = spfile;
clone of SQL 'alter system set log_file_name_convert =
"/orcl/", "/orclstd/" comment is
' ' scope = spfile;
clone of SQL 'alter system set control_files =
"D:\app\employee3\oradata\ORCLSTD\control01.ctl", "D:\app\employee3\flash_recovery_area\ORCLSTD\control02.ctl" comment =
' ' scope = spfile;
clone of SQL 'alter system set log_archive_max_processes =
5 comment =
' ' scope = spfile;
clone of SQL 'alter system set fal_client =
"Orclstd" comment =
' ' scope = spfile;
clone of SQL 'alter system set fal_server =
"Orcl" comment =
' ' scope = spfile;
clone of SQL 'alter system set diagnostic_dest =
"D:\app\employee3" comment =
' ' scope = spfile;
clone of SQL 'alter system set db_recovery_file_dest =
"D:\app\employee3\flash_recovery_area" comment =
' ' scope = spfile;
clone of SQL 'alter system set standby_file_management =
Comment by "AUTO" =
' ' scope = spfile;
clone of SQL 'alter system set log_archive_config =
Comment by "dg_config" (orcl, orclstd) =. =
' ' scope = spfile;
clone of SQL 'alter system set log_archive_dest_2 =
"service = orcl ASYNC = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd valid_for" comment =
' ' scope = spfile;
clone to stop immediately;
startup nomount clone;
}
execution of Script memory
SQL statement: alter system set audit_file_dest = comment "E:\app\RAJKUMAR\admin\orclstd\adump" = "' scope = spfile
SQL statement: alter system set dispatchers = ''(PROTOCOL=TCP) (SERVICE = orclstdXDB) "comment ="' scope = spfile
SQL statement: alter system set db_unique_name = comment "orclstd" = "' scope = spfile
SQL statement: alter system set db_file_name_convert = "/orcl/", "/orclstd/" comment = "' scope = spfile
SQL statement: alter system set log_file_name_convert = "/orcl/", "/orclstd/" comment = "' scope = spfile
SQL statement: alter system set control_files = "D:\app\employee3\oradata\ORCLSTD\control01.ctl", "D:\app\employee3\flash_recovery_area\ORCLSTD\control
02.CTL "comment ="' scope = spfile
SQL statement: alter system set log_archive_max_processes = 5 = comment "' scope = spfile
SQL statement: alter system set fal_client = comment "orclstd" = "' scope = spfile
SQL statement: alter system set fal_server = comment "orcl" = "' scope = spfile
SQL statement: alter system set diagnostic_dest = comment "D:\app\employee3" = "' scope = spfile
SQL statement: alter system set db_recovery_file_dest = comment "D:\app\employee3\flash_recovery_area" = "' scope = spfile
SQL statement: alter system set standby_file_management = comment "AUTO" = "' scope = spfile
SQL statement: alter system set log_archive_config = "dg_config = (orcl, orclstd)" comment = "' scope = spfile
SQL statement: alter system set log_archive_dest_2 = "service = orcl ASYNC = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd valid_for" comment = "'s
face = spfile
Instance Oracle to close
connected to the auxiliary database (not started)
Oracle instance started
Total System Global Area 1071333376 bytes
Bytes of size 1375792 fixed
528482768 variable size bytes
Buffers data 536870912 bytes
Redo buffers 4603904 bytes
allocated canal: stby
channel stby: SID = 63 type device = DISK
content of Script memory:
{
backup current controlfile to standby auxiliary copy format ' D:\APP\EMPLOYEE3\ORADATA\ORCLSTD\CONTROL01. CTL';
Restore clone controlfile to ' D:\APP\EMPLOYEE3\FLASH_RECOVERY_AREA\ORCLSTD\CONTROL02. CTL' of
' D:\APP\EMPLOYEE3\ORADATA\ORCLSTD\CONTROL01. CTL';
}
execution of Script memory
From backup 7 November 12
channel prmy1: from data file copy
copy of the control file ensures
name=E:\APP\RAJKUMAR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFORCL output file. ORA tag = RECID = 1 STAMP = 798743550 TAG20121107T171229
channel prmy1: datafile copy complete, duration: 00:00:03
Backup finished in 7 November 12
From restoration to November 7, 12
channel stby: copy of copy of control files
Restoration finished November 7, 12
content of Script memory:
{
SQL clone 'alter database sleep mounting database';
}
execution of Script memory
SQL statement: alter database mount rescue
output channel: prmy1
output channel: prmy2
output channel: prmy3
output channel: prmy4
exit canal: stby
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command duplicate Db at 07/11/2012 17:12:40
RMAN-05501: abandonment of duplicate target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\MIGRATION_DATA01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_INDX01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_DATA01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\USERS01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\UNDOTBS01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\SYSAUX01 auxiliary file name. DBF conflict with a file used by the target database
RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\SYSTEM01 auxiliary file name. DBF conflict with a file used by the target database
RMAN >
Thank you
Reverchonuser9192565 wrote:
11> set db_file_name_convert='/orcl/','/orclstd/' 12> set log_file_name_convert='/orcl/','/orclstd/'RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\MIGRATION_DATA01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_INDX01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_DATA01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\USERS01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\UNDOTBS01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\SYSAUX01.DBF conflicts with a file used by the target database RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\SYSTEM01.DBF conflicts with a file used by the target databaseThe strings that you entered in your file name conversion settings does not match where actually your data files. If the string does not match the names of files, there is no names of files to convert. Because you're on windows, how about something like this?
set db_file_name_convert='\ORCL\','\ORCLSTD\' set log_file_name_convert='\ORCL\','\ORCLSTD\'Hope that helps...
Patrik
-
Question about RMAN DUPLICATE command
Oracle version: 10.2
Operating system: Solaris 10
To create a physical standby DB, I'll take full DB more backup archivelog on main site and copy it to the location of the previous day.
I'm going to standby mode,
1. is it true that I need to keep the full backup on the main site when you run the RMAN DUPLICATE backup server? In the affirmative. Why? We have already copied the full backup to the backup site. Right?startup nomount pfile=/path/init.ora rman target sys/password@primDB auxiliary / RMAN> run { allocate channel t1 device type disk; allocate auxiliary channel t2 device type disk; duplicate target database for standby nofilenamecheck; }
2. why the command DORECOVER is optional?
3. several archived newspapers may have been generated after that full backups have been copied to the backup site. When you run the backup site COPY command, RMAN will extract the info again newly generated primary and apply automatically in standby mode?Hello;
I keep the RMAN backup on the primary until the copy is complete, so my RMAN catalog know about it. Sound cleaner this way. What magic RMAN can or can not do with it is not very important IMHO.
Don't forget that the news of the eve doesn't have to be registered with RMAN, because it is the same database as the main. However you can use a tape with the method too, so it's probably more to do with not having to repeat the same backup if you make a mistake.I've never had to use a DORECOVER to a double never. Completing this task at least 30 times and I think 'optional' is not a word strong enough. According to the doc DORECOVER specifies that RMAN should recover the database after it is created. I've never had to use it. See this doc for more information:
http://docs.Oracle.com/CD/B19306_01/backup.102/b14194/rcmsynta028.htm
On move any what archiving log new expectations before to start the double so the news of the day before can start working immediately, without additional measures. Usually the Data Guard will begin apply immediately and have RMAN does not do anything. None of the notes has any special note for additional archives moving after starting two copies. RMAN duplicates and Data Guard apply struggling upward.
Here are my notes on this topic: (these works on Oracle 10 or 11 of the Oracle)
http://www.Visi.com/~mseberg/duprman2.html
Best regards
mseberg
Published by: mseberg on March 17, 2012 13:07
-
Behavior of abnormal (Tag Date and place of automatic backup) RMAN script
Hi all
I have 11 GR 1 material running on Sun SOLARIS 10.
The parameter default RMAN for backup of control file is on DISK (format: u02/oracle/backup/rman/control/%F.ctl)
I have the RMAN script following (L0.rman):
Run {}
allocate channels ch1 type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
tag backup "${CURRENT_DATETIME}" additional 0 filesperset 3 format 'DB_%T_%U.dbf' database more archivelog;
output channel ch1.
}
host ' cp /oracle/app/oracle/product/11.1.0/db_1/network/admin/tnsnames.ora/u02/oracle/backup/rman/$(echo $CURRENT_DATETIME) /';
This is called by the following (L0.sh) script:
#! / bin/bash
CURRENT_DATETIME = "$(date + 20 %y %m %d %H %M)»;) export CURRENT_DATETIME
export ORACLE_SID = EDWH
export ORACLE_HOME=/oracle/app/oracle/product/11.1.0/db_1
mkdir/u02/oracle/backup/rman/$(echo $CURRENT_DATETIME)
RMAN nocatalog target / cmdfile = L0.rman log = L0_EDWH_$ CURRENT_DATETIME.log
The anomalies are as follows:
1. the backupsets are created with a literal tag "${CURRENT_DATETIME}" instead of "201010051915" - why?
FYI, the command 'host' at the bottom of L0.rman successfully copies the file in the right directory (/ u02/oracle/backup/rman/201010051915 /).
2. after the backup finishes, the automatic backup for the control and spfile is taken on SBT_TAPE instead of DISK - why?
Any help will be appreciated.1. well, this $CURRENT_DATETIME is variable shell, RMAN does not interpret it (she can't and doesn't have to.) HOST calls the external commands by spawning the shell in non-interactive mode and when placing the order for her, and since you have exported the variable is available to all processes having engineered and develop properly, then files are copied in the expected location. If you remove the '; CURRENT_DATETIME export"from your shell script, you will see files copied in/u02/oracle/backup rman / / because the variable will not be in the environment of the layed shell (it will be local to the script) and will expand to the empty string. You must pass $CURRENT_DATETIME to the RMAN script as a variable substitution so that the shell expands it before calling RMAN, like this:
L0. RMAN: {code}
Run {}
allocate channels ch1 type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
backup format tag & 1 extra strength 0 filesperset 3 'DB_%T_%U.dbf' database archivelog;
output channel ch1.
}
host ' cp /oracle/app/oracle/product/11.1.0/db_1/network/admin/tnsnames.ora/u02/oracle/backup/rman / $ CURRENT_DATETIME /';
{code}
L0.sh: {code}
#! / bin/bash
CURRENT_DATETIME = "$(date + 20 %y %m %d %H %M)»;) export CURRENT_DATETIME
export ORACLE_SID = EDWH
export ORACLE_HOME=/oracle/app/oracle/product/11.1.0/db_1
mkdir/u02/oracle/backup/rman / $ CURRENT_DATETIME
RMAN nocatalog target / cmdfile = L0.rman using $CURRENT_DATETIME log = L0_EDWH_$ CURRENT_DATETIME.log
{code}Note the * & 1 * variable substitution in the RMAN script and * using * keyword in the RMAN command line.
2. control file record is taken to the same media, that the last backup, this is normal. You can't "CONFIGURE CONTROLFILE AUTOBACKUP ON the DISC" or something like that, you can only enable or disable it and specify format for various types of devices. Default device type does not play here, you are precisely the configured default device type substitution tape backup.
-
Our framework is Oracle 11 g 2/Redhat 5.2. I create a RAMN script to schedule a cron job:
Can I create a script without using the recovery catalog?MAN> CREATE SCRIPT level_0_backup { backup incremental level 0 cumulative device type disk tag 'level0' database; backup device type disk tag 'level0' archivelog all not backed up delete all input; } 2> 3> 4> 5> RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of create script command at 08/27/2010 13:43:37 RMAN-06002: command not allowed when not connected to a recovery catalog
Or y at - it a way to create a rman backup job scheduled with the operating system without using the recovery catalog?Can I create a script without using the recovery catalog?
NO.
Or y at - it a way to create a rman backup job scheduled with the operating system without using the recovery catalog?
Yes using cron
check out the links and discussions:
http://www.Oracle-base.com/articles/Misc/OracleShellScripting.php
http://jhdba.WordPress.com/2008/03/20/RMAN-backup-script-example/
Re: calendar rman using the cron
Re: rman automatic batch text (windows) -
Backup RMAN of TAR FULL after finishing.
Hi all
We plan backups RMAN from EMGC 10
Databases / DB / availability / schedule backup / database backup schedule / all custom...
I can add the line of tar in the RMAN script but the RMAN does not tar - czvf...
How is it possible to tar backup after arriving? I can string a bash script?
Thank you
* TWhen you use the OEM GC configuration for running a scheduled backup, OEM GC run an RMAN session. You will not be able to change this option by inserting the shell commands.
What you could do, is have the OEM GC to create the RMAN script for you (or creat it yourself), store the RMAN script in your catalog RMAN and create a BONE type Job. In this job, you can run a shell script, which first start RMAN session and run the RMAN script stored, that you created, and then run your command "tar".
You can even think to do that with a multi step employment type, so that if your RMAN defective stage, you do not want the step of tar to execute.
Concerning
Rob
Maybe you are looking for
-
The Java plug-in 2 1.6.0.31 NPAPI should be disabled?
I was updating my sites Google Blogger, and got a Firefox error message that says that the Java plug-in for NAPAPI 1.6.0.31 2 must be turned off, in my opinion and I have to restart Firefox. I decided to disconnect from my Blogger account before you
-
Satellite A660 - 11 m: graphics issue - a few squares on the screen
Hello I have a problem with the graphics - when the screen of Windows 7 (64 Home edition) start something wrong with.I see a few places, for screen occasionally goes black (for 1 second) and after that, there is a nvidia driver on communication. When
-
OK, I just had a dv7-4165dx and wiped and reinstalled windows 7. I downloaded all the drivers for my laptop but it is not reading blu - ray. Is there a specific driver I need? Help, please!
-
Original graphical corruption of Crimson Skies.
When I try to execute a mission in the Original Crimson Skies, the game appears with black coating graphic distortions of the screen until it shuts down completely. I tried to run in compatibility modes, but nothing seems to stop the distortion. Any
-
Impossible to uninstall Windows Desktop Search 3.01
I couldn't uninstall Windows Desktop Search 3.01 because the uninstall program cannot find 'C:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.exe '. What I can do. I need to be uninstalled so I can upgrade to a new version to use with my Outlook 2