cancel
Showing results for 
Search instead for 
Did you mean: 

dbs/ada/input_parameters = 10000 doesn't work

Former Member
0 Kudos

Hello,

does anyone have experience with setting the parameter dbs/ada/input_parameters larger than the default value 2000?

Following problem:

Yesterday some short dumps occured because of a too complex SQL statement (marker count = 2772 > max. marker count = 2000).

After increasing the parameter dbs/ada/input_parameters = 10000 (SAP note 655018), different short dumps are processed on the system:

1. DBIF_RSQL_SQL_ERROR

***LOG BY4=> sql error -1114 performing PRE on table NAST [dbtran#7588]

***LOG BY0=> POS(1) Communication packet too small [dbtran#7588]

2. DBIF_RSQL_SQL_ERROR

BE***LOG BYL=> DBQ action required because of database error [dbsh#1104]

B1SQL code: -602, SQL text: POS(0) System error: Move error [dbsh.c#1112]

BE***LOG BY4=> sql error -602 performing PRE on table NAST [dbtran#7588]

BE***LOG BY0=> POS(0) System error: Move error [dbtran#7588]

Concerning sql error -1114, I only found SAP note 140739.

The parameter value for CommandBufferSize is 131072, so the note doesn't help.

It is always the same SQL statement that causes the trouble. The database version is 7.7.06.15 and the SAP Kernel is quite new (7.01 PL 105), so I would say that dbs/ada/input_parameters = 10000 should generally work.

it seems that about 3.000 input variables cause the program crash.

Regards

Thomas

Accepted Solutions (1)

Accepted Solutions (1)

lbreddemann
Active Contributor
0 Kudos

Hello Thomas,

the problem you face now is not about the total number of input variables, but instead it is caused by the size of the statement information that don't fit into one communication packet anymore.

To ease the analysis of this situation please open a support message.

regards,

Lars

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Lars,

it was a customer program that caused the trouble. In the meantime the coding was changed and the problem is solved now.

Regards

Thomas