 | | | AW: Integrity Violation during DBLOAD | AW: Integrity Violation during DBLOAD 2006-12-05 - By Schildberg, Steffen
Back
Hi Ralf,
Ralf Schneider [mailto:ml@(protected)] wrote:
> Betreff: Integrity Violation during DBLOAD
>
> I'm trying to migrate the data of one MAXDB instance
> (7.6.0.34 on Linux 64bit)
> to another (7.6.0.34 on Linux 32bit) using the loader. On the
> one side I used DBEXTRACT to extract the catalog and data:
>
> DBEXTRACT CATALOG OUTSTREAM FILE 'catalog' DATA OUTSTREAM FILE 'data'
>
> One the target machine I try to load the data with this command:
>
> DBLOAD CATALOG INSTREAM FILE 'catalog' DATA INSTREAM FILE 'data'
>
> During this command I get the following error:
>
> DBLOAD CATALOG INSTREAM FILE 'catalog' DATA INSTREAM FILE 'data'
> Error during execution
> -->-25451
> Integrity violation (SQL Error 350)
> ---
> Total number of tables (definition) imported: 17
> Total number of tables (data) imported: 1 (excluded: 0,
> failed: 2)
>
Well, yes. The table the Loader failed to export has a foreign key
either
self referential or not. This one causes problems when loading data in
format
PAGES (default format for DBEXTRACT/DBLOAD).
Please check the Loader system table TRANSFORMATIONMODEL with the GUID
found
for the DBLOAD command in the log file for the table with RESTART set to
true.
Remove temporarily the foreign key and restart the DBLOAD with the
following
command:
DBLOAD DATA INSTREAM FILE 'data' RESTART '<your guid>'
Or restart the whole process if possible and do separately load the
catalog and
data. After loading the catalog remove the foreign key and recreate it
after
successful load of data.
In newer versions the DB kernel is able to handle foreign keys while
loading PAGES.
Sorry for any inconveniences.
Regards,
Steffen
--
Steffen Schildberg
MaxDB Team
SAP Labs Berlin
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/maxdb?unsub=mysql@(protected)
|
|
|