Re: SQL Loader Oracle 8 bug???

I never heard of this either...this is the only info I was able to get from Metalink, it only describes some ALTER commands in Oracle 8:

Alter table xxx LOGGING

Specifies that subsequent Sqlloader Direct Path Insert operations against a non-partitioned table, table partition, or all partitions of a partitioned partitioned table, will be logged in the redo log file. It is the default. This is useful during media recovery if ARCHIVELOG mode is turned on.

In article <tOqZ1.1257$jE5.191738_at_client.news.psi.net>,   "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.
>
>

Satar Naghshineh
Oracle DBA/UNIX System Admin
Advanced Enterprise Solutions
(949) 756-0588
Oracle Re-Seller

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Oct 29 1998 - 00:00:00 CST