cancel
Showing results for 
Search instead for 
Did you mean: 

BIA Rollup failure with Remote communication failure

kuzhanthaivel_s
Explorer
0 Kudos

Hi,

In Process chain BIA rollup for cube getting failed.

Error message: Remote communication failure.

In sm21 : TREX_ICM - receiver error; return code = 402,return text = ICM_HTTP_TIMEOUT

Accepted Solutions (0)

Answers (2)

Answers (2)

natsuka_rastert
Explorer
0 Kudos

Hi Kuzhanthaivel,

The processchain failed due to ICM timeout, which means BWA was running long without respoinding to BW and ICM timeout was reached.

If the problem happens only one specific cube, there are some points to be checked.

1) Check ICM log

Please check the log in ICM trace file on the server where a processchain was running.

To see ICM trace file, please go to the server in SM51, call transaction SMCIM, navigate 'Goto' -> 'Trace File' -> 'Display All'.  Find the log when the code=402 ICM_HTTP_TIMEOUT happened.

Do you see 'temporarily out of MPI buffers-> rollup' message? If so, check the parameter 'mpi/total_size_MB' as per note 737625.

2) Check HTTP timeout value

When the job was cancelled due to the timeout? Was it while sending the data to BWA?

Please check how long it took since the last package was sent to BWA until the error happened.

This number should match to the value configured in TREXADMIN -> ABAP Customizing -> HTTP time out [seconds].

You can increase the timeout value to 3600 (1 hour) or 7200 (2 hours).

But usually a rollup/changerun process does not require so long in BWA. You should find out why BWA takes so long.

3) Check the index size

Is the index big but not split?  If the index should be split usually but is not split, please rebuild the BWA infocube or the index itself as per note 1789310 to make the index split.  You may not need to change 'initialReorg' if note 2103642 is implemented.

I cannot say much without checking the system.

It the above things do not help to your issue, please open an incident so that we can check further.

Kind Regards,

Natsuka


SAP Support

former_member220624
Contributor
0 Kudos

Hi,

Seems to be a temporary issue,can you repeat the step and check.

It would be good to have Basis team involved in case the issue persists.

Regards,

Amit

kuzhanthaivel_s
Explorer
0 Kudos

Hi

thanks Amit

We are repeated only solving this everyday.

while checking basis team RFC's are fine.

BIA is overloaded.

Regards,

Kuzhanthaivel.