Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only
Back to discussions
Expand all | Collapse all

Harmless Errors in ODBC Driver 17 for SQL Server

  • 1.  Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Thu January 23, 2020 07:43 PM
    Hi, all
    I am testing PAL 2.0.8 and found there are the following two harmless errors in ODBC Driver 17 for SQL Server in the TM1 server log.
    But no such error in 10.2.2 for the same process. Any idea? Thanks.

    4936 [2] ERROR 2020-01-24 10:37:50.232 TM1.SQLAPI S1000[Microsoft][ODBC Driver 17 for SQL Server]Connection is busy with results for another command
    4936 [2] ERROR 2020-01-24 10:37:50.232 TM1.SQLAPI S1010[Microsoft][ODBC Driver Manager] Function sequence error

    ------------------------------
    mvp morgan
    ------------------------------

    #PlanningAnalyticswithWatson


  • 2.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Thu January 23, 2020 08:18 PM
    Interestingly, if I tick "Use Unicode" then, the errors are gone. If untick, then still appears.

    ------------------------------
    mvp morgan
    ------------------------------

    Original Message


  • 3.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Fri January 24, 2020 12:49 AM
    no, it is not right pattern. Some tables still pop up these errors regardless of "Use Unicode" is ticked or not.

    ------------------------------
    mvp morgan
    ------------------------------

    Original Message


  • 4.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Fri January 24, 2020 08:32 AM
    Hi Morgan,

    Sounds like a minor defect!  Can you open a support ticket (PMR) for this?

    I'm fairly certain we didn't change anything specific to our ODBC code since 10.2.2.  Also worth noting that TM1 is simply showing the error from the SQL Server driver.  It's not our own error.  Did the SQL Server driver version also change when updating from 10.2.2 to PA?

    ------------------------------
    Stuart King
    IBM Planning Analytics Offering Manager
    ------------------------------

    Original Message


  • 5.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Fri January 24, 2020 04:48 PM
    Edited by System Admin Fri January 20, 2023 04:26 PM
    Hi, Stuart
    Thanks, I will probably test some more to see before I raise PMR with our business partner. Some points,
    1. 10.2.2 also uses ODBC Driver 17 for SQL Server but PA got a bit newer version.
    2. ODBC Driver 13 for SQL Server and even older ODBC Driver for SQL Server still gave these same errors when testing the same process.
    3. Seems like only some specific queries or tables will give out these errors.
    4. Have tried     UseSQLFetch, UseSQLFetchScroll and UseSQLExtendedFetch, seems no difference.
    5. Have tried MARS_Connection=Yes in ODBC, previous testing can suppress this error but now, seems not working anymore.  And TI process performance is slowed down with this ODBC change.

    ------------------------------
    mvp morgan
    ------------------------------

    Original Message


  • 6.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Tue February 04, 2020 04:13 PM
    Hi, Stuart
    I think I found a way to reproduce this error.
    1. creating a new process based on ODBC connection with SQL query from any table/view
    2. untick "Use Unicode"
    3. put one line code with anything in Metadata. e.g. "x=1;" and leave all other tabs. But if the same code in Data, no ODBC errors pop up.
    4. run the process and you will have those errors.

    There are three ways to resolve it,
    1. Ignore it as they look harmless so far and only appear when Metadata tab has codes in it with Unicode unticked.
    2. Tick "Use Unicode"
    3. Set "MARS_Connection=Yes" in ODBC connection
    However, the #2 and #3 will result in downgraded TI performance to a large extent. 
    These errors can appear in all different kinds of SQL Server ODBC drivers as I tested as long as you have the process setup as above. Therefore, I agree it could be a minor bug in PA. I have sent an email to our business partner. They could submit a ticket later. Thanks.


    ------------------------------
    mvp morgan
    ------------------------------

    Original Message


  • 7.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Fri January 24, 2020 10:49 AM
    looks like there is something lock the connection. Maybe there is sql command executed and cannot stop?
    you can test the any sql command in the server, in your local and see the result to find which sql command causing the problem

    ------------------------------
    Veronika Gultom
    ------------------------------

    Original Message


  • 8.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Fri January 24, 2020 04:50 PM
    Thank, SQL server end is fine and command can be executed successfully in SSMS. Even TI can be cancelled successfully.

    ------------------------------
    mvp morgan
    ------------------------------

    Original Message


  • 9.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Mon January 25, 2021 10:49 AM
    Just an FYI, we started getting these exact errors when we first upgraded to 2.0.94.24.  We downgraded back to the prior version when we found a substantial bug that required that version to be pulled.  Immediately after upgrading again to version 2.094.51 the issue returned though it does seem harmless....

    ------------------------------
    Scott Schatz
    ------------------------------

    Original Message


  • 10.  RE: Harmless Errors in ODBC Driver 17 for SQL Server

    Posted Mon January 25, 2021 11:08 AM
    Please see: https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_nfg.2.0.0.doc/c_paw_nfg_enhanced_error_logging.html

    In short, the ODBC error were always happening, we just expose them in the tm1server.log file now.  Assuming the TI processes and ODBC connection worked before 2.0.9.4, we would expect them to work the exact same way in 2.0.9.4.  The error messages can be safely ignored or you could try and address them in the ODBC configuration.

    ------------------------------
    Stuart King
    IBM Planning Analytics Offering Manager
    ------------------------------

    Original Message


Related Content