CS-Mars NFS Backup
Dear all,
i am using NFS sharing folder(located on a server) in order to backup cs-mars events.
the space on the server is full, i tried to extend the server with an external hard disk(usb connection) where i created an NSF sharing folder, but solution failed.
it seem the folder should be located on an internal hard disk.
so i have to add and connect a new hard disk on board. any other suggestion?
one more thing, i am trying to move NFS shared folder containts to a new location, but cuting files is not allowed. i stoped the nfs sharing on the folder but the same issue (not allowed). i changed the nfs folder to a new folder with cs-mars, but also i am not able to cut or delete the files on the first nfs sharing.
please advice how may i delete those files. (one pna file is kept on all day folders and i am not allowed to delete it, access is denied).
thank you
Hello
If its a Windows box, download something like Proccess Explorer and find the file/handle locking the NFS archive files and then stop that process, you can then copy/move them anywhere you like
http://technet.microsoft.com/en-us/sysinternals/bb896653
For *nix, check the file permissions (ls command) and then use chmod to modify accordingly
Regards
Farrukh
Similar Messages
-
Cisco Prime 2.1 HA and NFS backup
Hi,
I've just configured my Cisco Prime with the external NFS backup server using instruction from the Administration Guide,
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/administrator/guide/PIAdminBook/backup_restore.html#pgfId-1085464
all works fine but I'm wondering what about HA server? Should I configure all the same steps I did on a primary server?
Regards
GunterNo, this instruction is for how to configure backup server and how to configure Cisco Prime to be able to use NFS for backup files. It works, I did this and there was no problem during the configuration. The only thing I'm wondering is that I did this on the primary Cisco Prime and not on the HA CP server. So what will hempen if the primary fail and the HA switch over as a primary? Should I configure the same repository on it, should I enable NFS on the HA server also?
-
MARS - NFS on Unix Services for Windows and deleting files
Hello !
I've prepared NFS server on W2k3 server with Unix Services for Windows installed. It works OK, the only problem is moveing/deleting files and folders. It seems like a problem with permissions for anonymous user. Does anybody have similar experience ?If you receive the following error message "Error ./pnarchiver Thread 2051:PN-0102:SQL error: ORA-01005: null password given; logon denied" then there is a Problem with archiving to NFS server. The directories for the archiving are properly created on the server but those directories remain empty. The workaround is that an inter operability issue exists between MARS and CygWin NFS server running on Windows 2003 server. To work around such inter operability issues, replace the NFS server with Microsoft Windows Services for Unix.
-
ISE 1.3 or Prime 2.1 NFS Backup to Synology NAS
Hello,
I have try this week to Backup the ISE and Prime to a Synology NAS.
Since a time i´m sure that the configuration on ISE an Prime are ok also DNS an Ping are ok.
The staging url is nfs://<servername>.it.lokal:/volume1/CiscoBackup/
The debug on both shows me an mount problem.
Username an password is correct configured.
Have anybody a idea to solve this problem.
Thanks!Hi cciesec2011,
thanks for reply.
I am curious about backup of ise 1.2 and certificates. can you share any link/document related to this.
Thanks,
Aditya -
I'm trying to use NFS to backup Cisco ISE on a schedule but I'm having difficulty. I'm not sure what the settings should be or the proper syntax.
Hello David,
Please share your ISE running configuration to find and verify syntex.
Source or destination URL for an NFS network server. Use url nfs://server:path1.
Server is the server name and path refers to /subdir/subsubdir. Remember that a colon (:) is required after the server for an NFS network server.
Also please reverify below required format:
The path must be valid and must exist at the time you create the repository. The following three fields are required depending on the protocol that you have chosen.
–ServerName—(Required for TFTP, HTTP, HTTPS, FTP, SFTP, and NFS) Enter the hostname or IPv4 address of the server where you want to create the repository.
–Username—(Required for FTP, SFTP, and NFS) Enter the username that has write permission to the specified server. Only alphanumeric characters are allowed.
–Password—(Required for FTP, SFTP, and NFS) Enter the password that will be used to access the specified server. Passwords can consist of the following characters: 0 through 9, a through z, A through Z, -, ., |, @, #,$, %, ^, &, *, (, ), +, and =. -
Hello all,
Hopefully someone can help me out as I dont know linux at all to verify some information.
I have MARS configured to backup to a NFS server. I recently received a notification from MARS stating that one of the backups failed.
Because I do not have access to the NFS server (Managed Services is why), what other ways can I verify that the NFS backup is succeeding? Whenever I attempt to use the GUI to pull raw messages from the NFS server it essentially times out.
Anything on the cli available? Any and all help/ideas are appreciated.
MARS is running 4.2.6 ( 2458 ). Yea, old, but customer absolutely refuses to give us the time of day to upgrade it.Also there is a 'pnexp' command available on the CLI. Even tough it is meant to export 4.x database before importing it into a new 5.x box (Generation 1). It can be used for 'immediate backups' as per the Cisco engineer on this thread:
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Expert%20Archive&topic=Security&topicID=.ee7f99a&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cbeaa98/18#selected_message
Once you enter the pnexp CLI
Do the following:
export config 10.1.1.1:/archive.
Then enter the following command:
pnexp> status
Data exporting process is currently running, please use command 'log {all|recent}' to view running logs and/or progress.
pnexp> log
Aug 25 09:44:47.192 2008@LM_INFO@Thread 1024:Number of events exported: 1227522, ~0.18% completed, overall speed = 30688.05 eps
Aug 25 09:44:47.192 2008@LM_INFO@Thread 1024:Estimated-Time-To-Complete: 6 hours 18 minutes
CTRL-C
As you can see I'm doing a full backup here (config+event/report data etc), don't run that just to 'test' NFS. Its better to use the 'config' option :)
Regards
Farrukh -
RMAN, RAC, NFS, and server lock ups
Good day. My environment is:
--a 2-node RAC
--Enterprise Edition 11.2.0.3
--RHEL 5.1
The goal is to use RMAN to push backups to a shared NFS mount (on a different server). Both nodes will have access to this location (in the event one node goes down, the other can still run backups). Easy, right?
Wrong.
I've tried every NFS mount option in the book. Most work just fine, some don't. When I use the recommended NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0
or
rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid
The mount works normally. I can "ls" and "mkdir" and "touch" and "vi" and "cp" files back and forth from the NFS backup location to the RAC node all day long. No problems. However, when I try to do almost anything in RMAN which requires writing to the NFS backup location such as the command "backup archive all delete input;" (or even things as simple as a Crosscheck or RMAN configuration change which writes any changes back to the autobackup ControlFile) the node locks up. There are no errors (or if there are, I don't know where to find them), even when I use RMAN log.
Just to recap: I run a Crosscheck (or any RMAN process that writes to the NFS backup location), the node will lock up, and I can let it sit for a day, inaccessible, with CRSCTL on the other node saying it's offline, and the node will never come out of a "frozen" state. It cannot be pinged or connected to.
I think I can safely rule out NFS mount options at this point.
I understand (after extensive reading of MOS docs and testing) that RAC RMAN can and does suffer from inefficient I/O when writing to an NFS mount. I don't think that's the culprit either. The autobackup ControlFile is not that big and I cannot see how running a simple Crosscheck would lock an entire node.
I am hoping someone has encountered this in the past and hopefully it's just a simple misconfiguration somewhere.My NFS line in /etc/fstab is (these options are for supporting 11.2.0.3, 11.1.0.7, and 10.2.0.4/5 simultaneously): server.domain:/NFS_Export /backup nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
Before you installed GI, did you by chance do a yum update? I've encountered a similar issue which ended up being due to mkinitrd creating a corrupted kernel; mkinitrd is invoked during the GI installation when the ADVM drivers are added and in my case mkinitrd created a new kernel prior to the new kernel being installed. Second to that, make sure you have the matching kernel headers to your kernel version. If they are different then you could probably get away with just creating a new kernel with mkinitrd and relinking GI/RDBMS homes, but be prepared to wipe GI and reinstall. -
Database backup with lost archive logs
How can I get a database backup when all the archive logs have been lost?
here's the full test of the backup:
Recovery Manager: Release 9.2.0.7.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to target database: ESKHDEV1 (DBID=4075873486)
using target database controlfile instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk format '/sbdbarc/backups/eskhdev1/%U' maxpiecesize 2000 M;
3> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' database;
4> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' archivelog all not backed up;
5> release channel oem_backup_disk1;
6> }
allocated channel: oem_backup_disk1
channel oem_backup_disk1: sid=18 devtype=DISK
Starting backup at 10-OCT-08
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00013 name=/spte/oracle/oradata/ESKHDEV1/leafdat02.dbf
input datafile fno=00011 name=/spte/oracle/oradata/ESKHDEV1KLXTEMP.dbf
input datafile fno=00001 name=/spte/oracle/oradata/ESKHDEV1/system01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2jjsq87q_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:00:45
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00002 name=/spte/oracle/oradata/ESKHDEV1/undotbs01.dbf
input datafile fno=00008 name=/spte/oracle/oradata/ESKHDEV1/tools01.dbf
input datafile fno=00005 name=/spte/oracle/oradata/ESKHDEV1/example01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_1_1 comment=NONE
channel oem_backup_disk1: starting piece 2 at 10-OCT-08
channel oem_backup_disk1: finished piece 2 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_2_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:20
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00017 name=/spte/oracle/oradata/ESKHDEV1/parentidx01.dbf
input datafile fno=00015 name=/spte/oracle/oradata/ESKHDEV1/lral3201.dbf
input datafile fno=00010 name=/spte/oracle/oradata/ESKHDEV1/xdb01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2ljsq8bn_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:05
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00012 name=/spte/oracle/oradata/ESKHDEV1/leafdat01.dbf
input datafile fno=00006 name=/spte/oracle/oradata/ESKHDEV1/indx01.dbf
input datafile fno=00003 name=/spte/oracle/oradata/ESKHDEV1/cwmlite01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2mjsq8dp_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00014 name=/spte/oracle/oradata/ESKHDEV1/leafidx.dbf
input datafile fno=00009 name=/spte/oracle/oradata/ESKHDEV1/users01.dbf
input datafile fno=00004 name=/spte/oracle/oradata/ESKHDEV1/drsys01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2njsq8g4_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00016 name=/spte/oracle/oradata/ESKHDEV1/parentdat01.dbf
input datafile fno=00007 name=/spte/oracle/oradata/ESKHDEV1/odm01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2ojsq8if_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:35
Finished backup at 10-OCT-08
Starting backup at 10-OCT-08
current log archived
channel oem_backup_disk1: starting archive log backupset
channel oem_backup_disk1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1260 recid=1236 stamp=667755183
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2pjsq8lf_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:00:02
Finished backup at 10-OCT-08
Starting Control File and SPFILE Autobackup at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-02 comment=NONE
Finished Control File and SPFILE Autobackup at 10-OCT-08
released channel: oem_backup_disk1
RMAN> delete noprompt obsolete device type disk;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=18 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 2 17-MAR-08
Backup Piece 2 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
Backup Set 6 17-MAR-08
Backup Piece 6 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
Backup Set 7 17-MAR-08
Backup Piece 7 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
Backup Set 8 17-MAR-08
Backup Piece 8 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
Backup Set 9 17-MAR-08
Backup Piece 9 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
Backup Set 10 17-MAR-08
Backup Piece 10 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
Backup Set 11 17-MAR-08
Backup Piece 11 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
Backup Set 12 17-MAR-08
Backup Piece 12 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
Backup Set 13 17-MAR-08
Backup Piece 13 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
Backup Set 14 17-MAR-08
Backup Piece 14 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
Backup Set 15 17-MAR-08
Backup Piece 15 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
Backup Set 16 17-MAR-08
Backup Piece 16 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
Backup Set 17 17-MAR-08
Backup Piece 17 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
Backup Set 18 17-MAR-08
Backup Piece 18 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
Backup Set 19 17-MAR-08
Backup Piece 19 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
Backup Set 20 17-MAR-08
Backup Piece 20 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
Backup Set 21 17-MAR-08
Backup Piece 21 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
Backup Set 22 17-MAR-08
Backup Piece 22 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
Backup Set 23 17-MAR-08
Backup Piece 23 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
Backup Set 24 17-MAR-08
Backup Piece 24 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
Backup Set 25 17-MAR-08
Backup Piece 25 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
Backup Set 26 17-MAR-08
Backup Piece 26 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
Backup Set 27 17-MAR-08
Backup Piece 27 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
Backup Set 28 17-MAR-08
Backup Piece 28 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
Backup Set 29 17-MAR-08
Backup Piece 29 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
Backup Set 30 17-MAR-08
Backup Piece 30 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
Backup Set 31 17-MAR-08
Backup Piece 31 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
Backup Set 32 17-MAR-08
Backup Piece 32 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
Backup Set 33 17-MAR-08
Backup Piece 33 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
Backup Set 34 17-MAR-08
Backup Piece 34 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
Backup Set 35 17-MAR-08
Backup Piece 35 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
Backup Set 36 17-MAR-08
Backup Piece 36 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
Backup Set 37 17-MAR-08
Backup Piece 37 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
Backup Set 38 17-MAR-08
Backup Piece 38 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
Backup Set 39 17-MAR-08
Backup Piece 39 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
Backup Set 40 17-MAR-08
Backup Piece 40 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
Backup Set 41 17-MAR-08
Backup Piece 41 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
Backup Set 42 17-MAR-08
Backup Piece 42 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
Backup Set 43 17-MAR-08
Backup Piece 43 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
Backup Set 44 17-MAR-08
Backup Piece 44 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
Backup Set 45 17-MAR-08
Backup Piece 45 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
Backup Set 46 17-MAR-08
Backup Piece 46 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
Backup Set 47 17-MAR-08
Backup Piece 47 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
Backup Set 48 17-MAR-08
Backup Piece 48 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
Backup Set 49 17-MAR-08
Backup Piece 49 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
Backup Set 50 17-MAR-08
Backup Piece 50 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
Backup Set 51 17-MAR-08
Backup Piece 51 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
Backup Set 52 17-MAR-08
Backup Piece 52 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
Backup Set 66 10-OCT-08
Backup Piece 68 10-OCT-08 /sbdbarc/backups/eskhdev1/2bjsppct_1_1
Backup Set 67 10-OCT-08
Backup Piece 69 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_1_1
Backup Piece 70 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_2_1
Backup Set 68 10-OCT-08
Backup Piece 71 10-OCT-08 /sbdbarc/backups/eskhdev1/2djsppgq_1_1
Backup Set 69 10-OCT-08
Backup Piece 72 10-OCT-08 /sbdbarc/backups/eskhdev1/2ejsppir_1_1
Backup Set 70 10-OCT-08
Backup Piece 73 10-OCT-08 /sbdbarc/backups/eskhdev1/2fjsppl6_1_1
Backup Set 71 10-OCT-08
Backup Piece 74 10-OCT-08 /sbdbarc/backups/eskhdev1/2gjsppnh_1_1
Backup Set 72 10-OCT-08
Backup Piece 75 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-00
Backup Set 73 10-OCT-08
Backup Piece 76 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-01
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2bjsppct_1_1 recid=68 stamp=667739549
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_1_1 recid=69 stamp=667739594
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_2_1 recid=70 stamp=667739639
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2djsppgq_1_1 recid=71 stamp=667739674
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2ejsppir_1_1 recid=72 stamp=667739739
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2fjsppl6_1_1 recid=73 stamp=667739814
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2gjsppnh_1_1 recid=74 stamp=667739889
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-00 recid=75 stamp=667739965
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-01 recid=76 stamp=667742372
Deleted 9 objects
RMAN-06207: WARNING: 48 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
List of Mismatched objects
==========================
Object Type Filename/Handle
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
RMAN> release channel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 10/10/2008 15:33:09
RMAN-06474: maintenance channels are not allocated
RMAN> exit;
Recovery Manager complete. -
Simple home network backup strategy ?
I have a simple home network of 4 machines on a router, all running Arch. None of the boxes are a server. I do not have NFS nor Samba running. I want a simple, incremental cron-based weekly backup process, to be backed up to a spare hard drive on one of the computers (eg hostname "master"). I believe rsync with ssh might be the easiest way to go, something like: "rsync -e ssh -varuzP /home/whoever master:/mnt/tmp/backups".
The cron job would first of all make sure the master computer is online, or send a message to the user to that effect. My problem is I do not know how to remotely mount, from a cron job, the second hard drive on "master". I suppose I could ensure that "master" auto mounts that drive each session but I would prefer not to do that. Any ideas appreciated.Another strategy for you to consider...
At a slightly different time each night (or whatever interval you want), have each computer on your network create a backup archive of itself. I recommend xz compression for this because it is slow to compress and small, but fast to decompress. eg
include="$include /root"
include="$include /home"
exclude="$exclude --exclude=/home/*/.mozilla/firefox/*/*Cache/*"
exclude="$exclude --exclude=/home/*/.mozilla/firefox/*/bookmarkbackups/*"
exclude="$exclude --exclude=/home/*/.mozilla/firefox/*/urlclassifier3.sqlite"
datestamp="$(date +%Y-%m-%d-%H%M%S)"
tar --ignore-failed-read $exclude -cf - $include | xz > "/backups/backup-$HOSTNAME-$datestamp.txz"
Next, if the security is needed, have the computer encrypt the archive using a GPG public key created for this purpose. (By using a public key, you don't need to be there to type in the password, and you don't need to include a password on the command line.)
gpg --always-trust -r 0xAAAAAAAA -o "/backups/backup-$HOSTNAME-$datestamp.txz.gpg" -e "/backups/backup-$HOSTNAME-$datestamp.txz"
(Where "0xAAAAAAAA" is your public key ID)
You can then delete the .txz original.
Then have each computer copy its backup file to each of the other computers on the network. You can do this by sharing an NFS backup folder on each computer, rsync, or using any other method or protocol. In some cases you could alternatively have a computer fetch a backup from another computer.
You can write a single script to do all of this on every computer, and have it read the $HOSTNAME variable so it can determine what machine it is running on.
Later in the night, have each computer run a separate script that checks that all the backups for today are present in its own backup folder, including those from all other computers. If there is a problem, have it send an admin alert, perhaps using local email or a CLI smtp client like msmtp. If there isn't a problem, have each computer run a cleanup routine to delete old backups. eg
# Remove backups older than 10 days
find -L /backups/ -type f -mtime +10 -name "backup-*.gpg" -execdir rm {} \;
This strategy is good for relatively low-volume dynamic data, like a /home folder and /etc. I find I like having separate backups from each of the past 10 days, rather than one incremental backup. For larger static data (music, movies, etc) you may want to use an incremental backup.
Advantages:
Redundancy - every computer keeps backups of all the others
Decentralized - no need for, or reliance on, a dedicated master
If the network is down, each computer at least creates a local backup.
With static tar archives instead of incremental, you have snapshots of the folders as they were several days or weeks ago. This way if you discover a problem later, you can go further back than an incremental backup allows.
Each computer can backup a custom set of folders for itself. And each computer can store backups for a different number of days, depending on its storage capacity.
Issues:
Be sure to have a copy of the GPG secret key! If the only backups of it you have are encrypted with the public key, you're in trouble. One way to avoid this is to have your backup script support a manual mode which encypts with a conventional passphrase instead of the public key. You can run this manual mode to create a static backup occassionally, and it will prompt you for the passphrase. The backup will thus contain an accessible copy of the key pair used for the automatic backups.
Sometimes NFS will hang for hours rather than producing an error. This is why it's good to have a separate script on a separate cron job which checks if the backups were created successfully and sends an admin alert.
Always test backups! It is terrible to discover your backup wasn't being created as you expected when you go to use it. Test to make sure you can decrypt and decompress it, and that it contains everything you expect.
Last edited by IgnorantGuru (2010-04-06 14:31:22) -
Relationship between current incarnation & Backups/ RMAN-20011
Hi
I have
the following situation in RMAN:
Incarnations:
>
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 CURRENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 ORPHAN 997986 02-MAR-11
>
Backups:
>
RMAN> list backup;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
176 56.57M DISK 00:00:42 02-MAR-11
BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
List of Archived Logs in backup set 176
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 977121 02-MAR-11 988286 02-MAR-11
1 3 988286 02-MAR-11 994189 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of Datafiles in backup set 187
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
201 4.48M DISK 00:00:01 02-MAR-11
BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
List of Archived Logs in backup set 201
Thrd Seq Low SCN Low Time Next SCN Next Time
1 4 994189 02-MAR-11 996336 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
214 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
244 757.50K DISK 00:00:01 02-MAR-11
BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
List of Archived Logs in backup set 244
Thrd Seq Low SCN Low Time Next SCN Next Time
1 5 996336 02-MAR-11 997210 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of Datafiles in backup set 261
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
279 742.00K DISK 00:00:01 02-MAR-11
BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
List of Archived Logs in backup set 279
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 997210 02-MAR-11 997953 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
297 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
*342 438.00K DISK 00:00:00 02-MAR-11*
BP Key: 345 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104935
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
List of Archived Logs in backup set 342
Thrd Seq Low SCN Low Time Next SCN Next Time
*1 7 997953 02-MAR-11 998260 02-MAR-11*
BS Key Type LV Size Device Type Elapsed Time Completion Time
*364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11*
BP Key: 366 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104937
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of Datafiles in backup set 364
File LV Type Ckp SCN Ckp Time Name
*1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf*
*2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf*
*3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf*
*4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf*
BS Key Size Device Type Elapsed Time Completion Time
*387 7.58M DISK 00:00:02 02-MAR-11*
BP Key: 392 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110421
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
List of Archived Logs in backup set 387
Thrd Seq Low SCN Low Time Next SCN Next Time
*1 8 998260 02-MAR-11 1000465 02-MAR-11*
BS Key Type LV Size Device Type Elapsed Time Completion Time
*410 Full 9.36M DISK 00:00:10 02-MAR-11*
BP Key: 412 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110425
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 1000507 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
483 Full 9.36M DISK 00:00:05 02-MAR-11
BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
571 Full 9.36M DISK 00:00:04 02-MAR-11
BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
667 Full 9.36M DISK 00:00:18 04-MAR-11
BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE Included: Modification time: 04-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
RMAN>
>
I want rebuild the Database with the Backup (bold text).
And I get the error after executed 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' from TAG "TAG20110302T063849";
5> # SHUTDOWN IMMEDIATE;
6> STARTUP NOMOUNT;
7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
8> STARTUP MOUNT;
9> SET UNTIL SCN 1000507;
10> RESTORE DATABASE;
11> RECOVER DATABASE;
12> ALTER DATABASE OPEN RESETLOGS;
13> }
database is already started
Starting restore at 04-MAR-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag=TAG20110302T110425
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
output file name=/CDATA/TESTDB/control01.ctl
output file name=/CFLASH/TESTDB/control02.ctl
Finished restore at 04-MAR-11
database is already started
database mounted
released channel: ORA_DISK_1
executing command: SET until clause
Starting restore at 04-MAR-11
Starting implicit crosscheck backup at 04-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=136 device type=DISK
Crosschecked 11 objects
Finished implicit crosscheck backup at 04-MAR-11
Starting implicit crosscheck copy at 04-MAR-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 04-MAR-11
searching 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: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /CDATA/TESTDB/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /CDATA/TESTDB/users01.dbf
channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag=TAG20110302T104937
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:13:45
Finished restore at 04-MAR-11
Starting recover at 04-MAR-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/04/2011 13:47:17
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog
>
How can I know the right incarnation to reset current?
Please , help
reagards
hqr200475
Edited by: hqt200475 on 04.03.2011 06:19Hi Werner,
I tried some experiments to find out the Relationship between current incarnations & Backups !
Here is a listing 2 hours before with the incarnation 460:
>
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
RMAN> list backup;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
176 56.57M DISK 00:00:42 02-MAR-11
BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
List of Archived Logs in backup set 176
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 977121 02-MAR-11 988286 02-MAR-11
1 3 988286 02-MAR-11 994189 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of Datafiles in backup set 187
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
201 4.48M DISK 00:00:01 02-MAR-11
BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
List of Archived Logs in backup set 201
Thrd Seq Low SCN Low Time Next SCN Next Time
1 4 994189 02-MAR-11 996336 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
214 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
244 757.50K DISK 00:00:01 02-MAR-11
BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
List of Archived Logs in backup set 244
Thrd Seq Low SCN Low Time Next SCN Next Time
1 5 996336 02-MAR-11 997210 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of Datafiles in backup set 261
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
279 742.00K DISK 00:00:01 02-MAR-11
BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
List of Archived Logs in backup set 279
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 997210 02-MAR-11 997953 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
297 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
342 438.00K DISK 00:00:00 02-MAR-11
BP Key: 345 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104935
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
List of Archived Logs in backup set 342
Thrd Seq Low SCN Low Time Next SCN Next Time
1 7 997953 02-MAR-11 998260 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11
BP Key: 366 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104937
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of Datafiles in backup set 364
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
387 7.58M DISK 00:00:02 02-MAR-11
BP Key: 392 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110421
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
List of Archived Logs in backup set 387
Thrd Seq Low SCN Low Time Next SCN Next Time
1 8 998260 02-MAR-11 1000465 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
410 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 412 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110425
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 1000507 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
483 Full 9.36M DISK 00:00:05 02-MAR-11
BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
571 Full 9.36M DISK 00:00:04 02-MAR-11
BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
667 Full 9.36M DISK 00:00:18 04-MAR-11
BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE Included: Modification time: 04-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
RMAN> @TESTDB_rr.rman
RMAN> RUN
2> {
3> # STARTUP NOMOUNT;
4> # RESTORE SPFILE TO '/u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' from TAG "TAG20110302T063849";
5> # SHUTDOWN IMMEDIATE;
6> STARTUP NOMOUNT;
7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
8> STARTUP MOUNT;
9> SET UNTIL SCN 1000507;
10> RESTORE DATABASE;
11> RECOVER DATABASE;
12> ALTER DATABASE OPEN RESETLOGS;
13> }
database is already started
Starting restore at 04-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=12 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/04/2011 13:29:58
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN> **end-of-file**
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
>
regards
hqt200475 -
Retention policy for incremental cumulative backup question
Hi,
I have a production database configured with retention policy for 30 days window. No catalog is used.
The backup plan is:
Sunday - Level 0 backup.
Weekdays - Incremental 1 cumulative backup.
I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
Thanks for your help!
RMAN> list backup summary;
using target database control file instead of recovery catalog
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
*14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
21 B F A SBT_TAPE 08-MAR-10 1 1 NO
24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
27 B F A SBT_TAPE 08-MAR-10 1 1 NO
35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
38 B F A SBT_TAPE 09-MAR-10 1 1 NO
46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
49 B F A SBT_TAPE 10-MAR-10 1 1 NO
57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
60 B F A SBT_TAPE 11-MAR-10 1 1 NO
66 B A A SBT_TAPE 12-MAR-10 1 1 NO
67 B A A SBT_TAPE 12-MAR-10 1 1 NO
68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
70 B A A SBT_TAPE 12-MAR-10 1 1 NO
71 B F A SBT_TAPE 12-MAR-10 1 1 NO
77 B A A SBT_TAPE 14-MAR-10 1 1 NO
78 B A A SBT_TAPE 14-MAR-10 1 1 NO
79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
81 B A A SBT_TAPE 14-MAR-10 1 1 NO
82 B F A SBT_TAPE 14-MAR-10 1 1 NO
88 B A A SBT_TAPE 15-MAR-10 1 1 NO
89 B A A SBT_TAPE 15-MAR-10 1 1 NO
90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
92 B A A SBT_TAPE 15-MAR-10 1 1 NO
93 B F A SBT_TAPE 15-MAR-10 1 1 NO
99 B A A SBT_TAPE 16-MAR-10 1 1 NO
100 B A A SBT_TAPE 16-MAR-10 1 1 NO
101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
103 B A A SBT_TAPE 16-MAR-10 1 1 NO
104 B F A SBT_TAPE 16-MAR-10 1 1 NO
109 B A A SBT_TAPE 17-MAR-10 4 1 NO
110 B F A SBT_TAPE 17-MAR-10 1 1 NO
111 B A A SBT_TAPE 17-MAR-10 1 1 NO
112 B F A SBT_TAPE 17-MAR-10 1 1 NO
113 B A A SBT_TAPE 17-MAR-10 1 1 NO
114 B A A SBT_TAPE 17-MAR-10 1 1 NO
115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
117 B A A SBT_TAPE 17-MAR-10 1 1 NO
118 B F A SBT_TAPE 17-MAR-10 1 1 NO
123 B A A SBT_TAPE 18-MAR-10 2 1 NO
124 B F A SBT_TAPE 18-MAR-10 1 1 NO
125 B A A SBT_TAPE 18-MAR-10 2 1 NO
126 B F A SBT_TAPE 18-MAR-10 1 1 NO
127 B A A SBT_TAPE 18-MAR-10 1 1 NO
128 B F A SBT_TAPE 18-MAR-10 1 1 NO
129 B A A SBT_TAPE 18-MAR-10 1 1 NO
130 B F A SBT_TAPE 18-MAR-10 1 1 NO
131 B A A SBT_TAPE 18-MAR-10 1 1 NO
132 B A A SBT_TAPE 18-MAR-10 1 1 NO
133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
135 B A A SBT_TAPE 18-MAR-10 1 1 NO
136 B F A SBT_TAPE 18-MAR-10 1 1 NO
142 B A A SBT_TAPE 19-MAR-10 2 1 NO
143 B F A SBT_TAPE 19-MAR-10 1 1 NO
144 B A A SBT_TAPE 19-MAR-10 1 1 NO
145 B F A SBT_TAPE 19-MAR-10 1 1 NO
146 B A A SBT_TAPE 19-MAR-10 1 1 NO
147 B F A SBT_TAPE 19-MAR-10 1 1 NO
148 B A A SBT_TAPE 19-MAR-10 1 1 NO
149 B F A SBT_TAPE 19-MAR-10 1 1 NO
150 B A A SBT_TAPE 19-MAR-10 1 1 NO
151 B A A SBT_TAPE 19-MAR-10 1 1 NO
152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
154 B A A SBT_TAPE 19-MAR-10 1 1 NO
155 B F A SBT_TAPE 19-MAR-10 1 1 NO
161 B A A SBT_TAPE 21-MAR-10 1 1 NO
162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
164 B A A SBT_TAPE 21-MAR-10 1 1 NO
165 B F A SBT_TAPE 21-MAR-10 1 1 NO
171 B A A SBT_TAPE 22-MAR-10 1 1 NO
172 B F A SBT_TAPE 22-MAR-10 1 1 NO
173 B A A SBT_TAPE 22-MAR-10 1 1 NO
174 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
Backup Set 8 07-MAR-10 Backup Piece 19 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_5_1
Backup Set 8 07-MAR-10 Backup Piece 18 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_4_1
Backup Set 8 07-MAR-10 Backup Piece 17 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_3_1
Backup Set 8 07-MAR-10 Backup Piece 16 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_2_1
Backup Set 8 07-MAR-10 Backup Piece 15 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_1_1
Backup Set 7 07-MAR-10 Backup Piece 14 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_5_1
Backup Set 7 07-MAR-10 Backup Piece 13 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_4_1
Backup Set 7 07-MAR-10 Backup Piece 12 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_3_1
Backup Set 7 07-MAR-10 Backup Piece 11 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_2_1
Backup Set 7 07-MAR-10 Backup Piece 10 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_1_1
Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
Edited by: user12019850 on 22-Mar-2010 10:53 AMAnother database with the same configuration and same plan seems fine:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
797 B A A SBT_TAPE 20-FEB-10 1 1 NO
803 B A A SBT_TAPE 20-FEB-10 1 1 NO
804 B F A SBT_TAPE 20-FEB-10 1 1 NO
805 B A A SBT_TAPE 20-FEB-10 1 1 NO
806 B F A SBT_TAPE 20-FEB-10 1 1 NO
807 B A A SBT_TAPE 20-FEB-10 1 1 NO
808 B F A SBT_TAPE 20-FEB-10 1 1 NO
809 B A A SBT_TAPE 21-FEB-10 1 1 NO
810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
812 B A A SBT_TAPE 21-FEB-10 1 1 NO
813 B F A SBT_TAPE 21-FEB-10 1 1 NO
818 B A A SBT_TAPE 21-FEB-10 1 1 NO
819 B F A SBT_TAPE 21-FEB-10 1 1 NO
820 B A A SBT_TAPE 21-FEB-10 1 1 NO
821 B F A SBT_TAPE 21-FEB-10 1 1 NO
822 B A A SBT_TAPE 21-FEB-10 1 1 NO
823 B F A SBT_TAPE 21-FEB-10 1 1 NO
824 B A A SBT_TAPE 22-FEB-10 1 1 NO
825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
827 B A A SBT_TAPE 22-FEB-10 1 1 NO
828 B F A SBT_TAPE 22-FEB-10 1 1 NO
833 B A A SBT_TAPE 22-FEB-10 1 1 NO
834 B F A SBT_TAPE 22-FEB-10 1 1 NO
835 B A A SBT_TAPE 22-FEB-10 1 1 NO
836 B F A SBT_TAPE 22-FEB-10 1 1 NO
837 B A A SBT_TAPE 22-FEB-10 1 1 NO
838 B F A SBT_TAPE 22-FEB-10 1 1 NO
839 B A A SBT_TAPE 22-FEB-10 1 1 NO
840 B F A SBT_TAPE 22-FEB-10 1 1 NO
841 B A A SBT_TAPE 23-FEB-10 1 1 NO
842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
844 B A A SBT_TAPE 23-FEB-10 1 1 NO
845 B F A SBT_TAPE 23-FEB-10 1 1 NO
850 B A A SBT_TAPE 23-FEB-10 1 1 NO
851 B F A SBT_TAPE 23-FEB-10 1 1 NO
852 B A A SBT_TAPE 23-FEB-10 1 1 NO
853 B F A SBT_TAPE 23-FEB-10 1 1 NO
854 B A A SBT_TAPE 23-FEB-10 1 1 NO
855 B F A SBT_TAPE 23-FEB-10 1 1 NO
856 B A A SBT_TAPE 24-FEB-10 1 1 NO
857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
859 B A A SBT_TAPE 24-FEB-10 1 1 NO
860 B F A SBT_TAPE 24-FEB-10 1 1 NO
865 B A A SBT_TAPE 24-FEB-10 1 1 NO
866 B F A SBT_TAPE 24-FEB-10 1 1 NO
867 B A A SBT_TAPE 24-FEB-10 1 1 NO
868 B F A SBT_TAPE 24-FEB-10 1 1 NO
869 B A A SBT_TAPE 24-FEB-10 1 1 NO
870 B F A SBT_TAPE 24-FEB-10 1 1 NO
871 B A A SBT_TAPE 24-FEB-10 1 1 NO
872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
874 B A A SBT_TAPE 24-FEB-10 1 1 NO
875 B F A SBT_TAPE 24-FEB-10 1 1 NO
880 B A A SBT_TAPE 24-FEB-10 1 1 NO
881 B F A SBT_TAPE 24-FEB-10 1 1 NO
882 B A A SBT_TAPE 25-FEB-10 1 1 NO
883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
885 B A A SBT_TAPE 25-FEB-10 1 1 NO
886 B F A SBT_TAPE 25-FEB-10 1 1 NO
891 B A A SBT_TAPE 25-FEB-10 1 1 NO
892 B F A SBT_TAPE 25-FEB-10 1 1 NO
893 B A A SBT_TAPE 25-FEB-10 1 1 NO
894 B F A SBT_TAPE 25-FEB-10 1 1 NO
895 B A A SBT_TAPE 25-FEB-10 1 1 NO
896 B F A SBT_TAPE 25-FEB-10 1 1 NO
897 B A A SBT_TAPE 25-FEB-10 1 1 NO
898 B F A SBT_TAPE 25-FEB-10 1 1 NO
899 B A A SBT_TAPE 25-FEB-10 1 1 NO
900 B F A SBT_TAPE 25-FEB-10 1 1 NO
901 B A A SBT_TAPE 25-FEB-10 1 1 NO
902 B F A SBT_TAPE 25-FEB-10 1 1 NO
903 B A A SBT_TAPE 26-FEB-10 1 1 NO
904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
906 B A A SBT_TAPE 26-FEB-10 1 1 NO
907 B F A SBT_TAPE 26-FEB-10 1 1 NO
912 B A A SBT_TAPE 26-FEB-10 1 1 NO
913 B F A SBT_TAPE 26-FEB-10 1 1 NO
914 B A A SBT_TAPE 26-FEB-10 1 1 NO
915 B F A SBT_TAPE 26-FEB-10 1 1 NO
916 B A A SBT_TAPE 26-FEB-10 1 1 NO
917 B F A SBT_TAPE 26-FEB-10 1 1 NO
918 B A A SBT_TAPE 27-FEB-10 1 1 NO
919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
921 B A A SBT_TAPE 27-FEB-10 1 1 NO
922 B F A SBT_TAPE 27-FEB-10 1 1 NO
927 B A A SBT_TAPE 27-FEB-10 1 1 NO
928 B F A SBT_TAPE 27-FEB-10 1 1 NO
929 B A A SBT_TAPE 27-FEB-10 1 1 NO
930 B F A SBT_TAPE 27-FEB-10 1 1 NO
931 B A A SBT_TAPE 27-FEB-10 1 1 NO
932 B F A SBT_TAPE 27-FEB-10 1 1 NO
933 B A A SBT_TAPE 28-FEB-10 1 1 NO
934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
936 B A A SBT_TAPE 28-FEB-10 1 1 NO
937 B F A SBT_TAPE 28-FEB-10 1 1 NO
942 B A A SBT_TAPE 28-FEB-10 1 1 NO
943 B F A SBT_TAPE 28-FEB-10 1 1 NO
944 B A A SBT_TAPE 28-FEB-10 1 1 NO
945 B F A SBT_TAPE 28-FEB-10 1 1 NO
946 B A A SBT_TAPE 28-FEB-10 1 1 NO
947 B F A SBT_TAPE 28-FEB-10 1 1 NO
948 B A A SBT_TAPE 01-MAR-10 1 1 NO
949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
951 B A A SBT_TAPE 01-MAR-10 1 1 NO
952 B F A SBT_TAPE 01-MAR-10 1 1 NO
957 B A A SBT_TAPE 01-MAR-10 1 1 NO
958 B F A SBT_TAPE 01-MAR-10 1 1 NO
959 B A A SBT_TAPE 01-MAR-10 1 1 NO
960 B F A SBT_TAPE 01-MAR-10 1 1 NO
961 B A A SBT_TAPE 01-MAR-10 1 1 NO
962 B F A SBT_TAPE 01-MAR-10 1 1 NO
963 B A A SBT_TAPE 02-MAR-10 1 1 NO
964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
966 B A A SBT_TAPE 02-MAR-10 1 1 NO
967 B F A SBT_TAPE 02-MAR-10 1 1 NO
970 B A A SBT_TAPE 02-MAR-10 1 1 NO
971 B F A SBT_TAPE 02-MAR-10 1 1 NO
972 B A A SBT_TAPE 02-MAR-10 1 1 NO
973 B F A SBT_TAPE 02-MAR-10 1 1 NO
974 B A A SBT_TAPE 02-MAR-10 1 1 NO
975 B F A SBT_TAPE 02-MAR-10 1 1 NO
976 B A A SBT_TAPE 03-MAR-10 1 1 NO
977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
979 B A A SBT_TAPE 03-MAR-10 1 1 NO
980 B F A SBT_TAPE 03-MAR-10 1 1 NO
983 B A A SBT_TAPE 03-MAR-10 1 1 NO
984 B F A SBT_TAPE 03-MAR-10 1 1 NO
985 B A A SBT_TAPE 03-MAR-10 1 1 NO
986 B F A SBT_TAPE 03-MAR-10 1 1 NO
987 B A A SBT_TAPE 03-MAR-10 1 1 NO
988 B F A SBT_TAPE 03-MAR-10 1 1 NO
989 B A A SBT_TAPE 04-MAR-10 1 1 NO
990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
992 B A A SBT_TAPE 04-MAR-10 1 1 NO
993 B F A SBT_TAPE 04-MAR-10 1 1 NO
996 B A A SBT_TAPE 04-MAR-10 1 1 NO
997 B F A SBT_TAPE 04-MAR-10 1 1 NO
998 B A A SBT_TAPE 04-MAR-10 1 1 NO
999 B F A SBT_TAPE 04-MAR-10 1 1 NO
1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
Backup Set 804 20-FEB-10
Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
Edited by: user12019850 on 22-Mar-2010 11:03 AM -
Oracle 10.2.0.5 Ent Ed on RHEL 5
Currently I have an NFS mounted storage array that I'm backing up my 50Gb database to. The backup policy is level 0 on Sunday, level 1 incremental the remaining days, and archivelog backup and delete input every hour. The database is the backbone to some poorly written applications that cause it to generate about 150Gb of redo per day.
I want to start using flashback database and can't find a good resource or "oracle by example" for doing so. I have the documentation that details setting up flashback, but it's not geared toward already having a backup plan in place.
Basically I'm trying to find out if I can use the NFS backup area for the Flash Recovery Area, or if I need to add another san attached lun to hold all my flashback files and then keep my current back strategy in place for nightly backups and hourly archivelog backups.Ben;
You should be able to. see "3.5.1 Choosing a Location for the Flash Recovery Area"
http://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup005.htm
It seems to be all about the "Share"
Additional Information
http://docs.oracle.com/html/B14399_01/app_nas.htm#CHDIAGAD
See - "NFS Mount Options "
Best Short Note I found
http://radpacs.palmettohealth.org/documents/server/topics/65853.html#sharing
Oracle Notes
ORA-27054 ERRORS WHEN RUNNING RMAN WITH NFS [ID 387700.1]
Receiving error Ora-27054 When Running Rman With NFS [ID 424785.1]
NFS Option Failure [ID 729518.1]
Mount Options for Oracle files when used with NFS on NAS devices [ID 359515.1]
http://www.rmanbackup.com/rmanerrorcodes/ora-27054-rman-nfs/
Best Regards
mseberg
Edited by: mseberg on Jul 9, 2012 9:45 AM
Edited by: mseberg on Jul 9, 2012 12:12 PM -
I have one 10g SE database running on Linux x86_64; I have migrated this database resently with upgrade;
I used export-import utilities for perform this task;
Some information about this database:
OS version: "Linux xxx.qqq.ru 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux"
SQL> select * from v$version;
BANNER
Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
I noticed that rman perform backup operation too long; For example here I place piece of rman log from one database backup operation:
executing script: backup_db_nfs
allocated channel: nfs
channel nfs: sid=1275 devtype=DISK
Starting backup at 31-07-10 04:00:04
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00028 name=/db/u12/oradata/billing/excellent_02.dbf
input datafile fno=00030 name=/db/u12/oradata/billing/excellent_04.dbf
input datafile fno=00032 name=/db/u12/oradata/billing/excellent_06.dbf
input datafile fno=00034 name=/db/u12/oradata/billing/excellent_08.dbf
input datafile fno=00029 name=/db/u11/oradata/billing/excellent_03.dbf
input datafile fno=00031 name=/db/u11/oradata/billing/excellent_05.dbf
input datafile fno=00033 name=/db/u11/oradata/billing/excellent_07.dbf
input datafile fno=00035 name=/db/u11/oradata/billing/excellent_09.dbf
channel nfs: starting piece 1 at 31-07-10 04:00:05
channel nfs: finished piece 1 at 31-07-10 04:34:21
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 04:34:21
channel nfs: finished piece 2 at 31-07-10 05:08:36
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 3 at 31-07-10 05:08:36
channel nfs: finished piece 3 at 31-07-10 07:38:43
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.3.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:38
channel nfs: throttle time: 3:###:42
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00036 name=/db/u12/oradata/billing/excellent_10.dbf
input datafile fno=00038 name=/db/u12/oradata/billing/excellent_12.dbf
input datafile fno=00040 name=/db/u12/oradata/billing/excellent_14.dbf
input datafile fno=00042 name=/db/u12/oradata/billing/excellent_16.dbf
input datafile fno=00037 name=/db/u11/oradata/billing/excellent_11.dbf
input datafile fno=00039 name=/db/u11/oradata/billing/excellent_13.dbf
input datafile fno=00041 name=/db/u11/oradata/billing/excellent_15.dbf
input datafile fno=00043 name=/db/u11/oradata/billing/excellent_17.dbf
channel nfs: starting piece 1 at 31-07-10 07:38:43
channel nfs: finished piece 1 at 31-07-10 08:13:18
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 08:13:18
channel nfs: finished piece 2 at 31-07-10 08:47:24
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 3 at 31-07-10 08:47:24
channel nfs: finished piece 3 at 31-07-10 11:17:20
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.3.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:37
channel nfs: throttle time: 3:###:59
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00044 name=/db/u12/oradata/billing/excellent_18.dbf
input datafile fno=00046 name=/db/u12/oradata/billing/excellent_20.dbf
input datafile fno=00047 name=/db/u12/oradata/billing/index_all_02.dbf
input datafile fno=00049 name=/db/u12/oradata/billing/index_all_04.dbf
input datafile fno=00045 name=/db/u11/oradata/billing/excellent_19.dbf
input datafile fno=00048 name=/db/u11/oradata/billing/index_all_03.dbf
input datafile fno=00050 name=/db/u11/oradata/billing/index_all_05.dbf
input datafile fno=00052 name=/db/u11/oradata/billing/index_all_07.dbf
channel nfs: starting piece 1 at 31-07-10 11:17:20
channel nfs: finished piece 1 at 31-07-10 12:16:46
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2655.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 12:16:46
channel nfs: finished piece 2 at 31-07-10 14:55:53
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2655.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:33
channel nfs: throttle time: 3:###:02
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00051 name=/db/u12/oradata/billing/index_all_06.dbf
input datafile fno=00053 name=/db/u12/oradata/billing/index_all_08.dbf
input datafile fno=00055 name=/db/u12/oradata/billing/index_all_10.dbf
input datafile fno=00057 name=/db/u12/oradata/billing/index_all_12.dbf
input datafile fno=00054 name=/db/u11/oradata/billing/index_all_09.dbf
input datafile fno=00056 name=/db/u11/oradata/billing/index_all_11.dbf
input datafile fno=00058 name=/db/u11/oradata/billing/index_all_13.dbf
input datafile fno=00060 name=/db/u11/oradata/billing/index_all_15.dbf
channel nfs: starting piece 1 at 31-07-10 14:55:53
channel nfs: finished piece 1 at 31-07-10 18:34:30
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2674.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:37
channel nfs: throttle time: 3:###:44
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00019 name=/db/u12/oradata/billing/excellent_big_02.dbf
input datafile fno=00021 name=/db/u12/oradata/billing/excellent_big_04.dbf
input datafile fno=00068 name=/db/u12/oradata/billing/support_excl_04.dbf
input datafile fno=00024 name=/db/u11/oradata/billing/excellent_big_07.dbf
input datafile fno=00026 name=/db/u11/oradata/billing/excellent_big_09.dbf
input datafile fno=00012 name=/db/u13/oradata/billing/pay_assist_01.dbf
input datafile fno=00004 name=/db/u13/oradata/billing/users_01.dbf
input datafile fno=00023 name=/db/u12/oradata/billing/excellent_big_06.dbf
input datafile fno=00025 name=/db/u12/oradata/billing/excellent_big_08.dbf
input datafile fno=00027 name=/db/u12/oradata/billing/excellent_big_10.dbf
channel nfs: starting piece 1 at 31-07-10 18:34:30
channel nfs: finished piece 1 at 31-07-10 21:59:27
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2695.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:24:57
channel nfs: throttle time: 3:###:13
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00059 name=/db/u12/oradata/billing/index_all_14.dbf
input datafile fno=00061 name=/db/u12/oradata/billing/index_all_16.dbf
input datafile fno=00063 name=/db/u12/oradata/billing/index_all_18.dbf
input datafile fno=00065 name=/db/u12/oradata/billing/index_all_20.dbf
input datafile fno=00062 name=/db/u11/oradata/billing/index_all_17.dbf
input datafile fno=00064 name=/db/u11/oradata/billing/index_all_19.dbf
input datafile fno=00015 name=/db/u12/oradata/billing/monitor_01.dbf
channel nfs: starting piece 1 at 31-07-10 21:59:27
channel nfs: finished piece 1 at 01-08-10 00:50:14
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2712.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:50:47
channel nfs: throttle time: 2:###:07
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00002 name=/db/u12/oradata/billing/undotbs_01.dbf
input datafile fno=00011 name=/db/u12/oradata/billing/index_all_01.dbf
input datafile fno=00009 name=/db/u12/oradata/billing/mviewlog_01.dbf
input datafile fno=00008 name=/db/u11/oradata/billing/support_excl_01.dbf
input datafile fno=00010 name=/db/u11/oradata/billing/excellent_01.dbf
input datafile fno=00067 name=/db/u11/oradata/billing/support_excl_03.dbf
input datafile fno=00007 name=/db/u11/oradata/billing/tpcctab_01.dbf
input datafile fno=00013 name=/db/u11/oradata/billing/tpchtab_01.dbf
input datafile fno=00005 name=/db/u13/oradata/billing/web_01.dbf
input datafile fno=00006 name=/db/u13/oradata/billing/alien_users_01.dbf
channel nfs: starting piece 1 at 01-08-10 00:50:14
channel nfs: finished piece 1 at 01-08-10 02:08:00
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2729.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 01-08-10 02:08:00
channel nfs: finished piece 2 at 01-08-10 03:40:46
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2729.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:50:32
channel nfs: throttle time: 2:###:12
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00016 name=/db/u12/oradata/billing/excellent_big_01.dbf
input datafile fno=00017 name=/db/u12/oradata/billing/monitor_lob_01.dbf
input datafile fno=00066 name=/db/u12/oradata/billing/support_excl_02.dbf
input datafile fno=00020 name=/db/u11/oradata/billing/excellent_big_03.dbf
input datafile fno=00022 name=/db/u11/oradata/billing/excellent_big_05.dbf
input datafile fno=00069 name=/db/u11/oradata/billing/support_excl_05.dbf
input datafile fno=00001 name=/db/u13/oradata/billing/system_01.dbf
input datafile fno=00003 name=/db/u13/oradata/billing/sysaux_01.dbf
input datafile fno=00018 name=/db/u13/oradata/billing/excl_addition_01.dbf
input datafile fno=00014 name=/db/u13/oradata/billing/arm_xml_01.dbf
channel nfs: starting piece 1 at 01-08-10 03:40:46
channel nfs: finished piece 1 at 01-08-10 06:02:03
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2742.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:21:17
channel nfs: throttle time: 2:###:51
Finished backup at 01-08-10 06:02:03
Size of this database:
SQL> select sum(user_bytes)/1024/1024/1024 from dba_data_files;
SUM(USER_BYTES)/1024/1024/1024
456.025085
I have another database that runs on the same hardware platform, eith the same configuration, and under the same OS. and oracle instance has the same configuration (except oracle version: there is 9.2.0.8);
Size of this, database is ~700Gb, and this database load is heavier that database with slow rman;
But on this database rman makes full-db backup in 10 hours, usually;
I read note 360443.1, and I checked - how long rman perform full database backup with validate option;
This time, practicaly, is equal database backup time ~24 hours;
Almost all database datafiles are splaced on disk array - stripe 10 and /db/u11 and /db/u12 - are mount points of two partitions created on this disk array;
/db/u13 - this is raid 5;
Now I wish to know in details - where time is spent and my question is: can anybody suggest me - what should I do for find it;Instance configuration
audit_file_dest /var/log/oracle/billing/audit
audit_sys_operations TRUE
audit_trail OS
background_dump_dest /var/log/oracle/billing/bdump
compatible 10.2.0.3.0
control_files /db/u11/oradata/billing/ctrl00.ctl, /db/u12/oradata/billing/ctrl01.ctl, /db/u00/oradata/billing/ctrl02.ctl, /db/u13/oradata/billing/ctrl03.ctl
core_dump_dest /var/log/oracle/billing/cdump
db_block_checking TRUE
db_block_checksum TRUE
db_block_size 8192
db_cache_advice ON
db_cache_size 24696061952
db_file_multiblock_read_count 64
db_keep_cache_size 3221225472
db_name billing
db_recycle_cache_size 3221225472
db_writer_processes 4
disk_asynch_io FALSE
dispatchers (protocol=tcp)(listener=mts_1522)(dispatchers=2), (protocol=tcp)(listener=mts_1523)(dispatchers=2)
filesystemio_options DIRECTIO
global_names FALSE
java_pool_size 1342177280
job_queue_processes 10
large_pool_size 536870912
lock_sga TRUE
log_archive_dest /db/archive/billing
log_archive_format %T_%S_%r.arclog
log_buffer 144326144
log_checkpoint_interval 10000
log_checkpoints_to_alert TRUE
log_checkpoint_timeout 0
max_dispatchers 5
max_dump_file_size 100M
max_shared_servers 350
nls_date_format DD.MM.RR
nls_language AMERICAN
nls_numeric_characters .,
nls_territory RUSSIA
open_cursors 1500
open_links 17
open_links_per_instance 34
optimizer_index_caching 90
optimizer_index_cost_adj 15
optimizer_mode RULE
pga_aggregate_target 24696061952
processes 1200
query_rewrite_enabled TRUE
remote_login_passwordfile EXCLUSIVE
resource_limit TRUE
session_cached_cursors 900
sessions 1500
sga_max_size 38654705664
sga_target 38654705664
shared_pool_size 3221225472
shared_servers 150
shared_server_sessions 1000
star_transformation_enabled FALSE
timed_statistics TRUE
undo_management AUTO
undo_retention 10800
undo_tablespace UNDOTBS1
user_dump_dest /var/log/oracle/billing/udump
workarea_size_policy AUTO
You can see here that parameter filesystemio_options has value DIRECTIO;
This is becouse last week I had accident on this database and, as result, I had to turn off async io for oracle;
All time before, since database mirgate moment, this parameter had value SETALL, and disk_asynch_io parameter had value true;
And rman has kept his inappropriate behaviour since this time (e.g.: since database mirgate); -
I have what I thought was a simple backup strategy but am failing to get it to work properly. Running 10.2.0.4, my desire is to run a nightly full image copy to the flash recovery disk including archive logs, control file, etc. Next morning, I wish to copy the previous backup to an shared storage disk mounted by NFS. My RMAN defaults are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO COPY;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_<snip>.f; # default
My nightly full backup job is simply:
BACKUP DATABASE PLUS ARCHIVELOG;
My script for copying the prior backup is failing with RMAN-20230. The script is:
run
ALLOCATE CHANNEL C1 DEVICE TYPE DISK FORMAT 'mnt/bkup/%U';
BACKUP DATAFILECOPY LIKE 'sysdate - 1' TAG 'offsite';
There seems to be a problem with 'DATAFILECOPY'. I have run this exact script using backup sets before and it works correctly. When I moved to data file copies, that's when the problems started. Does anyone have ideas?RMAN> backup as copy database format '/backup/rman/%f-%T';
Starting backup at 31-MAR-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile fno=00004 name=/oradata/db01/users01.dbf
output filename=/backup/rman/4-20090331 tag=TAG20090331T212809 recid=14 stamp=682982904
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=/oradata/db01/system01.dbf
output filename=/backup/rman/1-20090331 tag=TAG20090331T212809 recid=15 stamp=682982933
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile copy
input datafile fno=00003 name=/oradata/db01/sysaux01.dbf
output filename=/backup/rman/3-20090331 tag=TAG20090331T212809 recid=16 stamp=682982957
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
input datafile fno=00002 name=/oradata/db01/undotbs01.dbf
output filename=/backup/rman/2-20090331 tag=TAG20090331T212809 recid=17 stamp=682982968
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
Finished backup at 31-MAR-09
Starting Control File and SPFILE Autobackup at 31-MAR-09
piece handle=/backup/rman/c-1306541374-20090331-03 comment=NONE
Finished Control File and SPFILE Autobackup at 31-MAR-09
RMAN> list copy of database;
List of Datafile Copies
Key File S Completion Time Ckp SCN Ckp Time Name
15 1 A 31-MAR-09 658265 31-MAR-09 /backup/rman/1-20090331
17 2 A 31-MAR-09 658287 31-MAR-09 /backup/rman/2-20090331
16 3 A 31-MAR-09 658277 31-MAR-09 /backup/rman/3-20090331
14 4 A 31-MAR-09 658259 31-MAR-09 /backup/rman/4-20090331
13 4 A 31-MAR-09 658227 31-MAR-09 /backup/rman/1306541374-20090331
RMAN> backup datafilecopy like 'sysdate';
Starting backup at 31-MAR-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/31/2009 21:35:02
RMAN-20230: datafile copy not found in the recovery catalog
RMAN> backup datafilecopy like '20090331';
Starting backup at 31-MAR-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/31/2009 21:35:17
RMAN-20230: datafile copy not found in the recovery catalog
RMAN> backup datafilecopy like '%20090331%';
Starting backup at 31-MAR-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: including datafile copy of datafile 00004 in backupset
input filename=/backup/rman/4-20090331
channel ORA_DISK_1: including datafile copy of datafile 00001 in backupset
input filename=/backup/rman/1-20090331
channel ORA_DISK_1: including datafile copy of datafile 00003 in backupset
input filename=/backup/rman/3-20090331
channel ORA_DISK_1: including datafile copy of datafile 00002 in backupset
input filename=/backup/rman/2-20090331
channel ORA_DISK_1: starting piece 1 at 31-MAR-09
channel ORA_DISK_1: finished piece 1 at 31-MAR-09
piece handle=/backup/rman/2ekbavt1_1_1 tag=TAG20090331T213529 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: including datafile copy of datafile 00004 in backupset
input filename=/backup/rman/1306541374-20090331
channel ORA_DISK_1: starting piece 1 at 31-MAR-09
channel ORA_DISK_1: finished piece 1 at 31-MAR-09
piece handle=/backup/rman/2fkbavuo_1_1 tag=TAG20090331T213529 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
Finished backup at 31-MAR-09
Starting Control File and SPFILE Autobackup at 31-MAR-09
piece handle=/backup/rman/c-1306541374-20090331-04 comment=NONE
Finished Control File and SPFILE Autobackup at 31-MAR-09
RMAN> -
Control_file_record_keep_time vs retention policy
Its not thread nor question just read from documents and tried to imply the fact of documents and i think its written correct what i tried to do proof it practically ,neither i am trying to be smart just share with you guys is my observation correct or not.i am using FRA area for backup.
<quote>
Relation between RMAN retention period and control_file_record_keep_time
RMAN backup keeps the backup metadata information in the reusable section of the controlfile.Its depends on the parameter CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days before a reusable record in the control file can be reused.
In the event a new record needs to be added to a reusable section and there is not enough space then it will delete the oldest record, which are aged enough.
Backup retention policy is the rule to set regarding which backups must be retained (whether on disk or other backup media) to meet the recovery and other requirements.
If the CONTROL_FILE_RECORD_KEEP_TIME is less than the retention policy then it may overwrite reusable records prior to obsoleting them in the RMAN metadata. Therfor it is recommended that the CONTROL_FILE_RECORD_KEEP_TIME should set to a higher value than the retention policy.
Formula
CONTROL_FILE_RECORD_KEEP_TIME = retention period + level 0 backup interval + 1
For e.g.
e.q. level 0 backup once a week with retention policy of a recovery windows of 14 days then in this
case the CONTROL_FILE_RECORD_KEEP_TIME should be 14+7+1=22
<quote>
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>
SQL> alter system set control_file_record_keep_time=1
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 1
RMAN> configure retention policy to redundancy 3
2> ;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 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:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T185951_3N5T2RTX_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:17
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169270_3N5T598C_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190313_3N5T94SG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:22
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169477_3N5TCPVW_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190500_3N5TDGC9_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169556_3N5TG65X_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Archive Log 30 19-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_1_3N35QQX7_.ARC
Archive Log 31 19-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_2_3N39LR86_.ARC
Archive Log 32 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_3_3N4RZBXV_.ARC
Archive Log 33 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_4_3N4W8SLF_.ARC
Archive Log 34 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_5_3N4Y1CN7_.ARC
Archive Log 35 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_6_3N4Z6LGF_.ARC
Archive Log 36 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_7_3N53S4XK_.ARC
Archive Log 37 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_8_3N57XHYB_.ARC
Archive Log 38 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_9_3N5C52D8_.ARC
Archive Log 39 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_10_3N5C83YB_.ARC
Archive Log 40 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_11_3N5K9J2Z_.ARC
Archive Log 41 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_12_3N5MMXHO_.ARC
Archive Log 42 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_13_3N5N566W_.ARC
Archive Log 43 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_14_3N5RVB4G_.ARC
RMAN>
Now i just delete alls backup and increase the control_file_record_keep_time 7 which will be more then retention policy redundancy 3
RMAN> list backup
2> ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
6 Full 512M DISK 00:01:10 20-NOV-07
BP Key: 6 Status: AVAILABLE Compressed: NO Tag: TAG20071120T185951
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
List of Datafiles in backup set 6
File LV Type Ckp SCN Ckp Time Name
1 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
7 Full 2M DISK 00:00:04 20-NOV-07
BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190110
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP
Controlfile Included: Ckp SCN: 478975 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
8 Full 513M DISK 00:01:15 20-NOV-07
BP Key: 8 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190313
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
List of Datafiles in backup set 8
File LV Type Ckp SCN Ckp Time Name
1 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
9 Full 2M DISK 00:00:02 20-NOV-07
BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190437
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP
Controlfile Included: Ckp SCN: 480346 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full 513M DISK 00:00:52 20-NOV-07
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190500
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
1 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full 2M DISK 00:00:02 20-NOV-07
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190556
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP
Controlfile Included: Ckp SCN: 480449 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
RMAN> delete backup
2> ;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
6 6 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
7 7 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169270_3N5T598C_.BKP
8 8 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
9 9 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169477_3N5TCPVW_.BKP
10 10 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
11 11 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169556_3N5TG65X_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP recid=6 stamp=639169192
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP recid=7 stamp=639169273
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP recid=8 stamp=639169396
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP recid=9 stamp=639169478
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP recid=10 stamp=639169502
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP recid=11 stamp=639169558
Deleted 6 objects
RMAN> delete archivelog all
2> ;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
specification does not match any archive log in the recovery catalog
RMAN> list backup
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 1
SQL> alter system set control_file_record_keep_time=7
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191412_3N5TXRSG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170131_3N5V03YT_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191655_3N5V2S20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170261_3N5V462Z_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191836_3N5V5X20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170362_3N5V7C1K_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups foundnothing obsolete it means control_file_record_keep_time will not affect backups unless it will be less then or equal
to retention policy.
Note : Please agree or disagree with me may be i would be wrong
KhurramSorry for alls readers after a long practical observation at my own database server i came across that my observation was wrong and absurd in this first post, the above observation is not due to control_file_record_keep_time ,its due to something obvious which i am going to share you guys here.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM <DIR> .
03/17/2008 03:44 PM <DIR> ..
03/17/2008 03:44 PM 9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
1 File(s) 9,750,528 bytes
2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
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
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
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
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM <DIR> .
03/17/2008 03:59 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM <DIR> .
03/17/2008 04:09 PM <DIR> ..
03/17/2008 04:09 PM 9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
1 File(s) 9,751,552 bytes
2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
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 240 17-MAR-08
Backup Piece 231 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set 241 17-MAR-08
Backup Piece 232 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log 403 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram
Maybe you are looking for
-
Clarity required on these questions pls help?
HI , Need your help in solving these questions, these are questions asked in during interviews a) Dyamic actions, how to create a customer specific dynamic action , specify configured fields and rules? b) how to create Customer specific infotype, , p
-
How do you keep the hotspot activated?
I love the hotspot feature and am glad they have enabled that feature on the iPad and iPhone. Yes I know the data is no longer unlimited for most, but the feature is cool none the less. My question for the community though - is there any way to set t
-
I am missing something here! Maybe it is my advanced years (85) I have 2 IP cameras that I managed to control via Virgin Super Hub but since switching to BT the Home Hub 4 has me confused. Can someone please give me a step by step example of how to p
-
A couple of weeks ago I uninstalled Quicktime from my laptop, by simply dragging it from my Applications folder to the Trash. I didn't delete any other files, and I left Appcleaner out of it b/c I knew I would be downloading it again. I went to Apple
-
Hi Experts, I found there are two bash_profile in system for our RAC in linux. that means each account in linux have a bash_profile in system? Thanks JIm