Running Data Studio Web Console 3.1.1 on Windows 2008 R2 server using CYGWIN with LUW 9.7 Fix Pack 7, I am getting frequent scheduled jobs reporting as "Failed" when they obviously completed correctly. It is getting quite annoying to have to open up the Job log to see the result to verify whether there was a failure. Even more frustrating is that 95% of the time the Error Message says only "null". After manually verifying a proper execution, I have come to accept this a successful execution, but this is obviously not the way the application should be functioning. I shouldn't have to guess at whether the a job reported as "Failed" is actually a failure.
Name: Daily backup for XXXDEV
CONNECT TO XXXDEV;
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
BACKUP DATABASE XXXDEV TO "\\xxxserver\D$\DB2\Backups9.7" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
BACKUP DATABASE XXXDEV TO "D:\DB2\Backups" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
CONNECT TO XXXDEV;
Start Time: 2012-11-04 17:03:00
End Time: 2012-11-04 17:11:14
Error message: null
Result: The job execution failed. Execution Status code 3
I am assuming that DSWC is having an issue finding the job execution in the log (with TRACE ON, when I get the null error message, there are no entries in the Job Manager log for the job).
Here is another example with an Executable/Shell script which is slightly different with a failure even though everything worked just fine:
Name: Export all
cmd /c rmdir \\\\xxxserver\\d$\\EXPORTED9.7\\PRD /S /Q
cmd /c mkdir \\\\xxxserver\\d$\\EXPORTED9.7\\PRD
cmd /c rmdir E:\\EXPORTED9.7\\PRD /S /Q
cmd /c mkdir E:\\EXPORTED9.7\\PRD
DB2MOVE XXXPRD EXPORT -u xxxxx -p xxxxx -aw
cmd /c xcopy E:\\EXPORTED9.7\\PRD\\*.* \\\\xxxserver\\d$\\EXPORTED9.7\\PRD\\
Start Time: 2012-11-05 08:07:38
End Time: 2012-11-05 08:22:08
Result: The job execution failed. Execution Status code: 3
Are these known issues with DSWC? It would be nice to have some reliability on the "Succeeded" and "Failed" statuses.
I am also having an issue with the Job History Settings. I have the setting at 10 days for 'Succeeded' and 10 days for 'Failed', but I am not seeing any purging of the Job History at all. I still have every job from 9/17 up through today in the Job History log.
If anyone has experience similar problems, I would appreciate any suggestions on how to correct this issue.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2012-11-12T00:33:46Z by bluey01
Pinned topic Several issues with Job Manager History/log in DSWC 3.1.1 on LUW 9.7 FP 7
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-12T00:33:46Z at 2012-11-12T00:33:46Z by bluey01
bluey01 110000ENQX41 PostsACCEPTED ANSWER
Re: Several issues with Job Manager History/log in DSWC 3.1.1 on LUW 9.7 FP 72012-11-12T00:33:46Z in response to RandyJ.MillerI understand your pain on this. I also had issues with the job scheduler. My first suggestion is to change the scheduler to never delete Job History - on linux the jobs just stopped running after some time. By settign the Job History to never delete, I got a stable setup. The product seesm to be buggy around this area - you can see details on this thread : https://www.ibm.com/developerworks/forums/thread.jspa?threadID=429312&tstart=45
Not sure if this will fix your problems, but if its related to the job manager history, its worth a try.