Short Dump:DBIF_RSQL_SQL_ERROR; Exception :CX_SY_OPEN_SQL_DB

Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
     SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.525
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.652
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line  SourceCde
  1622              ID 'DATA' FIELD jobinfo_egj.
  1623
  1624           rc = 1.
    EXIT.
  ELSE.
    db_steplist-priparkey = tmp_key.
  ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog   = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag   = 'X'.
DIF.
steplist-sdldate  = newjob_head-sdldate.
steplist-sdltime  = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
  ENDIF.
  CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
  jobinfo_egj SEPARATED BY '/'.
  CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
        ID 'KEY'  FIELD tbtcp_insert_db_error
        ID 'DATA' FIELD jobinfo_egj.
  rc = 1.
  EXIT.
ENDIF.
rc = 0.
DFORM.                               " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.

Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards

Similar Messages

  • Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB

    Hi,
    i need some guides to solve this problem.
    The program works fine in client DEV. However, when it's in QAS, we encounter  short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
    info from short dump:
    An SQL error occurred when accessing a table.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "FILL_T_DATA_TABLE" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "FILL_T_DATA_TABLE"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-24371: data would not fit in current prefe
    buffer"
    Internal call code.........: "[RSQL/FTCH/VBUK ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
    "FILL_T_DATA_TABLE"
    If you cannot solve the problem yourself, please send the...
    Information on where terminated
    The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
    "FILL_T_DATA_TABLE".
    The main program was "ZSDR_SHIPPING_REPORT ".
    The termination occurred in line 3561 of the source code of the (Include)
    program "ZSDR_SHIPPING_REPORT"
    of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
    35610).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
    in line 3468
    of the (Include) program "ZSDR_SHIPPING_REPORT ".
    source code:
    035490
    035500   *get all open sales orders (those that are deemed open at the Sales
    035510   *Order "Header" level)
    035520     clear open_orders.
    035530     refresh open_orders.
    035540     select * into corresponding fields of table open_orders
    035550       from vbuk
    035560       where ( vbtyp = 'C' or vbtyp = 'I' )
    035570         and ( gbstk = 'A' or gbstk = 'B' ).
    035580
    035590   *get all open deliveries(some sales orders may be closed yet the
    035600   *associated Delivery is not yet PGI'd)
         >     clear open_deliveries.
    035620     refresh open_deliveries.
    035630     select * into corresponding fields of table open_deliveries
    035640       from vbuk
    035650       where vbtyp = 'J'
    035660         and ( wbstk = 'A' or wbstk = 'B' ).
    035670
    035680   *get sales orders associated with the Open deliveries
    Please advice.
    Thanks.

    Thanks for the response.
    Hi Renga,
    The error happens in second selection.
    this is the souce code:
    data: begin of open_orders occurs 0,
            vbeln like vbuk-vbeln,
            gbstk like vbuk-gbstk,
            vbtyp like vbuk-vbtyp,
          end of open_orders.
    data: begin of open_deliveries occurs 0,
            vbeln like vbuk-vbeln,
            wbstk like vbuk-wbstk,
            vbtyp like vbuk-vbtyp,
          end of open_deliveries.
    *get all open sales orders (those that are deemed open at the Sales
    *Order "Header" level)
      clear open_orders.
      refresh open_orders.
      select * into corresponding fields of table open_orders
        from vbuk
        where ( vbtyp = 'C' or vbtyp = 'I' )
          and ( gbstk = 'A' or gbstk = 'B' ).
    *get all open deliveries(some sales orders may be closed yet the
    *associated Delivery is not yet PGI'd)
      clear open_deliveries.
      refresh open_deliveries.
      select * into corresponding fields of table open_deliveries
        from vbuk
        where vbtyp = 'J'
          and ( wbstk = 'A' or wbstk = 'B' ).
    Hi Prabhu,
    how to identify the problem in DB02?
    Please advice.
    Thanks.
    regards.

  • Short dump 'DBIF_RSQL_SQL_ERROR' in R/3 system

    Hi,
    In the daily extraction process in BW a load process(infopackage) fails due to short dump "DBIF_RSQL_SQL_ERROR" in the source system(R/3) side.
    The load getting the 20000 records but the process failed due to above error. i have made the request red and delete the request from the respective data target and repeate the load, it isthrowing same error "DBIF_RSQL_SQL_ERROR" with 0 records.
    my question is if i solve the error and repeate the load can i get previous delta records with the latest delta.
    Can any one give a solution.
    Thanks

    Hi,
    If you are marking the dataload as "RED" in monitor before deleting the request, you will get the same delta with next load.
    You can verify this in next load  @ monitor. It will show you the request type as 'Repeat of last delta' and normal requests will be shown as 'Delta'.
    In case you are manually running the infopackage, system will prompt the message something like' last detla request was incorrect, repeat the last delta'.
    Regards,
    Pratap Sone

  • Short Dump: DBIF_RSQL_SQL_ERROR

    Hello experts,
    I am getting lot of dumps in my BI system (Windows+ Oracle 10.2)
    How to correct part is :
    Database error text........: "ORA-00600: internal error code,
    [20084], [29798105], [7], [29798105], [7], [], [], []"
    Internal call code.........: "[RSQL/FTCH/TBTCO ]"
    Please check the entries in the system log (Transaction SM21).
    And System log is :
    Database error 600 requires database administrator to intervene
    Database error 600 at FET access to table TBTCO
    > ORA-00600: internal error code, arguments: [20084],
    > [29798105], [7], [29798105], [7], [], [], []
    Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    > Short dump "081006 160347 NW04SBI7 B7I00 " generated
    How will I proceed in this scenario ?
    Waiting for your guidance!
    Thanks in advance!
    Abhilash

    And the trace file would be:
    ACTION NAME:(55090) 2008-10-07 10:00:59.826
    MODULE NAME:(SAPLBTCH                                ) 2008-10-07 10:00:59.826
    SERVICE NAME:(SYS$USERS) 2008-10-07 10:00:59.826
    SESSION ID:(58.401) 2008-10-07 10:00:59.826
    2008-10-07 10:00:59.826
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []
    Current SQL statement for this session:
    SELECT "JOBNAME" , "JOBCOUNT" , "JOBGROUP" , "INTREPORT" , "STEPCOUNT" , "SDLSTRTDT" , "SDLSTRTTM" , "BTCSYSTEM" , "SDLDATE" , "SDLTIME" , "SDLUNAME" , "LASTCHDATE" , "LASTCHTIME" , "LASTCHNAME" , "RELDATE" , "RELTIME" , "RELUNAME" , "STRTDATE" , "STRTTIME" , "ENDDATE" , "ENDTIME" , "PRDMINS" , "PRDHOURS" , "PRDDAYS" , "PRDWEEKS" , "PRDMONTHS" , "PERIODIC" , "DELANFREP" , "EMERGMODE" , "STATUS" , "NEWFLAG" , "AUTHCKNAM" , "AUTHCKMAN" , "SUCCNUM" , "PREDNUM" , "JOBLOG" , "LASTSTRTDT" , "LASTSTRTTM" , "WPNUMBER" , "WPPROCID" , "EVENTID" , "EVENTPARM" , "BTCSYSREAX" , "JOBCLASS" , "PRIORITY" , "EVENTCOUNT" , "CHECKSTAT" , "CALENDARID" , "PRDBEHAV" , "EXECSERVER" , "EOMCORRECT" , "CALCORRECT" , "REAXSERVER" , "RECLOGSYS" , "RECOBJTYPE" , "RECOBJKEY" , "RECDESCRIB" , "TGTSRVGRP" FROM "TBTCO" WHERE "JOBNAME" LIKE :A0 ESCAPE '#' AND ( "STATUS" = :A1 OR "STATUS" = :A2 ) AND "STRTDATE" >= :A3 AND ( "STRTDATE" < :A4 OR "STRTDATE" = :A5 AND "STRTTIME" <= :A6 )
    Call Stack Trace -
    calling              call     entry                argument values in hex     
    location             type     point                (? means dubious value)    
    _ksedst38           CALLrel  _ksedst10           0 1
    _ksedmp898          CALLrel  _ksedst0            0
    _ksfdmp14           CALLrel  _ksedmp0            3
    _kgeriv+146          CALLreg  00000000             B5863A8 3
    _kgeasi92           CALLrel  _kgeriv0            B5863A8 76720C4 4E74 4
                                                       E80D310
    _qerbtRop346        CALLrel  _kgeasi0            B5863A8 76720C4 4E74 2 4 0
                                                       1C6AED9 0 0 7 0 0 1C6AED9 0 0
                                                       7 0
    _qersoFetch+366      CALLptr  00000000            
    _qerbtFetch+607      CALL???  00000000            
    _kdibr1sf+55         CALL???  00000000             317EC790 0 0 1 317EC790
                                                       E80D498
    _qerbaFndOl125      CALLrel  _kdibr1sf0          EBC8198 317EC790 E80D498
                                                       DDC51C4
    _qerbaStrmAnd145    CALLrel  _qerbaFndOl0       
    _qerbaFetch121      CALLrel  _qerbaStrmAnd0     
    _kdibr1sf+55         CALL???  00000000             317EC61C 0 0 1 317EC61C 0
    _qerbtFetch1448     CALLrel  _kdibr1sf0          ECB3F54 317EC61C 0 ECB3F68
    _qertbFetchByRowID+  CALL???  00000000             317EC464 0 E80D828 1
    475                                               
    _qeruaFetch+253      CALL???  00000000            
    _opifch2+3115        CALL???  00000000             317EC0FC 1E9B2F4 E80D9D8 18
    _opiefn0348         CALLrel  _opifch20           89 4 E80DB7C
    _opiefn21           CALLrel  _opiefn00           4E 4 E80F698 0 0 0 0 0 0 0
    _opiodr+1099         CALLreg  00000000             4E 4 E80F698
    _ttcpip+1273         CALLreg  00000000             4E 4 E80F698 C9
    _opitsk+1017         CALL???  00000000            
    _opiino1087         CALLrel  _opitsk0            0 0
    _opiodr+1099         CALLreg  00000000             3C 4 E80FC30
    _opidrv819          CALLrel  _opiodr0            3C 4 E80FC30 0
    _sou2o45            CALLrel  _opidrv0            3C 4 E80FC30
    opimaireal112     CALLrel  _sou2o0             E80FC24 3C 4 E80FC30
    _opimai92           CALLrel  opimaireal0       2 E80FC5C
    _OracleThreadStart@  CALLrel  _opimai+0           
    4+708                                             
    77E64826             CALLreg  00000000            
    Thanks,
    Abhilash

  • Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

    Hi All,
    I am loading a COPA cube from a DSO.
    There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
    When i checked in SM21 transaction code, i got the following message
    10:41:52 BTC  018 500 AMRUKV                     BY  O Deadlock occurred
    10:41:53 BTC  018 500 AMRUKV                     BY  4 Database error 60 at INS access to table /BIC/FCSDV
    10:41:53 BTC  018 500 AMRUKV                     BY  0 > ORA-00060: deadlock detected while waiting for resource
    10:41:54 BTC  018 500 AMRUKV                     AB  0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    10:41:58 BTC  018 500 AMRUKV                     AB  1 > Short dump "080818 104154 s0173bel PB100 " generated
    10:41:58 BTC  018 500 AMRUKV                     D0  1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
    In transaction code ST22 i got the following message:
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          18.08.2008 10:41:54
    Short text
         SQL error in the database when accessing a table.
    What happened?
         The database system detected a deadlock and avoided it by rolling back
         your transaction.
    What can you do?
         If possible (and necessary), repeat the last database transaction in the
          hope that locking the object will not result in another deadlock.
         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_ICFACT" "(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:
         The database system recognized that your last operation on the database
         would have led to a deadlock.
         Therefore, your transaction was rolled back
         to avoid this.
         ORACLE always terminates any transaction that would result in deadlock.
         The other transactions involved in this potential deadlock
         are not affected by the termination.
    How to correct the error
        Database error text........: "ORA-00060: deadlock detected while waiting for
         resource"
        Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
        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"
        "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
        "WRITE_ICFACT"
        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
        "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
        RAISING clause of the procedure.
        To prevent the exception, note the following:
    Can anybody suggest on what can be done?
    Thanks in Advance,
    Regards
    A.T

    Hi ,
    This is a table space issue....
    u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
    U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
    This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
    Thanks
    Sandeep

  • Transport with return code 12 ,short dump with 'DBIF_RSQL_SQL_ERROR'

    Dear All,
    My trasnport contains infoprovider. DTP,transpformations, character realtionships , aggregation levels ,web templates, programs.
    I got a transport failed with Return code 12, and it is showing message :
    Program terminated (job: RDDEXECL, no.: 06031600)
       See job log
    Execution of programs after import (XPRA)
    End date and time : 20101026060421
    Ended with return code:  ===> 12 <===
    I have short dump with 'DBIF_RSQL_SQL_ERROR' exception 'CX_SY_OPEN_SQL_DB'.
    in how to correct the error :
    below is the detials.
    Database error text........: "ORA-01578: ORACLE data block corrupted (file #
    211, block # 79950)#ORA-01110: data file 211:
    '/oracle/RBW/sapdata15/xbw_188/xbw.data188'#ORA-26040: Data block was loaded
    using the NOLOGGING option"
    did someone has the same problem .
    Help is really appreciated.
    Regards
    Veera

    I am afraid you will need to esclate this to BASIS team.. seems some issue with database

  • Short dump in custom report in production

    Hi Experts,
      I have a custom report which is run through SM37 as a background job. it takes long time to run and then get canceled with       short dump in production but it runs fine in development.
    description of short dump.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          03.05.2010 11:33:06
    Short text
    |    SQL error in the database when accessing a table.

    Hi,
    Please go through the below notes
    [Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1379839]
    [Note 1098183 - RunErr dbif_rsql_sql_error with exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1098183]
    [Note 1410849 - Runtime error DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"|https://service.sap.com/sap/support/notes/1410849]
    This is mainly program error and need corrections...
    Compare the Patch level on both DEV and PRD server. Also make sure, whether program you are using on developement is modified (Corrected) or standard one.
    If you search for the SAP Notes with "DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB" string, you will get several hits. See the notes which are applicable in your scenario...
    Regards.
    Sumit Nene

  • Short Dump while fetching values from a Database view

    Hi ALL,
    Here is the code that is giving short dump
    SELECT * FROM ZVMATLMOVE INTO TABLE I_MATLMOVE
        WHERE BUDAT >= V_LASTRUN_DATE
        AND   WERKS IN S_WERKS
        AND   LIFNR IN S_LIFNR
        AND   EBELN IN S_EBELN
        AND   MATNR IN S_MATNR
        AND   BWART IN S_BWART
    (Please don't say that I am using * in the select query,
    I knew that it is not a good way of fetching values)
    Declaration of the internal table is:
    DATA  I_MATLMOVE LIKE ZVMATLMOVE OCCURS 0 WITH HEADER LINE.
    The variable V_LASTRUN_DATE is:
    DATA  V_LASTRUN_DATE LIKE SY-DATUM.
    We will be getting the lastrundate value from another table. And it is passing correct value (ex. 20060731)
    ZVMATLMOVE is a database view created for MKPF and MSEG table. And I checked both table were consistent.
    Dump Analysis:
    Runtime errors         DBIF_RSQL_SQL_ERROR          
    Exception              CX_SY_OPEN_SQL_DB
    Every thing is fine. But I don't know how it is going to dump. Any suggestions?

    Hi !
    It seams that your table is not correct / fully activated.
    To check it out you should try the following:
    - Go to the SE11
    - Give it your table name and go to "Display"
    - Check if the table is "active"
    - Choose "Utilities->Database Object->Check" and see
      if there are any errors
    - go back and choose "Utilities->Runtime Object->Check"
      and see if there are any errors
    If there are any errors - try to activate the table again. You may need the "Utilities->Database Utiliy" for that.
    After there are no more errors by checking all these your program should work.
    Regards
    Rainer
    Some points would be nice if thate helped a bit.

  • Short Dump while INSERTING to a DB Z table

    There is one report that we are running in production. Earlier it was taking about 2hrs to run and now it's taking about 14-15 hours to run after we applied the Support Pack. I must agree that the report is not well written by the previous developers and I have been asked to rewrite it but in the meanwhile, they want to continue running the old one.
    This report deletes all the existing records first and then updates a Z table. Last week when they tried to run the report as batch job it got cancelled after running 22000 secounds and my basis team told me that logs are getting saturated and we need to use Truncate Statement instead of DELETE from table statement and that is what I did but again when they tried running the report in production it got cancelled again and this time after 55000 secs and this time it's getting cancelled in the last step when we are inserting the records back to the table from the internal table.
    So can you please tell me how can I take care of this.
    My Findings:
    1. Report updates a Z table for 700K records which is really not a very big size.
    2. Z table size category is customized for upto 48K to 93K . Does this matter when I try to update 700K records at a time.
    3. There is no foreign key relations in the Z table
    4. I feel that, it could be a basis problem like, memory related. Any light on this?
    5. The program currently uses INSERT statement.Can I try for a success using MODIFY statement. All validations are handled before inserting to remove the duplicates.So I dont see any issues using INSERT statement
    6. Can we use a commit statement after INSERT or MODIFY?
    7. From SAP help, I see that there is a limitation on the number of records can be inserted or modified. Any idea on the number?
    Thanks & Best Regards,
    Kiran Babu Dasari

    Dump:
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          01/01/2009 10:17:22
    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........: "SQL0964C The transaction log for the database is
    full. SQLSTATE=57011 row=1"
    Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
    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"
    "ZPMM_BWLOAD_R_V2" or "ZPMM_BWLOAD_INC02"
    "FILL_ZTMM_PU_FOR_BW"
    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
    "FILL_ZTMM_PU_FOR_BW" "(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 700
    Application server... "ucerp13"
    Network address...... "192.168.254.23"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "00C4B5BE4C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 34
    Shortdump setting.... "full"
    Database server... "ucerp10"
    Database type..... "DB6"
    Database name..... "RP1"
    Database user ID.. "SAPRP1"
    Terminal................. " "
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 26 2008 20:51:39"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "DB6_81 "
    Patch level. 183
    Patch text.. " "
    Database............. "DB6 08.02., DB6 09."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 16192
    EM...... 234631488
    Heap.... 0
    Page.... 24576
    MM Used. 28706288
    MM Free. 197532304
    User and Transaction
    Client.............. 400
    User................ "BATCHUC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "49597E9619C40076E1008000C0A8FE17"
    Program............. "ZPMM_BWLOAD_R_V2"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "ZPMM_BWLOAD_R_V2" - in
    "FILL_ZTMM_PU_FOR_BW".
    The main program was "ZPMM_BWLOAD_R_V2 ".
    In the source code you have the termination point in line 2886
    of the (Include) program "ZPMM_BWLOAD_INC02".
    The program "ZPMM_BWLOAD_R_V2" was started as a background job.
    Job Name....... "ZPMM_BWLOAD_R_V2"
    Job Initiator.. "BATCHSCHED"
    Job Number..... 10261500
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "FILL_ZTMM_PU_FOR_BW" "(FORM)", but it was neither handled locally
    nor declared
    in the RAISING clause of its signature.
    The procedure is in program "ZPMM_BWLOAD_R_V2 "; its source code begins in line
    2751 of the (Include program "ZPMM_BWLOAD_INC02 ".
    Source Code Extract
    Line
    SourceCde
    2856
    itab_result-rec_no   = recnum.
    2857
    ENDIF.
    2858
    2859
    11/30/05 - Change it back after sorting
    2860
    IF linetype = 'AAA'.
    2861
    itab_result-linetype = 'INI'.
    2862
    ENDIF.
    2863
    itab_result-extractdate = e_sdate.
    2864
    itab_result-mandant     = sy-mandt.
    2865
    MODIFY itab_result INDEX indx.
    2866
    2867
    SELECT SINGLE
    2868
    rec_no
    2869
    ponumber
    2870
    FROM ztmm_pu_for_bw
    2871
    INTO CORRESPONDING FIELDS OF itab_duprec
    2872
    WHERE rec_no     = recnum
    2873
    AND ponumber   = pono
    2874
    AND   linetype = linetype
    2875
    AND   line_no  = lineno
    2876
    AND   changenr = chgno
    2877
    AND   chgind_h = indh
    2878
    AND   chgind_p = indp
    2879
    AND   tblname  = tbl
    2880
    AND   fldname  = fld.
    2881
    IF sy-subrc <> 0.
    2882
    MOVE-CORRESPONDING itab_result TO itab_result_bw.
    2883
    APPEND itab_result_bw.
    2884
    nrecs_results = nrecs_results + 1.
    2885
    >>>>>
    INSERT ztmm_pu_for_bw FROM TABLE itab_result_bw.
    2887
          INSERT zztmm_pu_for_bw FROM TABLE itab_result_bw.
    2888
    2889
    CLEAR itab_result_bw.
    2890
    REFRESH itab_result_bw.
    2891
    ENDIF.
    2892
    ENDLOOP.
    2893
    *change to array insert for performance
    2894
          INSERT ZZTMM_PU_FOR_BW FROM TABLE itab_result_bw.
    2895
    2896
    ENDFORM.                    " fill_ztmm_pu_for_bw
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    4
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Load Purchasing Info. for BW Reporting
    SY-MSGTY
    E
    SY-MSGID
    TD
    SY-MSGNO
    600
    SY-MSGV1
    T710-08L04
    SY-MSGV2
    K01
    SY-MSGV3
    EN
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20081231
    SY-UZEIT
    190013
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    2 FORM         ZPMM_BWLOAD_R_V2                    ZPMM_BWLOAD_INC02                    2886
    FILL_ZTMM_PU_FOR_BW
    1 EVENT        ZPMM_BWLOAD_R_V2                    ZPMM_BWLOAD_R_V2                      192
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       2 Ty.          FORM
    Name  FILL_ZTMM_PU_FOR_BW
    SY
    #######ৡ###################A###P#################ż#############################T#######린 u#̀##
    00000000000000000000000000000000000000010000000000000000000000000000000000000000000000FB000000
    000000090000000000000000000000000000000A0000000001000000000000000000000000000000000000F9000300
    0000000E0000000000000000000400050000000B0000000007000000000000000000000000000105000000FB270000
    0000010100000000000000000101010000000000000000040C000000000000000000000000000604000000F005000C
    ITAB_RESULT_BW-WAERS
    USD
    00000
    00000
    55422
    53400
    ITAB_RESULT-WAERS
    USD
    00000
    00000
    55422
    53400
    ITAB_RESULT_BW+5358(10)
    #U#C# #
    0205040202
    0005030000
    ITAB_RESULT+4160(10)
    #U#C# #
    0205040202
    0005030000
    AMTCRCHGPOSREGUA2
    00000000000
    0000000000C
    ITAB_RESULT_BW+5378(572)
    #S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
    0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
    000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
    ITAB_RESULT+4170(572)
    #S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
    0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
    000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
    C_INITIAL
    @0E@
    000000
    000000
    434422
    005000
    ITAB_RESULT_BW-ORT01
    Cincinnati
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    46666666762222222222222222222222222
    39E39EE1490000000000000000000000000
    ITAB_RESULT-ORT01
    Cincinnati
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    46666666762222222222222222222222222
    39E39EE1490000000000000000000000000
    ITAB_RESULT_BW-PSTLZ
    45206
    0000000000
    0000000000
    3333322222
    4520600000
    ITAB_RESULT-PSTLZ
    45206
    0000000000
    0000000000
    3333322222
    4520600000
    ITAB_RESULT_BW-REGIO
    OH
    000
    000
    442
    F80
    ITAB_RESULT-REGIO
    OH
    000
    000
    442
    F80
    ITAB_RESULT_BW-STRAS
    2709 Woodburn Ave.
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    33332566667762476222222222222222222
    270907FF4252E0165E00000000000000000
    ITAB_RESULT-STRAS
    2709 Woodburn Ave.
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    33332566667762476222222222222222222
    270907FF4252E0165E00000000000000000
    %_SPACE
    0
    0
    2
    0
    ITAB_RESULT_BW+6154(4)
    0202
    0000
    ITAB_RESULT+4908(4)
    0202
    0000
    LW_LINES
    164
    000A
    0004
    ITAB_RESULT_BW-TELF1
    961-1122
    0000000000000000
    0000000000000000
    3332333322222222
    961D112200000000
    ITAB_RESULT-TELF1
    961-1122
    0000000000000000
    0000000000000000
    3332333322222222
    961D112200000000
    ITAB_RESULT_BW-LAND1
    US
    000
    000
    552
    530
    ITAB_RESULT-LAND1
    US
    000
    000
    552
    530
    COUNTROCHGNEGCONOVER1K2
    0
    0000
    0000
    ITAB_RESULT_BW+6158(337)
    #0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
    0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
    00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
    ITAB_RESULT+4950(337)
    #0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
    0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
    00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
    ITAB_CHGLOG[]
    Table IT_33[587x1576]
    \PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_CHGLOG[]
    Table reference: 25
    TABH+  0(20) = 070000009070DB38000000000000000000000000
    TABH+ 20(20) = 00000019000000210000024B00000628FFFFFFFF
    TABH+ 40(16) = 040000000000149000082C9401800000
    store        = 0x070000009070DB38
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 25    (0x00000019)
    label        = 33    (0x00000021)
    fill         = 587   (0x0000024B)
    leng         = 1576  (0x00000628)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000095
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A0E13E70
    pgHook       = 0x07000000B2EBC728
    idxPtr       = 0x07000000906BA5E0
    shmTabhSet   = 0x0000000000000000
    id           = 32    (0x00000020)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 1024  (0x00000400)
    lineAlloc    = 592   (0x00000250)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 469   (0x000001D5)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    ITAB_RESULT_BW+3592(1026)
    0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ITAB_RESULT+5798(1026)
    0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ITAB_RESULT_BW-MANDANT
    400
    000
    000
    333
    400
    ITAB_RESULT-MANDANT
    400
    000
    000
    333
    400
    AMTTCCHGPOSREGST2
    00000000000
    0000000000C
    ITAB_RESULT_BW[]
    Table IT_132[1x6760]
    \PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_RESULT_BW[]
    Table reference: 51
    TABH+  0(20) = 07000000A9A1FEA8000000000000000000000000
    TABH+ 20(20) = 00000033000000840000000100001A68FFFFFFFF
    TABH+ 40(16) = 0400000000003140000224C401800000
    store        = 0x07000000A9A1FEA8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 51    (0x00000033)
    label        = 132   (0x00000084)
    fill         = 1     (0x00000001)
    leng         = 6760  (0x00001A68)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000248
    occu         = 2     (0x00000002)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A283E980
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 141   (0x0000008D)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 2     (0x00000002)
    lineAlloc    = 2     (0x00000002)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    ITAB_RESULT_BW
    400##͒4500034945
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3330053333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    4000024500034945000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    COUNTTCCHGNEGCONST3
    0
    0000
    0000
    <%_TABLE_ZTMM_PU_FOR_BW>
    AMTTOTAL3
    00000000000
    0000000000C
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    T023T
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T024
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T161
    00000                                   00000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222223333322222222222222222222222222222222222333332222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    TWLAD
    000000000000000000000000
    000000000000000000000000
    222222222222222222222222
    000000000000000000000000
    ZTMM_BOA
    0000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ZTMM_PU_FOR_BW
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2220002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ZTPU_DOCTYPE
    0000000000000000000000000000000000
    0000000000000000000000000000000000
    2222222222222222222222222222222222
    0000000000000000000000000000000000
    USR02
    ####0000000000000000             #                        000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222220000333333333333333322222222222220222222222222222222222222333333333333333333333
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SSCRFIELDS
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_BLUESQUAREX
    @3X@
    000000
    000000
    435422
    038000
    Internal notes
    The termination was triggered in function "HandleRsqlErrors"
    of the SAP kernel, in line 786 of the module
    "//bas/700_REL/src/krn/runt/absapsql.c#11".
    The internal operation just processed is "SQLS".
    Internal mode was started at 20081231190002.
    Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = 4294967296
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x0x11c0f5d60
    => Stack address = 0xfffffffffff8040
    => Stack low     =  0xfffffffffff8040
    => Stack high    =  0xffffffffffff800
    => Stack Trace:
         AixStack() at 0x1000c945c
         CTrcStack2() at 0x1000c9554
         rabax_CStackSave__Fv() at 0x1000b3ee0
         ab_rabax() at 0x1000b0628
         ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10058c010
         HandleRsqlErrors__F9RsqlError9CloseMode() at 0x1017f1e94
         SqlsExecuteCall__FUcP11DynCallInfo() at 0x1017efc68
         ab_jsqls__Fv() at 0x1017ea82c
         ab_extri__Fv() at 0x100419ca0
         ab_xevent__FPCUs() at 0x10094e47c
         ab_trigg__Fv() at 0x10094e168
         ab_run() at 0x1011aabb8
         N_ab_run() at 0x100f6edc0
         dynpmcal() at 0x100f6d9c4
         dynppai0() at 0x100f6b2c8
         dynprctl() at 0x100f7375c
         dynpen00() at 0x100f6761c
         Thdynpen00() at 0x1000e3c6c
         TskhLoop() at 0x1000e5b64
         ThStart() at 0x1001000c0
         DpMain() at 0x101301d34
         nlsui_main() at 0x101abea68
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    ZPMM_BWLOAD_R_V2
    0
    12/31/2008
    10:10:08
    409600
    E
    1
    Prg
    SAPMSSY0
    1
    05/30/2008
    12:59:05
    92160
    E
    2
    Prg
    SAPMSSYD
    1
    08/16/2006
    12:06:37
    21504
    E
    3
    Prg
    SAPFSYSCALLS
    1
    09/09/2004
    14:18:32
    7168
    E
    4
    Prg
    RSDBRUNT
    0
    12/13/2008
    02:15:03
    254976
    E
    5
    Prg
    SAPLSPRI
    5
    12/13/2008
    02:14:06
    342016
    E
    6
    Typ
    PRI_PARAMS
    0
    11/02/1998
    09:46:12
    5120
    7
    Typ
    ARC_PARAMS
    0
    08/28/1997
    08:36:28
    6144
    8
    Typ
    PRI_LAYOUT
    0
    11/06/2003
    20:30:04
    2048
    9
    Typ
    PRIPAR_EXT
    0
    05/18/2004
    14:07:03
    3072
    10
    Typ
    PRIPAR_EX2
    0
    11/09/2000
    14:10:39
    2048
    11
    Typ
    PRIPAR_EX3
    0
    05/18/2004
    14:07:03
    5120
    12
    Typ
    TPRI_DEF
    0
    11/09/2000
    14:24:28
    5120
    13
    Typ
    USR01
    0
    05/30/2008
    19:06:47
    4096
    14
    Typ
    TSP1D
    0
    11/15/2000
    17:58:02
    5120
    15
    Prg
    SAPLSPOO
    15
    12/13/2008
    02:14:06
    160768
    E
    16
    Prg
    SAPLRSPOLSTDRV
    16
    12/13/2008
    02:13:54
    58368
    E
    17
    Typ
    TSPOPTIONS
    0
    01/29/1997
    19:13:56
    2048
    18
    Typ
    TSP03
    0
    11/02/1998
    09:57:05
    5120
    19
    Typ
    TSP0A
    0
    11/15/2000
    17:58:02
    6144
    20
    Typ
    TSP03C
    0
    11/21/2003
    11:41:10
    7168
    21
    Typ
    TSP03T
    0
    03/23/1998
    18:21:38
    6144
    22
    Typ
    TSP06A
    0
    11/15/2000
    17:58:02
    7168
    23
    Prg
    SAPCNVE
    23
    09/09/2004
    14:36:10
    8192
    E
    24
    Prg
    SAPLSPOC
    24
    12/13/2008
    02:15:07
    137216
    E
    25
    Typ
    TSP03L
    0
    07/10/1997
    00:46:18
    2048
    26
    Typ
    RSPOCHECK
    0
    08/13/1997
    12:53:10
    4096
    27
    Typ
    TSP03A
    0
    07/10/1997
    00:46:15
    3072
    28
    Prg
    SAPLSPOR
    28
    12/13/2008
    02:15:07
    39936
    E
    29
    Prg
    SAPLSPOB
    29
    05/30/2008
    09:36:14
    67584
    E
    30
    Prg
    SAPLSDEX
    30
    09/09/2004
    14:20:42
    22528
    E
    31
    Typ
    DD07T
    0
    05/30/2008
    00:38:18
    3072
    32
    Typ
    DEVPAR
    0
    12/04/2000
    12:46:11
    3072
    33
    Typ
    RSPOATTR
    0
    11/10/1999
    17:44:19
    2048
    34
    Typ
    RSSCR
    0
    03/30/2005
    10:21:45
    5120
    35
    Prg
    RSDBSPBL
    0
    03/30/2005
    10:21:58
    72704
    E
    36
    Prg
    SAPDB__S
    0
    03/30/2005
    10:22:01
    19456
    E
    37
    Typ
    VARID
    0
    05/12/1997
    16:51:30
    4096
    38
    Typ
    SSCRFIELDS
    0
    05/13/1997
    12:54:26
    5120
    39
    Prg
    %_CSYDB0
    0
    03/30/2005
    10:21:45
    35840
    E
    40
    Prg
    RSDBSPVA
    0
    12/13/2008
    02:15:03
    133120
    E
    41
    Typ
    RSVAMEMKEY
    0
    05/07/1997
    13:07:49
    5120
    42
    Prg
    RSDBSPMC
    0
    08/16/2006
    11:55:58
    79872
    E
    43
    Typ
    DDSHDESCR
    0
    09/03/1997
    03:05:16
    4096
    44
    Typ
    SPPARAMS
    0
    05/07/1997
    13:10:38
    2048
    45
    Prg
    SAPLICON
    45
    05/30/2008
    13:22:44
    27648
    E
    46
    Prg
    %_CICON
    45
    05/30/2008
    13:22:44
    107520
    E
    47
    Typ
    ICONT
    0
    08/16/2006
    11:55:57
    2048
    48
    Prg
    SAPLSABE
    48
    09/09/2004
    14:18:36
    12288
    E
    49
    Prg
    SAPLSECU
    49
    05/30/2008
    11:07:13
    87040
    E
    50
    Typ
    RSSUBINFO
    0
    10/14/1999
    22:01:03
    2048
    51
    Typ
    RSEXFCODE
    0
    08/13/1997
    12:52:57
    2048
    52
    Prg
    SAPLDSYA
    52
    05/30/2008
    12:53:05
    45056
    E
    53
    Prg
    SAPFSDS1
    52
    03/30/2005
    10:22:01
    52224
    E
    54
    Typ
    TDCLD
    0
    11/02/1998
    09:51:35
    6144
    55
    Prg
    SAPLSDOD
    55
    01/25/2006
    10:59:45
    45056
    E
    56
    Typ
    DOKIL
    0
    05/12/1997
    16:46:17
    3072
    57
    Prg
    SAPLLANG
    57
    09/09/2004
    14:18:35
    10240
    E
    58
    Typ
    T002
    0
    05/30/2008
    00:53:58
    2048
    59
    Prg
    SAPFSPOR
    0

  • Error in HRPAD31 ( Short dump Analysis )

    Hi friends,
    When i am changing the existing qualification or adding new qualification it is showing this error in short dump
    Pls advise me if there is some relationship i am missing in 031 ?
    here is the description of short dump
    Runtime Error  DBIF_RSQL_SQL_ERROR 
    Exception        CX_SY_OPEN_SQL_DB                                   
    Occurred on     10.09.2008 at   10:48:39                                                                               
    An SQL error occurred when accessing a table.                                                                               
    What happened?                                                                               
    What can you do?                                                                               
    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer   
    termination messages, especially those beyond their normal deletion        
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below   
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB',  wasneither                                                                   
    caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"                                                                  
    Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.                                 
    The reason for the exception is:                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure "ADATA_DB" 
    "(FORM)", or declared in the procedure's RAISING clause.                       
    To prevent the exception, note the following:                                  
    Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"        
    Internal call code.........: "RSQL/INSR/HRPAD31"                
    Please check the entries in the system log (Transaction SM21).                                                                               
    You may able to find an interim solution to the problem           
    in the SAP note system. If you have access to the note system yourself, use the following search criteria:                                                                               
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                       
    "SAPLRHAP" or "LRHAPF1K"                                                       
    "ADATA_DB"                                                                     
    System environment                                                                               
    SAP Release.............. "620"                                                                               
    Application server....... "Development"                                    
    Network address.......... "200.200.200.10"                             
    Operating system......... "Windows NT"                                 
    Release.................. "5.2"                                        
    Hardware type............ "2x IA64 Level 3"                            
    Character length......... 8 Bits                                       
    Pointer length........... 64 Bits                                      
    Work process number...... 1                                            
    Short dump setting....... "full"                                                                               
    Database server.......... "Development"                                    
    Database type............ "ORACLE"                                     
    Database name............ "VC3"                                        
    Database owner........... "SAPR3"                                                                               
    Character set............ "English_United State"                                                                               
    SAP kernel............... "640"                                        
    Created on............... "Aug 16 2007 23:23:39"                       
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "                                                                               
    Patch level.............. "196"                                        
    Patch text............... " "                                                                               
    Supported environment....                                              
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 
    User, transaction...                                                                               
    Client.............. 600                                                      
    User................ "HUSER"                                                
    Language key........ "E"                                                      
    Transaction......... "PP01 "                                                  
    Program............. "SAPLRHAP"                                               
    Screen.............. "MP100100 6000"                                          
    Screen line......... 16                                                                               
    Information on where terminated                                                                               
    The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".        
    The main program was "MP100100 ".                                                                               
    The termination occurred in line 57 of the source code of the (Include)  program LRHAPF1K"                                                           
    of the source code of program "LRHAPF1K" (when calling the editor 570).       
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the  procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.                                              
    The procedure is in the program "SAPLRHAP ". Its source code starts in line 8  of the (Include) program "LRHAPF1K ".                                                                               
    PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

    Hi Ted,
    It is working, i just logged off and logged in. Now there is no error.
    Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
    I appreciate on more time for your knowledge.
    I have rewarded the points also....  
    Regards
    HR user

  • Short dump error while filling setup tables for 2LIS_06_INV

    Hi All,
    I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
    Error
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text
        SQL error in the database when accessing a table.
    plz can anyone help me out...

    Dear friends,
    I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
    error:in detail.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text
        SQL error in the database when accessing a table.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
        The main program was "RMCENEUR ".
        In the source code you have the termination point in line 827
        of the (Include) program "LMRMBWF01".
        The program "SAPLMRMBW" was started as a background job.
        Job Name....... "RMCENEUR"
        Job Number..... 10524100
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
         declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLMRMBW "; its source code begins in line
        806 of the (Include program "LMRMBWF01 ".
      806 FORM bw_retrieve_db_co  USING    t_mcrbkey_bv    TYPE mcrbkey_t
      807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
      808                                  t_ekbe_acc      TYPE t_ekbe
      809                         CHANGING t_mcrbco        TYPE mcrbco_t.
      810
      811   TYPES: BEGIN OF s_target.
      812   TYPES: table_left LIKE rbco.
      813   TYPES: table_right TYPE rbex.
      814   TYPES: END OF s_target.
      815   TYPES: t_target TYPE TABLE OF s_target.
      816
      817
      818   DATA: t_rbco_nbv  TYPE t_target,
      819         t_rbco_bv   TYPE t_target,
      820         s_rbco      TYPE s_target,
      821         s_ekbe      LIKE ekbe,
      822         s_mcrbco    TYPE mcrbco,
      823         l_index     LIKE sy-tabix.
      824
       825 * Data source: invoice item non-background
      826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
    *>>>>>     SELECT * FROM  rbco AS r LEFT OUTER JOIN rbex AS i*
      828        ON   ( rmandt = imandt AND
      829               rbelnr = ibelnr AND
      830               rbuzei = ibuzei AND
      831               rcobl_nr = icobl_nr )
      832        INTO TABLE t_rbco_nbv
      833        FOR ALL ENTRIES IN t_mcrbkey_nbv
      834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
      835              r~belnr = t_mcrbkey_nbv-belnr.
      836   ENDIF.
      837 * Data source: invoice item background
      838   IF NOT t_mcrbkey_bv[] IS INITIAL.
      839     SELECT * FROM  rbco AS r LEFT OUTER JOIN rbex AS i
      840        ON   ( rmandt = imandt AND
      841               rbelnr = ibelnr AND
      842               rbuzei = ibuzei AND
      843               rcobl_nr = icobl_nr )
      844        INTO  TABLE t_rbco_bv
      845        FOR ALL ENTRIES IN t_mcrbkey_bv
      846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
    Thnks in advance

  • Infopackage in process chain failing due to short dump on regular basis.

    HI Experts,
    There is a daily process chain in which one of the element (infopackage) fails due to short dump on regular basis (At least twice in a week) please find the message below
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text                                                                               
    SQL error in the database when accessing a table.
    And in job log it is showing ARFCSTATE = SYSFAIL
    We are able to resolve it just manual update and the process goes fine no issues but my question here is what is the exact reason for this and how to resolve it permanently or decrease the frequency of the error.
    Please if any one can tell the root cause and the solution to avoid the issue in future on regular basis.
    and also can any one elaborate what is ARFCSTATE = SYSFAIL,for trfc check we don't have access to SM58 in ECC side
    and trfc is fine in bw side
    Appreciate for not giving the general solutions like repeated solutions already posted in SDN
    with regards,
    musai

    You can contact your BASIS person he can help you reg table space issue. it says used space is 98% and free space is 1.03%.
    ask your basis to set a threshold to check the space and send a mail notification to all daily regarding the space allocation and utilization.
    ARFCSTATE = SYSFAIL means the TRFC did not processed properly to the BW system from source.
    Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE.
    Are there any hung TRFCs which are not processed to BW side. have you checked it
    first check
    load monitor -- menu -- environment -- job overview -- status of job(is it finsihed or not?) - check the job log -- ther try to find out the hung TRFc
    press find --tyep "sysfail" ok -- it will display all the hung or fialed TRFCs which are not processed to BW system.
    if you find the hung TID with respect to your load.. next goto SM58 trasaction to process the trfcs manually or use the load monitor menu -- environment -- transaction RFC -- source sys -- it will take you to same SM58 screen -- click F8 it will display the hung TRFc in that duration.
    select the TRFc and click on F6 to process them manually.
    also check the loackwaits anddead locks in ST04/DB6COCKPIT.( ask basis to check) if any dead locks are there they will take care of it.
    check for short dumps in st22 if any and try to analyse.
    Check the SM21 system logs.

  • Need help regarding short dumps in BW

    hi all,
    We have a problem in our production.Thousands of short dumps have been created in a day stating
    "Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB"
    =====================
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure "INSERT_ODS"
    "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The exception must either be prevented, caught within the procedure
    "INSERT_ODS"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-14400: inserted partition key does not map to
    any partition"
    ===================
    The RSRV check shows "Inconsistency: High value for table /BIC/B0000xxx000: 0002 ; PARTNO value in RSTSODS: 010."
    When a repair was run on this table the short dumps stopped.Is there any other steps that should be taken to avoid such dumps in future/is there something that we have missed to maintainin in BW.
    Please explain in detail, it will be of great help.
    Thanks

    Hi All,
    Thanks a lot for the valuable messages.
    So when all these stated notes are followed, and if in future if a simillar problem comes, the recovery step would be running the RSRV test and repair on the particular object?
    Thanks once again.
    Shailaja

  • Short Dump, Exception condition "NOT_EXIST" raised

    Dear Colleagues!
    I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
    I am trying to load data to ODS with full load and filtering via a DTP.
    In the monitoring the load doesn't even get started.
    I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
    I also tried to replicate and active all the rules and objects again.
    And in the source system if I test the extractor it works fine.
    I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
    Hope you can help!
    Regards Silje
    Does anyone have any ideas?
    regards, Uros

    Hi again,
    I tried RSBDELTAREPAIR and it worked!
    Thanks to the forum again!
    Silje

  • Short dump - CX_SY_OPEN_SQL_DB during MODIFY statement

    In production system, sometimes it dumps with this error:
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB
    And here is the code cause this problems:
    CALL FUNCTION 'ENQUEUE_E_TABLE'
      EXPORTING
      mode_rstable = 'E'
      tabname     = 'ZVKN_TRPHIST'.
    MODIFY zvkn_trsphist FROM TABLE lt_trsphist. <<<<<< Error
    CALL FUNCTION 'DEQUEUE_E_TABLE'
      EXPORTING
      mode_rstable = 'E'
      tabname = 'ZVKN_TRPHIST'.
    IF sy-subrc EQ 0.
      return-type = 'S'.
    ELSE.
      ROLLBACK WORK.
      return-type = 'E'.
    ENDIF.
    I have tried to use ENQUEUE statement with WAIT but no succeed. How to manage with no dump?

    Hi, thanks for your reply.
    Did you mean that adding COMMIT WORK AND WAIT when ENQUEUE is success and before modify statement?
    I not get it clearly. I use the code below. Is this ok to transport to Production?
    CALL FUNCTION 'ENQUEUE_E_TABLE'
        EXPORTING
          MODE_RSTABLE         = 'E'
          TABNAME              = 'ZVKN_TRPHIST'
    *   VARKEY               =
    *   X_TABNAME            = ' '
    *   X_VARKEY             = ' '
    *   _SCOPE               = '2'
          _WAIT                = 'X' 
    *   _COLLECT             = ' '
        EXCEPTIONS
          FOREIGN_LOCK         = 1
          SYSTEM_FAILURE       = 2
          OTHERS               = 3
       IF SY-SUBRC <> 0.
         return-type = 'E'.
         return-number = sy-msgno.
         return-id = sy-msgid.
         CALL FUNCTION 'MESSAGE_TEXT_BUILD'
           EXPORTING
             msgid               = sy-msgid
             msgnr               = sy-msgno
             msgv1               = sy-msgv1
             msgv2               = sy-msgv2
             msgv3               = sy-msgv3
             msgv4               = sy-msgv4
           IMPORTING
             message_text_output = return-message.
         ROLLBACK work.
         RETURN.
       ELSE.
         COMMIT WORK AND WAIT.
         MODIFY zvkn_trsphist FROM TABLE lt_trsphist.
         CALL FUNCTION 'DEQUEUE_E_TABLE'
           EXPORTING
             mode_rstable = 'E'
             tabname      = 'ZVKN_TRPHIST'.
         RETURN-type = 'S'.
       ENDIF.

Maybe you are looking for

  • Text Entry Boxes and their content not being captured in Automatic Recording

    I have searched the forums here and elsewhere extensively and whilst I have found people with similar issues, I have yet to find a solution. My problem is this: I am trying to record myself using a piece of software which contains numerous text field

  • Acer Aspire V3-731 - Window 8.1 - Live Updater not downloading

    I am on Windows 8.1 and I keep getting the Live Updater pop-up advising that there is an update for Intel VGA Driver. When I click to install it simply comes back with no specific error code and does not do any installation. This has happened now at

  • Documents in Crystal report on BW report

    Dear experts, we use Crystal Report on BW reports. During the planning process our user enter some comments as documents within BW system. (f.e. Year, Version, SalesOrg 1 --> comment 1,... Year, Version, SalesOrg n --> comment n) These documents shou

  • MacBook Pro/ProTools version to use with Digi 002 (or switch to Logic)??

    I was in the middle of a recording session using a PowerBook running ProTools LE7.4.1 with a Digi 002 interface when my drive crashed (techs are telling me it was just old age).  I realize now I was playing with fire using 5-6 year old equipment & sh

  • Can't connect to c-rio 9068

    I have the full 2013 development system which includes the real time module. I'm trying to use it with the c-9068 for the first time. I'm able to see it in MAX and everything seems fine. When I add it to a project, I can see the modules but I can't c