The database manager is not able to accept new requests
Posted: Tue Apr 01, 2014 1:50 pm
I am getting an error while running the job to insert data into a DB2 table. Our DB2 is on Mainframe and we are connecting through a gateway.
The error I am getting is
TABLE_ERROR,0: SQLExecute reported: SQLSTATE = 40003: Native Error Code = -1224: Msg = [IBM][CLI Driver] SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 (CC_DB2DBStatement::executeInsert, file CC_DB2DBStatement.cpp, line 578)
SQLEndTran(SQL_ROLLBACK) reported: SQLSTATE = 08003: Native Error Code = -99999: Msg = [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 (CC_DB2Connection::rollback, file CC_DB2Connection.cpp, line 1328)
Two columns of the TABLE_ERROR are CLOBs.
Using DB2 Connector stage. Keep conductor connection alive is set to no.
Lock Wait mode is set to - Wait Indefinitley and also tried with Use the lock timeout database configuration parameter.
I have contacted DB admin and he mentioned the problem is not on their side.
Please let us know why we are having an error. Do I need to provide anyother details ?
The error I am getting is
TABLE_ERROR,0: SQLExecute reported: SQLSTATE = 40003: Native Error Code = -1224: Msg = [IBM][CLI Driver] SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 (CC_DB2DBStatement::executeInsert, file CC_DB2DBStatement.cpp, line 578)
SQLEndTran(SQL_ROLLBACK) reported: SQLSTATE = 08003: Native Error Code = -99999: Msg = [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 (CC_DB2Connection::rollback, file CC_DB2Connection.cpp, line 1328)
Two columns of the TABLE_ERROR are CLOBs.
Using DB2 Connector stage. Keep conductor connection alive is set to no.
Lock Wait mode is set to - Wait Indefinitley and also tried with Use the lock timeout database configuration parameter.
I have contacted DB admin and he mentioned the problem is not on their side.
Please let us know why we are having an error. Do I need to provide anyother details ?