Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MTS and Oracle (Again !!!)

Status
Not open for further replies.

Hennito

IS-IT--Management
Jan 29, 2002
1
GB
Hello all,

We have the following setup.

NT Server running MTS talking to Oracle 8 on Unix We have followed the Microsoft Technet document to the letter regarding MTS talking to Oracle, including reapplying the service pack and option pack.


Twice a day (at least) we get the following error written to the SQLNET.log on our MTS server. This causes an Oracle process on the Unix box to hit 100% processor utilisation and the only resolution is to kill the process which we have now set up automation to do. No errors are reported to NT event log and all performance monitoring shows normal behaviour.

Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\WINNT\System32\mtx.exe)(HOST=PROCENARCMTS01)(USER=Administrator))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.1.7.2.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.1.7.2.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 8.1.7.2.0 - Production
Time: 30-JAN-2002 10:07:13
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 126
nt OS err code: 0

Any ideas/experiences of anything similar would be appreciated especially from Oracle DBAs who have experienced problems getting MTS and Oracle to work.

Thanks
 
TNS-00126 Missing Connection Manager name and address in TNSNET.ORA

Cause: The Interchange name specified in INTCHG.ORA is not defined in the TNSNET.ORA file.

Action: Define one Connection Manager name and set of addresses for each Interchange in the network. Regenerate the configuration files.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top