Symptom
The activation of a request of DSO/ADSO takes longer than expected. The slow/hanging statement can look like this:
SELECT DISTINCT <FIELDNAME>
FROM <ADSO_AQ_TABLE>
WHERE ( ( <FIELDNAME> ) NOT IN (
SELECT <FIELDNAME>
FROM <CHARACTERISTIC_SID_TABLE>
WHERE DATAFL = 'X' ) )
In scale-out systems this problem is more likely to happen.
In SM12, tables RSENQ_PROT_ENQ and RSPCENQUEUE may be locked.
The BI_PROCESS_ODSACTIVAT job log can have the following entries:
RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 2 LINE 243 RSAR 051
Status transition 2 / 2 to 7 / 7 completed successfully RSBK 222
RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_START_OK LINE 261 RSAR 051
Read more...
Environment
- SAP NetWeaver 7.50
- SAP BW/4HANA
Product
Keywords
stucked, stuck,CL_SQL_STATEMENT==============CP, Sequential Read of DB , KBA , BW4-DM-ADSO , DataStore Object (Advanced) , BW-WHM-DBA-ADSO , DataStore Object (advanced) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.