|
- Alan
rob@xxxxxxxxx wrote:
1) There should be two messages in the joblog: Submitted, and actually started. The job scheduler may have submitted it to a busy job queue?
2) When the job scheduler submits it. Perhaps something else has a lock on something. Like your nightly backup. While it is running check 12. Work with locks, if active. If it isn't a lock, other performance issue? Perhaps your system runs a night/day job that switches around memory pools?
3) Check the job description used by the job scheduler entry. Thinks like classes, etc may come into play here.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
