SAP IQ Cockpit leaves open shared locks in the IQ server after I log out from Cokpit

[fernando_amores]

Hello,

I hope someone knows how to solve this, as my experience with SAP tech support has not been that good.

I log in on Cockpit, go to the Explore tab. Open Schema Objects, open Tables, click on Tables, then select any table. I select its properties.

I connect to my IQ server (dbisql), run sp_iqlocks and find many shared locks.

Back in Cockpit, I log out from Cockpit.

Now from dbisql I see the Cockpit connection is still open (it seems Cockpit uses a connection pool) and the locks are still active. Few hours later, the IQ database starts getting full because those locks cause table versioning.

I looked at my SQL trail and the Cockpit connection opens an explicit transaction by issuing a set "chained" on command:

+1,<,1110,EXEC_ANY_IMM,set "chained" on

How can this be prevented?

Thank you,

Fernando

[fernando_amores]

Hello everyone,

I opened incident#428221/2016 with SAP support. They acknowledged the defect and the engineer in charge created KBA#2420936 (https://launchpad.support.sap.com/#/notes/2420936/E).

There is a CR 805248 for this.

Regards,

Fernando

[RolandKramer]

Hi,

Which is the SAP IQ version you are using? There were Updates also for the IQ Cockpit itself beside die IQ corrections.

See the latest SAP IQ Updates in the following Document - SAP First Guidance – SAP-NLS Solution with SAP IQ

Best Regards Roland