Troubleshooting SOA Gateway Client side issues

"adabasDriver::readLFdata() returned -300148, indicating Command 'LF' for dbid=1756, fnr=13: Rsp 148 (No active database was found, start the nucleus)

The Adabas database is not running, or cannot be accessed.

Resolution:

• Contact the administrator of your Adabas database to get it started.

• Use the control centre to change the DBID that the Web Service is using.

• Change the SVC that SOA Gateway is using to allow it to access the required DBID.

"adabasDriver::listGet() returned -300152, indicating Command 'L1' for dbid={dbid}, fnr={fnr}: Rsp 152 (The internal user buffer was not large enough to contain the user buffer areas) "

The SOA Gateway Adabas driver employs the Adabas "Multifetch" feature to reduce IPC (Inter-Process Communication) with the Adabas database server for maximum performance.

For a LIST or SELECT request a default of 64 records to be "multifetched" is applied, an Adabas response code 152 is returned when the buffer areas required to return 64 records of the size determined by the SOA Gateway XRD for the WebService in question exceed the Adabas LU parameter.

Resolution:

• Increase the Adabas LU parameter

• Reduce the size of the data to be transferred per record, for example by lowering the "maxOccurs" setting for MU and/or PE fields within the XRD

• Use the SOAP header option SOAGateway_Internal_Adabas_Multifetch_Limit to specify a value, lower than the default of 64, that results in a transfer buffer size small enough to not exhaust the LU parameter setting.