A hot backup, or one taken while the database is active, can only give a read-consistent copy but doesn’t handle active transactions. You must ensure that all redo logs archived during the backup process are also backed up.
Limitations on hot or on-line backups:
๔ The database must be operating in ARCHIVELOG mode for hot backups to work.
๔ Hot backups should only be done during off or low-use periods.
The hot backup consists of three processes:
1. The tablespace data files are backed up.
Make a script. Select all the talespaces, make 'alter tablespace tablespace_name begin backup'. Copy the corresponding datafiles. then 'alter tablespace tablespace_name end backup'.
2. The archived redo logs are backed up.
select the member from v$logfile and copy them.
Then 'alter system switch logfile;'.
archive log all;
see the archive destination from v$parameters. copy the files.
3. The control file is backed up.
alter database backup control file to /tape1/ora_conbackup.bac;
1 comment:
Thank you so much it has been a very good guide, now to make hot backup, oracle is without a doubt simple and easy utilizing your guidance. Thank you
Post a Comment