Showing posts with label settings. Show all posts
Showing posts with label settings. Show all posts

Friday, March 9, 2012

MSDTC w/ Oracle 8i EventID=4156

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?
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:

Originally posted by Mirna Da Costa
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?

MSDTC w/ Oracle 8i EventID=4156

On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MT
xOCI registry settings in order to correct the problem of failed ODBC connec
tions to an Oracle 8.1.7 linked server.
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
"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 th
e 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 l
ong 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 conn
ections to an Oracle 8.1.7 linked server.
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
> "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 do
wn the session.
> Since making the registry change, 328 of these errors have occurred to dat
e. 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 dat
e.
> 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
Mirna Da Costa wrote:[vbcol=seagreen]
> *Hello !!
> I have the exact same error message. Did you find any resolution for
> this '
> Mirna.-
>
> "elpepe" wrote:
>
> MSDTC\MTxOCI registry settings in order to correct the problem of
> failed ODBC connections to an Oracle 8.1.7 linked server.
> events in the application log - String message: Session idle timeout
> over, tearing down the session.
> to date. The first one occurred ~2 hours after making the registry
> change.
> requiring long access times (minutes) that used to take a split
> second.
> to date.
acsekar
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message808237.html

Wednesday, March 7, 2012

MSDTC settings in a cluster.

Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:

> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
[vbcol=seagreen]
> On the node that has control of the MSDTC resource. The cluster service ta
ke
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
>

MSDTC settings in a cluster.

Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
> On the node that has control of the MSDTC resource. The cluster service take
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
> > Hi everyone,
> >
> > I am new to this so any help will be much appreciated.
> >
> > I have a problem running triggers between two SQL servers. I am running
> > Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> > which pointed me to enable MSDTC by checking the Allow Outbound and
> > Allow Inbound checkboxes. My question is where do I set these boxes on
> > the cluster, on the nodes that make up the cluster or on both?
> >
> > Thanks for your help!
> > Eugene.
> >
> >