Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

background job taking long time

Former Member

‎11-28-2008 5:55 AM

0 Kudos

Hi All,

We scheduled the archiving deletion job in development system, it is taking 18 hr to delete just 700000 document from the database. When we ran the same job in test mode that time it has taken 1 hour in the same system. I checked in sm50 for number of work process. There are still 4 more background work processes are free. What could be the reason for this? Any pointers to this will help greatly.

Thanks in advance.

with regards,

Lata.

3 REPLIES 3

Sandeep_Kumar
Product and Topic Expert
Product and Topic Expert

‎11-28-2008 7:36 AM

0 Kudos

Hi,

If you are deleting the documents from database then please check the number of UPDATE processes available.

Rgds,

Sandeep

Former Member
In response to Sandeep_Kumar

‎11-28-2008 9:20 AM

0 Kudos

Hi Sandeep,

could you please explain me why UPDATE processes are required for deletion? and usually how many UPDATE work processes are required?

Thanks in advance.

With Regards,

Lata.

abdul_hakim
Active Contributor

‎11-28-2008 9:26 AM

0 Kudos

Hi,

Generally Archiving Jobs will take lot of time. When we used to schedule the archiving job for deleting the idocs(around 200000) it used to take 4 to 5hrs. What im suggesting you is Jus Check the system performance with your BASIS guys and try to delete fewer no of objects in a Job.

Cheers,

Hakim