Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi Ken I haven't tried it myself, but did you try to assign the SUB job to another server than the DB server? Logically one would think that the WRI job should inherit the executing target from the SUB job, but I don't know if it works like that in practice. If that doesn't work, check out the last section of the documentation in the link below. http://tiny.cc/sfv36 Regards, LEH From: Ken_Kwan via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com] Sent: 30. mai 2010 12:07 To: Lars-Erik Hallsten Subject: [sap-basis] Archiving - write job's execution target Posted by Ken_Kwan (SAP Basis) on May 30 at 8:01 AM Dear All, As you guys you know, whenever we trigger the Write Job via TxCode: SARA. A SUBMISSION job : ARV_FI_DOCUMNT_SUB20100527121927 will be created. When the SUBMISSION job: ARV_FI_DOCUMNT_SUB20100527121927 is completed, the WRITE job : ARV_FI_DOCUMNT_WRI20100530070050 will be trigerred. However, I realized that, the WRITE job being triggered by the SUBMISSION job will be automatically assigned with the DB server as the Execution Target. My question is, is that possible to avoid this ? Our WRITE jobs always get delayed due to there is only limited BGD work processes in DB server, and we don't plan to increase the DB server's BGD work processes because it will affect the DB server's performances. Kindly advise me on this. Thanks in advanced. Best Regards, Ken | __.____._ Copyright © 2010 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Lars-Erik Hallsten SAP Basis Enthusiast
Contributed 1,000 posts in a group to earn a Gold Achievement _.____.__ |