Re: SQL Loader Oracle 8 bug???

Hi Gary

Yes, I am sad to say that this alert is most definitely true. I have experienced the problem and it caused me to need to re-build my 8.0.4 database from scratch!!

I have the necessary code to upgrade to 8.0.5 but due to other pressures, I have not yet been able to try out the fixes!!

I'd advise getting the upgrade to 8.0.5 and trying it out on a test machine, first with 8.0.4, then with the upgrade. The problem definitely exists; I just worry what new bugs have been introduced in 8.0.5!

Good luck

Mark.

On Tue, 27 Oct 1998 21:20:25 GMT, "Gary Eckhardt" <Gary_Newsmail_at_dci-ltd.com> wrote:

>Hi All,
>
>I received this mail message from a business associate,
>and I've never heard anything about it. Has anyone else?
>This is a great impact because we're currently migrating
>our DB to 8.0.4.1 and perform direct loads exclusively.
>
>Thanks for any information.
>
>----- cut here ----- cut here ----- cut here ----- cut here -----
>
>Please be aware, and make other interested parties aware (developers)
>that a high impact alert has been issued for Oracle8.
>
>The bug is generic across all platforms and results is data dictionary
>corruption. It is fixed in 8.0.5.
>
>The nature of the bug is that when a SQLLoader direct load is interrupted
>the data dictionary is corrupted with incorrect segment header information.
>Corruption of this sort would require a point in time recovery or a
>complete rebuild of the database.
>
>The workaround is to always use conventional loads or ensure that
>direct loads are not interrupted or killed.
>
>
>
Received on Wed Oct 28 1998 - 00:00:00 CST