Hello Christian, the messages mean that not all allocated temporary pages are released. This is used by a key merge in a join statement or a create index statement. The situation can occur if a statement is cancelled. It will be fixed.
Kind regards Uwe -----Original Message----- From: JUNG, Christian [mailto:[EMAIL PROTECTED] Sent: Dienstag, 3. Januar 2006 11:22 To: MaxDB Mailinglist (E-Mail) Subject: knldiag.err: BD550FieldQueue:PageLeak Hello, we had some problems in a SAP R/3-System running with a MaxDB 7.5.0.30 on Linux. First I thought about some problems with the database and therefore took a look in the log-files. I've found these messages which don't make much sense to me in 'knldiag': ---%<--- 2006-01-02 11:04:36 6025 11577 COMMUNIC Cancel request for T91 2006-01-02 11:04:36 6036 53000 B*TREE BD500: Next cancelled: 91 2006-01-02 11:04:36 6036 ERR 53000 OBJECT BD550FieldQueue:PageLeak: 113 2006-01-02 11:04:36 6036 ERR 53000 OBJECT BD550FieldQueue:PageLeak: 19 2006-01-02 11:04:36 6036 ERR 53000 OBJECT BD550FieldQueue:PageLeak: 54 ---%<--- I don't think that's the cause of the R/3-problem but I'm curious to get an explanation of what happened there. The database runs fine, there a no problems and a quick search via google didn't reveal anything. Do I have to worry about these messages? The exactly build is 'X32/LINUX 7.5.0 Build 030-121-100-791' running on SuSE SLES 9 with Linux SMP-kernel 2.6.5-7 build 191. Greets & a happy new year Chris phone: +49 6898/10-4987 fax: +49 6898/10-54987 http://www.saarstahl.de -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
