In article <3397D5DA.7A4A_at_ats.nld.alcatel.nl>, ven_at_ats.nld.alcatel.nl says...
>
>I am looking into the possibilities Oracle can give me
>to do 'hot backups'. From a developers point of view I don't
>have to do anything, except require that the database is started
>in the ARCHIVELOG mode. (at least that is what I read so far,
>if I am wrong in this assumption, please let me know).
>
>I am pretty sure that when I write the above as a conclusion
>I will immediately be getting responses (from within my company)
>saying that this solution is not workable because of performance issues.
>Therefor I am asking this group for 'field' experiences. Are there
>any reports or does anyone have experience that indicates that the
>performance of the Oracle database degrades (significantly) or
>hardly affects it when running in archivelog mode ?
>
- From what I understand about hot backups, you will have more activity in the
'redo' logs because Oracle data blocks will be written to them rather than
just the data inserted/updated/deleted. This is why Oracle recommends
not putting all tablespaces in 'backup' mode all at once.
- You will have disk I/O and CPU contention with Oracle and the backup utility.
- Keep an eye on the archived logs so disk doesn't fill up due to
more data archived(item #1).
- Make sure you have enough redo logs AND you can archive them fast enough.
If you wrap on the redo logs and Oracle is not finished archiveing them, everthing
stops until the redo log is archived.
Scott Overby E-mail scott.overby_at_sdsdata.com
Sr. Systems Analyst
Strategic Data Systems FAX (414) 459-9123
615 Penn Ave.
Sheboygan, WI 53082
Received on Fri Jun 06 1997 - 00:00:00 CDT
