Oracle ODBC intermitent connection failure

Post Reply
jed
Posts: 56
Joined: Wed Sep 02, 2009 11:33 am
OLAP Product: TM1
Version: 10.2.2
Excel Version: 2016
Location: Australia

Oracle ODBC intermitent connection failure

Post by jed » Fri Sep 06, 2019 5:17 am

We have a strange situation with Oracle (oracle 12cR2client 32bit) failing on connection.

2 identical servers (same OS, same ODBC drivers, same TM1 version (10.2.2), same TM1 data)...TI updates from ERP scheduled every 30 minutes. On one server some of the TI processes fail at every run (different processes failing each time) but on the other server it never fails.

This is currently causing a massive headache as the one failing is on our production server and IT are scratching their heads as to why and what the difference is between the 2 servers.

Any ideas of what we could look into?

User avatar
tiagoblauth
Posts: 20
Joined: Wed Jul 08, 2015 11:50 am
OLAP Product: TM1, Cognos BI
Version: 10.2.1
Excel Version: 2010

Re: Oracle ODBC intermitent connection failure

Post by tiagoblauth » Mon Oct 14, 2019 5:12 pm

I had a similar case and it was network failure. Monitor network and try to use an Oracle client to do some tests.

User avatar
macsir
Community Contributor
Posts: 677
Joined: Wed May 30, 2012 6:50 am
OLAP Product: TM1, SSAS
Version: 9.5 - 10.2
Excel Version: 97 - 2013
Contact:

Re: Oracle ODBC intermitent connection failure

Post by macsir » Mon Oct 14, 2019 8:03 pm

Any detailed log info?
In TM1,the answer is always yes though sometimes with a but....
http://tm1sir.blogspot.com.au/

jed
Posts: 56
Joined: Wed Sep 02, 2009 11:33 am
OLAP Product: TM1
Version: 10.2.2
Excel Version: 2016
Location: Australia

Re: Oracle ODBC intermitent connection failure

Post by jed » Tue Oct 15, 2019 12:49 am

Just thought I'd post an update...after a month of connection failures whenever we loaded data from ERP we discovered that the source of the problem was that someone in IT had decided to setup network teaming on our server. Would have been good if they told us they were making a change :roll: we could have avoided 4 weeks of escalating the issue till it finally got to the people who said "Oh yeah, we made a change that could have caused this problem"...seriously :x

Post Reply