TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post Reply
User avatar
mce
Community Contributor
Posts: 332
Joined: Tue Jul 20, 2010 5:01 pm
OLAP Product: Cognos TM1
Version: Planning Analytics Local 2.0.x
Excel Version: 2013 2016
Location: Istanbul, Turkey

TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post by mce » Mon Jul 13, 2020 1:19 pm

Hello,

We upgraded from 2.0.7 to 2.0.9.1 in a test environment for one of our clients.
But TM1 server keeps crashing immediately when we execute TM1 processes connecting to Oracle DB via ODBC. Not only when executing the process, it crashes even when opening such processes in Architect. It happens in all such processes regardless of the SQL Query.
This is the last message seen in TM1 server log, before TM1 server dies.
2388 [2] DEBUG 2020-07-13 13:42:45.797 TM1.SQLAPI Doing SQLConnectW( "XXXXXX", "xxxxxxxx" )

Thanks in advance for all responses.
Regards

User avatar
ykud
Posts: 112
Joined: Sat Jan 10, 2009 10:52 am
Contact:

Re: TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post by ykud » Tue Jul 14, 2020 1:57 am

mce wrote:
Mon Jul 13, 2020 1:19 pm
Hello,

We upgraded from 2.0.7 to 2.0.9.1 in a test environment for one of our clients.
But TM1 server keeps crashing immediately when we execute TM1 processes connecting to Oracle DB via ODBC. Not only when executing the process, it crashes even when opening such processes in Architect. It happens in all such processes regardless of the SQL Query.
This is the last message seen in TM1 server log, before TM1 server dies.
2388 [2] DEBUG 2020-07-13 13:42:45.797 TM1.SQLAPI Doing SQLConnectW( "XXXXXX", "xxxxxxxx" )

Thanks in advance for all responses.
Regards
OS? We saw something similar on RedHat when oracle driver couldn't write to it's log and sent a message about it to TM1. And that 'i cannot write to my log' warning message from unixodbc was crashing TM1 server. Adding a log folder or fixing permissions for this log made the error go away.

Worth adding
TM1.ODBC=DEBUG
TM1.SQLAPI=DEBUG
to tm1s-log.properties to see if maybe there's anything coming back.

Cheers

ardi
Community Contributor
Posts: 109
Joined: Tue Apr 02, 2013 1:41 pm
OLAP Product: tm1, cognos bi
Version: 10.1
Excel Version: 2007

Re: TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post by ardi » Fri Oct 16, 2020 9:20 pm

mce wrote:
Mon Jul 13, 2020 1:19 pm
Hello,

We upgraded from 2.0.7 to 2.0.9.1 in a test environment for one of our clients.
But TM1 server keeps crashing immediately when we execute TM1 processes connecting to Oracle DB via ODBC. Not only when executing the process, it crashes even when opening such processes in Architect. It happens in all such processes regardless of the SQL Query.
This is the last message seen in TM1 server log, before TM1 server dies.
2388 [2] DEBUG 2020-07-13 13:42:45.797 TM1.SQLAPI Doing SQLConnectW( "XXXXXX", "xxxxxxxx" )

Thanks in advance for all responses.
Regards
Hey,

We are experiencing the same issue after upgrading to PA 2.0.9.2

Did you guys found any solution?

Thanks

User avatar
mce
Community Contributor
Posts: 332
Joined: Tue Jul 20, 2010 5:01 pm
OLAP Product: Cognos TM1
Version: Planning Analytics Local 2.0.x
Excel Version: 2013 2016
Location: Istanbul, Turkey

Re: TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post by mce » Sat Oct 17, 2020 11:26 pm

Upgrading Oracle Client to Oracle 12 solves the problem. PA 2.0.9.1 does not seem to support older Oracle client versions.

ardi
Community Contributor
Posts: 109
Joined: Tue Apr 02, 2013 1:41 pm
OLAP Product: tm1, cognos bi
Version: 10.1
Excel Version: 2007

Re: TM1 Server Crash with TI Processes with ODBC Data sources in PA 2.0.9.1

Post by ardi » Mon Oct 19, 2020 11:33 pm

mce wrote:
Sat Oct 17, 2020 11:26 pm
Upgrading Oracle Client to Oracle 12 solves the problem. PA 2.0.9.1 does not seem to support older Oracle client versions.
Thank you!

We managed to find an ODBC driver that works but that is not a Native Oracle driver and it does not support some SQL statement (does not support Transaction COMMIT / ROLLBACK)

This issue is also reported at IBM since 2018 but IBM as usually says this is an Oracle issue not a TM1 issue

Very frustrating

Post Reply