cancel
Showing results for 
Search instead for 
Did you mean: 

Short dump while compressing

Former Member
0 Kudos

When I loaded data into inventory cube through 2LIS_03_BX and when I am compressing it by unmarking "No Marker Update" it is going into short dump.

-


Run-time error "MESSAGE_TYPE_X" occurred

Erroranalysis

Short text of error mesage:

System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-3-

Technical information about the message:

Diagnosis

This internal error is a targeted termination since the program has an incorrect status.

Procedure

Analyse the situation and inform SAP

Message classe...... "BRAIN"

Number.............. 299

Variable 1.......... "RSMDATASTATE"

Variable 2.......... "RSM_DATASTATE_CHECK-3-"

Variable 3.......... " "

Variable 4.......... " "

Variable 3.......... " "

Variable 4.......... " "

-


Information on where terminated

The termination occurred in the ABAP program "SAPLRSMDATASTATE" in "DUMP".

The main program was "RSABW_START_NEW ".

The termination occurred in line 143 of the source code of the (Include)

program "LRSMDATASTATEF01"

of the source code of program "LRSMDATASTATEF01" (when calling the editor

1430).

-


132 FORM dump USING i_subrc TYPE sy-subrc

133 i_no_dump TYPE rs_bool

134 CHANGING e_err_text.

135

136 DATA: l_subrc(10) TYPE c,

137 l_text(30) TYPE c.

138

139 l_subrc = i_subrc. CONDENSE l_subrc.

140 CONCATENATE 'RSM_DATASTATE_CHECK-' l_subrc '-' INTO l_text.

141 e_err_text = l_text.

142 IF i_no_dump = rs_c_false.

>>>>> MESSAGE x299(brain) WITH 'RSMDATASTATE' l_text.

144 ELSE.

145 RAISE error.

146 ENDIF.

147

148 ENDFORM. " dump

-


Any help would be largely appreciated.

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Answers (3)

Answers (3)

Former Member
0 Kudos

The problem got solved. As refereed by Siegfried Szameitat I checked the

Note 754687 - Consulting :Admin.data target/initial filling/compression which helped me solve the problem.

If you want to delete a cube completely and then load requests into this cube, you must always roll up this request first into the aggregates before you can compress the requests because the aggregates are already active and filled as initial.

If you do not need any aggregates, deactivate the aggregates before the initial deletion.

If the initial deletion were NOT to set up the aggregates as initial after the deletion, the rollup would never run successfully in a process chain: You would always have to 'manually' check that the aggregates are filled as initial after every complete deletion.

Thanks everybody for all your help.

Varma

Former Member
0 Kudos

Hello Subramanya

Check the QM status of the load...sometime you see the request green but its QM status is yellow...try to do that and check if request is active...

Thanks

Tripple k

Former Member
0 Kudos

Pl check the request that you are trying to compress is updated to the cube.

Ravi Thothadri