Memory dump in contract data load

Hi,
e are doing CRM service contract data load from flat file to CRM using
BAPI_BUSPROCESSND_CREATEMULTI and it is giving ABAP memory dump.Please
see attached file for more details about dump.
Following steps we are doing.
1.Call following functional modules in loop to create service contract.
2. call
call function 'BAPI_BUSPROCESSND_CREATEMULTI'
    tables
      header          = lt_header
      item            = lt_item
      sales           = lt_sales
      partner         = lt_partner
      appointment     = lt_appointment
      status          = lt_status
      input_fields    = lt_input_fields
      created_process = lt_created_process
      return          = lt_return
      scheduleline    = lt_scheduleline
      pricing         = lt_pricing
      billing         = lt_billing
      objects         = lt_objects
      condition_create = lt_condition_create
     billplan        = lt_billplan
     billplan_date   = lt_billplan_date
       cancel          = lt_cancel
      document_flow   = lt_docflow.
2.call
      call function 'CRM_ORDER_SAVE'
    exporting
      it_objects_to_save = lt_objects_to_save
      iv_no_bdoc_send    = 'X'
    exceptions
      document_not_saved = 1
      others             = 2.
3. call
          call function 'BAPI_TRANSACTION_COMMIT'
    exporting
      wait = 'X'.
4.call
           call function 'CRM_ORDER_INITIALIZE'
    exporting
      it_guids_to_init           = lt_guid_16
      iv_initialize_whole_buffer = 'X'
      iv_init_frame_log          = 'X'
    exceptions
      error_occurred             = 1
      others                     = 2.
5.close the loop.
Though we are every time calling 'CRM_ORDER_INITIALIZE' it's still
giving following dump. Looks like 'CRM_ORDER_INITIALIZE' is not
initializing the memory.
Dump details
STORAGE_PARAMETERS_WRONG_SET
&INCLUDE INCL_INSTALLATION_ERROR
What happened?
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 256701152 bytes from the operating
system with 'malloc' when the operating system reported after a
further memory request that there was no more memory space
available.
Could you please suggest how to clear the memory?
-Kavitha

Hi Kavitha,
What are the approx. number of records you are trying to Populate? You can follow the below given sequence for loading the data.
1. call function 'BAPI_BUSPROCESSND_CREATEMULTI'
2. CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
Example:
call function 'BAPI_BUSPROCESSND_SAVE'
      EXPORTING
        update_task_local = false
        save_frame_log    = true
     IMPORTING
      log_handle        = lv_loghandle
      TABLES
        objects_to_save   = lt_objects_to_save
        saved_objects     = lt_saved_objects
        return            = lt_return.
3.   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
i think this would work without problem. Let me know whether you still get ABAP Dump.
Regards
Abinash

Similar Messages

Short Dump Error While Data load

Hi Experts,
Data load to an ODS in production server has been failed because of Short dump error. The error message shows " OBJECTS_OBJREF_NOT_ASSIGNED ".
Request you to please help me out with a solution ..
Regards,
Vijay

Hi Vijay,
follow the steps below (May Help you)
Goto Monitor screen>Status Tab> using the wizard or the menu path >Environment -> Short dump> In the warehouse
Select the Error and double click
Analyse the error from the message.
1.-->Go to Monitor
-->Transactional RFC
-->In the Warehouse
-->Execute
-->EDIT
-->Execute LUW
Refresh the Transactional RFC screen and go to the Data Target(s) which have failed and see the status of the Request-->Now it should be green.
2.In some cases the above process will not work (where the Bad requests still exists after the above procedure).
In that case we need to go to the Data Targets and need to delete the bad requests and do the update again
Regards,
BH

Short Dump in master data load

In a master dataload from BI to APO, i'm getting these short dumps...
CALL_FUNCTION_SIGNON_REJECTED
TIME_OUT
MESSAGE_TYPE_X
RAISE_EXCEPTION
Kindly help me out getting these dumps rectified..

Hai message type x error have number of parameters for it one may be due to error in logical source system .Other may be inactive datatargets and lot more.
Time out is becouse of upfront loading trigger in the background and ask basis to extend the process time to max sap standards.
others may be due to lack of workprocess unavailability check it as well.
Goodday.

DATA LOAD ISSUE /NO ROLL UP MEMORY

Hello Team,
I have this master data load failure for FIS_BELNR. The problem which I think that everytime it tries to load it runs out of internal table space in the backend. I really don't know what it means. This data is been failing everyday because of the same problem.
I have attached all the screen shots and ABAP short dump analysis screen shots as well. One can read in details why is it failing it tells exactly what the problem is , but how to fix it.
Any more details needed please let me know.
ABAP runtime errors    TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
       Occurred on     25.10.2007 at 02:53:55
>> Short dump has not been completely stored. It is too big.
No roll storage space of length 2097424 available for internal storage.
                                                                                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:
hat can you do?
ry to find out (e.g. by targetted data selection) whether the
ransaction will run with less main memory.
f there is a temporary bottleneck, execute the transaction again.
f the error persists, ask your system administrator to check the
ollowing profile parameters:
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
ztta/roll_extension       (10.000.000 - 500.000.000)
      Amount of memory per user in extended memory (EM)
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
bap/heap_area_dia:        (10.000.000 - 1.000.000.000)
      Restriction of memory allocated to the heap with malloc
      for each dialog process.
arameters for background processes:
Error analysis
The internal table "IT_62" could not be enlarged further.
You attempted to create a block table of length 2097424 for the internal
table "IT_62". This happens whenever the OCCURS area of the internal table
is exceeded. The requested storage space was not available in the roll
area.
The amount of memory requested is no longer available.
How to correct the error
Please try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 2595024
Extended memory (EM)........... 2001898416
Assigned memory (HEAP)......... 1886409776
Short area..................... 16639
Paging area.................... 24576
Maximum address space.......... "-1"
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"
"SAPLZ_BW_EXTRACTORS " or "LZ_BW_EXTRACTORSU24 "
"Z_BW_AP_GL_BELNR"
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.
Thanks

Hello,
The memory of your internal table wants beyond the system configured threshold.
Decrease your package size or extend the mentioned parameters (basis task):
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
ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
abap/heap_area_total (100.000.000 - 1.500.000.000)
Regards, Patrick Rieken

Data Load PSA to IO (DTP) Dump: EXPORT_TOO_MUCH_DATA

Hi Gurus,
Iu2019m loading Data from PSA to IO: 0BPARTNER. I habe around 5 Mil entries.
During the load the control Job dumps with the following dump:
EXPORT_TOO_MUCH_DATA
1. Data must be distributed into portions of 2GB
2. 3 possible solutions:
    - Either increase the sequence counter (field SRTF2) to include INT4
    or
    -export less data
    or
    -distribute the data across several IDs
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:
"EXPORT_TOO_MUCH_DATA" " "
"CL_RSBK_DATA_SEGMENT==========CP" or "CL_RSBK_DATA_SEGMENT==========CM00V"
"GET_DATA_FOR_EXPORT"
This is not the first time I do such large load.
The Field: SRTF2 is already an INT4 type.
Version BI: 701. SP06
I found a lot of OSS Notes for monitoring jobs, Industry solutions, by BI change runu2026 nothing however to data loading process.
Has anyone encountered this problem please?
Thanks in advance
Martin

Hi Martin,
There were series of notes which may be applicable here.
However if you have semantic grouping enabled it may be that this is a data driven issue.
The System will try to put all records into one package in accordance with teh semantic key.
If it is too generic many records could be input to one data package.
Please choose another (more) fields for semantic grouping - or unselect all fields if the grouping is not nessessary at all.
1409851 - Problems with package size in the case of DTPs with grouping.
Hope this helps.
Regards,
Mani

Sql*loader core dump on unicode data

I get a core dump when trying to load multibyte data with sqlloader.
ASCII data loads fine. The database was created with character set =
UTF8 and national character set = UTF8. Sqlloader CHARACTERSET is
UTF8.
The target table does NOT have nchar, nclob, or nvarchar2 columns. Is this an issue?
Environment:
Target: Oracle8.1.5 on RedHat Linux6.x
Data source: SQLServer extract on NT.
Wayne Martin

Jim,
If you telnet to the device, look under the root (/local1/) director for the following directories...
/core_dir/
/crash/
In one of them will be a file that was created when a process failed and restarted. The file name will have a process name and a time stamp as part of it. The Cisco TAC has tools that can decode the actual cause of the crash and see if it's something that is known or not. I would take a full sysreport of the box, collect the crash file via FTP and attach those to a TAC case for them to review. They should be able to let you know what caused it and if there is any reason to be concerned along with any workarounds/related DDTS/code fixes that are out there for resolution.
FYI: The alarm will persist until you remove the crash file from the above directories. I usually "delfile" the file once I've FTPed it off.
Hope that helps,
Dan

Master data load gives dump with exception CX_RSR_X_MESSAGE

Hi all,
I scheduled master data load for 0MATERIAL in our BI 7.0 Quality server. The load ended in dump with the exception CX_RSR_X_MESSAGE. The data has loaded into PSA( 37257 from 37257 records) but the technical status is red and has not updated the master data object.
I have seen note 615389 which talks about number range but the check is successful. The data load was successful in development server. This error has occured only in Quality.
We are on SP 12 in BI 7.0.
We are moving to production soon, so this is an urgent issue. I would appreciate if anyone responds soon. Points will be rewarded.
with regards,
Ashish

Hi,
The log of the dump is given below.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
and
therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
Information on where terminated
Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 78
of the (Include) program "LRRMSU13".
Source Code Extract
Line
SourceCde
48
*... Nachricht an den Message-Handler schicken
49
50
*... S-Meldung wenn kein Handler initialisiert
51
DATA: l_type TYPE smesg-msgty,
52
l_zeile TYPE rrx_mesg-zeile.
53
CALL FUNCTION 'MESSAGES_ACTIVE'
54
IMPORTING
55
zeile = l_zeile
56
EXCEPTIONS
57
not_active = 1.
58
IF sy-subrc NE 0.
59
l_type = 'S'.
60
ELSE.
61
l_type = 'W'.
62
ENDIF.
63
64
CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
65
EXPORTING
66
i_class = 'BRAIN'
67
i_type = l_type
68
i_number = '299'
69
i_msgv1 = i_program
70
i_msgv2 = i_text.
71
ELSE.
72
DATA: l_text TYPE string,
73
l_repid TYPE syrepid.
74
75
l_repid = i_program.
76
l_text = i_text.
77
>>>>>
RAISE EXCEPTION TYPE cx_rsr_x_message
79
EXPORTING text = l_text
80
program = l_repid.
81
ENDIF.
82
83
ENDFUNCTION.
I went to SM21 and went through the system log. There was a log with the following text ORA-20000: Insufficient privileges#ORA-06512: at
"SYS.DBMS_STATS", line 2150#ORA-06512: at "SYS.DBMS_STATS.
I found a note 963760 for this error. After the changes said in this note were done I reloaded the data and it worked fine. Data load for another data source which gave dump now worked.
I am not sure if the note did the trick. So i am keeping this post open in case someone finds another solution or can confirm the solution which worked for me.
Thanks Oliver and Oscar, for replying.
regards,
Ashish

Data load failing with a short-dump

Hello All,
There is a data load failing with the following short-dump:
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_FOEV_ERROR_IN_FUNCTION
Full text:
"UNCAUGHT_EXCEPTION" CX_FOEV_ERROR_IN_FUNCTIONC
"CL_RSAR_FUNCTION==============CP" or "CL_RSAR_FUNCTION==============CM004"
"DATE_WEEK"
It seems as if it is failing in a function module - please advise.
Regards,
Keith Kibuuka

Did you read OSS [Note 872193 - Error in the formula compiler|https://service.sap.com/sap/support/notes/872193] or OSS [Note 855424 - Runtime error UNCAUGHT_EXCEPTION during upload|https://service.sap.com/sap/support/notes/855424]
Regards

Infocube data loads fail with UNCAUGHT_EXCEPTION dump after BI 7.01 upgrade

Hi folks,
We're in the middle of upgrading our BW landscape from 3.5 to to 7.01. The Support pack we have in the system is SAPKW70103.
Since the upgrade any of the data loads going to infocubes are failing with the following
ABAP dump UNCAUGHT_EXCEPTION
CX_RSR_COB_PRO_NOT_FOUND.
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
Has anyone come accross this issue and if so any resolutions you adopted to fix this. Appreciate any help in this regard.
Thanks
Mujeeb

hi experts,
i have exactly the same problem.
But I can`t find a test for infoobjects in rsrv. How can I repair the infoobject 0REQUEST`?
Thx for all answers!
kind regards
Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM
Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM

Error while starting data loading on InfoPackage

Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors         MESSAGE_TYPE_X
Date and Time          19.01.2009 14:41:22
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).
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
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
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" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
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 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop.      " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id    = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount        = l_s_rsbatchheader-jobcount
320
jobname         = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others          = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list           = l_t_server
327
exceptions
328
no_server_list = 1
329
others         = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME' field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host   = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc    = l_subrc
346
wp_index = l_wp_index
347
wp_pid   = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no           = l_wp_index.
352
l_s_rsbatchheader-ts_start        = l_tstamps.
353
l_s_rsbatchheader-uname           = sy-uname.
354
l_s_rsbatchheader-module_name     = l_module_name.
355
l_s_rsbatchheader-module_type     = l_module_type.
356
l_s_rsbatchheader-pc_variant      = i_pc_variant.
357
l_s_rsbatchheader-pc_instance     = i_pc_instance.
358
l_s_rsbatchheader-pc_logid        = i_pc_logid.
359
l_s_rsbatchheader-pc_callback     = i_pc_callback_at_end.

Hi,
i am also getting related this issue kindly see this below short dump description.
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).
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
    Short text of error message:
    Variant RSPROCESS0000000000705 does not exist
    Long text of error message:
     Diagnosis
         You selected variant 00000000705 for program RSPROCESS.
         This variant does not exist.
     System Response
     Procedure
         Correct the entry.
    Technical information about the message:
    Message class....... "DB"
Number.............. 612
    Variable 1.......... "&0000000000705"
    Variable 2.......... "RSPROCESS"
    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" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
    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 701
    Application server... "CMCBIPRD"
    Network address...... "192.168.50.12"
    Operating system..... "Windows NT"
Release.............. "6.1"
    Hardware type........ "16x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "CMCBIPRD"
    Database type..... "MSSQL"
    Database name..... "BIP"
    Database user ID.. "bip"
    Terminal.......... "CMCBIPRD"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 9 2012 23:43:54"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 196
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 16384
MM Used. 2143680
MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
    Language Key........ "E"
Transaction......... " "
    Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
System.............. "BIP"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron without reply and transactional (emode 0, imode
     0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 75
    of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line SourceCde
   45         l_t_info        TYPE rs_t_rscedst,
   46         l_s_info        TYPE rscedst,
   47         l_s_mon         TYPE rsmonpc,
   48         l_synchronous   TYPE rs_bool,
   49         l_sync_debug    TYPE rs_bool,
   50         l_eventp        TYPE btcevtparm,
   51         l_eventno       TYPE rspc_eventno,
   52         l_t_recipients TYPE rsra_t_recipient,
52 l_t_recipients TYPE rsra_t_recipient,
53         l_s_recipients TYPE rsra_s_recipient,
54         l_sms           TYPE rs_bool,
55         l_t_text        TYPE rspc_t_text.
56
57   IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59     CALL FUNCTION 'RSPC_PROCESS_FINISH'
60       EXPORTING
61         i_logid       = i_logid
62         i_chain       = i_chain
63         i_type        = i_type
64         i_variant     = i_variant
65         i_instance    = i_instance
66         i_state       = i_state
67         i_eventno     = i_eventno
68         i_hold        = i_hold
69         i_job_count   = i_job_count
70         i_batchdate   = i_batchdate
71         i_batchtime   = i_batchtime
72       EXCEPTIONS
73         error_message = 1.
74     IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77     ELSE.
78       EXIT.
79     ENDIF.
80   ENDIF.
81 * ==== Cleanup ====
82   COMMIT WORK.
83 * ==== Get Chain ====
84   IF i_chain IS INITIAL.
85     SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86            WHERE log_id = i_logid.
87   ELSE.
88     l_chain = i_chain.
89   ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92   DO.
93     CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94       EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru

Several LR3 issues - Crashes, memory dumps, and other oddities

I recently built a new PC dedicated to my photo work.
i7 2600k, 16gb DDR 3 ripjaws, 128GB crucial m4 SSD, (2) x 1TB 7200 HDDs (mirrored), Sapphire Radeon HD 5570.
The first month or so of use LR worked great. However, recently I have been getting several errors and oddities.
1) Randomly closes. I can restart it without a problem and pick back up where I left off. There are not warnings or signs that it is about to close.. it just does.
2) "Unexpected end of file". Unable to edit photo. Preview does show, however. I have never seen this error before on other machines.
3) Memory dumps. I assume this is related to LR3 as that is the only program I am actively using when it happens (Chome is always open as well, however) I will have the dump files examined to know for sure.
4) Something new that just started today. In the preview bar on the bottom, as I scroll through the photos I see the previews of other photos.. some photos from other folders I took weeks or months ago. When I hover over the image it changes to what it should be. I am seeing 2 instances of this. 1 with a photo from this particular shoot and one from one I did over a month ago. Everything I scroll back and forth (rapidly or not) as the previews load it loads the wrong files first, multiple times (around 8 or 9 in a row) and then they slowly change to what it should be.
I am not sure if I am properly describing this error but it is really weird.
Also, this seems to only happen on the images off a CF card. I was borrowing a friends D200 as a 2nd body for a party. When I scroll through the images off my SD card I do not see the issue appear. When I get to the CF portion of the folder is when I see the problem....
I just updated LR today but these issues occured prior to the update and still exist afterwards.
Do I need to do a fresh install of LR?
What precautions do I need to take in doing so to insure my catalogue stays intact?
Thanks for your help.

I am still having issues.
The crash dumps are far less frequent now. I think it may have been a catalogue issue maybe? I started a new one and things were better.
However, I am consistantly getting the "Lightroom has stopped working" and it closes down..... repeatedly. Very Very annoying.
It is not a major issue to just restart Lightroom, esp since it is on an SSD, it pops right back up instantly.
All of my files are on the HDD, however, not the SSD.
I had reinstalled LR3 once before which did not help. Any other suggestinos?
I can't imagine a reinstall of Windows would do anything for me. I have no issues with anything other than LR.
Could my video card be playing a role in the errors? I do notice weird random artifacts in my images sometimes when I add a brush stroke, or clone something out. Or sometimes just simply zooming in will great these weird multicolored lines in the image. Zooming out makes it go away. It is random when it shows up and often times closing and reopening LR will make it go away. So these are not permanent artifacts in the image unless I export the file with them showing. This leads me to think maybe the video card is having some issues. All drivers are up to date. It is not a high end card. Based on all my research when buidling this machine, a basic video card is all that is needed as RL is CPU and memory intensive, which is where I put most of my $. (i7 2600k and 16GB DDR3)

Open HUB ( SAP BW ) to SAP HANA through DB Connection data loading , Delete data from table option is not working Please help any one from this forum

Issue:
I have SAP BW system and SAP HANA System
SAP BW to SAP HANA connecting through a DB Connection (named HANA)
Whenever I created any Open Hub as Destination like DB Table with the help of DB Connection, table will be created at HANA Schema level ( L_F50800_D )
Executed the Open Hub service without checking DELETING Data from table option
Data loaded with 16 Records from BW to HANA same
Second time again executed from BW to HANA now 32 records came ( it is going to append )
Executed the Open Hub service with checking DELETING Data from table option
Now am getting short Dump DBIF_RSQL_TABLE_KNOWN getting
If checking in SAP BW system tio SAP BW system it is working fine ..
will this option supports through DB Connection or not ?
Please follow the attachemnet along with this discussion and help me to resolve how ?
From
Santhosh Kumar

Hi Ramanjaneyulu ,
First of all thanks for the reply ,
Here the issue is At OH level ( Definition Level - DESTINATION TAB and FIELD DEFINITION )
in that there is check box i have selected already that is what my issue even though selected also
not performing the deletion from target level .
SAP BW - to SAP HANA via DBC connection
1. first time from BW suppose 16 records - Dtp Executed -loaded up to HANA - 16 same
2. second time again executed from BW - now hana side appaended means 16+16 = 32
3. so that i used to select the check box at OH level like Deleting data from table
4. Now excuted the DTP it throws an Short Dump - DBIF_RSQL_TABLE_KNOWN
Now please tell me how to resolve this ? will this option is applicable for HANA mean to say like , deleting data from table option ...
Thanks
Santhosh Kumar

CALL_FUNCTION_CONFLICT_TYPE Standard Data loading

Hi,
I am facing a data loading problem using Business content on CPS_DATE infocube (0PS_DAT_MLS datasource).
The R/3 extraction processes without any error, but the problem occurs in the update rules while updating the milestone date. Please find hereunder the log from the ST22.
The real weird thing is that the process works perfectly in development environment and not in integration one (the patch levels are strongly the same: BW 3.5 Patch #16).
I apologise for the long message below... this is a part of the system log.
For information the routine_0004 is a standard one.
Thanks a lot in advanced!
Cheers.
   CALL_FUNCTION_CONFLICT_TYPE
Except.                CX_SY_DYN_CALL_ILLEGAL_TYPE
Symptoms.                                                Type conflict when calling a function module
Causes                                                        Error in ABAP application program.
     The current ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" had to be terminated because one of the statements could not be executed.
     This is probably due to an error in the ABAP program.
     A function module was called incorrectly.
Errors analysis
     An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was neither caught nor passed along using a RAISING clause, in the procedure "ROUTINE_0004"
     "(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 call to the function module "RS_BCT_TIMCONV_PS_CONV" is incorrect:
The function module interface allows you to specify only fields of a particular type under "E_FISCPER".
    The field "RESULT" specified here is a different field type.
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:
    "CALL_FUNCTION_CONFLICT_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC
    "GP420EQ35FHFOCVEBCR6RWPVQBR" or "GP420EQ35FHFOCVEBCR6RWPVQBR"
    "ROUTINE_0004"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".                                              2. A suitable printout of the system log To obtain this, call the system log through transaction SM21. Limit the time interval to 10 minutes before and 5 minutes after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs, supply the source code.
       To do this, select the Editor function "Further Utilities-> Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
     "ROUTINE_0004"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
Environment system SAP Release.............. "640"
Operating system......... "SunOS"   Release.................. "5.9"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 2
Short dump setting....... "full"
Database type............ "ORACLE"
Database name............ "BWI"
Database owner........... "SAPTB1"
Character set............ "fr"
SAP kernel............... "640"
Created on............... "Jan 15 2006 21:42:36"   Created in............... "SunOS 5.8 Generic_108528-16 sun4u"
Database version......... "OCI_920 "
Patch level.............. "109"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version..... "640"
Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10"
SAP Release.............. "640"
The termination occurred in the ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" in
     "ROUTINE_0004".
   The main program was "RSMO1_RSM2 ".
The termination occurred in line 702 of the source code of the (Include)
     program "GP420EQ35FHFOCVEBCR6RWPVQBR"
    of the source code of program "GP420EQ35FHFOCVEBCR6RWPVQBR" (when calling the editor 7020).
   Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE" occurred in the procedure "ROUTINE_0004" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
    The procedure is in the program "GP420EQ35FHFOCVEBCR6RWPVQBR ". Its source code starts in line 685 of the (Include) program "GP420EQ35FHFOCVEBCR6RWPVQBR ".
672      'ROUTINE_0003' g_s_is-recno
673      rs_c_false rs_c_false g_s_is-recno
674      changing c_abort.
675     catch cx_foev_error_in_function.
676     perform error_message using 'RSAU' 'E' '510'
677             'ROUTINE_0003' g_s_is-recno
678             rs_c_false rs_c_false g_s_is-recno
679             changing c_abort.
680   endtry.
681 endform.
682 ************************************************************************
683 * routine no.: 0004
684 ************************************************************************
685 form routine_0004
686   changing
687   result type g_s_hashed_cube-FISCPER3
688   returncode     like sy-subrc
689     c_t_idocstate type rsarr_t_idocstate
690     c_subrc        like sy-subrc
691     c_abort        like sy-subrc. "#EC *
692   data:
693     l_t_rsmondata like rsmonview occurs 0 with header line. "#EC *
694
695 try.
696 * init
variables
697   move-corresponding g_s_is to comm_structure.
698
699 * fill the internal table "MONITOR", to make monitor entries
700
701 * result value of the routine
>>>>    CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'
703          EXPORTING
704               I_TIMNM_FROM       = '0CALDAY'
705               I_TIMNM_TO         = '0FISCPER'
706               I_TIMVL            = COMM_STRUCTURE-CALDAY
707               I_FISCVARNT        = gd_fiscvarnt
708          IMPORTING
709               E_FISCPER          = RESULT.
710 * if the returncode is not equal zero, the result will not be updated
711   RETURNCODE = 0.
712 * if abort is not equal zero, the update process will be canceled
713   ABORT = 0.
714
715   catch cx_sy_conversion_error
716         cx_sy_arithmetic_error.
717     perform error_message using 'RSAU' 'E' '507'
718             'ROUTINE_0004' g_s_is-recno
719             rs_c_false rs_c_false g_s_is-recno
720             changing c_abort.
721   catch cx_foev_error_in_function.
System zones content
Name                Val.
SY-SUBRC           0
SY-INDEX           2
SY-TABIX           0
SY-DBCNT           0
SY-FDPOS           65
SY-LSIND           0
SY-PAGNO           0
SY-LINNO           1
SY-COLNO           1
SY-PFKEY           0400
SY-UCOMM           OK
SY-TITLE           Moniteur - Atelier d'administration
SY-MSGTY           E
SY-MSGID           RSAU
SY-MSGNO           583
SY-MSGV1           BATVC 0000000000
SY-MSGV2           0PROJECT
SY-MSGV3
SY-MSGV4
Selected variables
Nº       23 Tpe          FORM
Name    ROUTINE_0004
GD_FISCVARNT
    22
    00 RS_C_INFO                                                      I
      4
      9
COMM_STRUCTURE-CALDAY
20060303
33333333
20060303
SYST-REPID GP420EQ35FHFOCVEBCR6RWPVQBR   4533345334444454445355555452222222222222 704205135686F365232627061220000000000000
RESULT
000
333
00

You have an update routine in which youar callin FM 'RS_BCT_TIMCONV_PS_CONV'. Parameter e_fiscper must be the same that type of the variable you use (you can see the data tyoe in FM definition, transaction se37). You should do somethin like the following.
DATA: var type <the same that e_fiscper in FM definition>
CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'
EXPORTING
I_TIMNM_FROM = '0CALDAY'
I_TIMNM_TO = '0FISCPER'
I_TIMVL = COMM_STRUCTURE-CALDAY
I_FISCVARNT = gd_fiscvarnt
IMPORTING
E_FISCPER = var.
result = var.
--- ASSIGN POINTS IS USEFUL.

Which LKM and IKM to use for Fast data loading b/w MSSQL 2005 and Oracle 11

Hi,
Can anybody help us to decide which LKMs and IKMs are best for data loading between MSSQL and Oracle.
Staging Area is Oracle. We have to load around 400Million rows from MSSQL to Oracle 11g.
Best regards,
Muhammad

Thanks Ayush,
You are right and it has dumped the file very quickly; but it is giving error on sqlldr call thorugh jython. I have reaised SR with oracle to look into it further.
thanks again and have a very nice time.
Regards,
Muhammad

QUERY PERFORMANCE AND DATA LOADING PERFORMANCE ISSUES

WHAT ARE QUERY PERFORMANCE ISSUES WE NEED TO TAKE CARE PLEASE EXPLAIN AND LET ME KNOW T CODES...PLZ URGENT
WHAT ARE DATALOADING PERFORMANCE ISSUES WE NEED TO TAKE CARE PLEASE EXPLAIN AND LET ME KNOW T CODES PLZ URGENT
WILL REWARD FULL POINT S
REGARDS
GURU

BW Back end
Some Tips -
1)Identify long-running extraction processes on the source system. Extraction processes are performed by several extraction jobs running on the source system. The run-time of these jobs affects the performance. Use transaction code SM37 Background Processing Job Management to analyze the run-times of these jobs. If the run-time of data collection jobs lasts for several hours, schedule these jobs to run more frequently. This way, less data is written into update tables for each run and extraction performance increases.
2)Identify high run-times for ABAP code, especially for user exits. The quality of any custom ABAP programs used in data extraction affects the extraction performance. Use transaction code SE30 ABAP/4 Run-time Analysis and then run the analysis for the transaction code RSA3 Extractor Checker. The system then records the activities of the extraction program so you can review them to identify time-consuming activities. Eliminate those long-running activities or substitute them with alternative program logic.
3)Identify expensive SQL statements. If database run-time is high for extraction jobs, use transaction code ST05 Performance Trace. On this screen, select ALEREMOTE user and then select SQL trace to record the SQL statements. Identify the time-consuming sections from the results. If the data-selection times are high on a particular SQL statement, index the DataSource tables to increase the performance of selection (see no. 6 below). While using ST05, make sure that no other extraction job is running with ALEREMOTE user.
4)Balance loads by distributing processes onto different servers if possible. If your site uses more than one BW application server, distribute the extraction processes to different servers using transaction code SM59 Maintain RFC Destination. Load balancing is possible only if the extraction program allows the option
5)Set optimum parameters for data-packet size. Packet size affects the number of data requests to the database. Set the data-packet size to optimum values for an efficient data-extraction mechanism. To find the optimum value, start with a packet size in the range of 50,000 to 100,000 and gradually increase it. At some point, you will reach the threshold at which increasing packet size further does not provide any performance increase. To set the packet size, use transaction code SBIW BW IMG Menu on the source system. To set the data load parameters for flat-file uploads, use transaction code RSCUSTV6 in BW.
6)Build indexes on DataSource tables based on selection criteria. Indexing DataSource tables improves the extraction performance, because it reduces the read times of those tables.
7)Execute collection jobs in parallel. Like the Business Content extractors, generic extractors have a number of collection jobs to retrieve relevant data from DataSource tables. Scheduling these collection jobs to run in parallel reduces the total extraction time, and they can be scheduled via transaction code SM37 in the source system.
8). Break up your data selections for InfoPackages and schedule the portions to run in parallel. This parallel upload mechanism sends different portions of the data to BW at the same time, and as a result the total upload time is reduced. You can schedule InfoPackages in the Administrator Workbench.
You can upload data from a data target (InfoCube and ODS) to another data target within the BW system. While uploading, you can schedule more than one InfoPackage with different selection options in each one. For example, fiscal year or fiscal year period can be used as selection options. Avoid using parallel uploads for high volumes of data if hardware resources are constrained. Each InfoPacket uses one background process (if scheduled to run in the background) or dialog process (if scheduled to run online) of the application server, and too many processes could overwhelm a slow server.
9). Building secondary indexes on the tables for the selection fields optimizes these tables for reading, reducing extraction time. If your selection fields are not key fields on the table, primary indexes are not much of a help when accessing data. In this case it is better to create secondary indexes with selection fields on the associated table using ABAP Dictionary to improve better selection performance.
10)Analyze upload times to the PSA and identify long-running uploads. When you extract the data using PSA method, data is written into PSA tables in the BW system. If your data is on the order of tens of millions, consider partitioning these PSA tables for better performance, but pay attention to the partition sizes. Partitioning PSA tables improves data-load performance because it's faster to insert data into smaller database tables. Partitioning also provides increased performance for maintenance of PSA tables for example, you can delete a portion of data faster. You can set the size of each partition in the PSA parameters screen, in transaction code SPRO or RSCUSTV6, so that BW creates a new partition automatically when a threshold value is reached.
11)Debug any routines in the transfer and update rules and eliminate single selects from the routines. Using single selects in custom ABAP routines for selecting data from database tables reduces performance considerably. It is better to use buffers and array operations. When you use buffers or array operations, the system reads data from the database tables and stores it in the memory for manipulation, improving performance. If you do not use buffers or array operations, the whole reading process is performed on the database with many table accesses, and performance deteriorates. Also, extensive use of library transformations in the ABAP code reduces performance; since these transformations are not compiled in advance, they are carried out during run-time.
12)Before uploading a high volume of transaction data into InfoCubes, activate the number-range buffer for dimension IDs. The number-range buffer is a parameter that identifies the number of sequential dimension IDs stored in the memory. If you increase the number range before high-volume data upload, you reduce the number of reads from the dimension tables and hence increase the upload performance. Do not forget to set the number-range values back to their original values after the upload. Use transaction code SNRO to maintain the number range buffer values for InfoCubes.
13)Drop the indexes before uploading high-volume data into InfoCubes. Regenerate them after the upload. Indexes on InfoCubes are optimized for reading data from the InfoCubes. If the indexes exist during the upload, BW reads the indexes and tries to insert the records according to the indexes, resulting in poor upload performance. You can automate the dropping and regeneration of the indexes through InfoPackage scheduling. You can drop indexes in the Manage InfoCube screen in the Administrator Workbench.
14)IDoc (intermediate document) archiving improves the extraction and loading performance and can be applied on both BW and R/3 systems. In addition to IDoc archiving, data archiving is available for InfoCubes and ODS objects.
Hope it Helps
Chetan
@CP..

Memory dump in contract data load

Similar Messages

Maybe you are looking for