Hi Ralph, Hahn, Ralph [mailto:[EMAIL PROTECTED] wrote: > > The output script looks like: > TABLEEXTRACT USER DATA OUTSTREAM FILE 'FB24_KAT' > > The input script looks like: > TABLELOAD USER DATA INSTREAM FILE 'FB24_KAT' > [snipped console output] > > I have also find in the file loader.prt: > > // M START 20040727 00110927 > // * > TABLELOAD USER DATA INSTREAM FILE 'FB24_KAT' > // * > // E -25011: Error executing internal SQL statement 'CREATE TABLE > LOA_SWAP (COL1 INT)': 'SQL error -6000 = Duplicate table name:LOA_SWAP > (error position: 14)'. > // M LOAD TRANSFORMATIONPACKAGE > x'01000000C7AC16F7180400005D1F0000B16CE4663D8ADEA1' > // * > // M EXECUTE PACKAGE TO TRANSFORM DATA > // * > // M Number of tables to transform: 70 > // * > // E -25009: Failure in db communication (receive): 6 = connection > broken. > // E -25801: Internal error [vls28_TLTable.cpp, 3473, -25009]; contact > technical support > // E -25801: Internal error [vls28_TLTable.cpp, 2966, -25801]; contact > technical support > // E -25801: Internal error [vls28_TLoad.cpp, 1566, -25801]; contact > technical support > > Can you help me please? > I suppose you run a CATALOGLOAD before running the TABLELOAD? If not please check the catalog of the user to load for a table named LOA_SWAP: If this table exists drop it with DROP TABLE LOA_SWAP.
If you run a CATALOGLOAD check the catalog of the user you extracted the data from for a table named LOA_SWAP. Delete this table. Then you have to CATALOGEXTRACT and TABLEEXTRACT this user again :-(. Actually this table is a table internally created (and subsequently almost immediately dropped) by the Loader when processing TABLELOAD to define the swapping type of the kernel to load. It seems that the table has (by what error/accident ever) not been dropped. Regards, Steffen -- Steffen Schildberg SAP DB Team SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
