SapDB crash with a SELECT statement

Hi,

I'm using SapDB version Kernel 7.3.0
Build 040-000-091-740, running on Linux.

Today I attempt to execute the follow SQL:

SELECT * FROM MoveType WHERE
id_sys LIKE 'VVP1%' AND
id_sys IN
('VVP1','VVP2','VPP1','VPP2','SC') AND
type = 'S' AND
subclass = 'FS'

this works fine, but if change the
value of LIKE clause to 'VVP2%' the
database crash with a Signal 11, and I
need to restart, the database error is:

2004-11-23 11:19:20 0 ERR 11330
COREHAND ABORTING due to signal 11

but this crash occurs only when the
row that have id_sys equals VVP2 and
only this row is returned and with
above WHERE clause, for example follow
SQL works fine:

SELECT * FROM MoveType WHERE
id_sys LIKE 'VV%' AND
id_sys IN
('VVP1','VVP2','VPP1','VPP2','SC')
type = 'S' AND
subclass = 'FS'

and this too:

SELECT * FROM MoveType WHERE
id_sys = 'VVP2'

to attempt discover the problem, I
create another table, with:

CREATE TABLE MoveType2 AS SELECT *
FROM MoveType

and then SELECT with problematic SQL,
works fine with this new table,
ok, creating new table solves the
problem, but create another, this
table as many foreign keys for her, then:

how I can recreate, restructure,
recover or whatever else, this table?
or
there is a way to check if this row on
database is corrupt? if Yes? There is
a way to recover?

Thanks for any help

Clovis
 
__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.br/



--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx