From: "David A. Owens" Subject: v$log_history and Y2K problem Date: 1998/03/03 Message-ID: <34FC1E5E.2393@criticaldata.com>#1/1 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Organization: http://www.criticaldata.com Mime-Version: 1.0 Reply-To: daveo@criticaldata.com Newsgroups: comp.databases.oracle.server,comp.databases.oracle,comp.databases.misc 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 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# --------- --------- -------------------- ----------- ------------ ARCHIVE_NAME -------------------------------------------------------------------- 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