Hello Jared, Please have a look into one of the files dbm.ebp and dbm.ebl. Most probably you will find, that your Backint got killed by the DBM Server after a certain timeout elapsed. If so, change the timeout with the help of parameter "TIMEOUT_SUCCESS" in the configuration file for Backint for MaxDB (see also http://dev.mysql.com/doc/maxdb/en/55/a81d36451f11d5992400508b6b8b11/fram eset.htm).
Best regards, Tilo Heinrich SAP Lab Berlin -----Original Message----- From: Jared Still [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 20, 2005 12:38 AM To: [email protected] Subject: MaxDB backups Hi All, I'm currently seeing an issue with backing up a MaxDB database. This is on Windows Server 2003, MaxDB 7.5, and Veritas NetBackup. While I had this setup on a test server, all worked fine. Moved the backups to the production NBU server, and now I am seeing the following errors in the dbm.prt file 2005-12-19 13:06:31 0x00000ec8 0 DBM command param_startsession 2005-12-19 13:06:32 0x00000ec8 0 DBM command param_abortsession 2005-12-19 13:06:33 0x00000ec8 0 DBM command param_startsession 2005-12-19 13:06:33 0x00000ec8 0 DBM command param_abortsession 2005-12-19 13:06:36 0x00000ec8 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE 2005-12-19 13:06:36 0x00000ec8 ERR -24988 DBM ERR_SQL: sql error 0x00000ec8 ERR -24988 DBM 100,Row not found 2005-12-19 15:04:42 0x00000de0 0 DBM command backup_start BACKBOOFULL DATA 2005-12-19 15:05:58 0x00000de0 ERR -24919 DBM ERR_BACKUPOP: backup operation was unsuccessful 0x00000de0 ERR -24919 DBM The backup tool was killed with 0 as sum of exit codes. The database request ended with code 0. I've googled for this with a number of different keywords: no help found. Any ideas on what the basic problem is here? Thanks, -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
