Oracle is designed to handle time changes. For
example switching to and from daylight savings. This is because the
archive logging is not dependent on a date. It has its own sequence.
Therefore changing the date and time even while oracle is up is no
problem. I have done this many times for testing. The only thing to
watch for is if you are using DBMS_JOBS. Changing the time may cause a job
not to execute or to run when you don't want it to. Just make sure there
is no time conflict with any of these jobs and also 'cron' jobs and go ahead and
change the time. I believe your backup strategy is an overkill which I
personally would not do but you decide if you would feel safer with the backups,
then go ahead with your plan.
HTH,
John>>> EShevtsov_at_flagship.ru 09/18/01 08:46AM
>>>Hi List,we have about 2 min difference between the time
on our db server and therest boxes in our network.Actually, the time on
DB server is 2min slow than the network time.It causesreal pain to
us.I think about the following order of time synchronization:1.
Normal shutdown the DB and listener2. immediate cold backup2. setup time
synchronization on the unix level3. startup the DB and listener4. Normal
shutdown DB and listener5. immediate cold backup6. startup DB and
listenerIs this correct ? Any possible troubles? Any good
links?Thanks in advance,Ed-- Please see the official
ORACLE-L FAQ: http://www.orafaq.com--
Author: Shevtsov, Eduard INET: EShevtsov_at_flagship.ruFat
City Network Services -- (858) 538-5051 FAX: (858)
538-5051San Diego, California --
Public Internet access / Mailing
Lists--------------------------------------------------------------------To
REMOVE yourself from this mailing list, send an E-Mail messageto:
ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and inthe message
BODY, include a line containing: UNSUB ORACLE-L(or the name of mailing list
you want to be removed from). You mayalso send the HELP command for
other information (like subscribing).
Received on Tue Sep 18 2001 - 18:04:29 CDT
