Hi Joao,
Joao [mailto:[EMAIL PROTECTED] wrote: > > COMMAND: > > DATAEXTRACT FOR DATALOAD TABLE ATG_MOVCOMPL > OUTFILE 'c:\Backup\restore.ssc' APPEND > OUTFILE 'c:\Backup\ATG_MOVCOMPL.DAT' > > LSERVER stops after a then folwing error : > > "The Instruction on "0x784a9789" references memory in > "0x4354453e". The > memory cannot be "read". > > Console Error Message : > "Replication server error (-4 : 'Connection broken')" > > Output of "loader.prt" : > > DATAEXTRACT FOR DATALOAD TABLE ATG_MOVCOMPL > OUTFILE 'c:\Backup\restore.ssc' APPEND > OUTFILE 'c:\Backup\ATG_MOVCOMPL.DAT' > > // * > // M LOAD TRANSFORMATIONPACKAGE x'' > // * > // M Number of tables to transform: 1 > // * > // M Number of views to transform: 0 > // * > // M Number of synonyms to transform: 0 > // * > INSERT INTO TRANSFORMATIONMODEL ( PACKAGEGUID, STEPID, CMD, > SEQ_NO, OWNER, > TABLENAME, TABLETYPE ) ( SELECT x'' , CMD_NO, CMD, SEQ_NO, OWNER, > TABLENAME, TABLETYPE FROM TEMP.LOA_SAVE_CATALOG_LS00 WHERE NOT > (TABLETYPE IN ('VIEW', 'SYNONYM') AND SEQ_NO > 0) ) > // * > // E -25392: '[SAP AG][SQLOD32 DLL][SAP DB]Integrity constraint > violation;200 POS(1) Duplicate key.' > // E -25392: '200' > > > I Think thats all Information I Can Give... > 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. Regards, Steffen -- Steffen Schildberg SAP DB Team SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
