Hot backup using script

hi,
please help me to take hot backup.
i want step by step procedure or send me some links
with regards,
Senthilkumarp

I think you'd be better asking about backups in the correct forum...
Try...
General Database Discussions
or
Recovery Manager (RMAN)

Similar Messages

How lot take log backup using script in HANA

We have SAP HANA SPS09.
1) We are using script provided by SAP Note#1651055 to take the data backup.But it seems it is not taking log backup.HOw can we schedule logbackup ? or we have to use DBACOCKPIT or Studio only?
2) My DB is log_mode OVERWRITE.I have taken backup using script.But when I tried to check the backup using below command
hdbbackupdiag --check -f -d /mnt/resource/backup/xb8_bkp_19022015/ --logDirs /mnt/resource/logbackup/,/usr/sap/XB8/HDB00/backup/log
ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
goazr1app904d:/usr/sap/XB8/HDB00>
Is it like we have the DB in OVERWRITE mode thats why we are getting this error?Will my recovery work ?
Thanks,
Mofizur

Did your issue got resolved?
We are having same issue. We are on Rev 82 and using DD Boost EMC to take the backup using BACKINT.
Though we are on Rev 82 I tried option provided by Pavan which didn't worked for me.
hdbbackupdiag --check --useBackintForCatalog --backintDataParamFile /opt/ddbda/config/sap_hana_ddbda.utl -d /usr/sap/A0T/SYS/global/hdb/backint
ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
Regards,
Nitin

Full Hot Backup using RMAN?

Dear all,
I want to take a full hot backup every week on sunday and the followings are the commands.
run
allocate channel ch1 type disk format '/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup
incremental level 0
database
plus archivelog delete input;
backup current controlfile;
backup spfile;
release channel ch1;
I have the following questions:
1) Am I need to define a directory named as "'/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck", so that the backup copies will put it here,right?
2) What format needs to be save in where and how to run it on weekly schedule basis?
3) I saw above script with "channel ch1", can I change it to "channel ch2"?
I am a beginner using RMAN, please let me know.
Best Regards,
amy

Which database version on which OS (looks like Unix/Linux)?
You have to create the directory '/db/BACKUP/RMAN', 'backup_%d...' is the filename created by RMAN.
%d Specifies the name of the database;
%t Specifies the backup set time stamp, which is a 4-byte value derived as the number of seconds elapsed since a fixed reference time. The combination of %s and %t can be used to form a unique name for the backup set;
%s Specifies the backup set number. This number is a counter in the control file that is incremented for each backup set. The counter value starts at 1 and is unique for the lifetime of the control file. If you restore a backup control file, then duplicate values can result. Also, CREATE CONTROLFILE initializes the counter back to 1;
%p Specifies the piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created;
%U Specifies a system-generated unique filename (default).
For scheduling a cron job could be defined or you use Enterprise Manager (10g and higher)
Channel name doesn't matter.
Werner

Frequency of Hot backups using RMAN

Hello.
After years of running various inhouse utilities to backup our Oracle databases we are now going to implement RMAN in our shop. We are running Oracle 10.2.0.4 EE databases on Solaris servers in Archivelog mode, so we'd like to perform "hot" backups. A caveat to this is that we also have "standby" databases that we manually manage via a series of scripts that works rather well and helps our CIO sleep at night.
So what we're trying to do is tackle one obstacle at a time. We'd like to implement RMAN hot backups (including archivelogs) without having RMAN remove the archivelog backups that are out there. We simply want RMAN to backup the archivelog files, we'll manage their movement and removal ourselves for the time being.
The script I have put together simply issues: Backup database plus archivelog format='/dumps/rman/F_Database_%d_set%s_%T_%U';
The configuration settngs (we want at least a 2 day recovery period) are:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/dumps/rman/controlfiles/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/dumps/rman/W_Database_%d_set%s_%T_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/xora01/app/oracle/product/10g/dbs/snapcf_glprd.f'; # default
We are using an RMAN catalog.
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.
Thanks for you opinions/suggestions...

Hi,
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.Your idea also not bad to save disk space. it is also depends on database size and space availability on your server.
or else you can go for weekly once fulll backup, remaining days incremental backups & archivelog backups.
rman incremental backups take only chanegd blocks so it wont occupy much space
1) sunday - full backup - level 0
2) monday - inc1 & arch
3) tuesday - inc2 & arch
4) wednesday - inc1 & arch
5) thursday - inc2 & arch
6) friday - inc1 & arch
7) saturday - inc2 & arch... & so on...
Thanks

Restoring a Hot backup using RMAN on a different server.

Hi
we are using oracle 10.2.0.4.0 on solaris 10 and using a separate catalog for RMAN backups.
we have taken a production db Hot backup as follows
level 0 backup on 28 th dec.
level 1 on 29,
level 1 on 30 and
level 1 on 31 st.
now today in the month of feb .
we would like to create a dev. DB on a diffent server which has diffent directory structure, i have to create a db using the above backups to setup the db like on 31 st Jan.
could you please provide the steps and advice how do i proceed.
Thansk fot the help.

Make level 0 and level 1 backups + control files backups + archived redo logs backup available on new host and use RMAN DUPLICATE.
See examples in http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1008564
Edited by: P. Forstmann on 2 févr. 2010 22:39
Edited by: P. Forstmann on 3 févr. 2010 07:57

Cold backup using script

Dear all,
I need a script to take cold backup of oracle database 10.2.0.3.0 .. such that if todays date is 28-oct-08.. then a folder with the name 28oct08 to be created in the backup location.then using the script user should login to the database shutdown the db and listener and make sure this is completely down and copy the complete oracle files and home location to the above mentioned folder in the server.. any links or points will help a lot ?
Kai

Kai, rather than write a script to perform a cold backup for whatever platform you are on I suggest you write a script to generate the cold backup script. The script can connect to the database, read various v$ and dba views such as dba_data_files to get the necessary data file information, and place the file names into OS copy commands. The resulting script should probably include steps to connect to and stop the database and to restart the database instance when it is complete.
Be sure to include a copy of your control file and the spfile in your backup. You do not need to include the online redo logs in your manual cold backup.
An alternate might be to run an rman backup while the database is in restricted session depending on how freely your site has given out the DBA role and/or restricted session privilege.
HTH -- Mark D Powell --

Restore hot backup using RMAN?

Hi,
We are taking hotbackup using rman level0,leve1,level2. Now i want to restore level 0 first then level 1 and level 2.. how to restore like this
Thanks in advance

You don't have to explicitly restore each L0, L1 etc backup.
When you specify a SET UNTIL, RMAN identifies the backups (starting with the latest L0 before the SET UNTIL) that are to be restored and attempts to restore them.
If the backups were to disk and are no longer on disk (i.e. you have moved them to tape), you have to ensure that the backups are made available (by copying them back from tape to disk).
You can use RESTORE DATABASE VALIDATE and RESTORE ARCHIVELOG VALIDATE to identify the backups that are required.
See http://hemantoracledba.blogspot.com/2010/03/misinterpreting-restore-database.html
Hemant K Chitale

Missing logfiles when hot backup is taken using RMAN

Hello All,
I am having the below situation .Please help to clarify.
I have taken hot backup using RMAN. Database is in Archivelog mode. It doesn't take backup of online redo logs. The status of my redo logs are as below. All are not archived.
/u01/app/oracle/oradata/redo01.log ----Active---Not Archived
/u01/app/oracle/oradata/redo03.log ----Active---Not Archived
/u01/app/oracle/oradata/redo03.log----Current---Not Archived
Now, I am using the backup to restore a database on another machine. But as the logs are not archived, I may miss some data.
How can I get the data also?
Regards
VJ..

I have taken hot backup using RMAN. Database is in Archivelog mode. It doesn't take backup of online redo logs. The status of my redo logs are as below. All are not archived.
/u01/app/oracle/oradata/redo01.log ----Active---Not Archived
/u01/app/oracle/oradata/redo03.log ----Active---Not Archived
/u01/app/oracle/oradata/redo03.log----Current---Not Archived
Now, I am using the backup to restore a database on another machine. But as the logs are not archived, I may miss some data.
How can I get the data also?If the redo log status is still "ACTIVE" that mean, still archiving is in progress,
You can give even
SQL> alter system checkpoint;and do you have any idea at what point you want to recover your database? Even though they are in ACTIVE stauts, when you are taking backup. Still you can apply them how much you want. There will be no lost data. But ensure you haven't opened[resetologs] database.

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Hot backup getting delayed everyday

Hi All,
Everyday our hot backup job is getting delayed by a significant time. Before the tablespaces are placed into begin backup mode we spotted the alert log flooded with the below message ,
Mon May 21 00:23:46 2012
Incremental checkpoint up to RBA [0x396b.3365.0], current log tail at RBA [0x396
b.3386.0]
Mon May 21 00:54:03 2012
Incremental checkpoint up to RBA [0x396b.3b81.0], current log tail at RBA [0x396
b.3b98.0]
Mon May 21 01:24:21 2012
Incremental checkpoint up to RBA [0x396b.495a.0], current log tail at RBA [0x396
b.497a.0]
Mon May 21 01:54:47 2012
Incremental checkpoint up to RBA [0x396b.5109.0], current log tail at RBA [0x396
b.5137.0]
Mon May 21 02:25:13 2012
Incremental checkpoint up to RBA [0x396b.6771.0], current log tail at RBA [0x396
b.67b6.0]
Also after the tablespaces are placed into begin backup mode before the end backup occurs the altert log is also flooded with the below messages,
Incremental checkpoint up to RBA [0x396b.24107.0], current log tail at RBA [0x39
6b.24afe.0]
Mon May 21 05:58:39 2012
Incremental checkpoint up to RBA [0x396b.2569e.0], current log tail at RBA [0x39
6b.257f2.0]
Mon May 21 06:28:56 2012
Incremental checkpoint up to RBA [0x396b.2815a.0], current log tail at RBA [0x39
6b.28925.0]
Mon May 21 06:59:14 2012
Incremental checkpoint up to .
Then the tablespaces are placed into end backup mode resulting in significant delay.
Please help how we can reduce the backup time and also please throw some light on these checkpoint related messages.

Hi Jonathon ,
Thanks for your valuable suggestion.
Here in our environment all the tablespaces go into hot backup mode at a time instead of one by one through a script.
Previously when the hot backup used to work fine the number of incremental checkpoints between begin backup and end backup were significantly less. It is also evident from the excerpt of the alert log file.
alter tablespace PROAIMIS01 begin backup
Completed: alter tablespace PROAIMIS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace SYSTEM begin backup
Completed: alter tablespace SYSTEM begin backup
Mon Apr 19 01:02:47 2010
alter tablespace MAPDS01 begin backup
Completed: alter tablespace MAPDS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace ADMN01 begin backup
Completed: alter tablespace ADMN01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace PACESIS01 begin backup
Completed: alter tablespace PACESIS01 begin backup
Mon Apr 19 01:02:47 2010
alter tablespace CTPDS01 begin backup
Completed: alter tablespace CTPDS01 begin backup
Mon Apr 19 01:07:47 2010
***Completed checkpoint up to RBA [0x1ced.2.10], SCN: 10912956469916***
***Mon Apr 19 01:14:13 2010***
***Incremental checkpoint up to RBA [0x1ced.fd.0], current log tail at RBA [0x1ced.***
***10a.0]***
***Mon Apr 19 01:44:32 2010***
***Incremental checkpoint up to RBA [0x1ced.73f.0], current log tail at RBA [0x1ced***
***.89e.0]***Mon Apr 19 01:51:58 2010*alter tablespace CTPIS01 end backup*Mon Apr 19 01:51:58 2010
Completed: alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace MAPDS01 end backup
Completed: alter tablespace MAPDS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace SYSAUX end backup
Completed: alter tablespace SYSAUX end backup
Mon Apr 19 01:51:58 2010
alter tablespace AUDT01 end backup
Completed: alter tablespace AUDT01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMIS01 end backup
Completed: alter tablespace PROAIMIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace MAPIS01 end backup
Completed: alter tablespace MAPIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace UNDO01 end backup
Completed: alter tablespace UNDO01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace USER01 end backup
Completed: alter tablespace USER01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMDS01 end backup
Completed: alter tablespace PROAIMDS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PACESIS01 end backup
Completed: alter tablespace PACESIS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace XDB01 end backup
Completed: alter tablespace XDB01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYMANTEC_I3_ORCL end backup
Completed: alter tablespace SYMANTEC_I3_ORCL end backup
Mon Apr 19 01:52:00 2010
alter tablespace CTPDM01 end backup
Completed: alter tablespace CTPDM01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace PACESDS01 end backup
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
Mon Apr 19 01:52:01 2010
alter database backup controlfile to trace
Completed: alter database backup controlfile to trace
Mon Apr 19 01:52:01 2010
alter database backup controlfile to '$CTLBKPDIR/$ORACLE_SID-$dt-$tm.ctl'
Completed: alter database backup controlfile to '$CTLBKPDIR/$ORACLE_SID-$dt-$tm.
ctl'
Mon Apr 19 01:52:03 2010
Beginning log switch checkpoint up to RBA [0x1cee.2.10], SCN: 10912957698129
Thread 1 advanced to log sequence 7406
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
Mon Apr 19 01:52:01 2010
alter database backup controlfile to trace
Completed: alter database backup controlfile to trace
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Completed: alter tablespace CTPDS01 begin backup
Mon Apr 19 01:07:47 2010
Completed checkpoint up to RBA [0x1ced.2.10], SCN: 10912956469916
Mon Apr 19 01:14:13 2010
Incremental checkpoint up to RBA [0x1ced.fd.0], current log tail at RBA [0x1ced.
10a.0]
Mon Apr 19 01:44:32 2010
Incremental checkpoint up to RBA [0x1ced.73f.0], current log tail at RBA [0x1ced
.89e.0]
Mon Apr 19 01:51:58 2010
alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
Completed: alter tablespace CTPIS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace MAPDS01 end backup
Completed: alter tablespace MAPDS01 end backup
Mon Apr 19 01:51:58 2010
alter tablespace SYSAUX end backup
Completed: alter tablespace SYSAUX end backup
Mon Apr 19 01:51:58 2010
alter tablespace AUDT01 end backup
Completed: alter tablespace AUDT01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMIS01 end backup
Completed: alter tablespace PROAIMIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace MAPIS01 end backup
Completed: alter tablespace MAPIS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace UNDO01 end backup
Completed: alter tablespace UNDO01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace USER01 end backup
Completed: alter tablespace USER01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PROAIMDS01 end backup
Completed: alter tablespace PROAIMDS01 end backup
Mon Apr 19 01:51:59 2010
alter tablespace PACESIS01 end backup
Completed: alter tablespace PACESIS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace XDB01 end backup
Completed: alter tablespace XDB01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace ADMN01 end backup
Completed: alter tablespace ADMN01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYMANTEC_I3_ORCL end backup
Completed: alter tablespace SYMANTEC_I3_ORCL end backup
Mon Apr 19 01:52:00 2010
alter tablespace CTPDM01 end backup
Completed: alter tablespace CTPDM01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace PACESDS01 end backup
Completed: alter tablespace PACESDS01 end backup
Mon Apr 19 01:52:00 2010
alter tablespace SYSTEM end backup
Completed: alter tablespace SYSTEM end backup
Mon Apr 19 01:52:01 2010
alter tablespace CTPDS01 end backup
Completed: alter tablespace CTPDS01 end backup
Mon Apr 19 01:52:01 2010
alter tablespace PERF01 end backup
Completed: alter tablespace PERF01 end backup
But for the last couple of days the number of incremental checkpoints seem to be higher between begin backup and end backup like below,
Incremental checkpoint up to RBA [0x396d.3129.0], current log tail at RBA [0x396
d.366c.0]
Tue May 22 03:14:23 2012
Incremental checkpoint up to RBA [0x396d.147a8.0], current log tail at RBA [0x39
6d.15ac8.0]
Tue May 22 03:44:45 2012
Incremental checkpoint up to RBA [0x396d.1c679.0], current log tail at RBA [0x39
6d.1d177.0]
Tue May 22 04:15:08 2012
Incremental checkpoint up to RBA [0x396d.20387.0], current log tail at RBA [0x39
6d.205dd.0]
Tue May 22 04:45:30 2012
Incremental checkpoint up to RBA [0x396d.20dcf.0], current log tail at RBA [0x39
6d.2109e.0]
Tue May 22 05:15:48 2012
Incremental checkpoint up to RBA [0x396d.23af5.0], current log tail at RBA [0x39
6d.23d6a.0]
Tue May 22 05:46:05 2012
Incremental checkpoint up to RBA [0x396d.245e3.0], current log tail at RBA [0x39
6d.245ef.0]
Tue May 22 05:47:08 2012
Also the parameter log_checkpoint_interval is set to zero here.
log_checkpoint_interval integer 0
And the parameter fast_start_mttr_target is set to 300
fast_start_mttr_target integer 300
Please suggest ..

Question on recovery from Hot backup

Whenever I tried to recover from my hot backup using recover database untill cancel (or any other until option)..
I get messages similar to the following :
SQL> recover database using backup controlfile until cancel ;
ORA-00279: change 212733060 generated at 11/18/2008 23:50:58 needed for thread
1
ORA-00289: suggestion : /d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00280: change 212733060 for thread 1 is in sequence #282
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/2_257_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/3_258_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 4
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
I have all my archive files in the archive dest location.
Is there any way to prevent this warning messages and let oracle find all the archive files?
As you can see from the messages, Oracle is finding the correct file, then why there is an error message and why we have to provide the file names one-by one.
Please help !!!

Oracle will look for needed archive logfile from your log archive destination.
If you are sure all these files are under /d01/oradata/devl/arc/, you can input AUTO, Oracle will work down the list until done.

Hot Backup Of Database

How much time would oracle take if I take Hot Backup (using Imp/Exp statement) of a 60 GB database? Are there some other ways also of taking Hot BackUp ? How much would it effect oracle's performance while backup is taking place as the database is 24 x 7 and is taking uploads every few seconds?

Do not use IMP/EXP as a backup strategy. These utilities are intended for moving data about. Backup means taking a copy of the OS files - data files, redo logs, etc. To find out more please read the docs.
Cheers, APC

Backup/recovery - hot backups

My backup strategy is hot backups
To test it out I copied the hot backups to a test machine (which had a previous copy of the instance)
When I tried to recover, the instance mounted but would not open
But on trying to open - it keeps insisting on recover using backup control file and never allows me to open .
Any help?
startup;
ORACLE instance started.
Total System Global Area 75292048 bytes
Fixed 64912 bytes
Variable Size 7938048 bytes
Database Buffers 67108864 bytes
Redo Buffers 180224 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Regards
Andy
null

While you are taking a hot backup of the database. Backup of controlfile is required. If you use tool like legato networker it takes controlfile backup automatically. If you do hot backup manually you have to take backup controlfile to trace. This type of backup controlfile doesn't contain the stop scn for each datafile its set to infinite so it asks for the archive log. You should apply the archivelog and open the database with the resetlogs option. You should apply to the current online redolog file to have upto date database from the other database by just making a switch logfile and copy the archived log to the test machine.
Hope you got what i am saying. I have made hot backups using legato networker which makes backup controlfile to trace.
Thanks and regards,
hari

RMAN hot backup requires archivelog all the time?

Hi all,
consider the case: a dml operation is running in oracle 11g database. after sometime it got completed and issued a commit statement. Now i took a full database hot backup using rman. but dint take archivelog backup(its must i know, but i want to know whether we can do incomplete recovery using only the full database backup and open database using RESETLOGS option?
Kindly let me know whether we can do incomplete recovery using only full database backup or we must need archivelog to open the database?
Regards,

Say your BACKUP DATABASE begins at 01:00am and finishes at 01:50am. At the minimum, you need to backup the Archivelogs from 01:00am to the first archivelolg after 01:50am. Technically you don't need the archivelogs of before 01:00am. However, if you want the ability to do a point in time recovery (which is a MUST for any production database), you would also backup the "earlier" archivelogs which can be used with the previous database backup.
Your commit does NOT guarantee that the database files are immediately updated -- DBWR "lazily" defers writing to the database files. Your commit is preserved in the online redo log. This has to be archived as an Archivelog and backed up.
Hemant K Chitale

When to use REUSE/SET, NO-ARCHIVELOGS in create controlfile in HOT BACKUP?

I am a trainee Oracle DBA and have the following queries. Kindly reply with detailed explanation as I want to get my concepts cleared!
Q1>> While doing a user managed hot backup, when we are creating a control file(CREATE CONTROLFILE) from trace for recovery when do we use the create control file with the following options:
*1. REUSE / SET*
*2. ARCHIVELOGS / NOARCHIVELOGS*
Q2>> In what scenarios do we re-create the control file while recovering datafiles from a hot backup??
Thanks a tonne!
Regards,
Bhavi

Hemant K Chitale wrote:
1.1 It is not "REUSE/SET". These are two very different clauses.
REUSE is when you want the CREATE to overwrite the existing controlfile(s). If the controlfile(s) {as named in the instance parameter file, initSID.ora or spfileSID.ora} is/are already present, the CREATE fails unless REUSE is specified.
SET is when you want to change the database name. Oracle then creates the controlfile(s) with the specified database name and updates the headers of all the datafiles. If you run a CREATE with a database name that is different from that in the datafile headers, the CREATE fails unless you include a SET to specify that the name must be changed. Note that this also means that the name in the instance parameter file must already have been updated.
1.2 ARCHIVELOG/NOARCHIVELOG is to set the database state. The same is achieved by issuing an "ALTER DATABASE ARCHIVELOG/NOARCHIVELOG" when the database is MOUNTed but not OPEN.
2. You'd run the CREATE CONTROLFILE if you do not have a binary backup of the controlfile.
Optionally, you can also use CREATE CONTROLFILE to rename all the datafiles by specifying the new locations of the datafiles -- the datafiles must already be present in the new locations, else the CREATE fails if it doesn't find a datafile that is included in the list of datafiles included in the CREATE statement.
RMAN is the correct way to run Backups. User Managed Backup scripts are used in cases like Storage-based Snapshots / SnapClones / BCV.
Hemant K ChitaleThanks that was really helpful..One last question when to use the resetlogs/noresetlogs clause in the create controlfile statement. I have noticed that at times it accepts resetlog while at times it accepts noresetlogs

Hot backup using script

Similar Messages

Maybe you are looking for