Skip to Content
author's profile photo Former Member
Former Member

Short dump when activate InfoProvider


When I try to activate via right click Key Figure 0CO_AREA (in RSA1/InfoSources/Controlling). I've got following short dump

1.SQL statement violates database system restriction

2. Run-time error "DBIF_RSQL_INVALID_RSQL" occurred

In Details (ST11) dev_w1 trace file i found

C Fri Sep 4 12:51:06 2009

C *** ERROR in DB6Execute[dbdb6.c, 4322] CON = 0 (BEGIN)

C &*** DbSlModifyDB6: Number of input parameters does not match the number of parameter markers ( 1 parameters; 0+

C &*** ).+

C &***+


C &*** cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, buffer_lobs=YES, op_type=8, reop+

C &***+

C &*** ABAP location info 'CL_RSDMD_ACTIVATE_MASTER_DATA=CP', 700+

C &*** SAP user 'XXX', transaction code 'RSA1'+

C &***+

C *** ERROR in DB6Execute[dbdb6.c, 4322] (END)

B ***LOG BYK=> current SQL statement exceeds a database limit [dbtran#11 @ 7482] [dbtran 7482 ]

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'

B RSLT: {dbsl=2, tran=16384}

B FHDR: {tab='/BI0/PCO_AREA', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,

B hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,

B init:p=(nil), init:#=0, wa:p=(nil), wa:#=0}

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'


B CRSR: {tab='', id=0, hold=0, prop=0x1200,, fae:blk=0,

B con:id=0, con:vndr=7, val=2,

B key:#=1, xfer=0, xin:#=1, row:#=0, upto=0, wa:p=0x7ffdebc23268}

SQL statement which generates dump is

DELETE FROM (<l_sx_itab>-name)

WHERE changed = rs_c_changed-delete

%_HINTS " note 1162665






I don't know which database limit is exceed. Any clue



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Sep 08, 2009 at 11:25 AM

    Hi Michal,

    that's a know DBSL problem that hits DELETE or UPDATE statements with SUBSTITUTE_VALUES hint.

    Please apply the latest version of dbdb6slib from service marketplace ( archive lib_dbsl* ) and restart you system.

    As a workaround you can also remove the SUBSTITUTE_VALUES hint in the ABAP coding. In any case I do not believe that this hint improoves performance. Because of the build in index heuristics The DB2 optimizer should choose an index access even without hint.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Michal,

      this bug hits only patch level 201 of the DBSL. Please update the DBSl.

      Regarding the ABAP code I do not believe that the hint helps in this case but it should not cause any problems either. If this hint is applied more PREPARE calls are neccessary since before every execution a new statement text is assembled.

      The advantage of SUBSTITUTE_VALUES hints is that the database optimizer get more information through the statement text. The downside is that a new statement is generated every time. E.g. you won't find the statement as a top scorer in a SQL cache analysis if the access plan is still bad.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.