Re: Bug 3798351 Importing a pre-existing table may DROP the table on an error
- From: Robert Freeman <robertgfreeman@xxxxxxxxx>
- To: robertgfreeman@xxxxxxxxx, exriscer@xxxxxxxxx, Oracle Mailinglist <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 22 Jun 2010 21:17:22 -0700 (PDT)
Sorry.... bug number is on the subject line.... long day, tired eyes!! :)
RF
Robert G. Freeman
Master Principal Consultant, Oracle Corporation, Oracle ACE
Author of various books on RMAN, New Features and this shorter signature line.
Blog: http://robertgfreeman.blogspot.com
________________________________
From: Robert Freeman <robertgfreeman@xxxxxxxxx>
To: exriscer@xxxxxxxxx; Oracle Mailinglist <oracle-l@xxxxxxxxxxxxx>
Sent: Tue, June 22, 2010 9:10:11 PM
Subject: Re: Bug 3798351 Importing a pre-existing table may DROP the table on
an error
Am I getting this right... an import failed, raised an error, and then as a
result of the error the import program dropped a table? Do you have a bug
number for this?
RF
Robert G. Freeman
Master Principal Consultant, Oracle Corporation, Oracle ACE
Author of various books on RMAN, New Features and this shorter signature line.
Blog: http://robertgfreeman.blogspot.com
________________________________
From: LS Cheng <exriscer@xxxxxxxxx>
To: Oracle Mailinglist <oracle-l@xxxxxxxxxxxxx>
Sent: Tue, June 22, 2010 3:17:04 PM
Subject: Bug 3798351 Importing a pre-existing table may DROP the table on an
error
Hi
I have a customer hit this nasty bug this morning.
Really really nasty which affects 9.2.0.5 and 9.2.0.6. It turns out customer
was trying to import a few thousands rows to the applicacion main table
(partitioned), composed by 800 million rows, the first import gave an error
complaining buffer size too small and that triggered a DROP TABLE which was
lighting fast by the way, dropping the table and all partitions took around 15
seconds, we suspect that it didnt even try to drop the table physically, just
updated data dictionary.
So what a disgrace my customer said, Oracle Software actually deleted his most
important database table and the doubt is what is Oracle responsability in this
situation? The system has been stopped 10 hours already due to this bug
(database is around 2TB and requires complete restore).
TIA
--
LSC
Other related posts:
