Open ODBC Connections

[cdhodge2002]

So I have a IT person who is saying that for time I ping their database I open a new session to their server. This being true but apparently TM1 is not closing the session and Each new load opens a new session. So after a month or so 100+ sessions are open and don't close until the TM1 server is rebooted. Is there a way to close these sessions other than putting a ODBCClose formula at the end of every process?

[Kyro]

I've only ever seen this happen when TI Processes (Which have a ODBC Datasource) abort. Perhaps check if thats been happening.

[paulsimon]

Hi

Are you simply reading from ODBC or are you using ODBCOpen, ODBCOutput and ODBCClose to output data? If its the former, then check to see whether there is an error of some sort that is preventing the connection from being closed. For example, is the process completing successsfully or is it erroring? I have never had a problem with connections being left open but I guess it will depend on the version of TM1 and the database.

If its the latter, check that ODBCClose is always being executed, eg there is no conditional logic that could stop it.

If there is nothing obvious, work with the DBA to monitor the connection.

Regards


Paul Simon

[lotsaram]

Likewise I have only ever seen ODBC connections stay open if a process aborts. If the process completes successfully or with minor errors then the connection should close. If a process aborting is causing your problem then adding ODBCClose to the Epilog won't do anything since the Epilog code won't be executed as the process has already aborted. You need to fix what is causing the abort error in the first place.