Skip to Content

1. Problem

  IQ became unresponsive due to cognos connection.

  We can see many cognos client connections which are holding the cursor.

2. Cause

  It may be caused by the queryReuse functionality in Cognos.

  When this Cognos setting is enabled, it uses the IQ internal cursors and does not release them.

  This results in IQ has no more cursors available and IQ got unresponsive.

3. Resolution

  

   Here are possible solutions for both sides (IQ and Cognos).


    1) IQ

      : Increase the options below and switch.

 

1) “-gm”
2) “-iqgovern”
3) “max_cursor_count”


    2) Cognos

       : Cognos doesn’t  keep the connection open and holds the IQ cursors after having finished with queries.

       
        1) queryReuse = 0 or disable   

HTH

Gi-Sung Jang

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Chris Baker

    What about setting Force_No_Scroll_Cursors=’On’ in IQ?

    This prevents the use of IQ_SYSTEM_TEMP for maintaining cursors so the result set immediately streams back to the client.

    You will probably have to turn off QueryReuse on Cognos anyway to use this as leaving it on might open cursors as scrollable.

    Regardless, it does not make sense to share IQ cursors.  Reuse only makes sense for a slower DBMS where a shared cursor might help prevent an expensive query from running again.

    Chris

    (0) 

Leave a Reply