From: Schildberg, Steffen (steffen.schildbergsap.com)
Date: Thu Jul 03 2003 - 08:53:55 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Joao [mailto:joaoinforap.pt] wrote:
>
>
> > Nope ;-) There is some more: what version of SAP DB Loader
> > do you use?
> > Are there any rows extracted at all? If so how many?
> >
> > To prevent the 'Integrity violation' error you could issue a
> > DELETE TRANSFORMATIONMODEL
> > as sysdba prior to running your command to extract.
> >
>
> OK,
> My DB LOADER Version is 7.4.3
>
Fine. But we need the so called build prefix, too ;-(
You can find it in loader.prt at the very beginning in the
following form
// M Loader 7.4.4 Build 002-000-000-000

> "Are there any rows extracted at all? If so how many?"
>
> Yes... Many rows have been extracted. I Cant Tell the exact
> number of rows but the file was about 300 Mb...
>
Well, I have right now no idea what happened. Has the ssc-file
been filled or is the generated command file empty?

Would you mind to run the extract again into a different
data file? How long did it take until it crashed?
To run the extract again I would suggest a slightly modified
command. Instead of running DATAEXTRACT FOR DATALOAD which
additionally generates CREATE TABLE/INDEX and DATALOAD commands
you should use the following command:

DATAEXTRACT * FROM ATG_MOVCOMPL
OUTFILE 'c:\Backup\ATG_MOVCOMPL_NEW.DAT'

This command gets all the data but does not generate any commands.

Thanks and sorry for any inconvenience.

Regards,
 Steffen
--
Steffen Schildberg
SAP DB Team
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
sapdb.generallistserv.sap.com
http://listserv.sap.com/mailman/listinfo/sapdb.general

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]