ABAP Dump when running S_ALR_87100205 (RFHABU00N)

Hi,
We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
has any one else faced this issue in the past and if so how was it resolved.
We are currently on SAP ECC 6.04.
Thanks,
Nitin

Hi,
What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
1883338 - RFHABU00N Long runtimes and termination
1965855 - RFHABU00/RFHABU00N: General Ledger View
1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
1939154 - RFHABU00N: Documents from non-leading ledgers ignored
Regards,
Eli

Similar Messages

  • ABAP dump when running an ALV report in a portal

    Hi,
      I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
      When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
      Please let me know if anybody has faced such issues.
    I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
    Thanks,
    Best regards,
    Ajith
    The ST22 error log is as follows:
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    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
    Short text of error message:
    Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
    Technical information about the message:
    Diagnosis
         You tried to send a data record to the front-end that contains
         84.550.400 bytes. However, the data volume is restricted to
         52.428.800 bytes.
    System Response
         The running application program was terminated with a runtime
         error.
    Procedure
         Restrict the data selection if possible or contact your system
         administrator.
    Procedure for System Administration
         You can set the maximum size of these data volumes using the kernel
         parameter 'abap/alvgrid/size_nodod_mb'  (in megabytes).
    Message classe...... "S>"
    Number.............. 890
    Variable 1.......... "84.550.400"
    Variable 2.......... "52.428.800"
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" C
    "SAPLAWRT" or "LAWRTU22"
    "ITS_CHECK_ALV_DATA_SIZE"
    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.
    Information on where terminated
    The termination occurred in the ABAP program "SAPLAWRT" in
    "ITS_CHECK_ALV_DATA_SIZE".
    The main program was "Z_BW_RECON_INV_RPT ".
    The termination occurred in line 25 of the source code of the (Include)
    program "LAWRTU22"
    of the source code of program "LAWRTU22" (when calling the editor 250).
    Source code extract
    000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
    000020   *"
    000030   ""Lokale Schnittstelle:
    000040   *"  IMPORTING
    000050   *"     REFERENCE(DATA_TABLE) TYPE  TABLE
    000060   *"
    000070
    000080     data n type i.
    000090     data currsize type i.
    000100     statics maxsize type i.
    000110     data par_value(56).
    000120     if maxsize is initial.
    000130       sy-subrc = 0.
    000140       CALL 'C_SAPGPARAM'  ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
    000150                           id 'VALUE' field par_value.
    000160       if sy-subrc ne 0.
    000170         maxsize = 52428800.       " Default 50 MB
    000180       else.
    000190         maxsize = 1048576 * par_value.
    000200       endif.
    000210     endif.
    000220     describe table data_table lines n.
    000230     currsize = sy-tfill * sy-tleng.
    000240     if currsize gt maxsize.
         >       message x890(s>) with currsize maxsize.
    000260     endif.
    000270   ENDFUNCTION.

    HI,
    This is a Memory problem.
    System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
    The data of your report is coming around 83 MB.
    Restrict your selection criteria of the Object and run the same report and see. it will work.
    Regards,
    Anji

  • ABAP dump while running the tcode MIGO

    Hi All,
    I am getting the abap dump while running the tcode MIGO when I searched I got two relevant sap notes but our functional team said that its not applicable in our case.
    Please find the details of ST22 analysis-:
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          17.04.2009 13:18:45
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
        Short text of error message:
        No RFC destination is defined for SAP Global Trade Services
        Long text of error message:
        Technical information about the message:
        Message class....... "/SAPSLL/PLUGINR3"
        Number.............. 002
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        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:
        "MESSAGE_TYPE_X" " "
        "SAPLMBWL" or "LMBWLU21"
        "MB_POST_GOODS_MOVEMENT"
    SAP Notes i have reffered 1098491, 1041122
    Currently we are running on SAP_APPL     600     0007     SAPKH60007     
    Regards,
    Prashant

    Hi Rohit,
    This particular note is valid for
    Support
    Packages Release Package
    Name
    PI 2004_1_46B SAPKIPZI38
    PI 2004_1_46C SAPKIPZI48
    PI 2004_1_470 SAPKIPZI58
    PI 2004_1_500 SAPKIPZI68
    Our system is running on PI_BASIS     2006_1_700     0005     SAPKIPYM05
    Pls suggest.
    Regards,
    Prashant

  • Program giving dump when run in background

    Hi All,
    I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
    The report works perfectly in foreground. But when I execute in background I am getting dump.
    Dump details are given below.
    ShrtText
        Unable to fulfil request for 134217728 bytes of memory space.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    What can you do?
        Try to find out (e.g. by targetted data selection) whether the
        transaction will run with less main memory.
        If there is a temporary bottleneck, execute the transaction again
        If the error persists, ask your system administrator to check the
        following profile parameters:
        o  ztta/roll_area            (1.000.000 - 15.000.000)
               Classic roll area per user and internal mode
               usual amount of roll area per user and internal mode
        o  ztta/roll_extension       (10.000.000 - 500.000.000)
               Amount of memory per user in extended memory (EM)
        o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
               Amount of memory (malloc) for all users of an application
               server. If several background processes are running on
               one server, temporary bottlenecks may occur.
               Of course, the amount of memory (in bytes) must also be
               available on the machine (main memory or file system swap).
               Caution:
               The operating system must be set up so that there is also
               enough memory for each process. Usually, the maximum address
               space is too small.
               Ask your hardware manufacturer or your competence center
               about this.
               In this case, consult your hardware vendor
        abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each dialog process.
        Parameters for background processes:
        abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each background process.
        Other memory-relevant parameters are:
        em/initial_size_MB:         (35-1200)
               Extended memory area from which all users of an
               application server can satisfy their memory requirement.
        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
        More main memory area was requested.
        However, all the available space has been used up.
        Possible reasons:
        - Many (large) internal tables.
        - Many (large) programs active.
        - Deep nesting of subroutines with a lot of local data.
    Can you please help on this ?

    Hi,
    Check you code properly.
    The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
    Check teh same.
    regards,
    Ankur Parab

  • ABAP Dump when calling Function Module Starting New Task

    Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
    I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
    METHOD start.
        CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
          STARTING NEW TASK me->id
          CALLING me->finish ON END OF TASK.
      ENDMETHOD.                    "start
    However I get the following ABAP dump:
    Short text
        Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
    The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
    The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
    <Garbled code removed>
    Moderator Message: Please post relevant portions of the code only.
    Edited by: Suhas Saha on Jul 17, 2011 1:17 PM

    Well, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
    The complete function group can be downloaded here (slinkee file):
    https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
    The complete program can be downloaded here (slinkee file):
    https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
    The complete ST22 dump can be found here:
    https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
    Basically I ST22 gives me the following:
    Runtime Errors         RPERF_ILLEGAL_STATEMENT
    Date and Time          17.07.2011 05:29:54
    |Short text                                                                                |
    |    Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"                 |
    |What happened?                                                                                |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                |
    |    The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated                     |
    |     because it has                                                                               |
    |    come across a statement that unfortunately cannot be executed.                                |
    And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
    |Error analysis                                                                                |
    |    There is probably an error in the program                                                     |
    |    "Z_ZZB1_CLOSE_PERIOD_TEST2".                                                                  |
    |    The program was probably called in a conversion exit                                          |
    |    or in a field exit. These are implemented by                                                  |
    |    function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or                                 |
    |    USER_EXIT_xxxxx_INPUT.                                                                        |
    |    Conversion exits are triggered during screen field transports or                              |
    |    WRITE statements, field exits during field transports from the                                |
    |    screen to the ABAP/4 program.                                                                 |
    |    In this connection, the following ABAP/4 statements are not allowed:                          |
    |                                                                                |
    I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working.

  • Hi Getting Abap dump when in RRP3 when deactivating the DP Planning area

    Hi
    We are using the Consumption group by this releasing Forecast to SNP at Customer level also along with product and location level,i am doing in dev only,
    Issue :I have deactivated the DP Planning area(because of some modification) then activated/Initialized the DP Planning area, After that when I see  in the RRP3 for the product  it is getting Abap dump,CVCs now it is available also, Please let me know how to correct it

    KKK,
    I doubt that the event of deactivating/reactivating the DP PA is the cause of your ABAP dumps in //RRP3.  More likely the problem is related to a LC inconsistency, or a userexit.
    Run all of your LC consistency checks, they are easy to do and quick to run.  And, like any other dump, read the messages in the dumps to find out what went wrong.
    Best Regards,
    DB49

  • ABAP Dump when using Shift Related Confirmations in CO11N

    Dear SAP Gurus,
    We have activated business function LOG_PP_SRN_CONF for doing shift
    related confirmations using T Code CO11N.
    On entering the production order and operation number in CO11N, the
    system proposes the actual data. Then we select the shift number.
    If we try to change the selected shift again, the system gives an ABAP
    dump - "OBJECTS_OBJREF_NOT_ASSIGNED" and exits the program.
    Please suggest some SAP Note or other solution for the problem.
    Thanks!
    With Regards,
    Nitin

    Dear Prasobh,
    Thanks for the quick reply.
    I have checked the OSS Note - 1359966 as mentioned by you.
    However, there are 2 things which make me feel that the note is not relevant to my scenario -
    1. The note says that the confirmation profile for CO11N includes the detail area "0240-Quantities: Subdivided Quantities". I'm not using this detail area in my confirmation profile. Instead, I'm using the detail area "0200-Quantities: yield/scrap/rework/reason".
    2. System may issue termination message COCF 000 when single-screen entry for the confirmation (CO11N) is called by another application such as the order information system (COOIS). However, I'm getting this dump when i run the T Code CO11N directly. Further, I don't get the termination message at all.
    Please suggest.
    With Regards,
    Nitin

  • Short dump when running EWA report

    Dear Expert,
    I got error dump when generating EWA report: OBJECTS_OBJREF_NOT_ASSIGNED_NO
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_GUI_GP=====================CP" had to be
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
         caught in
        procedure "IF_GRAPHIC_PROXY~EXPORT" "(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:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component.
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    Missing RAISING Clause in Interface
        Program                                 CL_GUI_GP=====================CP
        Include                                 CL_GUI_GP=====================CM017
        Row                                     1
        Module type                             (METHOD)
        Module Name                             IF_GRAPHIC_PROXY~EXPORT
    Trigger Location of Exception
        Program                                 CL_GUI_GP=====================CP
        Include                                 CL_GUI_GP=====================CM017
        Row                                     19
        Module type                             (METHOD)
        Module Name                             IF_GRAPHIC_PROXY~EXPORT
    Please advise asap since we need the report immediately.
    Thank you in advance,
    Rudi

    Hi,
    [This note|https://websmp109.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=944541&_NLANG=E] will solve your problem.
    feel free to revert back.
    --Ragu

  • ABAP Dump when executing DTP

    Dear gurus:
           I just faced an annoying problem when executing DTP in t-code RSA1. It appears an  ABAP dump here. The ABAP dump is briefly shown below. And I found that it seems to be an authorization problem, because when I use a new account which has SAP_ALL authorization, then it works. So it may lack of some authorizations, but it's hard to figure it out. T-code su53 cannot check it properly. Need your help and thanks a lot.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          2007.06.20 11:17:30
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
         Short text of error message:
         Invalid program status
         Long text of error message:
         Technical information about the message:
         Message class....... "RSBK"
         Number.............. 299
         Variable 1.......... " "
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "

    Hai Wei,
    This dump is due missing of OCX files while installing SAP GUI Front end just find out the exact files and copy and paste them in the Front end files files then ur prob will be solved.......
    If in case any issues let me know.
    Regards
    Madhavi

  • ABAP dump when user login in to PRD system

    Hi Experts,
    From today morning our users are facing one severe issue.The users when ever they login into the system the ABAP dump is occuring like "Database inconsistency: Start transaction SICK ",when i execute the SICK t-code it is showing errors.
    SAP System Check
    no application server offers an VB service
    Severe problems were detected during initial system check.
    Please, do not use that system before fixing these problems.
    our go live was before one month only,now we are facing this issue.our kernel release is 740 and DB sybase ASE 15.7.0.1010. please suggest us what can we do.
    regards,
    Patan Thavaheer.

    |15.05.2014                        Active parameters                        12:47:40                                                                                                                                                                                                                         |
    |Parameter Name                             |Parameter value                                                                                                                 Parameter Value - Continued                                                                                                     |
    |login/disable_multi_gui_login              |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_enq                            |1                                                                                                                                                                                                                                                               |
    |login/no_automatic_user_sapstar            |0                                                                                                                                                                                                                                                               |
    |SAPSYSTEMNAME                              |XXX                                                                                                                                                                                                                                                          |
    |SAPGLOBALHOST                              |XXXXXX                                                                                                                                                                                                                                                          |
    |SAPSYSTEM                                  |00                                                                                                                                                                                                                                                              |
    |INSTANCE_NAME                              |DVEBMGS00                                                                                                                                                                                                                                                       |
    |DIR_CT_RUN                                 |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64                                                                                                                                                                                                                           |
    |DIR_EXECUTABLE                             |$(DIR_INSTANCE)\exe                                                                                                                                                                                                                                             |
    |DIR_PROFILE                                |\\XXXXXX\sapmnt\XXX\SYS\profile                                                                                                                                                                                                                                 |
    |_PF                                        |$(DIR_PROFILE)\XXX_DVEBMGS00_XXXXXX                                                                                                                                                                                                                             |
    |SETENV_00                                  |PATH=$(DIR_EXECUTABLE);%PATH%                                                                                                                                                                                                                                   |
    |Start_Program_00                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)                                                                                                                                                                                                               |
    |_CPARG0                                    |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybjdbc.lst                                                                                                                                                                                                                  |
    |_CPARG1                                    |source:$(DIR_GLOBAL)/syb/NTAMD64                                                                                                                                                                                                                                |
    |Start_Program_01                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0) $(_CPARG1)                                                                                                                                                                                         |
    |Start_Program_02                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)                                                                                                                                                                                                               |
    |_CPARG2                                    |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybodbc.lst                                                                                                                                                                                                                  |
    |_CPARG3                                    |source:$(DIR_GLOBAL)/syb/NTAMD64/sybodbc                                                                                                                                                                                                                        |
    |Start_Program_03                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG2) $(_CPARG3)                                                                                                                                                                                         |
    |_CPARG4                                    |list:$(DIR_CT_RUN)/sapcrypto.lst                                                                                                                                                                                                                                |
    |Start_Program_04                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG4)                                                                                                                                                                                                    |
    |SAPJVM_VERSION                             |6.1.048                                                                                                                                                                                                                                                         |
    |DIR_SAPJVM                                 |$(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6                                                                                                                                                                                                                             |
    |jstartup/vm/home                           |$(DIR_SAPJVM)                                                                                                                                                                                                                                                   |
    |Start_Program_05                           |immediate $(DIR_CT_RUN)\strdbs.cmd XXX                                                                                                                                                                                                                          |
    |sec/libsapsecu                             |$(ssl/ssl_lib)                                                                                                                                                                                                                                                  |
    |ssf/ssfapi_lib                             |$(ssl/ssl_lib)                                                                                                                                                                                                                                                  |
    |rdisp/wp_no_dia                            |10                                                                                                                                                                                                                                                              |
    |rdisp/wp_no_btc                            |3                                                                                                                                                                                                                                                               |
    |_DW                                        |$(DIR_EXECUTABLE)\disp+work$(FT_EXE)                                                                                                                                                                                                                            |
    |Start_Program_06                           |local $(_DW) pf=$(_PF)                                                                                                                                                                                                                                          |
    |_IG                                        |$(DIR_EXECUTABLE)\igswd$(FT_EXE)                                                                                                                                                                                                                                |
    |Start_Program_07                           |local $(_IG) -mode=profile pf=$(_PF)                                                                                                                                                                                                                            |
    |rdisp/wp_no_vb                             |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_vb2                            |1                                                                                                                                                                                                                                                               |
    |rdisp/wp_no_spo                            |1                                                                                                                                                                                                                                                               |
    |ssl/ssl_lib                                |$(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)                                                                                                                                                                                                   |
    |SETENV_01                                  |SECUDIR=$(DIR_INSTANCE)/sec                                                                                                                                                                                                                                     |

  • Core dump when running the Proc Application

    I have client that has decided to upgrade from Oracle 10g to Oracle11g version. Presently the client code is compiled with Oracle version 11.1.0.7. We have tuxedo version as 9.0 patch02. When running the ProC application, I am getting the core dump. The stack trace for dump is as follows :-
    core 'core' of 7784: bp_Customer -C dom=KenanFX -g 5 -i 225 -u dsesun10 -U /users/denver/pc
    ffffffff6e8d9bbc kill (2, ffffffff7ffe002c, 1, ffffffff7de3b9a0, ffffffff7ffe0028, ffffffff7e10b5a0) + 8
    ffffffff7d27b1f4 skgesigCrash (ffffffff7ffe09a8, ffffffff7e10a070, 1a0c00, ffffffff7dfdbc40, d60a7c, 1) + 34
    ffffffff7d27b81c skgesig_sigactionHandler (ffffffff7d6fb9a0, ffffffff7ffe1800, ffffffff7ffe0990, ffffffff7e10b578, ffffffff7ffe0998, ffffffff7ffe09a8) + dc
    ffffffff6e8d62e0 __sighndlr (b, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff7d27b740, 0, a) + c
    ffffffff6e8c9e44 call_user_handler (ffffffff75f00200, ffffffff75f00200, ffffffff7ffe1520, 8, 0, 0) + 3e0
    ffffffff6e8ca03c sigacthandler (0, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff75f00200, 0, ffffffff6ea3c000) + 54
    --- called from signal handler with signal 0 (SIGEXIT) ---
    ffffffff7c24bb24 sqlrlc (ffffffff7e0f9fc0, 0, 60, c0, 4, 8) + 4
    ffffffff7c253594 sqlbrl (ffffffff7e0f9fc0, 1004bc630, 1004bc658, 1004bc5d0, ffffffff7ffe1b30, 2) + 114
    ffffffff7c2745ec sqlhvdsc (1004bc5c0, ffffffff7e0f9fc0, 8, ffffffff7fff27a0, 0, 1d676b0) + ac
    ffffffff7c274e68 sqlshv (c, 0, e, 0, f, 1c) + 128
    ffffffff7c25bd8c sqlsel (ffffffff7fff27a0, 1002d0850, 1002d0d80, 1, ffffffff7e0f9fc0, ffffffff7dd09d70) + 38c
    ffffffff7c24ed18 sqlcmex (1, ffffffff7ffe1e80, 0, c, 1002d0850, 0) + 278
    ffffffff7c24f724 sqlcxt (0, ffffffff74fd3800, ffffffff7fff27a0, ffffffff74e5d3e4, 16400, 0) + 44
    ffffffff74c65aec selectCMF_XIDDB (788, 16450, 2, ffffffff74fbb978, ffffffff7fff4344, ffffffff7971de60) + f14
    ffffffff79f5743c bp_AccountFind (0, 0, 1002b6118, 1002b6118, 1002b6118, 1002b6118) + 137c
    000000010001748c commonServiceWrapper (30, 0, 558, 1, 100140428, ffffffff6fa08560) + cac
    000000010001d1a4 I_AccountFind (100188220, 12336c, 2e60, 100186b80, ffffffff7fffa440, ffffffff6fa08560) + ec
    ffffffff7f25ea34 _tmsvcdsp (100186b80, 0, 1001f7b60, 800, 100186b80, 1400) + 11ac
    ffffffff7f28241c _tmrunserver (2bb4, 0, 100186b80, 10017c480, 10017d5a0, 0) + 11ac
    ffffffff7f25d47c _tmstartserver (1, 2c00, 100144c90, 800, 10017ebe0, 1001444e0) + 1ac
    0000000100014e4c main (1b, ffffffff7fffab18, ffffffff7fffabf8, ffffffff6e84b8e0, ffffffff75b05200, ffffffff75f00200) + 14
    0000000100014d9c _start (0, 0, 0, 0, 0, 0) + 17c
    Can you please help what is causing problem in the applications. Thanks in advanced.

    This forum is about C programming in general, and about using Oracle Studio C in particular.
    Your question seems to be about a database application that now crashes when run on an updated version of Oracle database.
    You mention "Proc" and ProC". If you are referring to the Pro*C compiler, that would also be a database question, since the Pro*C compiler is not related to Oracle Studio or Oracle Studio C.
    You are more likely to find a helpful answer in a database programming forum. Start here:
    https://forums.oracle.com/forums/category.jspa?categoryID=18

  • Removing ABAP dump when JDBC is down in RFC- JDBC- RFC scenario

    Hi All,
    I need help to build one scenario.
    I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.
    But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"
    Is it possible to implement without BPM, then How?
    If not possible then what could be the steps of BPM?
    Thanks & Regards

    Rohan,
    1.Recive Step should open the Synch - Asynch Bridge
    2. Block Step --> Send Synchronous inside this step with an Exception Hanler.
    3. Now in the exception ahndler step, do the necessary error handling requirement.
    4. Send Step --> closes Synch Asynch bridge.
    My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.
    Regards,
    Bhavesh

  • Dump when run J2I5 - Excise Registers Extraction

    Hi,
    When we run the J2I5 - Excise Registers Extraction (with Register RG23D), it is giving the run time error  The ABAP/4 Open SQL array insert results in duplicate database records.
    This error is showing after 04.08.2009 to till date..But before till 03.08.2009, it is working file...
    What should be the problem????

    Hi,
    Check notes:
    965938 J2I5 extraction gives a dump for RG23D
    957105 Short Dump while extracting RG23D register in J2I5
    842079 Additional changes to NCCD,ECS - J2I5
    1087108 RG23D:Short dump and timeout error in j2i6.
    1094202 DUMP while cancelling the download of register RG23D in 46C
    Regards,
    Eli

  • ABAP DUMP when I do a document flow

    Hi Experts-
    In transaction VA02, once inside the document, when I do a document flow, I am receiving ABAP run-time error message.
    However, when I do document from the initial screen of VA02, I am able to see the document flow.
    I have checked the OSS notes, but do not find any existing note related to this.
    Any thoughts?
    Cheers,
    Syed

    Hi:
    The best way to deal with this (if you have not ABAP experience) is to get a ABAPer to look at it with you.  You can check transaction ST22, there you will find the details of the dump.  when you double-click on your report (dump) and scroll down, you will see some numbers on the left of the page then there will be an interrupt in the sequence and an arrow -
    > will be seen, this would be the point where the dump occurred.  Hopefully this will give some clue to what is happening.
    Regards
    please reward if helpful
    Aaon

  • Dump when running macro

    Hello Folks,
    I have a alert creation macro in my planning book, the moment I run the macro it gives a dump. In ST22 transaction I get the name of run time error as "SAPSQL_INVALID_FIELDNAME".
    The same macro works fine in my dev system properly without any issue, the issue given here does not work only in the Quality system. Looks like the SAP system generates a internal program where this dump is caused.
    The abap'er could not debug the issue much as this is a internally created program.Some more details of the error are given below.
    Runtime Errors         SAPSQL_INVALID_FIELDNAME
    Exception              CX_SY_DYNAMIC_OSQL_SEMANTICS
    procedure "SELID_GET"
    contained field name "SEL_ZCPRODUCT" does not exist
    Any kind of pointers to resolve this will be appreciated.
    Regards,
    Vasudevan

    hi all ,
    When u run consistency check for one planning area 1, then the internal table reflects the structure of first Planning Area, if u try running macro belonging to PA2 then there is dump becasue the internal table has the structure of the PA1.
    This was due to the Table: /SAPAPO/TSAREATE (which has the internal table names of the planning area) having the same table for two plannig areas.
    While one Planning area inconsistency was run it corrected for the existing planning area, affecting the other to work.
    To rectify this delete one of the planning area table entry form table /SAPAPO/TSAREATE (for the inconsistent planning area) & then run the consistency check. This will create a new table for the second planning area and there will be no conflict.
    That will give a permanent soultion.
    Hope this helps.
    Cheers
    Anand

Maybe you are looking for

  • How can i create an apple id without a payment method or a free method?

    How can i create an apple id by using a free method?

  • PI 7.0 Production server restarts automatically

    Hi guys, We have installed and configured correctly a PI 7.0 system on Windows 2003 Standard Edition X64-bit with SQL Server 2005. We are on SP12. Everything, SLD, RFC connections work properly. The problem is that 4-5 days after the installation the

  • Export xmp from jpeg

    Hi, Photographer I use Internet in lots of coutries. I have to work in jpeg and i want to export XML to send by Internet. So Can I export XML from JPEG ? Can I see the modifications if I put the sidecars XML in the directory of jpeg without modificat

  • ORA-01006 in execute immediate

    Hi Everyone! Please help! What's wrong with this code? create or replace procedure rgo_test_forall as   v_actie                        varchar2( 200 ) := 'BEGIN';   cursor c_sjv   is     select   1 netb_totaal            , 'prf' profiel            ,

  • Java.sql.SQLException: No available resource. Wait-time expired.

    Hi all, The application platform is SunONE Application Server 7, and the database is ORACLE 9i. My Website application will raise the SQLException once a few days' running. Everything will be ok once the Application server has been restarted. The det