TM1 Forum

Posted: **Wed Jan 13, 2021 4:34 pm**

Hello,

We recently update all of our IBM applications (PA, CA, PAW, Controller, FAP, ..) and we started getting these error in our TM1Server log everytime we execute or open a TI:

Code: Select all

8288   []   ERROR   2021-01-10 04:00:24.664   TM1.SQLAPI   01000[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'DataSourceName'.
8288   []   ERROR   2021-01-10 04:00:24.664   TM1.SQLAPI   01000[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
8288   []   ERROR   2021-01-10 04:00:24.664   TM1.SQLAPI   01000[Microsoft][ODBC Driver Manager] Cursor library not used.  Load failed
8288   []   INFO   2021-01-10 04:00:24.685   TM1.SQLAPI   Checking Driver Capabilities for database "DataSourceName" 
8288   []   INFO   2021-01-10 04:00:24.685   TM1.SQLAPI         Driver supports SQLFetchScroll

Except these error message, everything behave as expected. I would like to know if there is a potential risk and/or what is the cause of that error message.

Thank you and have a nice day !

Note: if I uncheck the 'Use Unicode' box, the 3rd error disappear:

Code: Select all

2432   [36]   ERROR   2021-01-13 11:30:32.634   TM1.SQLAPI   01000[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'DataSourceName'.
2432   [36]   ERROR   2021-01-13 11:30:32.634   TM1.SQLAPI   01000[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
2432   [36]   INFO   2021-01-13 11:30:32.670   TM1.SQLAPI   Checking Driver Capabilities for database "DataSourceName" 
2432   [36]   INFO   2021-01-13 11:30:32.670   TM1.SQLAPI         Driver supports SQLFetchScroll

Posted: **Wed Jan 13, 2021 5:36 pm**

Have noticed this too. It seems the SQLAPI logger got a little too "verbose". I think this might be a bug and also might have already been patched in a fix pack.

See this https://www.ibm.com/support/knowledgece ... gging.html

Posted: **Thu Jan 14, 2021 1:53 pm**

Thanks Lotsaram,

I guess we need to understand what cause this error on our ODBC driver. I was thinking about removing TM1.SQLAPI logs from the tm1server log with the following line but I'm afraid I won't get the 'real' errors such as E16) Cannot connect to ODBC data source

Code: Select all

log4j.logger.TM1.SQLAPI=OFF

Posted: **Thu Jan 14, 2021 8:26 pm**

What is the version of your TM1 server? I have seen some in 2.0.8 but they disappeared after upgrading to 2.0.9.1.

Posted: **Thu Jan 14, 2021 11:25 pm**

macsir wrote: ↑Thu Jan 14, 2021 8:26 pm What is the version of your TM1 server? I have seen some in 2.0.8 but they disappeared after upgrading to 2.0.9.1.

PA 2.0.9.4 (11.8.00300.34)

Posted: **Wed Jan 26, 2022 8:48 pm**

I found this thread while looking at similar errors. In another location I was directed to the following IBM documentation that states they increased the logging of messages coming from ODBC drivers.

https://www.ibm.com/docs/en/planning-an ... 1serverlog

TM1 Forum

TM1.SQLAPI error message in TM1Server log

TM1.SQLAPI error message in TM1Server log

Re: TM1.SQLAPI error message in TM1Server log

Re: TM1.SQLAPI error message in TM1Server log

Re: TM1.SQLAPI error message in TM1Server log

Re: TM1.SQLAPI error message in TM1Server log

Re: TM1.SQLAPI error message in TM1Server log