Hi Thorn, Thorn Roby [mailto:[EMAIL PROTECTED] wrote: > > I'm trying to replicate a 500MB 7.4.03.17 Solaris 9 database to Maxdb > 7.5.00.08 on Redhat 9.0 Linux. I believe that I can't use > backup/restore > because of the byte order issue. I am running loadercli on the Maxdb > machine, using the following script: > // > USE USER dba dbapass SERVERDB mydb ON myhost.mydomain.com > // > SET MAXERRORCOUNT 50 > // > EXTRACT DB > CONFIGURATION INSTREAM FILE '/sap/b3config.dat' COMPRESSED ASCII > CATALOG OUTSTREAM FILE '/sap/b3catalog.dat' DDL > DATA OUTSTREAM FILE '/sap/b3tables.dat' PAGES > PACKAGE OUTSTREAM FILE '/sap/b3packagesource.dat' COMPRESSED > // > > The connection is established and shortly fails with the > following error: > > Error during execution > -->-25801 > Internal error [vls26_TETable.cpp, 536, -25392]; contact > technical support > > Defined maximum number of errors (1) reached > > The loader.prt contains this: > > // * > // M LOAD TRANSFORMATIONPACKAGE > x'01000000584F5F402E30010064ED887D237C3FD6FFFFFFFF' > // *
[snipped TRANSFORM CATALOG message] > // * > // M CONFIGURE TRANSFORMATIONPACKAGE > // * > // M EXECUTE PACKAGE TO TRANSFORM DATA > // * > // M Number of tables to transform: 24 > // * > // E -25009: Failure in db communication (receive): 4 = connection > aborted. > // E -25011: Error executing internal SQL statement 'BEGIN > SAVE TABLE > "AUDIT_LOG"': '-25009 > Failure in db communication (receive): 4 = connection aborted.'. > // E -25349: Error extracting PRIMARY data of table AUDIT_LOG. See > server logfile for more information. > // E -25009: Failure in db communication (request): 1 = wrong > connection state:requested. > UPDATE TRANSFORMATIONMODEL SET STARTTIME = TIMESTAMP WHERE > PACKAGEGUID = > x'01000000584F5F402E30010064ED887D237C3FD6FFFFFFFF' AND > owner = 'MATLDBA' AND tablename = 'CONSUMER' > // * > // E -25392: '' > // E -25801: Internal error [vls26_TETable.cpp, 536, > -25392]; contact > technical support > [snipped database errors] > > The remote database can be restarted and shows no errors on > Check Database. > Yes. The db goes off when extracting data. This actually does not change data at all. There is very likely a problem in adapting the data on the data pages (that will be delivered to the Loader) to the table structure which might have changed. > Am I supposed to put something in the "CONFIGURATION INSTREAM > FILE" or does it get created by loadercli? If it's supposed to have > content, is it documented anywhere? > You don't have to put anything into the configuration file. You can run your command without the configuration specification. But that's not the problem. The problem arises when the Loader tries to get information on table AUDIT_LOG. All other errors listed in loader.prt are subsequent errors because the Loader seems not to recognize that the db went off. Could you send me the definition of table AUDIT_LOG? Does the table have more than one key column and long columns? To get the data you could try another format for the data upon extracting/ loading. Your command should look like this: EXTRACT DB CATALOG OUTSTREAM FILE '/sap/b3catalog.dat' DATA OUTSTREAM FILE '/sap/b3tables.dat' RECORDS PACKAGE OUTSTREAM FILE '/sap/b3packagesource.dat' COMPRESSED RECORDS is a proprietary Loader data file format. But it does simple mass selects whereas in case of PAGES a special protocol between Loader and Kernel is used. Prior to doing the extract again you should delete all entries from system table TRANSFORMATIONMODEL. This is a special Loader system table where it logs the tables processed and some related parameters. In the release you use the Loader does not delete the entries after successfully processing a command. 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]
