ODBC Locking Database Issue

[Eric]

I have an access database where I have drill's setup from TM1 to show detail. It appears that there is an open ODBC connection keeping the database locked. I do not think it is the TM1 server because all TM1 services run under user tm1app and the ODBC lock is from user admin.

So I guess my question is to confirm my theory.

Does the TM1 ODBC connect with the service user,"tm1app", or are they run by a different user,"admin"?

* I also double checked. The DSN ODBC Connection is NOT setup with a fixed user and password.

[Steve Rowe]

Hi Eric,

I had a lot of trouble with TM1 locking an access DB it was loading data from. It seemed that often a lock was left behind or I would get strange out of memory issues being reported from ODBC.

I was not able to solve this and in the end I had to restart the box to clear the issues. There is a thred on this somewhere but I can't find it.

Cheers

[Martin Erlmoser]

we have this problem also with access dbs,.. recycle the server and it works again
but sorry i don't have a better solution

[Eric]

Found out a few things.

1) If you open the .ldb file in notepad it tell you all of the users that are connected
2) ODBCClose(); Does not work


Still no answer other than reboot. Still looking though the "jet engine" for something.

[Alan Kirk]

Found out a few things.

1) If you open the .ldb file in notepad it tell you all of the users that are connected
2) ODBCClose(); Does not work

Still no answer other than reboot. Still looking though the "jet engine" for something.

Just a couple of random, untested thoughts... often locking problems in Access result from a database being opened in Exclusive mode. Might be worth checking both the default open mode in the .mdb (Tools -> Options -> Advanced) and the DSN Configure... -> [Options] and make sure that the default mode is Shared and the Exclusive box is unchecked, respectively.