Re: v$log_history and Y2K problem

Oracle probably saw this [potential] problem and has hence made it a DATE field in Oracle 8.0.3 as follows:

SQL> desc v$log_history

 Name                Null?            Type
 ------------------------------- -------- ----
 RECID                NUMBER
 STAMP                NUMBER
 THREAD#                NUMBER
 SEQUENCE#                NUMBER
 FIRST_CHANGE#                NUMBER
 FIRST_TIME                DATE
 NEXT_CHANGE#                NUMBER
--------------------------------------------------------

David A. Owens wrote in message <34FC1E5E.2393_at_criticaldata.com>...
>Here's one I have not heard talked about before.
>
>I'm looking at the v$log_history view in Ora 7.3.3 and notice that the
>TIME column is definitely not Y2K compliant. In fact this column is
>defined as (eek!) a varchar2 string. I would like to use this column
>to manage my archive log files (i.e. age them out from offline storage)
>but I will have problems when the year rolls to 00. Is there any way
>to reformat this column or are there other underlying tables which
>represent the log switch date/time in a proper date type?
>
>Thanks for your reply:
>
><CUT>
Received on Tue Mar 03 1998 - 00:00:00 CET