We have a sequencer that triggers 35+ jobs in parallel which reads from multiple tables of single database (Same schema) and writes into dataset. Jobs are failing randomly due to the below errors. Change in the error is job name. Rest all same. Job completes successfully When we re-ran the failed job. Do we need to set any configuration setting
dbeR_RT_LI_SVFS_ASSOCIATE_src: The connector could not establish a connection to DB2 database XXXX using user username1.
dbeR_RT_LI_SVFS_ASSOCIATE_src: SQLConnect reported: SQLSTATE = 08001: Native Error Code = -30,081: Msg = [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "10.88.123.54". Communication function detecting the error: "connect". Protocol specific error code(s): "111", "*", "*". SQLSTATE=08001 (CC_DB2Connection::connect, file CC_DB2Connection.cpp, line 840)
We are running with one compute node and db2 is catalogued. Both type of jobs that completed successfully and failed are executed from same compute node.
on second thought ask DB2 admin if the listener goes down intermittently or if there are any connctivity issues between the servers or if you are hitting the connection limits.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
You obviously have a resource issue... but what exact resource I can't say but I'd double-check your kernel parameters. First thought - run fewer jobs at the same time. Regardless of settings, resources are not infinite.
-craig
"You can never have too many knives" -- Logan Nine Fingers
