[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
"OracleXaLib"="oraclient8.dll"
"OracleSqlLib"="orasql8.dll"
"OracleOciLib"="oci.dll"
It appeared to fix our problems -- but...
After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
Since making the registry change, 328 of these errors have occurred to date.
Are there any suggestions on how to rectify this problem?
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:
> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?
|||below is the likely solution
PRB: MS DTC Event 4156: "Session Idle Timeout Over"
Article ID : 290334
Last Review : February 20, 2002
Revision : 1.0
This article was previously published under Q290334
On this Page
SYMPTOMS
CAUSE
RESOLUTION
REFERENCES
SYMPTOMS
You may see the following entry in the application event log:
String message: Session idle timeout over, tearing down the session.
CAUSE
This message indicates that the connection between a Distributed Transaction Coordinator (DTC) client and Microsoft Distributed Transaction Coordinator (MS DTC) is being torn down due to inactivity.
RESOLUTION
This message is usually just informational and can be ignored. Under normal circumstances, MS DTC tears down inactive connections after 10 minutes of idle time.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
197810 FIX: Upgrading DTC to Close Idle Connections
250987 HOWTO: Reinstall MS DTC for a Nonclustered Windows NT 4.0 Server
279786 HOWTO: Reinstall MS DTC for a Nonclustered Windows 2000 Serve
Quote:
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:
> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?
No comments:
Post a Comment