cancel
Showing results for 
Search instead for 
Did you mean: 

BIREQU* job taking long time after migration

Former Member
0 Kudos

Hello,

We are having an issue running in our R/3 system with BIREQU* jobs.

The job is taking long time after system's migration from another service provider.

The job which was taking around 1000 seconds before migration now takes approx. 30,000 seconds.

Also this happens only at a particular time (at around 17:30 CET) everyday.

The job runs at other times also but the run-time is normal (600 sec app.)

Please help me on this.

Thanks ,

Uday

Accepted Solutions (0)

Answers (3)

Answers (3)

manumohandas82
Active Contributor
0 Kudos

Hi Uday ,

BIREQU * Jobs are BI Extraction Jobs  . Though all of them start with BIREQU* , they might be essentialy totally different extraction Jobs .


You need to consult with your BI/BW team to confirm on the above and also  find out what is the extraction which is running  at around 5:30 PM


Possible cause 1 .


You may also need to check SMQS and SMQR and see how many trfc's process are allowed . , By default the number of parallel trfc's will be limited to 2 ( to a BI/BW system from R/3) , You might need to increase this to a  higher value ( Depending on the number of dialog process you have )


Possible cause 2 .


     The BI team might be doing a full extraction every time after the upgrade . If this is the case check with them whether delta extarctions are possible


Possible cause 3


Hardware bottleneck around that time . ( Like backup / other parallelly running jobs / Insufficient Dialog work process for th e TRFC


Take a trace of the job using ST12 , and see where the maximum runtime is cunsumed . Ie is it at the database / ABAP level .


Anyways you will need to closely work with the BW team to sort out this issue


Thanks ,

Manu

IanSegobio
Advisor
Advisor
0 Kudos

Hello there,

Is there any major difference between the "job log" from the execution with normal runtime and the affected ones?

Cheers,
Ian.

yakcinar
Active Contributor
0 Kudos

Hello Udaya,

Could there be backup process running and locking the records at that time of the day?

Regards,

Yuksel AKCINAR

Former Member
0 Kudos

Hello Yuksel Akcinar,

Thanks for replying.

There are no backups scheduled at this time .

Uday

Sriram2009
Active Contributor
0 Kudos

Hi Udaya

1. You can enable the trace in SAP R3 system check the over all DB usage.

2.  Those jobs are belong to SAP BI system extraction jobs, either you can hold the BI triggers during the peak time(on 17.30 hours)  or reschedules some other timings.

Regards

SS