Runtime Errors DBIF_RSQL_INVALID_RSQL

[Former Member]

Hi experts,

I got a runtime error like below, when I display/change WBS element or park document, so I think it may be a database error.

Could you pls give me some advice? Thanks a lot.

Runtime Errors        DBIF_RSQL_INVALID_RSQL

Exception              CX_SY_OPEN_SQL_DB

Date and Time          2014.10.10 11:09:47

Short text

    Error in module RSQL of the database interface.

What happened?

    The rescources for further secondary database connections are exhausted.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator

    .

    You can use the ABAP dump analysis transaction ST22 to view and manage

    termination messages, in particular for long term reference.

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

    in

    procedure "WRITE_TO_DATABASE" "(FORM)", nor was it propagated by a RAISING

    clause.

    Since the caller of the procedure could not have anticipated that the

    exception would occur, the current program is terminated.

    The reason for the exception is:

    At the time when the program was terminated, there were too many

    database connections open at the same time.

How to correct the error

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

    "DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB"

    "SAPLPA_PACKAGE_SERVICES" or "LPA_PACKAGE_SERVICESF02"

    "WRITE_TO_DATABASE"

    The exception must either be prevented, caught within proedure

    "WRITE_TO_DATABASE" "(FORM)", or its possible occurrence must be declared in

    the

    RAISING clause of the procedure.

    To prevent the exception, note the following:

System environment

    SAP-Release 701

    Application server... "erpprdserver"

    Network address...... "192.168.55.39"

    Operating system..... "Windows NT"

    Release.............. "6.1"

    Hardware type........ "16x AMD64 Level"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 5

    Shortdump setting.... "full"

    Database server... "erpprdserver"

    Database type..... "DB6"

    Database name..... "PRD"

    Database user ID.. "SAPPRD"

    Terminal.......... "BJ-Desktop010"

    Char.set.... "C"

    SAP kernel....... 701

    created (date)... "Sep 23 2010 23:30:05"

    create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"

    Database version. "DB6_81 "

    Patch level. 111

    Patch text.. " "

    Database............. "DB6 08.02.*, DB6 09.*"

    SAP database version. 701

    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

    NT 6.0, Windows NT 6.1"

    Memory consumption

    Roll.... 16192

    EM...... 16759360

    Heap.... 0

    Page.... 49152

    MM Used. 4891632

    MM Free. 3485200

ser and Transaction

  Client.............. 800

  User................ "LIUYH"

  Language key........ 1

  Transaction......... "FBV0 "

  Transactions ID..... "FD2950E41DCFF1DFB3D278ACC0FA10B6"

  Program............. "SAPLPA_PACKAGE_SERVICES"

  Screen.............. "SAPLSLVC_FULLSCREEN 0500"

  Screen line......... 6

Information on where terminated

  Termination occurred in the ABAP program "SAPLPA_PACKAGE_SERVICES" - in

    "WRITE_TO_DATABASE".

  The main program was "RFPUEB00 ".

  In the source code you have the termination point in line 441

  of the (Include) program "LPA_PACKAGE_SERVICESF02".

  The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

  procedure "WRITE_TO_DATABASE" "(FORM)", but it was neither handled locally nor

    declared

  in the RAISING clause of its signature.

  The procedure is in program "SAPLPA_PACKAGE_SERVICES "; its source code begins

    in line

  405 of the (Include program "LPA_PACKAGE_SERVICESF02 ".

Source Code Extract

Line  SourceCde

  411        x_string      type xstring,

  412        off          type i,

  413        remainder    type i,

  414        db_con        type dbcon-con_name VALUE 'R/3*INACT_PACK'.

  415

  416  export inactive_packages from p_inactive_packages

  417    to data buffer x_string

  418    compression on.

  419  pakdatbuf_wa-relid = 'XS'.

  420  pakdatbuf_wa-srtfd = 'INACTIVE_PACKAGES'.

  421  pakdatbuf_wa-srtf2 = 0.

  422  perform get_time changing pakdatbuf_wa-cdate pakdatbuf_wa-ctime.

  423  off = 0.

  424  do.

  425    remainder = xstrlen( x_string ) - off.

  426    if remainder > c_pakdatbuf_len.

  427      pakdatbuf_wa-clustr = c_pakdatbuf_len.

  428      pakdatbuf_wa-clustd = x_string+off(c_pakdatbuf_len).

  429      append pakdatbuf_wa to pakdatbuf_tab.

  430    else.

  431      pakdatbuf_wa-clustr = remainder.

  432      pakdatbuf_wa-clustd = x_string+off(pakdatbuf_wa-clustr).

  433      append pakdatbuf_wa to pakdatbuf_tab.

  434      exit.

  435    endif.

  436    off = off + c_pakdatbuf_len.

  437    add 1 to pakdatbuf_wa-srtf2.

  438  enddo.

  439

  440 * write and commit via secondary db connection

>>>>>  delete from pakdatbuf connection (db_con) where relid like 'X%'.

  442  insert pakdatbuf connection (db_con) from table pakdatbuf_tab.

  443  commit connection (db_con).

  444

  445 endform.                    " WRITE_TO_DATABASE

[AnoopMayamkote]

Check the Declration and the fields in the internal table is same order at the time you are selecting in the report

[Former Member]

Dear Anoop Kumar Mayamkote,

Thanks for your prompt reply, could you pls give me some more specific instruction about your advice?

I don't understand what you'er saying above.

Thanks a lot again.

Regards

Johnson

[Former Member]

Let me add some information: I encountered the error when I display WBS in CJ20N, not perform report, and this error also appear in parking document in FI.

Thanks.

[AnoopMayamkote]

check u given input is correct or not..?

[Former Member]

It's not about input, all WBS element will occur this error when display or change in CJ20N project builder.

[Former Member]

Hi Tiejun,

I think since its deleting from that table using DB connection check out whether the DB connection is working properly.

I strongly suspect this is a DB connection issue.

[Former Member]

Hi Ramdas Nair,

Thanks for your reply, we have involved Basis to check this issue, but we have got noting now.

[neminath]

There is nothing wrong with your program or code.

Check if there is any issue with DB connection.

Get in touch with your DB team and Basis team.

Run your transaction again the ask DB and Basis team to monitor your transaction.

[Former Member]

Hi Neminath Havale,

Thanks for your suggestion, we have asked our Basis team to help us, if there is any new progress, I will update here.