Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Deadlock by API_Cursor SQL Server

  1. How-to
0
Votes
Undo
  1. Alexander Skorokhodov
    Alexander Skorokhodov
  2. PowerBuilder
  3. Sunday, 27 June 2021 14:05 PM UTC

Dear community:

This is not a PBL issue, but maybe someone has experience here:

My clients DB is deadlocked, and the culprits are multiple 

FETCH API_CURSOR0000000000000...
processes coming from the API Server.
How to disable such processes?
 
thank you, sasha
Table blob cannot be found?
FYI: Create multiple DSNs from a single PostgreSQ...
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 28 June 2021 20:21 PM UTC
  2. PowerBuilder
  3. # 1

Hi Alexander;

  Did you try disabling the SS MARS (Multiple Active Result Sets) option on your SS connection to see if that might be causing a collision error?

ie: SQLCA.DBParm = "ProviderString='MARS Connection=False'"

Regards ... Chris

Comment
Alexander Skorokhodov
  1. Alexander Skorokhodov
  2. Monday, 28 June 2021 22:19 PM UTC
Chris:

Thank you for advise, will try and let you know.

sasha







  1. Helpful
Alexander Skorokhodov
  1. Alexander Skorokhodov
  2. Tuesday, 29 June 2021 18:16 PM UTC
Chris:

So far, it appears that the issue was different here: in a couple of my SPs, selects fetched records based on field with missing index. A tool http://www.sqlnuggets.com/blog/sql-scripts-how-to-find-missing-indexes/

has been run, and it helped to fix this problem.



Your fix has not been installed, waiting on further development of situation.

thank you again

sasha

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 29 June 2021 18:22 PM UTC
Hi Sasha ... I am super glad that you found the issue on your end! :-)
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.