Re: Recovery from noarchive db corrected

2001-04-07 Thread Paul Drake
Sinardy, what's your uptime requirement? You're allowed a weekly cold shutdown for backup? what I'm asking is - when you are copying the datafiles to tape, its during a clean, cold shutdown, right? Have you ever tested the recovery portion of your backup/recovery scheme? If your 'copying files

RE: Recovery from noarchive db corrected

2001-04-06 Thread Sinardy Xing
Currently the application insert data from batch localy and a bit from online insertion. We have clustering for our database. noarchive, I do export tables after run batch (daily), weakly copy out all dbf files and ctl and redo log files. and copy them to tape. It's that true once the redo log

RE: Recovery from noarchive db corrected

2001-04-06 Thread Hallas, John
0) 115 945 6643 * +44 (0) 115 945 6774 -Original Message- From: Sinardy Xing [mailto:[EMAIL PROTECTED]] Sent: 06 April 2001 11:10 To: Multiple recipients of list ORACLE-L Subject: RE: Rec

RE: Recovery from noarchive db corrected

2001-04-06 Thread Hallas, John
To: Multiple recipients of list ORACLE-L Subject:RE: Recovery from noarchive db corrected Hi Hallas and All DBAs Thank you for your advise. I have a question if I turn on our archive redo log do I need to copy out

RE: Recovery from noarchive db corrected

2001-04-06 Thread Sinardy Xing
5 945 6774 -Original Message- From: Sinardy Xing [mailto:[EMAIL PROTECTED]] Sent: 06 April 2001 11:10 To: Multiple recipients of list ORACLE-L Subject: RE: Recovery from noarchive db

RE: Recovery from noarchive db corrected

2001-04-06 Thread Tim Sawmiller
I would tell them that THEY are then responsible for database recovery if a problem should occur. If the DBA is to be responsible, then the DBA should be able to utilize the recovery tools provided by the vendor (Oracle). [EMAIL PROTECTED] 04/06/01 12:45AM The developer application running

Re: Recovery from noarchive db corrected

2001-04-06 Thread David A. Barbour
Sinardy Xing wrote: The developer application running huge batch inserting data into database, that is what they told me, if you are me what you will do? Sinardy, You definitely want to turn archiving on. Without it, your recovery options are limited to the last offline backup of the

Re: Recovery from noarchive db corrected

2001-04-06 Thread Terry Ball
Here, here!!! If they can dictate the fact the the DB will not be in archive log mode, they must live with unrecoverability. Terry Tim Sawmiller wrote: I would tell them that THEY are then responsible for database recovery if a problem should occur. If the DBA is to be responsible, then

RE: Recovery from noarchive db corrected

2001-04-05 Thread Sinardy Xing
Our Developer prefer the archive off, I can't change that anymore :( -Original Message- Sent: Thursday, 5 April 2001 8:54 PM To: LazyDBA mailing list Turn archiving on. -Original Message- From: Sinardy Xing [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 4:57 AM

Re: Recovery from noarchive db corrected

2001-04-05 Thread Joseph S. Testa
assuming you're the dba, since when does the developer dictate recoverability to a DBA about a database. sounds like a role problem there. joe Sinardy Xing wrote: Our Developer prefer the archive off, I can't change that anymore :( -Original Message- Sent: Thursday, 5 April 2001

RE: Recovery from noarchive db corrected

2001-04-05 Thread Sinardy Xing
The developer application running huge batch inserting data into database, that is what they told me, if you are me what you will do? -Original Message- Testa Sent: Friday, 6 April 2001 11:55 AM To: Multiple recipients of list ORACLE-L assuming you're the dba, since when does the

RE: Recovery from noarchive db corrected

2001-04-05 Thread Suhen Pather
Sinardy, Who will recover the database in case of a failure? Turing on archiving would not hinder performance so much. Proper planning of your backup strategy and db setup will have little overhead on performance of your database. You cannot sacrifice backups for a marginal increase in

RE: Recovery from noarchive db corrected

2001-04-05 Thread Arn Klammer
The actual archiving of log files itself should not impact the performance of the insert jobs, unless the archiving process is slow enough to cause the database to pause while a log is archived so it can be reused. The only other reason why the developers wouldn't want it is if the space