Dump TSV_LIN_ALLOC_FAILED , when run job : SAP_COLLECTOR_FOR_JOBSTATISTIC

hi all the experts,
When the job SAP_COLLECTOR_FOR_JOBSTATISTIC ,
I searched in service.sap.com notes and have not achieved anything specific.
This is canceled and when I check the st22 said that there is not enough space in memory. annex the dump TSV_LIN_ALLOC_FAILED.
thanks and regards.
Gustavo Gonzalez
ShrtText                                                                               
No roll memory available to extend the index of an internal table.                                                                               
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                                                                               
The linear index of an internal table was supposed to be extended.                          
However, the 2293776 bytes of memory requested for it were not available     
in the roll area.                                                                               
Storage location: "Session memory"                                           
            Last error logged in SAP kernel                                   
Component............ "EM"                                                   
Place................ "SAP-Server sapsrv01_D01_01 on host sapsrv01 (wp 2)"   
Version.............. 37                                                     
Error code........... 7                                                      
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV " 
Description.......... " "                                                    
System call.......... " "                                                    
Module............... "emxx.c"                                               
Line................. 1886                                                   
How to correct the error                                                      
    Decide by analysis whether this request is reasonable or whether there    
    is a program error. Pay particular attention to the internal table        
    entries listed below.                                                     
    The amount of storage space (in bytes) filled at termination time was:                                                                               
Roll area...................... 1708928                                   
    Extended memory (EM)........... 114982560                                 
    Assigned memory (HEAP)......... 276176080                                 
    Short area..................... " "                                       
    Paging area.................... 24576                                     
    Maximum address space.......... " "                                                                               
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:                                                                               
    "TSV_LIN_ALLOC_FAILED" C                                                  
    "RSBPCOLL" or "RSBPCOLL"                                                  
    "START-OF-SELECTION"                                                      
System environment                                                                  
     SAP Release.............. "640"                                                                               
Application server....... "sapsrv01"                                            
     Network address.......... "10.0.0.15"                                           
     Operating system......... "Windows NT"                                          
     Release.................. "5.2"                                                 
     Hardware type............ "4x Intel 801586"                                     
     Character length......... 8 Bits                                                
     Pointer length........... 32 Bits                                               
     Work process number...... 2                                                     
     Short dump setting....... "full"                                                                               
Database server.......... "SAPSRV01"                                            
     Database type............ "MSSQL"                                               
     Database name............ "D01"                                                 
     Database owner........... "d01"                                                                               
Character set............ "English_United State"                                                                               
SAP kernel............... "640"                                                 
     Created on............... "Oct 3 2007 00:34:24"                                 
     Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"        
     Database version......... "SQL_Server_8.00 "                                                                               
Patch level.............. "203"                                                 
     Patch text............... " "                                                                               
Supported environment....                                                       
     Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"            
     SAP database version..... "640"                                                 
     Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,      
      Windows NT 6.0"                                                                               
Memory usage.............                            
Roll..................... 1708928                    
EM....................... 114982560                  
Heap..................... 276176080                  
Page..................... 24576                      
MM Used.................. 379558912                  
MM Free.................. 10752584                   
SAP Release.............. "640"

Hi ,
You can increase the roll area and see if this problem persists.
The parameter is ztta/roll_area .
Also , you can increase the Heap memory too (abap/heap_area_total).
But before increasing the meory , find out if there is any possibility to correct the program , by reducing the size ofthe internal table.
Regards,
Ponni.
from Eric Brunelle: begging for points is totally against forum rules. read them

Similar Messages

  • Data Services 4.0 error when running job - not updating repository table

    Hi All,
    I am hoping someone might have come across this error before.
    When running a data services job, from within Data Services Designer, when trying to re-run the same job, I get the following error messages:
    9332     2572     DBS-070300     17/10/2011 10:38:39 AM     |Data flow DF_XXXX_Data_DW1Date
    9332     2572     DBS-070300     17/10/2011 10:38:39 AM     SQL submitted to Oracle Server <BO3> resulted in error <ORA-00001: unique constraint (DS3_ADMIN.SYS_C005632) violated
    9332     2572     DBS-070300     17/10/2011 10:38:39 AM     >. The SQL submitted is <INSERT INTO AL_BW_REQUEST (REQUESTID,TYPE,VALUE,DF_NAME,CREATION_TIME) VALUES (
    9332     2572     DBS-070300     17/10/2011 10:38:39 AM     'REQU_4NIVIZ1G9S5B7LUY0HHP65ZJU', 3 , '29', 'DF_XXXX_Data_DW1Date',  to_date('2011.10.17 10:38:39', 'yyyy.mm.dd
    9332     2572     DBS-070300     17/10/2011 10:38:39 AM     hh24:mi:ss') )>.
    9332     2572     REP-100109     17/10/2011 10:38:39 AM     |Data flow DF_XXXX_Data_DW1Date
    9332     2572     REP-100109     17/10/2011 10:38:39 AM     Cannot save <RequestID info> into the repository. Additional database information: <SQL submitted to Oracle Server <BO3>
    9332     2572     REP-100109     17/10/2011 10:38:39 AM     resulted in error <ORA-00001: unique constraint (DS3_ADMIN.SYS_C005632) violated
    When I go and look into the Data Services repository AL_BW_REQUEST  table, the first time the job is run, all five fields in this table populate with data successfully. When re-running the job, on 3 out of the five fields within this table are populated but the VALUE and DF_NAME field are not populated, hence causing the primary key violation.
    Here is the data below from the AL_BW_REQUEST  table:
    REQUESTID                                      TYPE  VALUE     DF_NAME                               CREATION_TIME
    REQU_4NIVIZ1G9S5B7LUY0HHP65ZJU     3                      10/17/2011 10:38:38 AM
    REQU_4NJ503RVIFD3VLBJJEKBJ3OE2     3                       10/17/2011 10:33:37 AM
    REQU_4NJ4ZHSP9F93L3OAUDV6RHCMY     3                       10/17/2011 10:32:31 AM
    REQU_4NIV1NKP9645E394E7H12Q796     3                      10/17/2011 9:53:53 AM
    REQU_4NEYFNI2U68MBJOEWFJWVWWU2     3  24     DF_XXXX_Data_DW1Date      10/17/2011 9:47:58 AM
    If I truncate this table and re-run the DS job, it will not populate the VALUE and DF_NAME fields. 
    Does anyone know what could be causing this? The target source is BW.
    Seems like a bug to me.
    Thanks,
    Ainsley

    Hi Ramesh,
    Am a HANA apps consultant in India, would like to get in touch with you. but don't know how
    regards,
    Tilak

  • EXTREME NEED OF WHY WHEN RUNNING JOBS IN ADK FOR WIN7 OR 8 SAYS OPERATING SYSTEM NOT SUPPORTED ON ALL

    GUYS,GALS,FELLOW GEEKS, NERDS, PROFESSIONALS, AND the like. I have a major issue of why after installing ADK it says when after running that the operating system isnt supported? I see no rational of why it would do that. ANYONE who is privvy to such, please
    asap me a solution if there is one. Uninstalling it now. I just need a tool other than the fixit tools which are too archaec to deal with, or too light in diagnostics.
    leonard

    Are you running the required OS according to the document below?
    http://msdn.microsoft.com/en-us/library/windows/hardware/dn246959.aspx
    Juke Chou
    TechNet Community Support

  • Session getting locked when running jobs

    Hello:
    I am trying to kick of jobs:
    DECLARE
    X NUMBER;
    BEGIN
    SYS.DBMS_JOB.SUBMIT
    ( job => X
    ,what => 'ABC.A1;'
    ,next_date => to_date('16/10/2008 08:05:00','dd/mm/yyyy hh24:mi:ss')
    ,interval => 'TRUNC(SYSDATE+30)'
    ,no_parse => TRUE
    SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
    END;
    commit;
    DECLARE
    X NUMBER;
    BEGIN
    SYS.DBMS_JOB.SUBMIT
    ( job => X
    ,what => 'ABC.A2;'
    ,next_date => to_date('16/10/2008 08:05:00','dd/mm/yyyy hh24:mi:ss')
    ,interval => 'TRUNC(SYSDATE+30)'
    ,no_parse => TRUE
    SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
    END;
    commit;
    The first job starts fine. But the second job in encountering a session-locked error.
    What am I doing wrong?
    Venki

    With this query, you can show the sql blocker and blockee.
    Regards Salim.
    SELECT 'BLOCKER: '||BW.HOLDING_SESSION||'('||SB.USERNAME||') MODE: '||MODE_HELD||
            ' - SQL: '||BQ.SQL_TEXT BLOCKER,
           'BLOCKEE: '||BW.WAITING_SESSION||'('||SW.USERNAME||') MODE: '||MODE_HELD||
            ' - SQL: '||SQ.SQL_TEXT  BLOCKEE
         FROM DBA_WAITERS BW, V$SESSION SB, V$SESSION SW, V$SQLTEXT BQ, V$SQLAREA SQ
         WHERE BW.HOLDING_SESSION = SB.SID
        AND BW.WAITING_SESSION = SW.SID
        AND SB.PREV_SQL_ADDR = BQ.ADDRESS
        AND SW.SQL_ADDRESS = SQ.ADDRESS ;

  • Getting slapd to dump core when installed as a non-root users on linux

    Doesn anyone know how to allow slapd do dump core when running on linux(redhat as4) while being installed as a non-root user?
    I have tried the normal route of setting core to unlimited and that user to unlimited also in limits.conf.
    I can do a kill -11 $pid with an instance running as root to get a core but no luck with an instance as a non-root user.

    I forgot to mention that I'm running 6.1.

  • Raise_exception error when running DTP  to writ optmized DSO

    Hi guru's,
                  I have been getting this ABAP dump raise_exception when running a DTP to DSO,
    i went thru the dump, actually this DSO updating another standard DSO, i deleted the writ optzd DSO request before deleting the request from target it is updating. Tried to activate the data flow, created a new DTP and tried to run DTP (full load), still getting the same dump.
    any idea on this ,
    thanks,
               peter r

    Hi ,
    check this thread:
    ABAP Dump "RAISE_EXCEPTION"
    http://sap.ittoolbox.com/groups/technical-functional/sap-basis/abap-runtime-errors-raise_exception-397395?cv=expanded
    Hope it helps,
    Supriya

  • Report program when run in background job getting cancelled immediately

    Hi
    When i run a program in foreground i am able to see the output. But when run in background not able to run the job successfully. The job is getting cancelled immediately.
    I am using the below function module for output display. Should i need to pass any parameters in the below function module so that i can run the program in background  successfully.
      CALL METHOD DETAIL_GRID->SET_TABLE_FOR_FIRST_DISPLAY     
          EXPORTING                                            
            IS_LAYOUT         = IS_LAYOUT                    
            I_SAVE            = 'A'                        
            IS_VARIANT        = GS_VARIANT                   
          CHANGING                                           
            IT_FIELDCATALOG   = IT_FIELDCATALOG               
            IT_OUTTAB         = BLOCKED_STOCK_TAB_ALV[].     
    Please suggest.
    Thanks and regards
    Rajani Yeluri

    Hi Rajani.
      ALV require the DRYPOR(screen) for display but incase you run in back ground which have to write to spool but in spool we can only write in format of LIST REPORT not inter-active report like ALV. That why
    system cancelled your process immediately.
    Hope it helps.
    Sayan.

  • It has an error when run a program in background job

    Dear Expert,
    we have a program
    when run it in background,it has a error "Error during import of clipboard contents" but when run it normally(run in front workbench se38 or run the t-code),everything is ok.i've used typingJDBG in the command box to debuge the background job,there has no error.
    whould you like to tell me what had happen? thanks a lot!
    addition: the program used a function ALSM_EXCEL_TO_INTERNAL_TABLE
    Thanks & Regards,
    Kerry
    Edited by: Kerry Wang on Aug 24, 2009 2:12 PM
    Edited by: Kerry Wang on Aug 24, 2009 2:14 PM
    Edited by: Kerry Wang on Aug 24, 2009 2:14 PM

    Hi,
      You cannot use FMs to get data directly from the presentation server when program is executed in the backgroud.
    Check the thread : GUI_DOWNLOAD
    Regards,
    Himanshu

  • Error when running "role usage synchronization" job in ERM

    I get an error in my job log when I run "role usage synchronization".  Has anyone seen this before:
    179 12/8/09 5:02:47 PM Ready Job created
    179 12/8/09 5:03:31 PM Running Include users for user access review: A,L
    179 12/8/09 5:03:31 PM Running Exclude locked users with lock codes: 32,64
    179 12/8/09 5:03:31 PM Running Exclude Expired Users : Yes"
    179 12/8/09 5:03:31 PM Running Job running
    179 12/8/09 5:03:31 PM Running Role usage synchronzation for connector WBS is started
    179 12/8/09 5:03:33 PM Running Updated records for 21 users in database
    179 12/8/09 5:03:34 PM Running For 5 users there was no role assignment
    179 12/8/09 5:03:34 PM Running WBS : Total number of users 21, Total number of role assignments: 71
    179 12/8/09 5:03:34 PM Running Error in backend system/Web service; Input data length not a multiple of blocksize.
    179 12/8/09 5:03:34 PM Completed Job completed
    Thanks,
    Peggy

    Peggy,
       I have seen this kind of error more than a year back. May be the role name contains special character or somewhere in the role table there is a space or something. I will recommend you to open a message with SAP.
    Alpesh

  • Sorting array not working when run as a job

    I have a Powershell script that reads data from a log file, extracts a username and adds it to an array. I then sort the array to remove duplicates and export the data to a CSV file. The script works fine when run locally on the server but I need to call
    the script remotely for a number of servers and when I do this it does not output anything to the CSV. The script is run as a job.
    $ArrList = [System.Collections.ArrayList]@()
    # open file and read data
    $arrlist.Add("$final")
    $arrlist | sort -unique | out-file c:\scripts\iis_users.csv
    If I change the script to use add-content it can add entries to the same CSV file. But ideally I need to sort the output as there are many duplicates.

    Not sure why but that would only export the last user. I didn't have time to investigate so instead I decided to only add users to the array after first checking they didn't exist already:
    if ($arrlist -notcontains $final)
    $arrlist.Add("$final")
    add-content c:\scripts\iis_users.csv "$final"
    I thought this would create a performance hit but it seems almost as fast.

  • 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

  • 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

  • Error is thrown ONLY when the job is run doe delivery creation

    Dear SDNres,
    I am facing a tricky issue.
    I have a job that creates Sales order , Delivery, Billing.
    When the sales order contains line items <=8 then the job runs fine and creates delivery successfully
    When the sales order contains line items more than 8, then the job fails on delivery creation and the BDC captures error "customised error''
    Doubt:
    steps in manual creation:
    1)I create a Sales order with line items > 8
    2)then i create delivery manually .
    After the above 2 steps i dont get the error at all in case of manual creation
    But the same steps when the job does for a Sales order with line items >8 then the error comes and job fails.
    Kindly suggest me as to where i need to look for the error.
    Regards,
    SuryaD.

    Thanks for your response Dave.
    Yes i am doing a BDC Call Transaction.
    there is no BAPI.
    Trickier part is when i execute the job through debugging then i do not get the error.
    What could be the reason for this error.
    Is it some error in teh coding?
    regards,
    SuryaD.

  • Type Mismatch when run a job in DTW

    We migrated to SAP B1 SP01 PL09, we had a job for the datatransfer that was working normally but after updated when the job runs an error is showed: Type Mismatch.
    We tried to connect manually and work fine, the problem is in the Job:
    "C:Program FilesSAPData Transfer WorkbenchDTW.exe" -s c:prueba.xml
    I checked the sentence and is fine.
    Does anybody know why this happen??
    Thanks
    Daniela Nuñ

    Maybe the path is incorrect,have you check the name? maybe Program Files is incorrect but "Archivos de Programa" may work
    the upgrade maybe change some folder name.
    Me parece que la ruta podria estar incorrecta Daniela, quizas el nombre no es Program Files sino Archivos de Programa...ya revisaste eso? Quizas la actualizacion cambio algun nombre de carpetas
    Example
    "C:\Archivos de programa\SAP\Data Transfer Workbench\DTW.exe" -s C:\Documents and Settings\mquintanag\Mis documentos\testClientes.xml

  • How to set dynamic value for field Month when running background job ?

    Dear guys,
    I have a Z* report in our company, in the selection screen there is a period field (Month and Year) and this report running in background job periodically. My Question is how i can set for Month field become dynamic follow month value of date when this report executed ?
    Example :
    When Z* report running in background on 16.04.2008, Month Value will be 04 and when running on 16.05.2008, Month Value will be 05.
    Please advice.
    Regards
    Gunawan

    Dear guys,
    I have a Z* report in our company, in the selection screen there is a period field (Month and Year) and this report running in background job periodically. My Question is how i can set for Month field become dynamic follow month value of date when this report executed ?
    Example :
    When Z* report running in background on 16.04.2008, Month Value will be 04 and when running on 16.05.2008, Month Value will be 05.
    Please advice.
    Regards
    Gunawan

Maybe you are looking for