cancel
Showing results for 
Search instead for 
Did you mean: 

Rollup / Compression Failure

rajat_agrawal2
Explorer
0 Kudos

Problem: The rollup or compression completes but still I get the message that the "Job was manually set to cancelled" and then the step turns red.

Been facing this problem for past few days. Not for any particular chain, but it seems to come everyday in some or the other chain and sometimes in more than one chain.

The logs for the same are as below

01:44:19|Job started

01:44:19|Step 001 started (program RSPROCESS, variant &0000003694151, user ID ALEREMOTE)

01:44:19|Start process COMPRESS ZPCD_FIADV_ACTLY_PV_006 in run 4ORZM127FRU3MTHGW6ARW0NFL of chain

01:44:20|Performing check and potential update for status control table

01:44:21|FB RSM1_CHECK_DM_GOT_REQUEST called from PRG RSSM_PROCESS_COMPRESS;

01:44:21|Request '1,844,053'; DTA 'ZFADVC03'; action 'C'; with dialog 'X'

01:44:21|Leave RSM1_CHECK_DM_GOT_REQUEST in row 70; Req_State ''

01:44:21|FB RSM1_CHECK_DM_GOT_REQUEST called from PRG RSSM_PROCESS_COMPRESS;

01:44:21|Request '1,845,040'; DTA 'ZFADVC03'; action 'C'; with dialog 'X'

01:44:21|Leave RSM1_CHECK_DM_GOT_REQUEST in row 70; Req_State ''

01:44:21|FB RSM1_CHECK_DM_GOT_REQUEST called from PRG RSSM_PROCESS_COMPRESS;

01:44:21|Request '1,845,047'; DTA 'ZFADVC03'; action 'C'; with dialog 'X'

01:44:21|Leave RSM1_CHECK_DM_GOT_REQUEST in row 70; Req_State ''

01:44:21|FB RSM1_CHECK_DM_GOT_REQUEST called from PRG RSSM_PROCESS_COMPRESS;

01:44:21|Request '1,845,048'; DTA 'ZFADVC03'; action 'C'; with dialog 'X'

01:44:21|Leave RSM1_CHECK_DM_GOT_REQUEST in row 70; Req_State ''

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845048 LINE 43

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 243

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_START_OK LINE 261

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845047 LINE 43

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 7 LINE 243

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845040 LINE 43

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 243

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_START_OK LINE 261

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1844053 LINE 43

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 243

01:44:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_START_OK LINE 261

01:52:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845048 LINE 43

01:52:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 273

01:52:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845047 LINE 43

01:52:24|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 7 LINE 273

01:52:25|Status transition 7 / 7 to 8 / 8 completed successfully

01:52:25|RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_OK LINE 317

01:52:25|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1845040 LINE 43

01:52:25|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 273

01:52:25|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR 1844053 LINE 43

01:52:25|RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 8 LINE 273

01:52:25|InfoCube ZFADVC03 Successfully Compressed Up To Request 1,845,048

01:52:25|Aggregation of InfoCube ZFADVC03 to request 1845048

01:52:25|Mass insert of transaction data executed (125484 data records)

01:52:25|P-DIMID 3142 deleted from table /BIC/DZFADVC03P (InfoCube ZFADVC03)

01:52:25|Request 1845040 was summarized correctly

01:52:25|P-DIMID 3144 deleted from table /BIC/DZFADVC03P (InfoCube ZFADVC03)

01:52:25|Request 1845048 was summarized correctly

01:52:25|DB Statistics: 00000000 selects, 02717741 inserts, 00000000 updates, deletes 00000000

01:52:25|Request with P-Dimid 1845048 from InfoCube ZFADVC03 deleted (1573515 data records)

01:52:25|Request with P-Dimid 1845040 from InfoCube ZFADVC03 deleted (1144300 data records)

01:52:25|Aggregation of InfoCube 101027 to request 1845048

01:52:25|InfoCube ZFADVC03 Successfully Compressed Up To Request 1,845,048

01:52:28|Event RSPROCESS with parameter 4GOTFACJ4MDC8MI42K1JZW101 successfully triggered

01:52:28|Job finished

01:47:17|Job status was manually set to 'cancelled'

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Rajat,

Seems some issue in the Infocube ZFADVC03's Aggregates. Check the aggregates! If there's any partial aggregates active/not-filled (Green-Red), then try to deactivate them completely & process the chain. There;s no harm in deactivation, but you might need to activate them & fill after a few weeks or so if user reports any slowness in BEx queries.

I had a similar issue, I 1st deactivated the aggregates, as the rollup status in the info cube was still in processing (AGG symbol : u2211); So, after deactivating the aggregates & ensuring no ACRs / process chains are updating this cube, I ran the 2nd FM as below.

1. SAP_AGGREGATES_ACTIVATE_FILL Activating and Filling the Aggregates of an InfoCube

2. SAP_AGGREGATES_DEACTIVATE Deactivating the Aggregates of an InfoCube

Best Regards, @{

Edited by: Arun Bala G on Feb 8, 2012 4:08 PM

rajat_agrawal2
Explorer
0 Kudos

@Siva - No Attr Change Run job was running at that time

@Arun - But sometimes the problem is with Rollup step only not the compression of aggregates. Anything which I can try for rollup as well ?

Former Member
0 Kudos

Rollup step only not the compression of aggregates

I think you got confused with the terms! Rollup means filling the aggregates. Compression means making RQID 0.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Can you check whether any Attr change run job is running at that time?

Regards,

Siva A