Setting back the clock 2005-06-02 - By Powell, Mark D
The database will not care if you set the clock back one hour. You will
need to avoid running a point in time recovery that uses a time within
that hour but you can run a point in time recovery using SCN numbers
instead of time to recover to the proper point within the time change.
But the odds are you will not need to worry about this.
The question to be asked is will the application care if you set the
clock back? Did anyone use a date column as the key? If you repeat a
time then the application could get a ORA-00001 (See ORA-00001.ora-code.com) unique constraint
(%s.%s) violated error. Some reports that sort on date columns could be
a little strange since extra data might exist for a time period. These
are relatively minor issues. It is generally easiest to stop the
application for one hour till the database clock is once again in virgin
territory.
HTH -- Mark D Powell --
=20
-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of Eric Buddelmeijer
Sent: Thursday, June 02, 2005 12:29 PM
To: oracle-l@(protected)
Subject: Setting back the clock
Hello all,
=20
We have some sun database servers that have been transferred to the UK
while they originally have been configured in the Netherlands. The SA
wants to set the timezone to BST while it now is set to CEST, which
means the displayed time will be set back by 1 hour. Will this change
affect anything in the database? My concern lies mainly with SCN's and
point in time recovery. The database is not used very much yet, so it
will be possible to leave the database down for an hour. Can we just
stop the database, adjust the time and restart the database? What would
be the save approach?
=20
TIA,
Eric.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
|
|
