|
From: Tsuei, J. C. <jt...@dt...> - 2018-03-12 13:22:33
|
Squirrel and AQT or any client tools are using dynamic SQL (rather than COBOL on the mainframe that uses static SQL). SPUFI on the mainframe is using dynamic SQL too. Your DBA is 100% right. These tools will lock database catalog and directory. You should not leave your desk and go take coffee for 20 minutes after you received your SQL result set since it will still hold up locks. Even you have share lock it will still impact process that needs exclusive locks. Hope this helps to explain. DTCC Public (White) From: Rasmus Wiman [mailto:ras...@gm...] Sent: Monday, March 12, 2018 7:17 AM To: squ...@li... Subject: [Squirrel-sql-users] Squirrel locks DB2? ATTENTION! This email originated outside of DTCC; exercise caution. Hi, everyone. Our DBA dislikes that I use Squirrel-SQL. He says that it creates locks in the db. I don't understand this, it's extremely rare that I forget to commit (we are not allowed to use autocommit, regardless of what client we use) a transaction. We use DB2 and I connect to the databases using the IBM DB2 Net driver. I don't do anything people using other clients (AQT is popular here) don't do. How can I stop these locks from occurring? According to the DBA it's a generic JDBC issue that has no solution, is he right? Thanks, Rasmus DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. |
