Error DBIF_RSQL_SQL_ERROR and DBIF_REPO_SQL_ERROR while running DTP

Question

Hi to all,
I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
i have searched the SDN and found that it is due to table space problem.
if it is due to table space , how i will find it and how to correct it.
Please can any one tell we why it is coming and what is the solution for that.
i shall be thankful to you for this.
Regards
Pavneet Rana

Answer 1

Thanks for reply,
i have checked ST22 . and found the error text for 2 runtime error .
first for DBIF_RSQL_SQL_ERROR
second for  DBIF_REPO_SQL_ERROR
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          14.03.2011 22:00:21
Short text
     SQL error in the database when accessing a table.
What can you do?
     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.
How to correct the error
    Database error text........: "SQL30081N A communication error has been
     detected. Communication protocol being used: "TCP/IP". Communication API being
     used: "SOCKETS". Location where the error was detected: "200.1.1.66".
     Communication function detecting the error: "recv". Protoco"
    Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
    Please check the entries in the system log (Transaction SM21).
    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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "CL_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
    "GET_STATIC_BUFFER"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
   The exception must either be prevented, caught within proedure
   "GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
    the
   RAISING clause of the procedure.
   To prevent the exception, note the following:
Information on where terminated
    Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
     in "GET_STATIC_BUFFER".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 29
    of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
    The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
    Job Name....... "BIDTPR_2256_1"
    Job Initiator.. " a"
    Job Number..... 18254200
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
     code begins in line
    1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
Source Code Extract
Line  SourceCde
    1 method get_static_buffer.
    2   data l_s_storage type rsbm_s_storage.
    3   l_s_storage = get_s_storage( ).
    4   check l_s_storage-type = rsbm_c_storagetype-database..
    5   delete o_th_nodes_static where logid = n_logid.
    6   delete o_t_msg_static where logid = n_logid.
    7   delete o_t_logpar_static where logid = n_logid.
    8   select *
    9     from rsbmnodes connection (l_s_storage-id)
   10     appending corresponding fields of table o_th_nodes_static
   11     where logid = n_logid.
   12
   13   data l_count_monmess type sytabix.
   14   select count( * ) from rsbmonmess
   15     into l_count_monmess
   16     where logid = n_logid.
   17   if l_count_monmess > 50000.
   18     select * from rsbmonmess up to 50000 rows connection (l_s
   19       appending corresponding fields of table o_t_msg_static
   20       where logid = n_logid
   21       and   posit < 50
   22       order by node posit.
   23   else.
   24     select * from rsbmonmess connection (l_s_storage-id)
   25       appending corresponding fields of table o_t_msg_static
   26       where logid = n_logid
   27       order by node posit.
   28   endif.
>>>>>   select * from rsbmlogpar
   30     appending corresponding fields of table o_t_logpar_static
   31     where logid = n_logid.
   32   field-symbols: <l_s_nodes> type rsbmnodes,
   33                  <l_s_log> type s_log.
   34   read table o_th_log assigning <l_s_log>
   35     with table key logid = n_logid.
   36   if sy-subrc <> 0.
   37     break hoeferf.                                          "
   38   endif.
   39   loop at o_th_nodes_static assigning <l_s_nodes>.
   40     if <l_s_nodes>-node  > <l_s_log>-maxnode.
   41       <l_s_log>-maxnode = <l_s_nodes>-node.
   42     endif.
43   endloop.
44 * --- set datapackage buffer
45   cl_rsbk_dp_state=>free_buffer( n_requid ).
46   cl_rsbk_dp_state=>fill_buffer( n_requid ).
47 endmethod. 
Runtime Errors         DBIF_REPO_SQL_ERROR
Date and Time          14.03.2011 15:34:32
Short text
     SQL error "-99999" occurred when accessing program
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrato
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "CLI0108E Communication link failure.
      SQLSTATE=40003"
     Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
     Please check the entries in the system log (Transaction SM21).
     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_REPO_SQL_ERROR" " "
     "SAPLSYDB" or "LSYDBU27"
     "DB_COMMIT"
     If you cannot solve the problem yourself and want to send an error
     notification to SAP, include the following information:
     1. The description of the current problem (short dump)
        To save the description, choose "System->List->Save->Local File
     (Unconverted)".
     2. Corresponding system log
        Display the system log by calling transaction SM21.
        Restrict the time interval to 10 minutes before and five minutes
     after the short dump. Then choose "System->List->Save->Local File
     (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
    Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 7
    of the (Include) program "LSYDBU27".
    The program "SAPLSYDB" was started as a background job.
    Job Name....... "BIDTPR_2252_1"
    Job Initiator.. "A"
    Job Number..... 12541100
Source Code Extract
Line  SourceCde
    1 FUNCTION DB_COMMIT.
    2 *"----------------------------------------------------------------------
    3 *"*"Lokale Schnittstelle:
    4 *"----------------------------------------------------------------------
    5
    6   EXEC SQL.
>>>>>     COMMIT WORK
    8   ENDEXEC.
    9
   10 ENDFUNCTION 
please  can any one tell me cause for runtime error.
i shall be thankful to you for this.
regards
pavneet rana
Edited by: pavneet rana on Mar 15, 2011 1:29 PM