This is our problem with dbserver Version 4.27.0.5:
Following SQL Statement is executed in dbsys
select b.ID, b.BenName, b.KndNR, b.Datum,b.Betreff,b.text,k.katname,b.mailstat from vbericht b, "stamm/kategori" k where k.katid=b.katid
the result is ok.
But now, if we shut down dbsys immediately with the Windows task manager and we remove the disconnected session, the server log shows:
03.11.2009 12:38:11 [ERROR] Internal error removing session [DBISAM Engine Error # 10050 Invalid filter handle specified for the
table 'kategori'] [Client Version: 0,00 User Name: b Address: 127.0.0.1 Encrypted: No Thread: 0 Session: 29431312]
All tables which were opened in this session were locked for changes, the only solution is to restart the server.
Both tables can be found in the file tables.zip

Kindly regards
Bernd Kuhlmann
Rita Bosse Software Gmbh

Bernd,

<< This is our problem with dbserver Version 4.27.0.5:
Following SQL Statement is executed in dbsys
select b.ID, b.BenName, b.KndNR,
b.Datum,b.Betreff,b.text,k.katname,b.mailstat from vbericht b,
"stamm/kategori"  where k.katid=b.katid
the result is ok.
But now, if we shut down dbsys immediately with the Windows task manager
and we remove the disconnected session, the server log shows:
03.11.2009 12:38:11 [ERROR] Internal error removing session [DBISAM Engine
Error # 10050 Invalid filter handle specified for the
table 'kategori'] [Client Version: 0,00 User Name: b Address: 127.0.0.1
Encrypted: No Thread: 0 Session: 29431312]
All tables which were opened in this session were locked for changes, the
only solution is to restart the server.
Both tables can be found in the file tables.zip >>

I'm looking into this, and will let you know shortly what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

did you find something about our Problem?

Bernd Kuhlmann

"Tim Young [Elevate Software]" wrote:

Bernd,

<< This is our problem with dbserver Version 4.27.0.5:
Following SQL Statement is executed in dbsys
select b.ID, b.BenName, b.KndNR,
b.Datum,b.Betreff,b.text,k.katname,b.mailstat from vbericht b,
"stamm/kategori"  where k.katid=b.katid
the result is ok.
But now, if we shut down dbsys immediately with the Windows task manager
and we remove the disconnected session, the server log shows:
03.11.2009 12:38:11 [ERROR] Internal error removing session [DBISAM Engine
Error # 10050 Invalid filter handle specified for the
table 'kategori'] [Client Version: 0,00 User Name: b Address: 127.0.0.1
Encrypted: No Thread: 0 Session: 29431312]
All tables which were opened in this session were locked for changes, the
only solution is to restart the server.
Both tables can be found in the file tables.zip >>

I'm looking into this, and will let you know shortly what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Bernd,

<< did you find something about our Problem? >>

Sorry about the delay - a fix should be available in the next day or so.
I'm doing an ElevateDB build today, and then I'll be putting together a new
DBISAM build.

--
Tim Young
Elevate Software
www.elevatesoft.com

Bernd,

<< did you find something about our Problem? >>

Okay, I finally got a chance to investigate this, and it does not seem to be
an issue with the latest 4.29.  Can you try it with 4.29 and tell me what
you find out.  However, please try it on a copy of your database.  4.29 uses
a new BLOB block recycling design that is not compatible with 4.27 and
earlier, so you don't want to accidentally update your database using 4.29
until you actually want to move to 4.29.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

>Okay, I finally got a chance to investigate this, and it does not seem to be
>an issue with the latest 4.29.  Can you try it with 4.29 and tell me what
>you find out.  However, please try it on a copy of your database.  4.29 uses
>a new BLOB block recycling design that is not compatible with 4.27 and
>earlier, so you don't want to accidentally update your database using 4.29
>until you actually want to move to 4.29.

I could not reproduce the problem with 4.29. So it seems to be solved.

Bernd Kuhlmann

Bernd,

<< I could not reproduce the problem with 4.29. So it seems to be solved. >>

Good, I'm glad that the problem is resolved now.

--
Tim Young
Elevate Software
www.elevatesoft.com