Re: Oracle archive mode and hot backups
From: Palooka <nobody_at_nowhere.com>
Date: Fri, 07 Aug 2009 01:05:11 +0100
Message-ID: <YcKem.232475$875.167310_at_newsfe20.ams2>
On 06/08/09 23:53, John Hurley wrote:
> On Aug 6, 5:35 pm, Jeff Morgan<jefang6..._at_gmail.com> wrote:
>
> snip
>
>> We have an Oracle 10g database on UNIX moving to a new data center.
>> We are still testing a stage server. The DBA state that the standard
>> is to have the database in archive mode to allow for hot backups.
>>
>> We ran into an issue when the 17 gigs of space in the archive folder
>> was full. The DBA's solution was to write a script to automatically
>> delete archive files when the folder reaches 10 gigs. I questioned
>> the need to create archive files if they are ultimately deleted. The
>> DBA stated that the actual archive files are not used and can be
>> deleted. The archive mode is only used for hot backups.
>>
>> From what I have researched, the archive files are required for
>> recovery. Can anyone shed some light on the whole archive/hot backup?
>
> If you are not really in production on this system ... ditching the
> archive logs can be done as needed probably.
>
> Maybe the archive log files are being put into different locations
> simultaneously ( multiple copies ) so that copy that was getting
> ditched really is un-necessary.
>
> Best advice is to ask the relevant DBA a couple more questions and get
> them to explain exactly what is going on.
What a load of bollocks. Sybrand is entirely right. What on earth is the point of putting the database into archivelog mode, and then throwing away the archived logs?
Date: Fri, 07 Aug 2009 01:05:11 +0100
Message-ID: <YcKem.232475$875.167310_at_newsfe20.ams2>
On 06/08/09 23:53, John Hurley wrote:
> On Aug 6, 5:35 pm, Jeff Morgan<jefang6..._at_gmail.com> wrote:
>
> snip
>
>> We have an Oracle 10g database on UNIX moving to a new data center.
>> We are still testing a stage server. The DBA state that the standard
>> is to have the database in archive mode to allow for hot backups.
>>
>> We ran into an issue when the 17 gigs of space in the archive folder
>> was full. The DBA's solution was to write a script to automatically
>> delete archive files when the folder reaches 10 gigs. I questioned
>> the need to create archive files if they are ultimately deleted. The
>> DBA stated that the actual archive files are not used and can be
>> deleted. The archive mode is only used for hot backups.
>>
>> From what I have researched, the archive files are required for
>> recovery. Can anyone shed some light on the whole archive/hot backup?
>
> If you are not really in production on this system ... ditching the
> archive logs can be done as needed probably.
>
> Maybe the archive log files are being put into different locations
> simultaneously ( multiple copies ) so that copy that was getting
> ditched really is un-necessary.
>
> Best advice is to ask the relevant DBA a couple more questions and get
> them to explain exactly what is going on.
What a load of bollocks. Sybrand is entirely right. What on earth is the point of putting the database into archivelog mode, and then throwing away the archived logs?
If the database does not need backup, then don't do backups. If it does, then establish requirements, etc, etc.
Palooka Received on Thu Aug 06 2009 - 19:05:11 CDT