Re: Any performance issues for hot backups ??

There are some preformance issues when running hot backups, but when you consider that the alternate is to stop the database to make a backup or not to make one at all then I consider them to be non-issues.

When a tablespace is in backup mode additional entries are made in the redo log files. This extra activity is a small load that can be minimized by keeping the number of tablespaces in backup mode equal to the number of processes running backups commands. In other words do not alter all tablespaces into backup mode at one time, single thread the copies, and then alter everything out. Do this on a tablespace by tablespace basis.

If the online jobs run at night they may collide with batch jobs that process every row or large percentages of tables located on one disk. This can have a noticable impact, but tablespace distribution and file layout can be used to ease it.

Just minor problems. Hot backups are the best way to go.  

Mark Powell -- The only advise that counts is the advise that you follow so follow your own advise Received on Mon Jun 09 1997 - 00:00:00 CDT