Re: Bug 3798351 Importing a pre-existing table may DROP the table on an error
From: Nilo Segura <nilosegura_at_gmail.com>
Date: Wed, 23 Jun 2010 07:43:05 +0200
Message-ID: <AANLkTild7IEeAdtrepRXg-mYKeKl1XB6jvhu8eAUdKUI_at_mail.gmail.com>
An "old" bug....
9.2.0.5
9.2.0.6
Platforms affected Generic (all / most platforms affected) Fixed:
Date: Wed, 23 Jun 2010 07:43:05 +0200
Message-ID: <AANLkTild7IEeAdtrepRXg-mYKeKl1XB6jvhu8eAUdKUI_at_mail.gmail.com>
An "old" bug....
Bug 3798351 Importing a pre-existing table may DROP the table on an error
This note gives a brief overview of bug 3798351. The content was last updated on: 09-MAR-2005 Click here for details of each of the sections below. Affects:
Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 10.1.0.2Versions confirmed as being affected
9.2.0.5
9.2.0.6
Platforms affected Generic (all / most platforms affected) Fixed:
This issue is fixed in
9.2.0.7 (Server Patch Set)
Symptoms:
Related To:
Corruption (Logical)
Export/Import
Description
If a table is created with the MONITORING clause and exported and upon import (with ignore=y) an error occurs (egL: buffer too small) then the pre-existing table may actually get DROPPED by import.
Workaround:
Always use large buffer size for imports.
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jun 23 2010 - 00:43:05 CDT