You seen SRDB 23550 on Sunsolve?
Customer production system running Oracle version of 8.1.6 or less will have
the database control file corrupted if the the machine has been running 248
days without a reboot. This will require a rebuild and recovery of the
The issue is how Oracle interprets the number of "clock ticks" that the
kernel uses to keep track of time since the machine was booted. When the
number of clock ticks reaches (2 ^ 32) + 1, Oracle reads it as a negative
number and the corruption occurs.
The permanent solution is to install Oracle 8.1.7 when it releases.
The temporary workaround is to REBOOT THE SERVER BEFORE IT REACHES 248 DAYS
It's 3 days away from 248 days since y2k - A lot of systems were rebooted
around that time.
Columnated ruins domino,
Canvas the town and brush the backdrop.
Are you sleeping?