Filter condition in ABAP Initial Load Job

Question

Hi,
   The ECC Initial Load JOb for IDM has been failing continuously because of 'Out of Memory' Exception
Error Description - Unhandled Error in DSERuntime - Exception:java.lang.OutOfMemoryError
   All the FROM PASSES except the "ReadAbapUsers" pass has been running successfully. We believe this could be because of the huge number of Users and User-Role Assignments(2,61,000) present in ECC System.
   Hence we thought of breaking down this process(ReadAbapUsers) into smaller chunks.i.e., fetch all the users with loginuid starting with 1; then 2; then 3 and so on... But we are not sure of the way to implement this. Please suggest an alternative.
Regrads,
Joel

Answer 1

Hi, I dont know if you have resolved this already or not.. but have you considered increasing the heap size ?
-->
Reading stuff from an ABAP system can return a lot entries. The  
roles/entries are returned in one big lump of data, and the runtime needs to      
have enough space on the heap for this.                                   
Solution                                                                  
The maximum heap size can be set in the dispatcher prop file.                                                                               
Locate the the correct dispatcher prop file.                                                                               
This file is a java properties file. It will be called                    
"Dispatcher_Service_<dispatchername>.prop" i.e. if the dispatcher name    
is "test", the file name will be "Dispatcher_Service_test.prop"                                                                               
Locate the section                                                        
    additional Java options                                             
Set the maximum heap size to the desired size.                            
i.e To increase the maximum heap size to 512 Mb, set                      
JAVAOPTIONS=-Xmx512M                                                                               
You can set more than one java option here, but if you do so, you also    
have to set                                                               
MXDISPATCHER_EXECSTRING=1                                                                               
Also note that increasing the heap size has a performance impact. We      
therefore do not recommend doing this for the main dispatchers. Instead,  
create a separate dispatcher for running large jobs, and do this change   
only for this dispatcher.                                                                               
See SAP Note 1347301