2037093 - Consulting: Performance / Memory problems during delta/init in the status management with DTPs between infoproviders

• A DTP is executed either in delta or init mode (with or without data transfer) and the administration of the requests takes longer than expected.  Under certain circumstances the following dump might happen:

"TIME_OUT" " "
"CL_RSSM_STATMAN===============CP" or "CL_RSSM_STATMAN===============CM
"CHECK_STATUS"
The variable ME->P_H_REQMAP (Table IT_34299[62128x356]) contains a huge amount of records (>= 1.000). This variable can be found in the dump in ST22.

In case of an Oracle Database, at peak loading times the system generates a huge redo log for the tables TESTDATRNRPART* , which in a long term can cause database related errors and performance issues.

• A DTP is executed either in delta or init mode (with or without data transfer) and the closure of the request produces the following dump:
  
  "TSV_TNEW_PAGE_ALLOC_FAILED"
  "SAPLRSSTATMAN" bzw. LRSSTATMANU12
  "RSSTATMAN_UPDATE_DATASTATE_EXT"
  
  The internal table I_T_PART has more several thousand entries.
• A Transactional Infocube is updated and the following dump happens when the APO Request is closed:

    "TSV_TNEW_PAGE_ALLOC_FAILED"
    "SAPLRSS2" LRSS2U41
    "RSS2_CHECK_DM_FOR_VALID_SID"
 
>>>>>   sort l_t_part by partnr ascending.
  382   loop at l_t_part.

The internal table L_T_PART contains a high number of records (more than 1.000).

Independently of the used database and the volume of the loaded data (even when 0 records are loaded), one of the following can occur:

• The request activation of a standard DSO takes longer than expected.
• The exectuion of a DTP takes longer than expected during the status transition to "Executable".
• The execution of a DTP takes longer than expected during the status transition to "Set overall status to 'Green'".
• Callback to the Process Chain takes unusually long.
• Various memory dumps can happen (TSV_TNEW_PAGE_ALLOC_FAILED, SYSTEM_NO_ROLL) at certain stages of the DTP execution.
• DTP target contains the message: "Data Target Critical - Large Number of Request and/or Quick Growth"

Read more...

• SAP NetWeaver 7.0, 7.01, 7.02, 7.03, 7.3, 7.31, 7.4, 7.5

SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

RSSM_REDUCE_REQUESTLIST, RSSM_EXPAND_REQUESTLIST, request, DataStore object, DSO, InfoCube, write-optimized DSO, reduce, manage, administrate, 620361, RSSM_PROCESS_REQUDEL_MDT, RSS2_AUTODEL_REQU_MASTER_TEXT, RSSM_AUTODEL_REQU_MASTER_TEXT, delete requests, master data, texts, IOBJ, InfoObject, performance, rsiccont, rsreqdone, rsmonicdp, checkpoint, TESTDATRNRPART, lock, locking, sperre, sperrsituation, TESTDATRNRPART0, TESTDATRNRPART1, TESTDATRNRPART2, TESTDATRNRPART3, TESTDATRNRPART4, TESTDATRNRPART5, TESTDATRNRPART6, TESTDATRNRPART7, TESTDATRNRPART8, TESTDATRNRPART9, TESTDATRNRPARTA, TESTDATRNRPARTB, TESTDATRNRPARTC, TESTDATRNRPARTD, TESTDATRNRPARTE, TESTDATRNRPARTF, TESTDATRNRPARTG, TESTDATRNRPARTH, TESTDATRNRPARTI, TESTDATRNRPARTJ, TESTDATRNRPARTK, TESTDATRNRPARTL, TESTDATRNRPARTM, TESTDATRNRPARTN, TESTDATRNRPARTO, TESTDATRNRPARTP, TESTDATRNRPARTQ, TESTDATRNRPARTR, TESTDATRNRPARTS, TESTDATRNRPARTT, TESTDATRNRPARTU, TESTDATRNRPARTV, TESTDATRNRPARTW, TESTDATRNRPARTX, TESTDATRNRPARTY, TESTDATRNRPARTZ, rsar051, rsar 051, Enq hold by WP/My WP - Host/My Host, Data load issue, Unable to trigger any loads all resulting in MESSAGE_TYPE_X dumps , Data Load Error , BW loads are getting failed  Frequently, data load error , load data failed RSSM_DELETE_MY_ICUBETABS DISABLE DELTA LOG  , KBA , BW-WHM-DST , Data Staging , BW-WHM-DST-DTP , Data Transfer Process , BW-SYS-DB-ORA , BW ORACLE , How To