Ed,
Get your SAs to take a look at NTP (Network Time Protocol). You can setup an
NTP server and use NTP clients to sync up to it easily. In the case when an
NTP client catches up with the server, it just reduces or increases the
1/100 sec time clicks so that the time is caught up over a period of time
and even seconds are not missed.
John - you may also be missing cron jobs (and Oracle Apps scheduled
concurrent manager jobs in case you are using Apps) in case you take an
abrupt jump.
John Kanagaraj
Oracle Applications DBA
DB Soft Inc
Work : (408) 970 7002
Listen to great, commercial-free christian music 24x7x365 at
http://www.klove.com
** The opinions and facts contained in this message are entirely mine
and do not reflect those of my employer or customers **
-----Original Message-----
Sent: Tuesday, September 18, 2001 4:45 PM
To: Multiple recipients of list ORACLE-L
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
>>> [EMAIL PROTECTED] 09/18/01 08:46AM >>>
Hi List,
we have about 2 min difference between the time on our db server and the
rest boxes in our network.
Actually, the time on DB server is 2min slow than the network time.It causes
real pain to us.
I think about the following order of time synchronization:
1. Normal shutdown the DB and listener
2. immediate cold backup
2. setup time synchronization on the unix level
3. startup the DB and listener
4. Normal shutdown DB and listener
5. immediate cold backup
6. startup DB and listener
Is 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: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: John Kanagaraj
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
