Timed Out Error

[Former Member]

Hi Friends

I'm loading data into ODS and cube parelally.

The load failed on BW QA into ods and it has start routine on update rules and the load successful on Cube.

While updating into ods ,it's timed out.

How can we overcome with this Timed out problem.

Regards,

Chama.

[Former Member · Accepted solution]

In this case the number of records could be huge.

And since you have routines written in the update rules for the ODS it will take extra time.

To avoid the load from getting timed out you can go in for the following

Trigger the load when not many other jobs are running.

i.e when there are more free work processes.

since it is an ODS you can select the option to check for the SID (Master data) at the time of activation,thereby can reduce the load time.

If non of this helps then you will have to increase the time out time for the IP.

To do tat select the IP and under the scheduler option you hav "time out "

here increase the time accordingly.

Regards,

Savitha

[Former Member · Accepted solution]

Hi

I'm testing on QA and there are no other loads running .

How can we do this "since it is an ODS you can select the option to check for the SID (Master data) at the time of activation,thereby can reduce the load time"

I've checked scheduler in Infopack and wait time is setup to 2hours.

This same load ran successfully in Dev box but it's failing on QA with same settings.

Regards,

Chama.

Edited by: SAP BI on Aug 12, 2008 2:39 PM

Edited by: SAP BI on Aug 12, 2008 2:41 PM

[Former Member · Accepted solution]

Hi,

Reduce your data packet size to bring in less amount of data per infopackage. That should help. Your QA system will have more data volume than your test system.

Also check your routines from a performance perspective. Check where the most time is being spent at the time of data loading.

Cheers,

Kedar

[Former Member · Accepted solution]

Hi

Data packet size it set to 20000 and no of precessing is set to 3.

It's taking long while updating into cube which is on update rules.

The status is set to

'Delete status; back to request status'. by defualt.

Regards,

Chama.

Edited by: SAP BI on Aug 12, 2008 2:50 PM

[Former Member · Accepted solution]

Hi,

Reduce the data packet size even further. I strongly recommend to check any code in the update rules for performance. That might be your problem area. Also try to drop indexes on the cube before loading the data to the cube and then recreate them after loading is over.

Cheers,

Kedar

[Former Member]

hi,

Timed out problems may occur due to following reasons

1. RFC Connection problem

2. Server might be slow.

Did you check the connection b/w 2 systems ? Rt. Click on Source system and check ? Check in sm59 as well.

Did load turn red. i think setting the wait time can be changed.

In the Scheduler, you can set the maximum wait time after which a request is to be set to red in the Monitor for each InfoPackage. Do this via Scheduler -> Timeout-Time/Warning Handling. This setting overrides the system-wide setting for a particular InfoPackage(SPRO Setting).

you might want to verify that the extraction process is alive... sometimes if BW did not receive the data from the source system it could stay in YELLOW status and time-out eventually. If such case do happen then you have to check if it is IDoc-related problem or that your data is selected incorrectly via some exits or so.

Please ask basis in your project to extend the time to 3600 sec in the paramter rdisp/max_wprun_time.

assigning points is the way to say thanks

get back to me if you still facing problems

regards

vadlamudi