----- Original Message ----- From: "Schildberg, Steffen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 01, 2004 11:21 AM Subject: RE: Backup question
> Hi Matteo, > > Matteo Gattoni [mailto:[EMAIL PROTECTED] wrote: > > > > Using loader 7.5.00.18 to extract data from db istance > > version 7.5.1.0, I > > receive the error > > Segmentation Fault(coredump) > > both with > > DBEXTRACT CATALOG OUTSTREAM FILE '/tmp/sdb/PsfCata' DATA > > OUTSTREAM FILE > > '/tmp/sdb/PsfData' PACKAGE OUTSTREAM FILE '/tmp/sdb/PsfPack' > > and > > TABLEEXTRACT USER DATA OUTSTREAM FILE '/tmp/sdb/PsfData1'. > > > > The system create the CATALOG file properly but only one DATA > > file... It > > seems that it can't create or manage more then one data file. > > > Nope, thats not the case. As the log file states the DB has quit > working while extracting the data including index. > A look into knldiag would reveal the reason. > > > In the file loader.prt I have: > > > [snipped some log entries] > > // * > > // E -25009: Failure in db communication (receive): 4 = connection > > aborted. > > // E -25333: Error getting index definitions for table > > PRODUCT_DIMENSION > > (-25009 > > Failure in db communication (receive): 4 = connection aborted.). > > // E -25009: Failure in db communication (request): 1 = > > wrong connection state:requested. > > > At this point the DB is crashed. The next entry shows that the Loader tries > to update a Loader table which fails as there is no DB up and running. > > > UPDATE SYSDBA.TRANSFORMATIONMODEL SET STARTTIME = > > TIMESTAMP WHERE > > PACKAGEGUID = x'00000001415C0650000012D500000FFB0000000080CD904C' AND > > owner = 'TEST' AND tablename = 'PROVA' > > // * > > // E -25392: '' > > // E -25801: Internal error [vls26_TETable.cpp, 536, > > -25392]; contact > > technical support > > > > Have I missed something? > > > No. I would suggest you use a different format to get the data out of your DB. > Modify the TABLEEXTRACT command you used to > > TABLEEXTRACT USER DATA OUTSTREAM FILE '/tmp/sdb/PsfData1' RECORDS > > Doing so the Loader will use simple selects to get the data and save them in > a SAPDB proprietary format into the data file. With the command you used the > Loader saves the data as db pages and there might have been some problems with > 7.5.01 kernels. > I did it but it doesn't work with any istance. With one, I receive the error message -25010 SQL error -2003 = Output columns too long (error position: 48) Maybe a table is too huge, because when I use this file to populate an istance I have an error on the biggest table in my db. > > However, using the CATALOG file extracted (CATALOGLOAD USER > > INSTREAM FILE > > '/tmp/sdb/PsfCata1'), I receive the error > > -25392 > > '[MySQL MaxDB][LIBSQLOD SO][MaxDB] Syntax error or access > > violation;-2000 > > POS(575) Row too long' > > > This is a normal SQL error as your table definition defines a table of a width > that exceeds a db page size. I guess you created the table (all your tables?) > in sqlmode ORACLE. Unfortunately does the Loader not have this information upon > extracting the catalog. To work around the problem you can replace the first > line in your file PsfCata1: > SQLMODE INTERNAL > with: > SQLMODE ORACLE. > > Then running the CATALOGLOAD again the Loader should be able to create those > tables. > I used SQLMODE ORACLE. But the functions and procedures created in mode INTERNAL gave error so the loader stopped. Is there a way to switch automatically between the mode INTERNAL and ORACLE? > > 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] > > Thanks, Matteo -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
