I keep getting error -25329 ... not generated using TABLEEXTRACT (wrong
identifier) while using dbLoader to try and load data from a linux box to an
Win XP2000 PC.
The scripts used, and the error msg is listed below. The script works fine
when run from the Win2000 PC (using 7.4.3.17) against an older NT system
(7.4.3.10) with the appropriate name changes. But when I run it from
Win2000 box against the linux system (7.4.3.10), the catalog loads, but
tableloading bombs out.
Can anyone help - and what does the error msg actually mean?
Of secondary interest is the fact that we had to remove some (but not all)
of the referential constraints before unloading and add them back after the
load. I would have thought that the loading process was smart enough to
handle this without manual intervention - am I missing something?
/alix
Scripts used ....
loadercli -u demodba, demodbapass -d demouser -E 999 -b
c:\sapdb\loader\demo_load.script
c:\sapdb\loader\demo_load.script
--------------------------------
SET MAXERRORCOUNT 999
//
USE USER demodba demodbapass SERVERDB demodb ON localhost
//
CREATE user demouser password demopass DBA NOT EXCLUSIVE
//
USE USER demouser demopass SERVERDB demodb ON localhost
//
// loading the tables before the catalog (and running this script twice) can
fix a bug in the catalog loading that occurs when the catalog
// differs from the table load schema. Seems to work fine so far when the
db to be loaded is brand new, with no existing tables with
// possible conflicts. Reverse order ONLY if you have problems
// TABLELOAD USER data instream file 'c:\sapdb\loader\demo.data0001'
//
// this is the natural order to load the data, only needs to be run once.
//
CATALOGLOAD USER instream file 'c:\sapdb\loader\demo.catalog'
//
TABLELOAD USER data instream file 'c:\sapdb\loader\demo.data0001'
//
// add back the foreign keys that reference unique, non primary keys in
parent tables which were dropped before the data was loaded
// to prevent referential constraint errors.
//
Alter table "JET"."RULE_GROUP" FOREIGN KEY "RuleGroup_RuleGroup_FK"
("RuleGroupId") REFERENCES "JET"."RULE_SET" ("RuleGroupId") ON DELETE
CASCADE
//
Alter table "JET"."RULE_SEASONGROUP" FOREIGN KEY "Rule_SeasonGroup_Group_FK"
("SeasonGroupId") REFERENCES "JET"."RULE_SEASON" ("SeasonGroupId") ON
DELETE CASCADE
//
Alter table "JET"."RULE_ILGROUP" FOREIGN KEY "Rule_ILGroup_Group_FK"
("ILGroupId") REFERENCES "JET"."RULE_INTERLINING" ("ILGroupId") ON DELETE
CASCADE
//
Alter table "JET"."RULE_ROUTINGGROUP" FOREIGN KEY
"Rule_RoutingGroup_Group_FK" ("RoutingGroupId") REFERENCES
"JET"."RULE_ROUTING" ("RoutingGroupId") ON DELETE CASCADE
//
// Remember to backup up database immediately afterwards. The table loading
process puts the db into read only mode (as the process bypasses
// the normal logging process), so a complete backup is needed for the log
to take its reference from.
------------------------------------------------------------- error message
after running
TABLELOAD USER data instream file 'c:\sapdb\loader\demo.data0001'
-25329
The given data file 'c:\sapdb\loader\demo.data0001' was not generated using
TABLEEXTRACT (wrong identifier).
Successfully executed
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
