Hi,
There are most jobs that are exported as shell files and scheduled to run in third party tool.
Therefore, in case of failures, BODI/BODS jobs don’t generate error logs in job server log directory typically errors like 34/39.
Most relate to UNIX based semaphore logs/settings.
Please can you advise the best way to be able to trap and track the logs at BODS level.
Also any good way to track that CPU is utilized much due to poor coding/design of jobs.
Need best practices to avoid such kind of errors like out of memory, high CPU utilization etc.
Any useful links will be helpful too. Thanks.
its_ranjan (BOB member since 2011-02-16)