DB2EffPrcc,0: Fatal Error: Fatal: [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
[IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
SQLFetch: Error retrieving results from server.
No workaround since the issue's cause hasn't been identified. What about the answers to the second question - is this a new problem or did it work before? Does it affect just this job/table/database?
ArndW wrote:No workaround since the issue's cause hasn't been identified. What about the answers to the second question - is this a new problem or did it work before? Does it affect just this job/table/database? ...
This is a new problem.
There is a sequence with 7 jobs in it.
l1,l2,l3,l4,l5,l6,l7.
The job l4 is aborting with the above error. Once l4 runs then the next job is triggered.
Do you have any jobs that can read from or write to DB2 that are working? If yes, do you have any jobs that can read from or write to this particular table with this particulare userid that are working?