loadercli catalogextract - creates unparseable file...

In my ongoing efforts with moving data from one server to another...

Using 7.5.00.18 of loadercli, I did the following:

loadercli>catalogextract user outstream file 'catalogv30'

Checking the file created showed that it mostly looked great - all 30+ 
tables had the right definitions.  Using this extract to set up a new 
clean database gave this error:

loadercli>catalogload user instream 'catalogv30'
// *
// M    EXECUTE PACKAGE TO TRANSFORM CATALOG
// *
)   ID = :NEW.ID;(SELECT ID FROM GLOBAL.CHANNEL WHERE CHANNEL.NAME = 
:NEW.CHANNEL_NAME),
// *
// E -25392:    '[SAP AG][LIBSQLOD SO][SAP DB] Base table not 
found;-4004 POS(73) Unknown table name:TTSKU'
// M    Number of tables   transformed : 0
// *
// M    Number of views    transformed : 0
// *
// M    Number of synonyms transformed : 0
// *
// M    UNLOAD TRANSFORMATIONPACKAGE 
x'0100000017C44442011600004124ED5500F8C0A8FFFFFFFF'
/

A closer look at the end of the catalogv30 file has:

<snip>
CREATE  INDEX "TTSKU_TITLE_ID" ON "TTSKU" ("TITLE_ID"  ASC )
//
)   ID = :NEW.ID;(SELECT ID FROM GLOBAL.CHANNEL WHERE CHANNEL.NAME = 
:NEW.CHANNEL_NAME),
//
CREATE TABLE "SKU"
(
       "ID"               Fixed (10,0)    NOT NULL    DEFAULT SERIAL (1),
<snip>

Took awhile to figure out what this was... turns out this is a line from 
a trigger I created.  The rest of the trigger doesn't appear when I dump 
the file to the console.  However, if I open up the file in an editor I 
can see the correct trigger definition - I'm guessing the editor is 
filtering out some otherwise bad characters found in the extract.

Any ideas here?

Cheers,
David


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx