v$log_history and Y2K problem

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:

David A. Owens DBA --> www.criticaldata.com <daveo_at_criticaldata.com>

SQL> desc v$log_history;

 Name                            Null?    Type
 ------------------------------- -------- ----
 THREAD#                                  NUMBER
 SEQUENCE#                                NUMBER
 TIME                                     VARCHAR2(20)
 LOW_CHANGE#                              NUMBER
 HIGH_CHANGE#                             NUMBER
 ARCHIVE_NAME                             VARCHAR2(257)

SQL> select * from v$log_history;

  THREAD# SEQUENCE# TIME                 LOW_CHANGE# HIGH_CHANGE#
--------- --------- -------------------- ----------- ------------

        1 6 02/28/98 13:06:24 5633 5763 F:\ORANT\RDBMS73\%ORACLE_SID%00006.001         1 5 02/28/98 13:05:57 5517 5632 F:\ORANT\RDBMS73\%ORACLE_SID%00005.001         1 4 02/28/98 13:05:27 5368 5516 F:\ORANT\RDBMS73\%ORACLE_SID%00004.001 Received on Tue Mar 03 1998 - 00:00:00 CST