Help! Oracle down after log seq# reached 65535... (urgent)

Question

I'm using Oracle 8.0.5 on Linux, I've got an error message saying the LGWR process not functioning, and the instance go down!
After checking v$log, I found that the log seq# reached 65535 in the online redo log and a meesage in the alert file saying 65535 is the max. value and can not be extended....
Is there anyway to reset the log seq#??
And any solution for this problem?
null

Answer 1

Here is the official solution:
Solution Description:
=====================
The problem has been fixed in Releases 8.0.6 and 8.1.3 and higher. The
workaround is to recreate the control file with a smaller maxloghistory value.
If "MAXLOGHISTORY" is 65535, then when the log sequence number reaches 65535,
LGWR dies.
Solution Explanation:
=====================
"MAXLOGHISTORY" is one of the database settings specified in CREATE DATABASE
statement. It is the number of redo log files about which the control file can
keep information. This value determines how much space in the control file to
allocate for the names of the archive redo logs files.
The default value is operating system dependent. However, we have seen it
default to 65535 on certain platforms. You need to set it to an appropriate
value which is sufficient for automatic media recovery of the database.
You must recreate the control file when you want to change "MAXLOGHISTORY"
value.