ODBC Oracle connection loses connectivity overnight
Hi this is a non urgent question but one which has foxed me for a long time...
I'm maintaining a certain number of Access databases for a department in a large company. Most of these databases link to Oracle via ODBC using Oracle in OraHome 9201 or 901. What sometimes happens is that when these databases are left on overnight, the next day when the user attempts some kind of processing the user gets a connectivity problem and attempting to reconnect the Oracle tables either via code or the 'get external data' feaure in Access results in some kind of access denied error. This seems especially true if the account is read/write. Even recreating the DSN has no effect, and the only cure seems to be to re-boot the PC.
Non-ODBC applications e.g. TOAD remain unaffected.
My theory is that because the Oracle database undergoes data import overnight it locks out read-write accounts and somehow ODBC doesn't have the nounce to realise that the lock has been released ... but I'm just clutching at straws. Does anyone else have any experience of this phenomenon or have any explanation why it occurs or how it may be circumvented ?
I'm maintaining a certain number of Access databases for a department in a large company. Most of these databases link to Oracle via ODBC using Oracle in OraHome 9201 or 901. What sometimes happens is that when these databases are left on overnight, the next day when the user attempts some kind of processing the user gets a connectivity problem and attempting to reconnect the Oracle tables either via code or the 'get external data' feaure in Access results in some kind of access denied error. This seems especially true if the account is read/write. Even recreating the DSN has no effect, and the only cure seems to be to re-boot the PC.
Non-ODBC applications e.g. TOAD remain unaffected.
My theory is that because the Oracle database undergoes data import overnight it locks out read-write accounts and somehow ODBC doesn't have the nounce to realise that the lock has been released ... but I'm just clutching at straws. Does anyone else have any experience of this phenomenon or have any explanation why it occurs or how it may be circumvented ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmmmmm, I wouldn't write anything to reboot the computers. Just shut down the Access DB's. If you don't want to shut down the DB's then you could write something to "disconnect" the db's from oracle while the import takes place.
Just my thoughts.
Just my thoughts.
ASKER
Time to wrap this one up. Just for the record dds110 when I said people had an attitude towards rebooting PCs I meant rebooting them normally, I wasn't intending for my application to do it.
I wish I could've been more help to you. Good luck with your issue.
ASKER