Adabas nucleus response code = (255)

, , , ,
1

Hello Everyone,

We are constantly getting the following error when trying to access data from CONNX or SQL Server through a CONNX OLEDB linked server.

“Error Executing Query: Adabas nucleus response code = (255); ADD2 = (00000100) SubCode = (00) SubField = (10)”

We also randomly get 255 - insufficient resources on attached buffer pool error when trying to display FDT on some tables on DBA Work bench.

Here is our configuration:

ADABAS Version 6.2.1.01
Windows Server 2008 32 bits

results of displaying high waters:

                   ADANUC Version 6.2.1.01
    Database 111      High Water Marks      on 23-FEB-2012 11:12:59

Area/Entry Size In Use High Water %

User Queue 350 166 168 48
Command Queue - 1 7 -
Hold Queue - 0 50 -
Client Queue 200 159 162 81
HQ User Limit 150,000 - 50 0
Threads 20 1 20 100
Workpool 30,000,000 0 14,706,560 49
ISN Sort 10,000,000 - 2,273,448 22
Complex Search 10,000,000 - 10,000,000 100
Attached Buffer 1,605,632 1,247,232 1,317,888 82
ATBX (MB) 20 0 0 0
Buffer Pool 512,000,000 511,938,560 511,982,592 99
Protection Area 127,990
Active Area 38,397 - 34 0
XA Area 10 0 0 0
Group Commit 100 1 1 1
Transaction Time 7,200 - 2,420 33

We are not really sure about the ideal configuration for the following parameters:

NCL
LAB
LBP

Any help would be really appreciated.

Thanks

2

Jorge,

unfortunately there’s no “ideal configuration” you can calculate in advance.

This appears to be a Rsp255 / Subcode 1 which indicates a LAB overflow,
thus you will need to increase that parameter. By how much, you will ask ?
You will have to try, I’m afraid, there’s no rule of thumb :wink:

But if memory is no scarce resource on that server I’d say double it for a start.

NCL still has some cushion, so no immediate need to increase, but if you do,
don’t set it too high.

LBP - the high water mark here doesn’t tell anything, you will need to check
the BP stats.

3

Thanks Wolfgang,

We have just increased the LAB to 3,200,000 doubling our initial configuration.

So far so good and no 255 error code reported.

Will keep you posted!

4

We had the same issue, Adabase team have increased the LAB size, but after 2 days again this error started coming? Could there be any other issue… right now?

5

Dear all

I am being faced with the following error

NATURAL SECURITY LOGON FAILED DUE TO ADABAS RESPONSECODE: 255 on mainframe.

can this be related to the LBP parameter in dev.

ADARUN LBP=320000000 BUFFER POOL SIZE WAS 20480000

ADARUN LU=65535 INTERMEDIATE USER BUFFER AREA

using adabas v 8.3.3