RMAN Level 1 backup affects
O/S: Windows Server 2003
DB: Oracle 11gR2
We are in the midst of a production load process. Noticed that the level 2 backup from last night failed. Want to take a level 1 backup as soon as possible.
How will a level 1 backup affect a live system if it would done 'now' -- i.e., in the midst of a production load process?
Cheers!
The RMAN backup would not affect anything you do directly (assuming it is a hot backup). It will, however, consume quite a bit of disk and network IO, which in turn could slow most DB sessions/processes that require disk/network IO.
Iordan Iotzov
http://iiotzov.wordpress.com/
Similar Messages
-
Is an RMAN level 0 backup consistent (database in MOUNT code), or inconsistent (database is open)?
-ChuckPLease copy here the entire error stack. RMAN never gives just a sngle line error message. Its a series of error messages and looking all of them would be helpful to say something useful.
As Nayab asked, please post the db version as well.
HTH
Aman.... -
RMAN 0 level backup failed while releasing channels at end.
In RMAN 0 level backup, when it's about to finish, reports an error as releasing channels. It backed up about 98% datafiles.
Is this backup is usable. As we can not affort to take backup again as it's a big terabyte databse.
Please suggest.
Thanks in advance.
Aj.Do you have release stmts in the script
From 9i onwards oracle Release the channels automatically upon backing up, so you can remove the release channel lines if you have and try it -
Hi All,
Required level 0 backup script.
We have 10gR2 [10.2.0.4] Production instance, for backup required level 0 script.
Regards
ShaikShaik wrote:
Hi All,
Required level 0 backup script.
We have 10gR2 [10.2.0.4] Production instance, for backup required level 0 script.
Regards
ShaikHi shaik
RMAN>run {
backup incremental level 0 database plus archivelog ;
delete noprompt obsolete ;
for manual allocation channel for tape
RMAN > RUN {
ALLOCATE CHANNEL tape1 DEVICE TYPE sbt;
BACKUP DATABASE PLUS ARCHIVELOG;
RELEASE CHANNEL;
--neeraj -
Got error when creating a standby DB from rman: no backup or copy... Why?
We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
5> DUPLICATE TARGET DATABASE for standby
6> nofilenamecheck
7> dorecover;
8> }
9>
10> exit
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=582 devtype=DISK
allocated channel: aux2
channel aux2: sid=584 devtype=DISK
Starting Duplicate Db at 21-JUN-12
contents of Memory Script:
set until scn 12198261770353;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JUN-12
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
===========================================================================
The backups should have controlfile. There is rman show all display:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
Why and how to fix? Thanks for help!Here is the list of command:
RMAN> list backup of controlfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
5518 Full 4.57M DISK 00:00:07 17-JUN-12
BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Full 4.57M DISK 00:00:00 18-JUN-12
BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5526 Full 4.57M DISK 00:00:01 19-JUN-12
BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5530 Full 4.57M DISK 00:00:02 20-JUN-12
BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5534 Full 4.57M DISK 00:00:02 21-JUN-12
BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
==================================================================
I tried to catalog the controlfile:
RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
====================================================================
We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
Thanks for help! -
Hi,
we are using oracle10g(10.2.0.3).
is it possible to apply rman incremental backup on top of manual full backup?
Note:There is no level 0 backup available
Thanks
With Regards
UmairYes, you can.
Register your manual backup in recovery catalog as level 0 backup. Then take a fresh incremental backup. I have demonstrated the same in my article. You may download the same from here .
Go through the section "Rolling forward a backup".
Regards,
S.K. -
Quesion about the Basic concept of RMAN incremental backup
I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder -
Hi I have taken RMAN level 0 backup and scheduled level1 previously. Now we have moved the old datafiles and backupset and wanted to start from level 0 again. So we are running the same script and it is not running in level 0 but looking for level 1. and throwing errors. Now the flash recovery area is empty but only having the archivelogs and we want to take level 0 freshly. following is the error i am getting.
RMAN> run {
2> allocate channel oem_disk_backup device type disk;
3> recover copy of database with tag 'ORA\$OEM_LEVEL_0';
4> delete backup completed before 'SYSDATE-30' device type disk;
5> backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database plus archivelog ;
6> delete archivelog until time 'SYSDATE-30';
7> release channel oem_disk_backup;
8> }
9>
using target database control file instead of recovery catalog
allocated channel: oem_disk_backup
channel oem_disk_backup: sid=564 devtype=DISK
Starting recover at 20-AUG-07
no copy of datafile 6 found to recover
no copy of datafile 7 found to recover
no copy of datafile 8 found to recover
no copy of datafile 9 found to recover
no copy of datafile 10 found to recover
channel oem_disk_backup: starting incremental datafile backupset restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy fno=00001 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_system_3bk8d7hk_.dbf
recovering datafile copy fno=00002 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_undotbs1_3bk8f0m4_.dbf
recovering datafile copy fno=00003 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_sysaux_3bk8fhov_.dbf
recovering datafile copy fno=00004 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_users_3bk8fyrp_.dbf
recovering datafile copy fno=00005 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_becms_3bk7zghd_.dbf
channel oem_disk_backup: reading from backup piece /disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3d
ldd8z4_.bkp
released channel: oem_disk_backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/20/2007 21:25:04
ORA-19870: error reading backup piece /disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3dldd8z4_.bkp
ORA-19505: failed to identify file "/disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3dldd8z4_.bkp"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Recovery Manager complete.
Please help,
Thanks,
G.Take Level 0 backup using the below command and then go for the one you are executing
BACKUP INCREMENTAL LEVEL 0 TAG='ORA\$OEM_LEVEL_0' DATABASE;
Regards -
hi all
i would like to know the how many level of rman backup is available
increment level 0 and increment level 1 and increment level 2
how all this are differ from each other or what is the difference between this and what name we can use for instance differential incremental or cumulative incremental for level 1 and level 2
Regards<from-documentation>
Incremental backups can be either level 0 or level 1. A level 0 incremental backup, which is the base for subsequent incremental backups, copies all blocks containing data, backing the datafile up into a backup set just as a full backup would.
The only difference between a level 0 incremental backup and a full backup is that a full backup is never included in an incremental strategy.
</from-documentation>
Oracle® Database Backup and Recovery Basics
RMAN Incremental Backups
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm -
RMAN - Incremental backup / NOARCHIVELOG / Restore & Recover Until Cancel
I'm testing out a weekly plan as follows:
Sun : Shutdown db, RMAN level 0 Incremental Backup
Mon-Sat: Shutdown db, RMAN level 1 Incremental Backup.
The database is NOARCHIVELOG mode and is 10.2 XE.
I then run a restore (which I understand to be to move the datafiles from the backup set to their online location). My next aim is to do a recover.
I'm really confused at this point. Say I take the backup the night before (either a level 0 or 1, I'm assuming that this makes no difference) then in the morning I drop a table accidentally. Okay - I want to go back to the position after the backup. When I do recover, I understand that Oracle applies redo logs written since the backup.
So I don't want a recover, I want a recover until cancel. When I issue this command it is suggesting that I use an archive log file. Well obviously I don't have any of those so I press cancel thinking that this will bring me back to the point EXACTLY AFTER THE NIGHTLY BACKUP and with my table back. But it doesn't!
I would be really grateful if anyone has a definitive answer to this - what are the steps to recover a database to the point after the backup was taken ignoring any changes since the backup.
Thanks all.
Tom.Hi Werner
Do you mean if the online logs are available with the changes after the last backup until the database restore then there is a possibility to apply changes? Ie at this point I could put in the redo log names instead of the archive log names.
If they have been overwritten since the backup (ie cycled round completely) then is the behaviour to restore the database and then not apply any logs?
Do you know if this is documented anywhere? There seems to be an emphasis on ARCHIVELOG mode only, especially in the books I have seen.
Thanks,
Tom -
RMAN level 0 and level 1 tablespace/database relationships
If I take an incremental level 0 backup of an entire database and then take a level 0 of an individual tablespace, does an incremental level 1 backup of that tablespace reference the incremental level 0 of the tablespace or of the entire database? If I change the order of the level 0 backups, does it change the reference of the tablespace's level 1?
I guess what I'm asking is does the the level 1 incremental reference the latest level 0 regardless of whether it's for the whole database or just the tablespace or does a level 1 always reference it's own level 0?
Also, if I take a level 0 of the database Sunday night, and then a level 1 of the database every night after that as well as multiple level 1s of a tablespace throughout each day, will Tuesday night's database level 1 include all of Monday's tablespace level 1s?
I just can't seem to find oracle documentation about these relationships.Hemant K Chitale wrote:
"Database" and "Tablespace" are logical groupings for our convenience.
RMAN tracks backups at the datafile level.I think that is exactly what I was looking for. I just want to clarify my understanding.
If I run a level 0 on the database Sunday night, a database differential level 1 each night, and a level 0 on a specific tablespace each morning at 6AM followed by hourly tabelspace differential incrementals only for that tablespace, then Monday night's level 1 will be an incremental of the entire database pointing to Sunday's level 0 except for that specific tablespace for which it will be incremental from that tablespace's last level 1. Does that sound right? If so, then it sounds like to restore the entire database to its state on Tuesday at noon from media, I have to put these backups back on disk before running the RMAN restore:
- database level 0 from Sunday
- Monday night's database level 1
- Tuesday's tablespace level 0
- Tuesday's tablespace level1s from 7AM - noon
This means I can avoid putting Monday's tabelspace incrementals back right? From what I gather, the RMAN restore will put the blocks back into the datafiles at their correct SCNs, and then if there are any archive logs after that point in time, the RMAN recover will apply them. Does that all sound correct? -
Rman hot backup script gives error in R12.
hi experts
i m facing following prob when run the backup script. 1 day before the same script runs correctily but now it gives me error at the allocatioion of channel rest of command run correctly.
[root@testerp rman_log]# cat UAT_daily_rman_hot_bkp_01-11-14_140301.log
-bash: /root/.bash_profile: Permission denied
Recovery Manager: Release 11.1.0.7.0 - Production on Sat Jan 11 14:03:01 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: UAT (DBID=2855851979)
connected to recovery catalog database
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "end-of-file": expecting one of: "allocate, alter, advise, backup, beginline, blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, execute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, resync, repair, }, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
RMAN-01007: at line 12 column 1 file: standard input
RMAN>
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c2
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c3
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c4
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
Starting backup at 11-JAN-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=362 device type=DISK
channel ORA_DISK_1: starting incremental level 1 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00021 name=/d06/UAT/proddata/a_txn_data06.dbf
input datafile file number=00392 name=/d06/UAT/db/apps_st/data/a_txn_data01.dbf
input datafile file number=00401 name=/d06/UAT/db/apps_st/data/a_txn_data02.dbf
input datafile file number=00402 name=/d06/UAT/db/apps_st/data/a_txn_data03.dbf
input datafile file number=00022 name=/d06/UAT/proddata/a_txn_data07.dbf
input datafile file number=00014 name=/d06/UAT/db/apps_st/data/a_txn_data04.dbf
input datafile file number=00020 name=/d06/UAT/proddata/a_txn_data05.dbf
input datafile file number=00011 name=/d06/UAT/db/apps_st/data/sysaux01.dbf
input datafile file number=00018 name=/d06/UAT/db/apps_st/data/sysaux02.dbf
input datafile file number=00023 name=/d06/UAT/proddata/a_txn_data08.dbf
input datafile file number=00379 name=/d06/UAT/db/apps_st/data/undo01.dbf
input datafile file number=00024 name=/d06/UAT/proddata/sysaux03.dbf
input datafile file number=00025 name=/d06/UAT/proddata/sysaux04.dbf
input datafile file number=00033 name=/d06/UAT/proddata/a_txn_ind11.dbf
input datafile file number=00029 name=/d06/UAT/proddata/a_txn_ind09.dbf
input datafile file number=00030 name=/d06/UAT/proddata/a_txn_ind10.dbf
input datafile file number=00015 name=/d06/UAT/db/apps_st/data/a_txn_ind06.dbf
input datafile file number=00026 name=/d06/UAT/db/apps_st/data/a_txn_ind07.dbf
input datafile file number=00028 name=/d06/UAT/db/apps_st/data/a_txn_ind08.dbf
input datafile file number=00393 name=/d06/UAT/db/apps_st/data/a_txn_ind01.dbf
input datafile file number=00403 name=/d06/UAT/db/apps_st/data/a_txn_ind02.dbf
input datafile file number=00404 name=/d06/UAT/db/apps_st/data/a_txn_ind03.dbf
input datafile file number=00405 name=/d06/UAT/db/apps_st/data/a_txn_ind04.dbf
input datafile file number=00406 name=/d06/UAT/db/apps_st/data/a_txn_ind05.dbf
input datafile file number=00400 name=/d06/UAT/db/apps_st/data/a_media01.dbf
input datafile file number=00353 name=/d06/UAT/db/apps_st/data/system08.dbf
input datafile file number=00013 name=/d06/UAT/db/apps_st/data/system12.dbf
input datafile file number=00352 name=/d06/UAT/db/apps_st/data/system09.dbf
input datafile file number=00394 name=/d06/UAT/db/apps_st/data/a_ref01.dbf
input datafile file number=00407 name=/d06/UAT/db/apps_st/data/a_ref02.dbf
input datafile file number=00396 name=/d06/UAT/db/apps_st/data/a_summ01.dbf
input datafile file number=00395 name=/d06/UAT/db/apps_st/data/a_int01.dbf
input datafile file number=00008 name=/d06/UAT/db/apps_st/data/a_queue02.dbf
input datafile file number=00027 name=/d06/UAT/db/apps_st/data/a_queue03.dbf
input datafile file number=00031 name=/d06/UAT/db/apps_st/data/a_queue04.dbf
input datafile file number=00399 name=/d06/UAT/db/apps_st/data/a_queue01.dbf
input datafile file number=00001 name=/d06/UAT/db/apps_st/data/system01.dbf
input datafile file number=00002 name=/d06/UAT/db/apps_st/data/system02.dbf
input datafile file number=00003 name=/d06/UAT/db/apps_st/data/system03.dbf
input datafile file number=00004 name=/d06/UAT/db/apps_st/data/system04.dbf
input datafile file number=00005 name=/d06/UAT/db/apps_st/data/system05.dbf
input datafile file number=00398 name=/d06/UAT/db/apps_st/data/a_archive01.dbf
input datafile file number=00295 name=/d06/UAT/db/apps_st/data/system06.dbf
input datafile file number=00351 name=/d06/UAT/db/apps_st/data/system07.dbf
input datafile file number=00354 name=/d06/UAT/db/apps_st/data/system11.dbf
input datafile file number=00288 name=/d06/UAT/db/apps_st/data/system10.dbf
input datafile file number=00012 name=/d06/UAT/db/apps_st/data/apps_ts_tools01.dbf
input datafile file number=00016 name=/d06/UAT/db/apps_st/data/a_ref03.dbf
input datafile file number=00019 name=/d06/UAT/db/apps_st/data/MLSEIGL01.dbf
input datafile file number=00032 name=/d06/UAT/db/apps_st/data/RMAN01.dbf
input datafile file number=00397 name=/d06/UAT/db/apps_st/data/a_nolog01.dbf
input datafile file number=00314 name=/d06/UAT/db/apps_st/data/portal01.dbf
input datafile file number=00017 name=/d06/UAT/db/apps_st/data/a_int02.dbf
input datafile file number=00006 name=/d06/UAT/db/apps_st/data/ctxd01.dbf
input datafile file number=00010 name=/d06/UAT/db/apps_st/data/olap.dbf
input datafile file number=00009 name=/d06/UAT/db/apps_st/data/odm.dbf
input datafile file number=00007 name=/d06/UAT/db/apps_st/data/owad01.dbf
channel ORA_DISK_1: starting piece 1 at 11-JAN-14
[root@testerp rman_log]#
backup script is below:
in this script it returns error only at the channel allocaition rest of all backup command i run manually or with scirpt it runs correctly.4
i m not able to know why it returns error only at challnel allocation 1 day before it runs correctly.
[orauat@testerp rman_script]$ cat rman_backup.sh
#!/bin/sh
#ORACLE_SID=UAT
#BACKUP_START_TIME='date +"%y""%m""%d"_"%H""%M""%S"'
#ORACLE_HOME=/d06/UAT/db/tech_st/11.1.0
#PATH=$PATH:${ORACLE_HOME}:${ORACLE_HOME}/bin
#export ORACLE_SID
#export ORACLE_HOME
#export PATH
/d06/UAT/db/tech_st/11.1.0/bin/rman catalog rman/rman007 target sys/sysuat <<EOF
run
allocate channel c1 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_Arch_%c_%U';
sql 'alter system switch logfile';
sql 'alter system switch logfile';
sql 'alter system archive log current';
delete expired archivelog all;
crosscheck archivelog all;
backup archivelog all;
delete noprompt archivelog all completed before 'sysdate-4' backed up 1 times to disk;
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
backup incremental level 1 database;
delete expired backup device type disk;
delete obsolete device type disk;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
exit
EOF
regards
pritesh ranjanyes the script is edited
i have add some command line and edit it for take the full backup level=0 on the same directory with different formant name but location is same.
can i take full backup level 0 and incremental backup level 1 in the same directory with the different format name.
for exp:
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
i allocate these three channel for incremental level 1 backup;
the backup is done successfully without any error.
after that i have change
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
backup database incremental level 0
after doing the above changes it get the error. with the channel location.
i have to schedule daily incremental backup level 1 and weekly full backup level 0.
plz suggest me i have to take incremental 1 and full incremental level 0 backup on seperate directory for different format name.
regards
pritesh ranjan -
Hello,
my question might be a little strange, but I would just like to confirm my understanding to be sure about my testing.
Consider the following:
RMAN> list backup
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
5520 396.79M DISK 00:02:38 15-OCT-11
BP Key: 5541 Status: AVAILABLE Compressed: YES Tag: TAG20111015T190048
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T190048_79MKSH03_.BKP
List of Archived Logs in backup set 5520
Thrd Seq Low SCN Low Time Next SCN Next Time
1 37170 690296258 14-OCT-11 690301863 14-OCT-11
1 37171 690301863 14-OCT-11 690306944 14-OCT-11
1 37172 690306944 14-OCT-11 690312517 14-OCT-11
1 37173 690312517 14-OCT-11 690326343 14-OCT-11
1 37174 690326343 14-OCT-11 690328734 14-OCT-11
1 37175 690328734 14-OCT-11 690334332 14-OCT-11
1 37176 690334332 14-OCT-11 690354457 14-OCT-11
1 37177 690354457 14-OCT-11 690365309 14-OCT-11
1 37178 690365309 14-OCT-11 690383830 14-OCT-11
1 37179 690383830 14-OCT-11 690389381 14-OCT-11
1 37180 690389381 14-OCT-11 690399124 14-OCT-11
1 37181 690399124 14-OCT-11 690403117 14-OCT-11
1 37182 690403117 14-OCT-11 690408333 14-OCT-11
1 37183 690408333 14-OCT-11 690411748 14-OCT-11
1 37184 690411748 14-OCT-11 690417353 14-OCT-11
1 37185 690417353 14-OCT-11 690422345 14-OCT-11
1 37186 690422345 14-OCT-11 690428300 15-OCT-11
1 37187 690428300 15-OCT-11 690433347 15-OCT-11
1 37188 690433347 15-OCT-11 690439543 15-OCT-11
1 37189 690439543 15-OCT-11 690444502 15-OCT-11
1 37190 690444502 15-OCT-11 690450317 15-OCT-11
1 37191 690450317 15-OCT-11 690453707 15-OCT-11
1 37192 690453707 15-OCT-11 690457501 15-OCT-11
1 37193 690457501 15-OCT-11 690458775 15-OCT-11
1 37194 690458775 15-OCT-11 690464449 15-OCT-11
1 37195 690464449 15-OCT-11 690469446 15-OCT-11
1 37196 690469446 15-OCT-11 690474941 15-OCT-11
1 37197 690474941 15-OCT-11 690481459 15-OCT-11
1 37198 690481459 15-OCT-11 690484981 15-OCT-11
1 37199 690484981 15-OCT-11 690490292 15-OCT-11
1 37200 690490292 15-OCT-11 690495899 15-OCT-11
1 37201 690495899 15-OCT-11 690500991 15-OCT-11
1 37202 690500991 15-OCT-11 690508506 15-OCT-11
1 37203 690508506 15-OCT-11 690514835 15-OCT-11
1 37204 690514835 15-OCT-11 690519918 15-OCT-11
1 37205 690519918 15-OCT-11 690535732 15-OCT-11
1 37206 690535732 15-OCT-11 690626387 15-OCT-11
1 37207 690626387 15-OCT-11 690629393 15-OCT-11
1 37208 690629393 15-OCT-11 690634991 15-OCT-11
1 37209 690634991 15-OCT-11 690640154 15-OCT-11
1 37210 690640154 15-OCT-11 690646056 15-OCT-11
1 37211 690646056 15-OCT-11 690651236 15-OCT-11
1 37212 690651236 15-OCT-11 690656775 15-OCT-11
1 37213 690656775 15-OCT-11 690662593 15-OCT-11
1 37214 690662593 15-OCT-11 690668154 15-OCT-11
1 37215 690668154 15-OCT-11 690673574 15-OCT-11
1 37216 690673574 15-OCT-11 690677649 15-OCT-11
1 37217 690677649 15-OCT-11 690683129 15-OCT-11
1 37218 690683129 15-OCT-11 690688406 15-OCT-11
1 37219 690688406 15-OCT-11 690693988 15-OCT-11
1 37220 690693988 15-OCT-11 690698971 15-OCT-11
1 37221 690698971 15-OCT-11 690705146 15-OCT-11
1 37222 690705146 15-OCT-11 690710236 15-OCT-11
1 37223 690710236 15-OCT-11 690715886 15-OCT-11
1 37224 690715886 15-OCT-11 690719326 15-OCT-11
1 37225 690719326 15-OCT-11 690724866 15-OCT-11
1 37226 690724866 15-OCT-11 690729976 15-OCT-11
1 37227 690729976 15-OCT-11 690735596 15-OCT-11
1 37228 690735596 15-OCT-11 690740660 15-OCT-11
1 37229 690740660 15-OCT-11 690746167 15-OCT-11
1 37230 690746167 15-OCT-11 690751851 15-OCT-11
1 37231 690751851 15-OCT-11 690756900 15-OCT-11
1 37232 690756900 15-OCT-11 690759044 15-OCT-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
5521 Incr 0 494.68M DISK 00:03:24 15-OCT-11
BP Key: 5542 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79MKZP6W_.BKP
List of Datafiles in backup set 5521
File LV Type Ckp SCN Ckp Time Name
14 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\CCAPP.DBF
126 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\WAAPP.DBF
131 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\PSDEFAULT02.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Incr 0 193.66M DISK 00:01:38 15-OCT-11
BP Key: 5543 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML6DXJ_.BKP
List of Datafiles in backup set 5522
File LV Type Ckp SCN Ckp Time Name
3 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDOTBS01.DBF
4 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\USERS01.DBF
128 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX02.DBF
132 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDO3.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
5523 Incr 0 644.30M DISK 00:04:11 15-OCT-11
BP Key: 5544 Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML9NMK_.BKP
List of Datafiles in backup set 5523
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM01.DBF
2 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX01.DBF
127 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM02.DBF
129 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX03.DBF
BS Key Size Device Type Elapsed Time Completion Time
5524 18.86M DISK 00:00:10 15-OCT-11
BP Key: 5545 Status: AVAILABLE Compressed: YES Tag: TAG20111015T200023
Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T200023_79MLKTVM_.BKP
List of Archived Logs in backup set 5524
Thrd Seq Low SCN Low Time Next SCN Next Time
1 37233 690759044 15-OCT-11 690764137 15-OCT-11
1 37234 690764137 15-OCT-11 690768526 15-OCT-11
1 37235 690768526 15-OCT-11 690770962 15-OCT-11
RMAN> /** I left out some lines that seemed duplicate for my question - lines with the same SCN and some older archived logs. I can post the whole thing if it should turn out to be relevant.
What SCN would be appropriate for me to use, taking into account this is a level 0 incremental backup, to restore to the point of a full backup?
I'm fairly sure i can do the following: (and yes, this will result in a successful restore/recover)
run{
set until scn 690770341;
restore database;
switch datafile all;
recover database;
} But is that really the point that I should recover to? The other alternative would be to recover to the SCN of those archivelogs at the very bottom?
Thank you for any comments, whatever they are :-)I am copying the backups between different hosts (or external tape applications) and building the database from backups. So I create a blank instance and catalog the backup files, then specify an SCN to restore/recover.
Would the SCN part be unneeded? I guess if I want to recover to the latest possible state, I do not need to specify any SCN :-). For testing purposes I only specified the full backup SCN to save time, but in the event this would be needed in a production environment, you are right that I would need to recover to the latest possible SCN. Thanks for pointing that out. -
Standby database - RMAN level 0 - Recovery catalog - OEM.
We have configured rman level 0 backup from standby database on OEM. Job is running fine, but rman is not getting connected to recovery catalog. RMAN is connecting to target control file instead of recovery catalog. I understand we need to have DG broker configured for primary and standby for RMAN to connect recovery catalog if you run from OEM. We have configured the DG broker also. DG broker configuration is woriing fine. but Still Standby is not connecting the rman recovery catalog database.
Can anyone tell me what i should check.Catalog database is same for primary and standby. It is not working for both the version. What are all the basic check i need to do to debug the issue.
THIS IS LOG FROM OEM it is not connecting to target. instead of it is connecting to target control file.
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 6 22:40:28 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: CAAPRD1 (DBID=524360237, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
3> allocate channel oem_backup_disk2 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
4> allocate channel oem_backup_disk3 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
5> allocate channel oem_backup_disk4 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
6> allocate channel oem_backup_disk5 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
7> allocate channel oem_backup_disk6 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
8> allocate channel oem_backup_disk7 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
9> allocate channel oem_backup_disk8 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAATB1/level0/%U';
10> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_DATA' database;
11> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_ARCH' archivelog all not backed up;
12> release channel oem_backup_disk1;
13> release channel oem_backup_disk2;
14> release channel oem_backup_disk3;
15> release channel oem_backup_disk4;
16> release channel oem_backup_disk5;
17> release channel oem_backup_disk6;
18> release channel oem_backup_disk7;
19> release channel oem_backup_disk8;
20> } -
Rman full backup시 파일이 2개씩 생성 됩니다.
rman을 사용해서 cron으로 일요일 새벽마다 full backup 을 하고 있는데, 백업 볼륨 full 이 발생해서 로그를 살펴보니 아래와 같습니다.
같은 사이즈, 같은 생성 시각의 파일들이 2개씩 생성 되었습니다.
rman 백업에 별다른 작업을 하지 않았는데도 저렇게 결과가 나오니 어떻게 해야할지 감을 못잡겠습니다, 특히 아래 두껍게 표시한 줄은 로그도 좀 잘린것 같습니다.
■ rman full backup 수행 로그
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: ORCL (DBID=1151661191)
RMAN-06008: connected to recovery catalog database
RMAN>
RMAN-03021: executing script: full_backup
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: backup_loveme
RMAN-08500: channel backup_loveme: sid=224 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel backup_loveme: starting incremental level 0 datafile backupset
RMAN-08502: set_count=14779 set_stamp=619322468 creation_time=08-APR-07
RMAN-08010: channel backup_loveme: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00085 name=/sdisk02/data/ts01.dbf
RMAN-08522: input datafile fno=00027 name=/sdisk01/data/ts02.dbf
RMAN-08522: input datafile fno=00004 name=/sdisk01/data/temp01.dbf
RMAN-08522: input datafile fno=00006 name=/sdisk01/data/indx01.dbf
RMAN-08522: input datafile fno=00015 name=/sdisk01/data/ts03.dbf
RMAN-08013: channel backup_loveme: piece 1 created
RMAN-08503: piece handle=/sdisk03/backup/ff_driek734_14779_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:11:55
RMAN-08008: channel backup_loveme: starting incremental level 0 datafile backupset
RMAN-08502: set_count=14781 set_stamp=619323184 creation_time=08-APR-07
RMAN-080RMAN-08013: channel backup_loveme: piece 1 created
RMAN-08503: piece handle=/sdisk03/backup/ff_dsiek734_14780_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:11:55
RMAN-08008: channel backup_loveme: starting incremental level 0 datafile backupset
RMAN-08502: sRMAN-08013: channel backup_loveme: piece 1 created
RMAN-08503: piece handle=/sdisk03/backup/ff_dtiek7pg_14781_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:06:55
RMAN-08008: channel backup_loveme: starting incremental level 0 datafile backupset
RMAN-08502: set_count=14783 set_stamp=619323599 creation_time=08-APR-07
RMAN-080RMAN-08013: channel backup_loveme: piece 1 created
RMAN-08503: piece handle=/sdisk03/backup/ff_duiek7pg_14782_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:06:55
(후략...)
■ rman full backup 생성 파일
ls -al /sdisk03/backup/*
-rw-r----- 1 oracle dba 5780783616 4월 8 02:13 backup/ff_driek734_14779_1
-rw-r----- 1 oracle dba 5780783616 4월 8 02:13 backup/ff_dsiek734_14780_1
-rw-r----- 1 oracle dba 3423191552 4월 8 02:19 backup/ff_dtiek7pg_14781_1
-rw-r----- 1 oracle dba 3423191552 4월 8 02:19 backup/ff_duiek7pg_14782_1
(후략...)
■ RMAN> print script full_backup
allocate channel backup_loveme
type disk
format '/sdisk03/backup/ff_%u_%s_%p';
backup
incremental level=0
( database include current controlfile );
글 수정:
발로차는새문제가 해결 되었습니다만 원인이 오라클과 관련 없는 문제라... 글을 삭제 하고 싶은데 삭제 기능이 없네요 ^^
원인은 시스템에 cron 데몬이 2개가 돌고 있었습니다. 문제 해결은 가까운 곳부터 찾아야 하는것 같습니다 ㅜㅜ
포럼을 어지럽혀 죄송합니다.
Maybe you are looking for
-
Logout URL for 9iAS SSO Partner App
Hi, I've successfully set up an HTMLDB application as a Single Sign On partner APP. The login works perfectly, except I'm a little confused about the logout URL. Currently it is set to the default in the Authentication scheme, but it doesn't work too
-
Itried to upgrade my software at work which failed and wiped my phone . It then wouldnt restore either and put the phone in recovery mode. I installed a new version of itunes on a home computer and restored my phone but it now has none of my contacts
-
CSS not applying to a page if navigated to from one other page in the site
Hi, Quite new to dreamweaver. Built a site a few months ago and when updating the content I decided to update the style as well using the CSS sheet. Strange problem occurring.... When you navigate to the Contact Us page directly via URL or any but on
-
Adobe Air Problem with SQL Lite
Hi I am facing a strange, weired error.. and i am hating it SQLError: 'Error #3132: Data type mismatch.', details:'could not convert text value to numeric value.', operation:'execute', detailID:'2300' here is my code: stmt = new SQLStatement(); stmt.
-
Multiple toggle buttons to the same destination causes conflicts
I'm trying to set up multiple toggle buttons so that a user can click on a button at any time and set the state of the dashboard. Each toggle button has a unique value (and each one has the same static value for both on and off) and I've mapped all t