Raise Exception   Runtime error

Error analysis
A RAISE statement in the program "SAPLTHFB" raised the exception
condition "ALREADY_RUNNING".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" C
"SAPLTHFB" or "LTHFBU09"
"TH_INIT_COLLECTOR_ARRAY"
or
"SAPLTHFB" "ALREADY_RUNNING"
or
"RSM13000 " "ALREADY_RUNNING"
Source code extract
000430     end_of_data = 1.
000440     end_of_vbcontext = 1.
000450     describe field func length func_len in character mode.
000460
000470
000480   * J.B. (6.3.00): collective runs must not run concurrent for
000490   * one function module
000500   *
000510   * el (23.11.01): add server group to enqueue argument to allow
000520   *                parallel collective runs in different server groups
000530   describe field enq_vbcontext length context_len in character mode.
000540   gran_list-gname = 'UPDCOLLRUN'.
000550   gran_list-gmode = 'E'.
000560   gran_list-garg  =  client.
000570   offset = 3.
000580   gran_list-garg+3(func_len)  =  func.
000590   add func_len to offset.
000600   gran_list-garg+offset(context_len) = enq_vbcontext.
000610   append gran_list.
000620
000630   call 'C_ENQUEUE'
000640        id 'OPCODE'           field '1'
000650        id 'ENQOBJ'           field 'UPDCOLLRUN'
000660        id 'GRANULES'         field gran_list-sys
000670        id 'DELAY_ON_REJECT'  field  ' '
000680        id 'USTP'             field  '2'
000690        id 'COLLISION_UNAME'  field user
000700        id 'COLLISION_OBJECT' field obj
000710        id 'SYNCHRON'         field 'X'.
000720   if sy-subrc <> 0.
  >     raise already_running. -
/* error occurs at this line-----*\
000740   endif.
000750
000760
000770   if vbcontext = '*'.
000780     call 'ThVBCall' id 'OPCODE' field get_server_names
000790                     id 'VBCONTEXT' field vbcontext.
000800   endif.
plz help me to understand this error

Simple, you cannot run collective runs in parallel...
Note 436094 - Short dump ALREADY_RUNNING
If the collective run is running in parallel on different clients read
Note 595671 - Collective run processing in several clients
Regards
Juan

Similar Messages

  • Get a popup an exception runtime error has occurred in script unable to jit debug

    i get a pop up window, just-in-time debugging
    An exception 'runtime error' has occurred in script.
    However, no debuggers are registered that can debug this exception. Unable to JIT debug.

    '''I think I solved it myself yesterday, indirectly''' by deleting a Googleupdater.exe file dated 042511. It has been over 24 hours now and no sign of the 'Just-In-Time Debugger' pop-up. Whew...it was incessant.
    Not sure how I got the Googleupdater.exe file on my computer. I did download Microsoft Security Essentials to help find the JIT problem, but it failed to install properly and run. The next day I remembered it probably only runs on Internet Explorer (which we deleted in 2009) after testing out Firefox. I then also deleted Security Essentials.
    I also downloaded on April 25th the free version of MS Visual Basics because I read on eHow that you can adjust settings in the 'TOOL' menu to stop JIT Debugging pop-ups. However, the free version was 'MS Visual Studio Basic 2008 Express Edition - SP1' which did NOT provide access to JIT Debugging settings (so it was not a solution).
    I must say I switched Internet Security programs to AVAST! on TU | Apr26th and love it so far. Highly recommend looking into AVAST! ver 6.0 at CNET downloads - free. The anti-virus program is free, but everything else costs about $30US for a year. WORTH IT Love the options | settings | flexibility|user friendly windows.
    Trend Micro was then deleted. It had always blocked usage of our internal CD|DVD drive. To use the CD|DVD drive we had to shut off Trend Micro and then turn it back on again after we finished using the CD|DVD drive. NOT a preference - for sure. Jaykay

  • Error text missing in  raising exception (In ABAP mapping)

    Hi,
    iam using ABAP Mapping for 1 interface.
    Based on some condition  i am raising exception with error text. When i executed this in SXI_Mapping_test it's showing the Error text. But when i execute the interface directly error text is missing in the Error details.
    can any one figure out y its not coming..
    regards
    Kishore

    Hi,
    I think you need to write the error to mapping trace.
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/e18b1a0fc14f1faf884ae50cece51b/content.htm
    Regards
    Vijaya

  • Runtime error: Data_length_negative

    Hi Gurus,
    I have met one problem when i upload CSV file to BI, Please help me analysis it base below error message;
    tks;
    below is my steps
    1.create datasource;
    2.general info tab, input description
    3. extraction tab, input file name, value of data format is separated with separator (for example CSV),data separator is ,
    4.proposal tab, click "load example data",it can show correct data the same as CSV file;
    5.when i click fields tab, Popup show"field list no longer corresponds to dafault copy change? "Yes" or "NO" button"
    6.Click Yes, fields tab show correct data;
    7.click "read preview data " in preview Tab, show error infomation;
    ---Runtime error -description of exception;
    Runtime errors Data_length_negative
    Except. CX_XY_RANGE_OUT_OF_BOUNDS
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
          caught in
         procedure "_GET_DDIC_STRUCTURE" "(METHOD)", 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:
         In the executed program "CL_RSAR_PSA===================CP", the system
          attempted to access the field
         "ME->P_PSA_TECHNAME" using the length "-3".
         However, a partial field access with a negative length specification is
         not allowed.
    How to correct the error
         Use a positive length specification if a part of the field "ME->P_PSA_TECHNAME"
          is to be accessed.
    The current Abap program "CL_RSAR_PSA==============CP " has to be terminated bacause it has
    come across a statement that unfortunately can't be executed.
    Thanks

    Hi,
    check if version 12 of SAP Note 1064898 is implemented.
    Rgds,
    Colum

  • BW server raises exception SYSTEM_ERROR

    Hi,
    When trying to run a query in BEx, the BW Server is throwing an exception name SYSTEM_ERROR. These are the details
    <internal error> Recieving from the BW System failed. BW Server raised exception SYSTEM_ERROR
    Error Group: RFC_ERROR_SYSTEM_FAILURE
    Message: Time Limit exceeded
    I first referred to this thread Query Execution Error
    and this one
    Re: Error in Reprots: BW server raised exception:SYSTEM_FAILURE
    but I still have some doubts. First,
    this error is coming only for one specific report. Other reports are executing perfectly fine. If it was a problem with the SAPGUI or with the RFC connection itself, all reports on the BW system should have thrown the same error.
    Plus, the Message in my case is "Time Limit Exceeded", not Field Symbol not assigned, or RFC Destination on-existent.
    Is there any other note or do the above links also apply in this case?

    Restrict your query with some values and then try running the query. Generally, if the data volume is very high, the system shows this kind of error.
    You can also use a variable in your query and while running the query, select a smaller part og the data.
    Hope it will help you.
    Thanks.,.
    Shambhu

  • Runtime Errors Raise Exception in Solution Manager

    Hi Guru's,
    While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
    Error analysis
        A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
         exception
        condition "CNHT_ERROR_PARAMETER".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
    Could anyone suggest me on this issue.
    regards,
    Guna

    Hi Juan,
    As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
    Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
    regards,
    Guna

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" raised. 
    What happened? 
    The current ABAP/4 program encountered an unexpected 
    situation. 
    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. 
    Error analysis 
    A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    Since the exception was not intercepted by a superior 
    program, processing was terminated. 
    Short description of exception condition: 
    For detailed documentation of the exception condition, use 
    Transaction SE37 (Function Library). You can take the called 
    function module from the display of active calls. 
    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: 
    "RAISE_EXCEPTION" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    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. 
    System environment 
    SAP-Release 700 
    Application server... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "OCI_10201_SHARE (10.2.0.1.0) " 
    Patch level. 133 
    Patch text.. " " 
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." 
    SAP database version. 700 
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows 
    NT 6.0" 
    Memory consumption 
    Roll.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • How to raise exception in bor method without showing runtime error

    I want to raise custom exception in the bor method like below. However, it will show runtime error when executing codes below. Any knows how to raise custom exception in the bor method without runtime error?
    raise 9021.

    Hi Nick
    You need to define the exception 9021 for the method and then you use the macro EXIT_RETURN as below
    exit_return 9021 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    Regards
    Ravi

  • Runtime error raise_exception (Exception condition "NOT_EXIST" raised)

    Hi,
    I tried to ran a DTP to load data in a Standard DSO. Once I run the DTP ,instantly it is showing me short dump.I tried to ran it 2 times. Every time it shows me dump
    Runtime Errors         RAISE_EXCEPTION
    Short Text : Exception condition "NOT_EXIST" raised.
    Error Analysis : A RAISE statement in the program "SAPLRSSM" raised the exception
    condition "NOT_EXIST".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    Thanks in advance,
    Regards,
    Snehasish

    Hi,
    This kind of issues occur in BI7.0, the cause is not clear.
    You can once again delete the Data in the DSO using SE14(If Production system, make sure you contact your Basis team for this).
    You will have to use the table names(check the Delete data option & click on Activate and adjust databas)
    Thanks,

  • Runtime error Raise Exception Initial Product Catalog Replication

    Dear All,
    We are on CRM ISA MSA 5.0 SP8 & Trex 7 SP 30. Ours is a 3 system landscape. CRM Dev, Q, & P. Recently we added a new system in the landscape for Intergration Testing purpose. and its called as CRI which is a copy of the production Crm box.
    I did all the post installation activitiese and did all Connections (sm59, srmo) between Trex and CRM. After the connection was made, the RFC, SSR are all working fine.
    I did the settings in spro for the product catalog replication, created the ssr and then did a initial replication without document and it worked fine. I then did a replication with documents, I am getting a runtime error, RAISE_EXCEPTION. All the connections between the crm and trex box are working fine. everything is pinging, the FTP user has all the access on the IMS_DOCS_A5C folder.
    Can someone please let me know what the issue could be?
    Awaiting a postive response.
    Thanks in advance.
    Warm Regards,
    Rajeet Mathur

    Hi Rajeet,
    The intitial replication  transports product catalog data (for example, product items or text) to the index server. You can replicate all or individual product catalog variants. The replicated product catalog contents are transferred from the index server to the Web server. The product catalog contents are then available in the E-Commerce application. Multimedia objects are transferred from the product catalog to the Knowledge Provider Content Server and are subsequently published on the Web server.
    As you said that after you put in the documents the repliaction gives a runitme error, I beleive the replication to the contect server is giving problems.
    1. Have you created templates for folder and assigned them to the catalog types for the attachement of documents.
    2. While replication are you specifying the Publishing computer ID  with the checkbox transfer Document content ticked.
    Check in these details.
    Regards,
    Shalini Chauhan

  • 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

  • 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.

  • Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB

    Hi,
    Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
    Advance thanks.
    Regards,
    Balaji Viswanath.
    Code:
      SELECT bukrs
             lifnr
             augdt
             augbl
             zuonr
             gjahr
             belnr
             buzei
             waers
             dmbtr
             wrbtr
             zlsch
             shkzg
             blart
             gsber
             sgtxt
      INTO TABLE t_bsak_tmp
      FROM bsak CLIENT SPECIFIED
      WHERE mandt = sy-mandt AND
            lifnr IN r_lifnr AND
            bukrs IN s_bukrs AND
            augdt IN s_augdt AND
            blart IN s_blart.
      IF sy-subrc <> 0.
      No data found for selection criteria
        MESSAGE i018.
        LEAVE LIST-PROCESSING.
      ENDIF.
    Dump:
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     14.11.2005 at 14:35:22
    Error in the module RSQL accessing the database interface.
    What happened?
    Error in ABAP application program.
    The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
    because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that 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', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "GET_CLRD_VEN_DATA" "(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:
    The SQL statement generated from the SAP Open SQL Statement violates a
    restriction imposed by the database system used in R/3.
    Possible errors:
    o The maximum size of an SQL statement has been exceeded.
    o The statement contains too many input variables.
    o The space needed for the input data exceeds the available memory.
    o ...
    You can usually find details in the system log (SM21) and in the
    developer trace of the work process (ST11).
    If an error occurs the developer trace often informs you about the
    current restrictions.
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "GET_CLRD_VEN_DATA"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    The SAP Open SQL statement must be divided into several smaller units.
    If the problem occurred due to the use of an excessively large table
    in an IN itab construct, you can use the addition FOR ALL ENTRIES
    instead.
    When you use this addition, the statement is split into smaller units
    according to the restrictions of the database system used.
    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_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
    "/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    "GET_CLRD_VEN_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "ztm1003"
    Network address.......... "145.26.160.103"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C004DC4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 6
    Short dump setting....... "full"
    Database server.......... "ztm1003"
    Database type............ "ORACLE"
    Database name............ "A94"
    Database owner........... "SAPR3K"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 7 2005 20:44:35"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "85"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
    10.1.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    User, transaction...
    Client.............. 110
    User................ "INBVI0"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    in "GET_CLRD_VEN_DATA".
    The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    The termination occurred in line 503 of the source code of the (Include)
    program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
    the editor 5030).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
    code starts in line 501
    of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    Source code extract
    004730   &----
    004740   *       get country names from t005t
    004750   ----
    004760   FORM get_country_names.
    004770
    004780     t_lfa1_land[] = t_lfa1[].
    004790     SORT t_lfa1_land BY land1.
    004800     DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
    004810
    004820     IF NOT t_lfa1_land[] IS INITIAL.
    004830       SELECT land1
    004840              landx
    004850       INTO TABLE t_t005t
    004860       FROM t005t
    004870       FOR ALL ENTRIES IN t_lfa1_land
    004880       WHERE spras = sy-langu AND
    004890             land1 = t_lfa1_land-land1.
    004900       REFRESH t_lfa1_land.
    004910       SORT t_t005t BY land1.
    004920     ELSE.
    004930       MESSAGE i014 WITH 'No vendor data fetched'(001).
    004940     ENDIF.
    004950   ENDFORM.                    " get_country_names
    004960   &----
    004970   *&      Form  get_clrd_ven_data
    004980   &----
    004990   *       Cleared vendor data
    005000   ----
    005010   FORM get_clrd_ven_data .
    005020
    >     SELECT bukrs
    005040            lifnr
    005050            augdt
    005060            augbl
    005070            zuonr
    005080            gjahr
    005090            belnr
    005100            buzei
    005110            waers
    005120            dmbtr
    005130            wrbtr
    005140            zlsch
    005150            shkzg
    005160            blart
    005170            gsber
    005180            sgtxt
    005190     INTO TABLE t_bsak_tmp
    005200     FROM bsak CLIENT SPECIFIED
    005210   * the order of the fields are as in the secondary Index.
    005220     WHERE mandt = sy-mandt AND
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 59
    SY-FDPOS 0                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY
    SY-UCOMM
    SY-TITLE Vendor Payment  Details for IRD
    SY-MSGTY I                             SY-MSGID SF
    SY-MSGNO 616                           SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
    SY-MSGV2 RE                            SY-MSGV3 EN
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
         2 FORM         GET_CLRD_VEN_DATA
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             503
         1 EVENT        START-OF-SELECTION
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             135

    Hi Balaji,
    Here is what the dump said and my answers are right below them.
    <i>Possible errors:</i>
    o The maximum size of an SQL statement has been exceeded.</i>
    This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
    <i>o The statement contains too many input variables.</i>
    Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
    Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
    Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
    DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
    Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
    <i>o The space needed for the input data exceeds the available memory.</i>
    If the above changes are made and the problem is still there, then this is the next thing to look at.
    Srinivas

  • In SCM 5.0 Runtime Errors: DBIF_DSQL2_SQL_ERROR Exception: CX_SY_NATIVE_SQ

    Hi,
    I am getting following shortdump in my SCM 5.0 system with LiveCache 7.6.03 on AIX 5.3.
    Please help me.
    Runtime Errors         DBIF_DSQL2_SQL_ERROR
    Exception              CX_SY_NATIVE_SQL_ERROR
    Date and Time          01.07.2008 09:20:09
    Short text
    An SQL error occurred when executing Native SQL.
    What happened?
    The error "-4016" occurred in the current database connection "LCA".
    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.
    How to correct the error
    Database error text........: "POS(1) Unknown procedure
    name:SIM_SIMSESSION_GET_ACTIVE"
    Database error code........: "-4016"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE""
    Internal call code.........: "[DBDS/NEW DSQL]"
    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_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU23"
    "/SAPAPO/OM_SIMSESSION_GET_ALL"
    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
    "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", 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... "dewall43"
    Network address...... "10.40.16.43"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "00C912FC4C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 14
    Shortdump setting.... "full"
    Database server... "dewall43"
    Database type..... "ORACLE"
    Database name..... "APO"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jan 23 2008 21:25:00"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 144
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 1117168
    EM...... 0
    Heap.... 0
    Page.... 24576
    MM Used. 720672
    MM Free. 376056
    User and Transaction
    Client.............. 100
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "48692ABF23D6012AE10080000A28102B"
    Program............. "/SAPAPO/SAPLOM_CORE"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "/SAPAPO/SAPLOM_CORE" - in
    "/SAPAPO/OM_SIMSESSION_GET_ALL".
    The main program was "/SAPAPO/OM_DELETE_OLD_SIMS ".
    In the source code you have the termination point in line 39
    of the (Include) program "/SAPAPO/LOM_COREU23".
    The program "/SAPAPO/SAPLOM_CORE" was started as a background job.
    Job Name....... "/SAPAPO/OM_DELETE_OLD_SIMSESS"
    Job Initiator.. "DDIC"
    Job Number..... 08200801
    The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
    in
    procedure "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", but it was neither
    handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/SAPAPO/SAPLOM_CORE "; its source code begins in
    line
    1 of the (Include program "/SAPAPO/LOM_COREU23 ".
    Source Code Extract
    Line
    SourceCde
    9
    *"     REFERENCE(ET_ACTIVE_SIMSESSION) TYPE  /SAPAPO/OM_SIMSESSION_TAB
    10
    *"     REFERENCE(ET_RC) TYPE  /SAPAPO/OM_LC_RC_TAB
    11
    *"  EXCEPTIONS
    12
    *"      LC_CONNECT_FAILED
    13
    *"      LC_COM_ERROR
    14
    *"      LC_APPL_ERROR
    15
    16
    17
    data_def.
    18
    create_gen_com_params_default.
    19
    CLEAR ls_gen_com_params-client.
    20
    21
    Verbindung zum liveCache aufbauen
    22
    start_function 'OM_SIMSESSION_GET_ALL'.                   "#EC *
    23
    check_server.
    24
    connect_to_livecache.
    25
    IF et_simsession IS REQUESTED.
    26
    COM-Routine zum Auslesen aller trans. Sim.
    27
    EXEC SQL.
    28
    EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ALL" (
    29
    IN  :LS_GEN_COM_PARAMS,
    30
    OUT :LV_RC,
    31
    OUT :ET_SIMSESSION)
    32
    ENDEXEC.
    33
    Returncodes pruefen und evtl. Exception raisen
    34
    lv_subrc_sav = sy-subrc.
    35
    ENDIF.
    36
    IF et_active_simsession IS REQUESTED.
    37
    COM-Routine zum Auslesen aller aktiven trans. Sim.
    38
    EXEC SQL.
    >>>>>
    EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE" (
    40
    IN  :LS_GEN_COM_PARAMS,
    41
    OUT :LV_RC,
    42
    OUT :ET_ACTIVE_SIMSESSION)
    43
    ENDEXEC.
    44
    Returncodes pruefen und evtl. Exception raisen
    45
    lv_subrc_sav = sy-subrc.
    46
    ENDIF.
    47
    48
    end_performance_measure.
    49
    end_function_no_main om_simsession_get_all.
    50
    check_returncodes.
    51
    if iv_get_testguids = gc_false.
    52
    delete ET_ACTIVE_SIMSESSION where table_line cs '~'.
    53
    delete ET_SIMSESSION        where table_line cs '~'.
    54
    endif.
    55
    ENDFUNCTION.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    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
    Periodic Deletion of Hanging Simulation Versions
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080701
    SY-UZEIT
    092008
    SY-XPROG
    RSDBRUNT
    SY-XFORM
    %_INIT_PBO_FIRST
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    3 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU23                    39
    /SAPAPO/OM_SIMSESSION_GET_ALL
    2 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU12                    52
    /SAPAPO/OM_SIMSESSION_SELECT
    1 EVENT        /SAPAPO/OM_DELETE_OLD_SIMS          /SAPAPO/OM_DELETE_OLD_SIMS             67
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       3 Ty.          FUNCTION
    Name  /SAPAPO/OM_SIMSESSION_GET_ALL
    IV_GET_TESTGUIDS
    X
    0
    0
    5
    8
    ET_ACTIVE_SIMSESSION
    Table IT_9[0x44]
    \FUNCTION=/SAPAPO/OM_SIMSESSION_SELECT\DATA=LT_SIMSESSION
    Table reference: 2
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 0000000200000009000000000000002CFFFFFFFF
    TABH+ 40(16) = 04000021000026C00010249401800000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 2     (0x00000002)
    label        = 9     (0x00000009)
    fill         = 0     (0x00000000)
    leng         = 44    (0x0000002C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000192
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    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         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 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
    ET_RC
    Table[initial]
    ET_SIMSESSION
    Table[initial]
    OM_LC_NAME
    LCA
    000000000000000000000000000000
    000000000000000000000000000000
    444222222222222222222222222222
    C31000000000000000000000000000
    GC_OM_SYSUBRC
    -16842752
    F
    E
    SY-SUBRC
    0
    0000
    0000
    %_SPACE
    0
    0
    2
    0
    %_VIASELSCR
    0
    4
    OM_LC_APPL_NAME
    000000000000000000000000000000
    000000000000000000000000000000
    222222222222222222222222222222
    000000000000000000000000000000
    SPACE
    0
    0
    2
    0
    LS_GEN_COM_PARAMS
    DDIC                                 # /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222444422222222222222222222222222222222202254545424454444545444554452222222
    0000000000000000000000449300000000000000000000000000000000000F31010FFFDF45C545FFC4F39D30000000
    LV_RC
    00
    00
    00
    00
    GC_OM_SPP_FORECAST_EXT
    K
    4
    B
    GC_IMMEDIATE_TRANSFER
    65537
    0
    0
    GC_RESOURCE_MULTI
    16909060
    0
    1
    GV_SIMSESSION_TYPE
    0
    0
    2
    0
    OM_MEASURE_PERFORMANCE
    0
    0
    2
    0
    GC_OM_OBJECT_OUTPUT_NODE
    454827294
    1
    B
    OM_AS_KEY
    000000000000000000000000000000
    000000000000000000000000000000
    222222222222222222222222222222
    000000000000000000000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    No.       2 Ty.          FUNCTION
    Name  /SAPAPO/OM_SIMSESSION_SELECT
    IV_MIN_AGE_IN_HOURS
    1
    0000
    0001
    IV_SAVED_INCLUSIVE
    0
    0
    2
    0
    ET_OMS_VERSION
    Table[initial]
    ET_SIMSESSION_DELTA
    Table[initial]
    SCREEN
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GC_OM_RPM_PORD_DEL
    2004
    000D
    0074
    GC_OM_OBJECT_UNKNOWN
    66051
    0
    0
    GC_OM_OBJECT_ORDER
    16909060
    0
    1
    GS_OMS_VERSION
    00000000                      ########
    000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000C
    222222222222222222222233333333222222222222222222222200000000
    000000000000000000000000000000000000000000000000000000000000
    GC_MINTIME
    09011000
    1700002C
    GT_OMS_VERSION
    Table[initial]
    GC_APPLICATION_BLRG
    235868177
    0
    E
    GC_OM_OBJECT_MODE
    50595078
    0
    3
    GC_TRUE
    X
    0
    0
    5
    8
    RSJOBINFO
    00000000000000                                  ##
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GC_OM_OBJECT_RESOURCE
    67438087
    0
    4
    LT_SIMSESSION
    Table IT_9[0x44]
    GC_APPLICATION_CTPE
    168496141
    0
    A
    SY-REPID
    /SAPAPO/SAPLOM_CORE
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254544454454222222222222222222222
    F31010FF310CFDF3F25000000000000000000000
    GC_APPLICATION_MATP
    185339150
    0
    B
    SYST-REPID
    /SAPAPO/SAPLOM_CORE
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254544454454222222222222222222222
    F31010FF310CFDF3F25000000000000000000000
    GC_ATP_UPD_RPM
    R
    0
    0
    5
    2
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    VARI
    ###00000000000000      ############
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454244544445454445544522222222222222
    F31010FFFDF45C545FFC4F39D300000000000000
    GC_OM_OBJECT_RPM_GENERIC
    791687475
    2
    F
    SY-SUBRC
    0
    0000
    0000
    %_VIASELSCR
    0
    4
    SY-REPID
    /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454244544445454445544522222222222222
    F31010FFFDF45C545FFC4F39D300000000000000
    SY-MSGID
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    GC_TRANSPORT
    y
    0
    0
    7
    9
    SPACE
    0
    0
    2
    0
    SY-MSGNO
    000
    000
    000
    333
    000
    SY-MSGV1
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    GC_ITRUE
    16777623
    0
    1
    GC_FALSE
    0
    0
    2
    0
    SYST
    ###############################################################################T########X ####
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000E000200
    0000000000000000000000000000000000000006000000000000000000000000000000000000010500000001520000
    000001010000010000000000010001000000000A00000000000000000000000000000000000006040000000080000C
    GC_IFALSE
    104192
    0
    0
    GT_OMS_VERSION
    Table[initial]
    GC_MINTIME
    09011000
    1700002C
    GT_SIMS_DELTA
    Table[initial]
    SY-XFORM
    %_INIT_PBO_FIRST
    000000000000000000000000000000
    000000000000000000000000000000
    254445554454455522222222222222
    5F9E94F02FF6923400000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    SCREEN
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Internal notes
    The termination was triggered in function "DsqlErrorHandler"
    of the SAP kernel, in line 2062 of the module
    "//bas/700_REL/src/krn/runt/abexsql.c#2".
    The internal operation just processed is "DSQL".
    Internal mode was started at 20080701092008.
    Internal call code.........: "[DBDS/NEW DSQL]"
    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     = unlimited
    => Core limit      = 4294965248
    => File size limit = unlimited
    => Heap address  = 0x0x1152ede20
    => Stack address = 0xfffffffffff84a0
    => Stack low     =  0xfffffffffff84a0
    => Stack high    =  0xffffffffffff7a0
    => Stack Trace:
         AixStack() at 0x1000c7d94
         CTrcStack2() at 0x1000c7e8c
         rabax_CStackSave__Fv() at 0x1000b2d70
         ab_rabax() at 0x1000af728
         ab_dbdserr__FiPCUsT1T2P9DS_HEADERT2T1Pv() at 0x10057efbc
         DsqlErrorHandler__Fi() at 0x10135b8e8
         ExecuteCall__Fv() at 0x10135b454
         ab_jdsql__Fv() at 0x101356b40
         ab_extri__Fv() at 0x10040d93c
         ab_xevent__FPCUs() at 0x100a9d170
         ab_trigg__Fv() at 0x100a9ce5c
         ab_run() at 0x1014bee48
         N_ab_run() at 0x100d5bca8
         dynpmcal() at 0x100d5aa74
         dynppai0() at 0x100d58a08
         dynprctl() at 0x100d6047c
         dynpen00() at 0x100d52364
         Thdynpen00() at 0x1000e2410
         TskhLoop() at 0x1000e4254
         ThStart() at 0x1000fe324
         DpMain() at 0x10156c770
         nlsui_main() at 0x101a99998
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /SAPAPO/OM_DELETE_OLD_SIMS
    0
    28.09.2006
    17:13:54
    115712
    E
    1
    Prg
    SAPMSSY0
    1
    07.01.2008
    17:16:23
    92160
    E
    2
    Prg
    SAPMSSYD
    1
    27.09.2006
    18:38:20
    21504
    E
    3
    Prg
    SAPFSYSCALLS
    1
    03.12.2004
    17:45:45
    8192
    E
    4
    Prg
    RSDBRUNT
    0
    07.01.2008
    17:27:13
    254976
    E
    5
    Typ
    RSSCR
    0
    12.10.1999
    15:50:05
    5120
    6
    Prg
    RSDBSPBL
    0
    22.02.2005
    08:58:45
    72704
    E
    7
    Prg
    SAPDB__S
    0
    03.12.2004
    17:45:45
    19456
    E
    8
    Prg
    RSDBSPMC
    0
    27.09.2006
    18:23:16
    79872
    E
    9
    Typ
    DDSHDESCR
    0
    28.11.1997
    16:26:30
    4096
    10
    Typ
    SPPARAMS
    0
    07.03.1997
    14:48:48
    2048
    11
    Prg
    SAPLSABE
    11
    03.12.2004
    17:45:46
    13312
    E
    12
    Prg
    SAPLSECU
    12
    07.01.2008
    17:09:46
    87040
    E
    13
    Typ
    RSSUBINFO
    0
    25.02.2000
    15:47:23
    3072
    14
    Prg
    SAPLSTUP
    14
    07.01.2008
    17:08:20
    74752
    E
    15
    Prg
    SAPLCNDP
    15
    13.12.2007
    16:41:21
    195584
    E
    16
    Prg
    SAPLSCNT
    16
    22.02.2005
    08:58:56
    30720
    E
    17
    Prg
    SAPSHDTV
    16
    31.01.2005
    15:41:11
    33792
    E
    18
    Prg
    SAPFGUICNTL
    1
    22.02.2005
    08:58:14
    24576
    E
    19
    Prg
    SAPLOLEA
    19
    12.12.2007
    14:16:36
    96256
    E
    20
    Prg
    SAPLSGUI
    20
    07.01.2008
    17:16:23
    84992
    E
    21
    Prg
    SAPLSTTM
    21
    28.07.2005
    11:12:25
    69632
    E
    22
    Prg
    SAPLSBDC
    22
    07.01.2008
    17:09:02
    44032
    E
    23
    Prg
    SAPLSFES
    23
    07.01.2008
    17:27:14
    260096
    E
    24
    Prg
    SAPLTHFB
    24
    07.01.2008
    17:16:23
    394240
    E
    25
    Typ
    WPINFO
    0
    08.02.1999
    14:18:32
    6144
    26
    Prg
    SAPLURFC
    26
    07.01.2008
    17:13:39
    22528
    E
    27
    Prg
    SAPLSPLUGIN
    27
    03.12.2004
    17:45:46
    8192
    E
    28
    Typ
    SWCBCONT
    0
    07.10.1997
    12:13:50
    3072
    29
    Typ
    OLE_VERBS
    0
    09.02.1995
    13:23:37
    2048
    30
    Typ
    OLE_PA
    0
    13.01.1995
    11:06:59
    2048
    31
    Prg
    /1BCDWBEN/SAPL/SAPAPO/EN0001
    31
    08.06.2001
    20:33:24
    233472
    E
    32
    Prg
    SAPLSENA
    32
    12.12.2007
    14:18:37
    33792
    E
    33
    Prg
    /SAPAPO/SAPLOM_CORE
    33
    28.07.2005
    16:02:32
    502784
    E
    34
    Prg
    SAPLSAL2
    34
    07.01.2008
    17:15:35
    81920
    E
    35
    Typ
    /SAPAPO/OM_OMS_VERSIONS_STR
    0
    16.02.2006
    18:01:55
    3072
    36
    Prg
    CL_ABAP_CHAR_UTILITIES========CP
    36
    28.07.2005
    11:12:24
    13312
    E
    37
    Prg
    CX_SY_NATIVE_SQL_ERROR========CP
    37
    12.12.2007
    12:39:14
    13312
    E
    38
    Typ
    SCX_SRCPOS
    0
    08.07.2004
    09:59:00
    2048
    39
    Prg
    CX_SY_SQL_ERROR===============CP
    39
    28.07.2005
    11:12:24
    10240
    E
    40
    Prg
    CX_DYNAMIC_CHECK==============CP
    40
    28.07.2005
    11:12:24
    10240
    E
    41
    Prg
    CX_ROOT=======================CP
    41
    12.12.2007
    17:18:15
    11264
    E
    42
    Prg
    CX_NO_CHECK===================CP
    42
    28.07.2005
    11:12:24
    10240
    E
    43
    Prg
    CX_SY_NO_HANDLER==============CP
    43
    28.07.2005
    11:12:24
    10240
    E
    44
    Prg
    %_CSYDES
    0
    22.02.2005
    08:58:46
    8192
    E
    45
    Prg
    %_CSYDB0
    0
    22.02.2005
    08:58:45
    36864
    E
    46
    Typ
    RSVAMEMKEY
    0
    16.12.1996
    19:31:50
    2048
    47
    Prg
    %_CRSDS
    0
    22.02.2005
    08:58:21
    10240
    E
    48
    Prg
    %_CSLIS
    12
    17.02.2006
    08:58:39
    89088
    E
    49
    Typ
    DTC_S_LAYO
    0
    08.06.2001
    15:59:56
    6144
    50
    Typ
    CAT_SVARS
    0
    19.05.2004
    16:00:08
    3072
    51
    Typ
    SYST
    0
    03.12.2004
    17:45:35
    31744
    52
    Typ
    RSJOBINFO
    0
    09.02.1995
    13:25:17
    3072
    53
    Typ
    VARI
    0
    16.12.1996
    19:38:11
    6144
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  /SAPAPO/OM_DELETE_OLD_SIMS
    SYST                                     03.12.2004 17:45:35   00004612
    \0\0\0\0\0\x0001\0\x0001\0\0\0\0\0\x0001\0\0\0\0\0\0\0\0\0
    VARI                                       .  .       :  :     00003052
    Program  /SAPAPO/SAPLOM_CORE
    RSJOBINFO                                  .  .       :  :     00000164

    As per note 1619720, drop following two tables and then validate by running t-code lca03.
    drop table APPSYSNAME
    drop table APPSYSPARAM
    dbmcli -d LCSID -n hostname -u superdba,sdbapassword -uSQL SAPSID,password
    dbmcli on hostname : SID>sql_execute drop table APPSYSPARAM
    OK

  • Runtime Errors UNCAUGHT_EXCEPTION and Exception CX_RSR_COB_PRO_NOT_FOUND

    Hi ,
    When i tried to load data into my standard cube the following short dump error occure.
    The data was updated to PSA but while updating to further data target (my standard cube) the following error occured:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_COB_PRO_NOT_FOUND
    Date and Time          2010.12.13 10:20:48
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_RSR_COB_PRO_NOT_FOUND' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program
          'CL_RSR========================CP' has to be
         terminated.
    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.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_COB_PRO_NOT_FOUND', was not
         caught and
        therefore caused a runtime error.
        The reason for the exception is:
        0REQUEST is not a valid characteristic for InfoProvider

    Please check the infoobject 0REQUEST, whether it is in active state, if not acivate it.
    Check for 0REQUEST Object in Infocube level at characteristics tab, if it is not available try to add this characteristic to cube.
    if 0REQUEST is not available, install it from the content and include it in the cube.
    rgds, Ghuru

Maybe you are looking for

  • How to Block a Quote on Credit check and prevent suseqquent functions

    Hi, The client wants to prevent the Quotations which are blocked due to credit check to be turned in to sales order. We are maintaining credit group 40 , assigned it to quote, and maintained records in Fd32 and ova8. The item categories have been che

  • Can not create XML file from MS Access 2003

    Hi, I am getting error as "Error loading in DLL" when I use msaccess_exporter to create XML file for migrations usind Access 2003 DB. Does anyone know about this? If yes, could you please let me know how to resolve it? Thanks, Kartik

  • File Content Conversion-xml.keyfieldName missing

    I have datatypes like this Sender_DT                Material (1...n)                                                   MATNR           MTART                               Plant (1...n)                                         WERKS                    

  • Bug in cursor behaviour with duplicates

    Dear Oracle guys and girls, first of all: it sucks that i HAVE to provide business information (company name, address, even phone number) even if i just want to participate in this forum for private reasons. I even have to "unsubscribe" to the newsle

  • I have a problem with my ipod touch it does not light at all, what should I do?

    I have a problem with my ipod touch it does not light at all, what should I do?