Records in Extractor que stucked and got missed in BW

[Former Member]

Hi Experts,

In BW we found Infopackage picking '0' records from past 3 days and on analysis came to know that V3 jobs got stucked in r3 in LBWQ for the same duration of 3 days and the records for the same missed too in BW.Even though the LUWs are running now normally we are not getting the stucked LUWs to delta queue there by BW too. Now My ONLY QUESTION IS HOW TO RECOVER THE DATA FOR THE STUCKED LUWs in LBWQ(Extractor queue). which team will be responsible for this to do and what could we suggest them to do to get the only the missed luws.

Thanks in Advance

Thanks and regards

Raju.M

[Former Member]

Hi Raju,

This is the source system's admin team's responsibility. They should check regularly if the jobs have been running.

Have you found out why the jobs were not running. Or if they failed then why? I guess a structure change might have occurred.

If you can find out which records are to be loaded then you can fill the setup table and do a full repair load.

Regards,

Sujit.

[RamanKorrapati]

Hi Raju,

Please name data source and data flow design.

When the Luws are stucked, bw team need to inform basis team. basis team can do manually executing at SM58.

This is purely related BW team, who are montoring daily loads as per shifts. Once they got the error they need correct  it on first day it self or need to info to TM.

by doing repair full load at info pack  you can get missed records to psa.

Thanks