Hello Ralf,
 
Warm regards from Uwe. As your running database process is - due to a
bug - in an unfortunate state where any backups are prevented, you have
to restart your database before you are able to do any further backup.
To increase the chances of the restart, try to successfully forcing a
savepoint ("dbmcli -d ... -u ...,... sql_execute force savepoint", look
for error messages of this action in the file knldiag).
 
To avoid the backup problem in future please upgrade your MaxDB software
to build 7.5.00.24 or higher, as most probably your bug is fixed with
http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1133694 .
 
Please check also for hardware problems, as your real problem is the
"-9026 BD Bad datapage,write/check count".

Best regards,
Tilo Heinrich
SAP Labs Berlin
 
 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 12, 2006 4:25 PM
To: maxdb@lists.mysql.com
Cc: Heinrich, Tilo
Subject: AW RE: -104,DBM command impossible at this time - Lasts too
long...



First of all,  a big thanks for quick responsing to all Responsers! 

You are right, there was some unfortunate Backup-Action before... 

used Build: 014-121-073-298 

dbm.prt says: 

... some fine backup action before... 

2006-01-09 19:22:02 0x000013ef              0 DBM      command
medium_put completeF /var/opt/sdb/data/wrk/dbTest/SAV_dbTest_DATA34 FILE
DATA 64000 0 NO NO 
2006-01-09 19:22:02 0x000013ef              0 DBM      command
backup_replace completeF 
2006-01-09 19:24:19 0x000013ef              0 DBM      command
medium_put completeF /var/opt/sdb/data/wrk/dbTest/SAV_dbTest_DATA35 FILE
DATA 64000 0 NO NO 
2006-01-09 19:24:19 0x000013ef              0 DBM      command
backup_replace completeF 
2006-01-09 19:26:26 0x000013ef              0 DBM      command
medium_put completeF /var/opt/sdb/data/wrk/dbTest/SAV_dbTest_DATA36 FILE
DATA 64000 0 NO NO 
2006-01-09 19:26:26 0x000013ef              0 DBM      command
backup_replace completeF 
2006-01-09 19:28:38 0x000013ef              0 DBM      command
medium_put completeF /var/opt/sdb/data/wrk/dbTest/SAV_dbTest_DATA37 FILE
DATA 64000 0 NO NO 
2006-01-09 19:28:38 0x000013ef              0 DBM      command
backup_replace completeF 

2006-01-09 19:28:38 0x000013ef ERR     -24988 DBM      ERR_SQL: sql
error 
                    0x000013ef ERR     -24988 DBM      -9026,System
error: BD Bad datapage,write/check count mismatch 
2006-01-09 19:28:39 0x000013ef              0 DBM      command
medium_put completeF /var/opt/sdb/data/wrk/dbTest/SAV_dbTest_DATA38 FILE
DATA 64000 0 NO NO 
2006-01-09 19:28:40 0x000013ef              0 DBM      command
backup_replace completeF 
2006-01-09 19:28:40 0x000013ef ERR     -24988 DBM      ERR_SQL: sql
error 
                    0x000013ef ERR     -24988 DBM      -7078,No backup
is running 


After reading this, I started an structure-analysis, that ended in an
error. 

 studying the knldiag.err brings out the dirty places: 

2006-01-09 19:28:38  1819 ERR     4 Data     Checksum mismatch;
calculated: 131051870 found: 127889862 
2006-01-09 19:28:38  1819 ERR 52015 SAVE     write/check count mismatch
912005 
2006-01-09 19:28:38  1818 ERR 52012 SAVE     error occured, basis_err
300 
2006-01-09 19:28:38  1818 ERR 51080 SYSERROR -9026 BD Bad
datapage,write/check count 
2006-01-10 08:28:00  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:28:00  1822 ERR 53019 CHECK    Root pageNo: 1360207 
2006-01-10 08:32:15  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:32:15  1822 ERR 53019 CHECK    Root pageNo: 345952 
2006-01-10 08:32:15  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:32:15  1822 ERR 53019 CHECK    Root pageNo: 259927 
2006-01-10 08:32:30  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:32:30  1822 ERR 53019 CHECK    Root pageNo: 259965 
2006-01-10 08:41:52  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:41:52  1822 ERR 53019 CHECK    Root pageNo: 2958671 
2006-01-10 08:42:01  1819 ERR 53370 B*TREE   Illegal record length: 917 
2006-01-10 08:42:01  1819 ERR 53370 B*TREE   Corrupted data page:
1201297 
2006-01-10 08:42:01  1819 ERR 53000 B*TREE
0701000000000017F567000000000000 
2006-01-10 08:42:01  1819 ERR 53000 B*TREE   INDEX ROOT  106644 
2006-01-10 08:42:01  1819 ERR 53250 B*TREE   BAD INDEX 106644 (ROOT) 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Root pageNo: 106644 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Root pageNo: 500090 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Base error:
file_not_accessibl 
2006-01-10 08:42:01  1822 ERR 53019 CHECK    Root pageNo: 107843 
2006-01-10 11:23:27  1819 ERR 53000 B*TREE
0200000024AA07630100000007000000 
2006-01-10 11:23:27  1819 ERR 53000 B*TREE   ROOT  345952 
2006-01-10 11:23:27  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees: 74125

2006-01-10 11:23:38  1819 ERR     4 Data     Checksum mismatch;
calculated: 139872711 found: 127889862 
2006-01-10 11:23:38  1819 ERR    13 IOMan    Bad page on Data volume 1
blockno 2989782 
2006-01-10 11:23:40  1819 ERR     4 Data     Checksum mismatch;
calculated: 139872711 found: 127889862 
2006-01-10 11:23:40  1819 ERR    13 IOMan    Bad page on Data volume 1
blockno 2989782 
2006-01-10 11:23:42  1819 ERR     4 Data     Checksum mismatch;
calculated: 139872711 found: 127889862 
2006-01-10 11:23:42  1819 ERR    13 IOMan    Bad page on Data volume 1
blockno 2989782 
2006-01-10 11:23:44  1819 ERR    24 IOMan    Bad data page 912005 
2006-01-10 11:23:44  1819 ERR    18 Data     Bad data page 912005 of
filetype 'tfnAux' identified by root 259927 
2006-01-10 11:23:51  1819 ERR 53000 B*TREE
0200000024AA07650100000007000000 
2006-01-10 11:23:51  1819 ERR 53000 B*TREE   ROOT  259965 
2006-01-10 11:23:51  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees:
727843 
2006-01-10 11:24:26  1819 ERR 53000 B*TREE
0200000024AA07660100000007000000 
2006-01-10 11:24:26  1819 ERR 53000 B*TREE   ROOT  106644 
2006-01-10 11:24:26  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees:
1201297 
2006-01-10 11:24:36  1819 ERR 53000 B*TREE
0200000024AA07670100000007000000 
2006-01-10 11:24:36  1819 ERR 53000 B*TREE   ROOT  2958671 
2006-01-10 11:24:36  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees:
1065454 
2006-01-10 11:25:10  1819 ERR 53000 B*TREE
0200000024AA07680100000007000000 
2006-01-10 11:25:10  1819 ERR 53000 B*TREE   ROOT  107843 
2006-01-10 11:25:10  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees:
457498 
2006-01-10 11:26:01  1819 ERR 53000 B*TREE
0200000024AA07690100000007000000 
2006-01-10 11:26:01  1819 ERR 53000 B*TREE   ROOT  1360207 
2006-01-10 11:26:01  1819 ERR 53367 B*TREE   bd400_DeleteSubTrees:
242390 
2006-01-10 13:08:21  1822 ERR 53000 CHECK    Check data finished
unsuccessfully 


Then I detected the objects (SELECT * FROM roots WHERE...) belonging to
the bad pages: Only Indizes 

After dropping the Indizes the structure-analysis went through
successfully: 

2006-01-10 17:22:44 0x00003ccf              0 DBM      command
db_execute VERIFY 

glad - - so far! 

Then the next attempt to backup_start completeF 
ended as mentioned in the Topic 

Error -104. 

Considering the bad pages: Restarting the Database to me should be the
very last option. (Will she come back...?) 
At first the backup must be successfully executed.. 


Best Regards+Besides that: MaxDB is a very fine Product and your List is
First Class. 

Ralf 

---------------------------------------------------- 
Heinrich, Tilo wrote: 

Hello Ralf, 

What build are you using? Does restarting the database help? Have you 
cancelled any backups recently? 

Best regards, 
Tilo Heinrich 
SAP Labs Berlin 

-----Original Message----- 
From: [EMAIL PROTECTED] 
Sent: Thursday, January 12, 2006 12:12 PM 
To: maxdb@lists.mysql.com 
Subject: -104,DBM command impossible at this time - Lasts too long... 

Hi, List! 

This happens: 

system: MaxDB 7.5.0 
dbmcli on dbtest>backup_start completeF 

ERR 
-24988,ERR_SQL: sql error 
-104,DBM command impossible at this time 


The documentation says "execute statement later", 

but the mysterious infinite-running-dbm-command seems to stick somehow 
(so 
far for 2 days) and does not disappear. 

Is there any way to determine the process or to reset the dbmcli-message


background? 

Sessions or tasks don't show anything strange. 

Execution of db_clear did not remove the information. 

Analyzing the Structure was successful without errors. 

Any Ideas? 

Best regards+thanks for spending some resources on this problem... ;-), 

Ralf Bolduan 

mailto: [EMAIL PROTECTED] 

-- 
MaxDB Discussion Mailing List 
For list archives: http://lists.mysql.com/maxdb 
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED] 



Reply via email to