My experience in Y2K testing my application may tell you something.
This only relates to Oracle's real-time I/O functions. I've been
changing CPU_DTs on RS6000s to post-2000 dates. I've changed the date
many times in a day back and forth in the 2 centuries. I do not restart
the databases when I do this and have not encountered any problems.
Dates are passed correctly and when written to the database using
triggers are the correct date. We have transactions that send both 1999
& 2000 dates in one transaction and Oracle gets both correct. Oracle
7.3.4 seems to pick up the CPU_DT without intervention. I have not
however, run any extracts or Oracle administration functions
(exporting, archiving, etc) on Y2K.
- Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Received on Tue Oct 12 1999 - 15:07:05 CDT
