We encountered a production issue on Friday where ARSSOCKD would randomly crash, on two occasions.
We turned on trace but i have concerns with using that in a production system with heavy loads/retrievals/queries, and the issue possibly not happening again. I noticed in our QA system that we are using the arslog user exit. I have never personally used
I tested bringing down DB2, and i saw all those errors in the syslog.log.
ARS0013E DB Error: [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 -- SQLSTATE=08003, SQLCODE=-99999, File=arsseg.c, Line=6269 does n
ot exist
ARS0013E DB Error: [IBM][CLI Driver] SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or ha
s terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 -- SQLSTATE=40003, SQLCODE=-1224, File=arsid.c, Line=30
78 does not exist
Are there any performance implications as to using the arslog user exit in a production system, primarily on the performance side of things? How would this be compared to using TRACE with ALL=3?