Allbase error -4008

[Ray Kuehnle]

Trying to update a few records (6) from many (23,000) that could apply based on index. Transaction fails with -4008 and appearantly leaves the majority of Runtime Control Blocks utilized throughout the session. Have tried starting transaction as "Read Uncommited" but seems to have no effect. How do I perform the update without exhausting RCB, getting error -4008, and leaving session with majority of the RCBs tied up? Thanks, Ray

[Ray Kuehnle]

This is an HP forum, right? Allbase is/was an HP product...

[Jean-Luc Oudart]

Hi,

I'm not an Allbase user,
But found the error doc. Hope this help :

4008 MESSAGE ALLBASE/SQL shared memory lock allocation failed
in DBCore. (DBERR 4008)

CAUSE ALLBASE/SQL ran out of run-time control block
space. Your transaction was rolled back.

ACTION In multi-user mode, try your query again later
or
issue the ALTDBE command in SQLUtil to increase the
number of control block pages
or
use LOCK TABLE so that individual pages are not
locked
or
you may be able to use BEGIN WORK CS or BEGIN WORK
RU to prevent this error.

Regards,
Jean-Luc

[Jean-Luc Oudart]

Hi,

was Allbase a product on MPE ?

Therefore you may be wise posting on the MPE forum too !

Regards,
Jean-Luc

[Ray Kuehnle]

Hi Jean-Luc,
I guess we are the only ones following this thread. Thanks for getting back with me.
Actually, the Allbase product was available on both plateforms. I checked the MPE forum but nothing there either.
I fixed the problem by adding an compound index on both columns so that the update would not have to lock so many rows (it can go straight to those records that apply).
Apparently, there is a bug in Allbase that occurs when RCBs are exhausted (-4008) and the ones utilized so far are not released. Just have to make sure they do not get exhausted during a session...
Thanks Again,
Ray