| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Y2K problem of Oracle 7.1.6
On Tue, 22 Dec 1998 08:24:47 GMT, Karol Michaliak <delta_at_internet.sk>
wrote:
>What does it mean? Is the imp/exp useless when in the database are dates
>with year 2000 and more?
No, the *data* in your database has nothing to do with the possible wrong behaviour of the imp/exp utility at the begining of y2k. As Stephen has said, you can easily find what might happen by looking at catexp.sql yourself.
In short, if you are not performing incremental export (complete, cumulative, incremental) around the begining of the y2k, you'll never hit the bug. Also if you use this incremental export technique and you happen to run cumulative export before the incremental one in the year 2000 then you'll never know there was a bug hidden in the definition of some export supporting dictionary views.
Anyway, the easiest cure for this bug would be to open the catexp.sql with your editor and replace any occurance of the
TO_DATE('01-01-00','DD-MM-YY')
with
TO_DATE('01-01-1900','DD-MM-YYYY')
and rerun this script.
>Thanks,
>Karol
HTH,
Jurij Modic <jmodic_at_src.si>
Certified Oracle7 DBA (OCP)
 |
 |