RE: ** fall back backups

Did the analyst in the TAR say why he was recommending rebooting the database? I've never rebooted a database just because the clock changed and I can't see why it would make a difference. Doing a point-in-time recovery to a time between 1 and 2 AM (clocks went back an hour at 2 AM) will be problematic regardless of whether or not you reboot, but SCN based recover won't have a problem.  

There may be applications out there that do not handle daylight savings well (i.e. a DATE column as a primary key that gets duplicates), in which case you may do something like take the server offline for an hour while the clock changes. As a general rule, though, there is no need to bounce a database just because you changed the operating system's clock.  

Justin Cave <jcave_at_ddbcinc.com>

Distributed Database Consulting, Inc.

http://www.ddbcinc.com  

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of A Joshi Sent: Sunday, October 30, 2005 8:43 PM
To: oracle-l_at_freelists.org
Subject: ** fall back backups  

Hi,

  Now that clocks have been set back one hour (in us of a etc), it is time to bounce the databases. Since Oracle says it needs to be done (read some analyst in a TAR said it).

Is it for backups? I agree time based recovery to a point in time could lead to issues. However, will it affect the regular recovery until cancel which I think goes by SCN/log #. Please correct me if I am wrong.

Also once you have a couple of backups after the fall back resetting of clock is it still necessary to bounce databases and immediately take 2 backups?

  Apart from backups does setting the clock back affect anything else on the database? Thanks

Yahoo! FareChase - Search multiple travel sites in one click. <http://us.lrd.yahoo.com/_ylc=X3oDMTFqODRtdXQ4BF9TAzMyOTc1MDIEX3MDOTY2OD gxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--/SIG=110oav78o/**http%3a/f arechase.yahoo.com/>

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