Driver sql1224n a database agent could not

Problem Type Select the Nature of the Issue reported. User Types Select the Type of Users involved. Project Phases Select the Project Phase. System Information Last Modified Date. To Be Removed Title. URL Name. Article Record Type. The Overflow Blog. Podcast Making Agile work for data science.

Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 1. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Even so, I don't think there is anyway this could cause the or Does someone else know if there is a resource problem with this scheme?

I have 2 connection handles the other one disconnects successfully but the other doesn't. I used the connection handle to allocate a statement handle for queries using scrollable keyset driven cursors. I don't get any error in the allocation, preparation,binding, execution and fetching with the statement handle but when I try to disconnect , it returns CLIE.

If I don't perform any queries I can disconnect without any problems. The other connection handle I use to allocate forward only statement handle for SQLColumns and queries that lists index column names.

Does anyone have a similar exeprience? Any comments? I really need your help. Thanks in advance. You could double check that all your work is finished all statement handles free successfully on the client before disconnecting. I will be willing to be that you are not even reaching the upper limit of the default number of connections You are most likely failing on the 11th connection. It most likely is the Java app that is using shared memory connections that is causing the failure.

Doing this requires the following modifications: 1. The loopback node and the database must be catalogued as if they were remote. Even though the redbooks suggest that the following can cause data corruption, they are revising their own words as what they wrote is apparantly BS! It basically comes down to the number of memory segments that you are using.

The work-around is to turn extended shared memory ON. Changing the return parameter of the Java function to be "int" got things working for me: import COM. Have a look at the manual to see how DB2 manages Java objects. I guess it works fine as procedure because the parameters expected on the stack actually do match a procedure does not give a scalar return value. Yes, thank you so much Knut. Those were my problems exactly. I had also played around with the external name, but had gotten misled because I was using the not fenced parameter and at the time thought I was crashing in DB2.

Thanks again - It will be nice to start making some real headway finally. In that style, you get the input and output parameters on the stack like this: void udfEntry inparameter1, inparameter2, inparameter3, outparameter, null-indicator-for-inparameter1, null-indicator-for-inparameter2, null-indicator-for-inparameter3, null-indicator-for-outparameter, This discussion thread is closed Start new discussion. DB2 Database.

DB2 8. Complex Database, Basic Knowledge. SQLN - A database agent could not be started to service a request.