RE: Nologging clause

From: Arm, Mike (IS) <"Arm,>
Date: Thu, 2 Apr 2009 08:40:35 -0500
Message-ID: <87EDF3B5B6F28D48AACB5F85280FDFD90259EAF7_at_XMBIL121.northgrum.com>


 You need a trigger to bring up the Automatic Resume Writer.

Mike
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Yechiel Adar Sent: Thursday, April 02, 2009 2:37 AM
Cc: oracle-l_at_freelists.org
Subject: Re: Nologging clause

Apart from the technical question I think there is a problem with the basic assumption.
What happened if the CEO had his ticket refreshed and the database later went down.
In this case you will restore to the last backup of last night. The CEO will try to work and will not be able because the ticket in the database id old and expired.
Who do you think will not get a bonus that year.

I think that this kind of data should be in archive log database and on RAC, as the whole company will stop working if the server went down.

Adar Yechiel
Rechovot, Israel

William Wagman wrote:
> to house the repository for the tickets. There is no need to be able
> to do a point in time recovery of the CAS repository

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 02 2009 - 08:40:35 CDT

Original text of this message