'justageek' never used the word online. For non-archive system's cold backups you do want the log files - when restoring you copy data, control and log files and startup, that's all.
Printable View
'justageek' never used the word online. For non-archive system's cold backups you do want the log files - when restoring you copy data, control and log files and startup, that's all.
you dont need the online redo logs because they are not needed for recover whatsoever in restoring a cold backup, you can back them up as jmodic mentioned, it is harmless but not necessary
Can he just recreate the control file
by issuing first the ALTER DATABASE BACKUP CONTROLFILE TO TRACE command?
And for this trace file in bdump to identify
what are the necessary files to be copied from production
to development. Then edit it, customize the new directories
and new database name?
before he can use this script to actually duplicate the original database except perhaps of the new database name
and the new directory locations of the new db?
Just make sure that if your going to create the same
database in the same machine your switching your current
ORACLE_SID(maybe PRD) to the new ORACLE_SID(maybe DEV).
Before you clone the production database.
True, but "redo logs" and "online redo logs" mean exactly the same in this context. I used word "online" just to be very specific, so that noone will confuse "redo logs" with "archived redo logs".Quote:
Originally posted by julian
'justageek' never used the word online.
I do not understand why are you emphasizing the difference between archivelog and noarchivelog systems as regarding to cold backup. There is absolutely no difference between the two when performing cold backup. Yo only need to backup data files and controlfiles, that's all. You don't need to backup redo logs (=online redologs) in either of the configurations.Quote:
For non-archive system's cold backups you do want the log files - when restoring you copy data, control and log files and startup, that's all.
[/QUOTE]
I do not understand ...[/QUOTE]
Let me explain. In order to perform cold backup, and pay attention, the subject of this thread is cold backup, you shutdown normal, trans. or immed., then you back up all data files, redo lof files, control files, password files and parameters files (ref.: Oracle UNiversity B&R ILT) 4-10). When you backup a nonarchive DB you restore all those files after the shutdown abort. Then open (ref: Couchman's book page 736).
I just want to go back what justageek had ask:
When you(justageek) are talking about two environment (dev and prod),
did you mean two database in the same machine or two machines with
Production in one machine and development in second machine?
Keep it cool.
Julian,
Pls remember that when u shutdown abort..u need to have an instance recovery and ofcourse u need redo logs for that but to me a proper cold backup would be one that was shutdown normal which again means no need for redo logs.
I would go by jmodic.
Regards,
julian
you can back them up but they are NOT necessary because you shutdown the database cleanly
Just that the downside is you have to recreate the redo logs when you restore the cold backup
You can check Oracle 8i ILT page 4-5 Enterprise DBA Part 1B: Backup and Recovery Workshop (it´s page 4-5 on my PDF, if you have the book it may be in a different page)
[Edited by pando on 09-13-2001 at 06:46 AM]
Well, tell me what's easier: coping the 3-6 (whatever amount) of 4-10M files along with all the other ones or start recreating log files?
A consistent full backup of a non-archivelog DB is one containg the logs, even the init.ora and pwd files!
This discussion leads to nowhere... You may backup whatever you want, it's your database :-)
Redologs are recreated automatically! You don't need to recreate them manually! All you have to do is to add one word when starting the database after restore: RESETLOGS. So what's easier ? For me adding the word RESETLOGS is easier.Quote:
Originally posted by julian
Well, tell me what's easier: coping the 3-6 (whatever amount) of 4-10M files along with all the other ones or start recreating log files?
A consistent full backup (aka cold backup) *both in archivelog and non-archivelog* (as there is no difference, as I've allready said), DOES NOT NEED REDOLOG FILES. Not that it does not need them, Oracle Corp. explicitely discurage including redo logs in any kind of backup sets. See the manuals: http://otn.oracle.com/docs/products/...pst.htm#425901Quote:
A consistent full backup of a non-archivelog DB is one containg the logs, even the init.ora and pwd files!
Maybe you'll belive it from the mouth of Thomas Kyte:
==================================
an offline backup is "easy". do a shutdown (not shutdown abort)
and copy all
o datafiles
o controlfiles
to another location. You've just done your cold backup (or use backup manager). do not copy redo.
http://asktom.oracle.com/pls/ask/f?p...0_P8_DISPLAYID,F4950_P8_CRITERIA:1430804148892
==================================
Sure, you can include them, but hey, why not simply backup the whole system, this way you surely won't forget anything :). On one of the databases I'm looking after, we have 5 redo groups of 100M each. So why would I backup them, wasting half gigabytes of storage? And there are 2 members in each group. Should I include them in backup also, wasting another 500megs?
True.Quote:
This discussion leads to nowhere... You may backup whatever you want, it's your database :-)