Message-Id: <10708.124349@fatcity.com>
From: "Stephen Andert" <StephenAndert@firsthealth.com>
Date: Tue, 12 Dec 2000 11:00:47 -0700
Subject: Importing partitions without triggers

Hello:

Just discovered an interesting "feature".  Oracle 8.1.6 on Compaq Tru64 =
4.0f.  We did an export for one partition for some tables to move some =
data to an archive database.  Some of these tables have triggers that are =
not needed/wanted in the archive database so we included the parameter =
triggers=3Dn in the export command.  When we imported the dump file to the =
archive database, the tables that had triggers in the source failed.

We alternately disabled and dropped the triggers in the archive database =
and tried importing those tables again (tables=3DTABLE_NAME:PARTITION_NAME)=
 and it failed both times due to triggers.  We dropped the triggers and =
tried importing the tables again (tables=3DTABLE_NAME) and it worked, but =
still created the triggers.

My question is:  Since I used triggers=3Dn in the export, why does the =
import still create and enable the triggers when I import with the =
table:partition syntax but not with the table syntax?


Stephen Andert