cancel
Showing results for 
Search instead for 
Did you mean: 

Request Still Running -Reg

0 Kudos

Good morning Gurus,

While i am extracting the Data... i get the following error...

Kl. guide me..

Request still running

Diagnosis

No errors could be found. The current process has probably not finished yet.

System response

The ALE inbox of the SAP BW is identical to the ALE outbox of the source system

and/or

the maximum wait time for this request has not yet run out

and/or

the batch job in the source system has not yet ended.

Current status

Second step in the update

Regards,

Murugesh R

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

see the max set time for infopackage laod is 7hrs,and also go to job overview and job log.

check also sm50,whether ur process is running or not.

cheers,

shana

Assigning pts is the way of saying thanks in sdn

Answers (5)

Answers (5)

former_member204514
Contributor
0 Kudos

Hi ,

Can you check what is your second processing??

Since if it is the activation, then just change the status to green in manage screen of the Cube or DSO and then manually activate it.

I encountered with the same issue but manual activation helps me. But make sure that no of transfer records and added records.

Hope it helps...

Assaign points if helps...

Regards,

aanand

0 Kudos

Thanx for all ..

Thanks and Regards,

Murugesh R

0 Kudos

Thanks

Closed.

Former Member
0 Kudos

It dont appear to be an error....how long you waint until cancel the load?

Regards

Former Member
0 Kudos

Hi Murugesh,

In the RSMO tcode, click on this long running IP and then goto Environment>job overview> source system...

u can check the porgress of this job in the source system.

Else u check for any TRFC stucks in the source system.

to see this follow Environment> TRFCs-> in source system or use TCODE SM58

Then if there few TRFCs in recorded mode push them by clicking on them and press F6 (this is to execute the LUWs)

If there are many such TRFCs records in recorded state then u use the program "RSARFCEX " in the TCODE SE38

pls assing points, if this was useful

Regards,

Kalpana M.

former_member345199
Active Contributor
0 Kudos

Hi,

I will suggest you to check a few places where you can see the status

1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.

Also see if there is any 'sysfail' for any datapacket in SM37.

2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.

3) RSMO see what is available in details tab. It may be in update rules.

4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)

5) Check in SM58 and BD87 for pending tRFCs and IDOCS.

Once you identify you can rectify the error.

If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.

If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.

If you feel its active and running you can verify by checking if the number of records has increased in the data tables.

SM21 - System log can also be helpful.

Thanks,

JituK

Former Member
0 Kudos

Hi,

here ur job load time is crossed the predefined time... u can change the max wait time for task.. IN monitor of the load.. and there at menu bar..

either at extras or in environment u can see the wait time update option for loads... when u click that.. u can see the actual wait time that has been allocated to ur process...

Here u can change this to some where to 9hrs and and then refresh the screen.. now ur request will come back to yello status..

Also check whether the request is running or not in SM37 and in SM50.. and also check if there is any updates are going on!!!!.. if updates are not goingon for long duration then u can think of reload.....

if the updates are going fine then u can wait for some time to finish then load.. once the load is finished then u can change the wait time back to normal..

Thanks

assign points if this helps