About bearparc

A software development blog for the qualified developer

Blogroll

Application Server (24)
Business Intelligence (13)
Business Logic Layer (6)
C (3)
C++ (4)
CMMI (4)
Data Mining (3)
DataMart (11)
DataWarehouse (11)
ETL (7)
FAQ – Troubleshooting (8)
Framework (4)
Hardware (10)
Informatica Powercenter (6)
Investition (2)
J2ee (8)
Java (6)
JBoss (1)
Liferay (11)
LINUX (12)
matlab (3)
objektorientiertes Design (2)
OLAP (7)
Oracle (54)
Projektmanagement (5)
Prozeßmodelle (4)
Software (43)
SQL (28)
Uncategorized (41)
Web 2.0 (5)
Weblogic (17)
wordpress (5)
XML (2)

WP-Cumulus by Roy Tanck and Luke Morton requires Flash Player 9 or better.

www.brokerbase.ch network

Search



Add to Technorati Favorites Blogverzeichnis - Blog Verzeichnis bloggerei.de Deutsches Blog Verzeichnis blogoscoop Add to Google http://www.wikio.de
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

« | Main | »

ORA-12537: TNS: connection closed error

By Martin | August 30, 2010

The ORA-12537 is an information message and means that the connection has been closed. This can be caused by a number of reasons:
1. Database is shut down (maybe for nightly backup), but connection to database was kept by client.
2. A time-out occurred on the client-connection.
3. When firewall closes idle connections.
3. A configuration problem in sqlnet.ora or listener.ora.
4. You have a path name that is too long for the Oracle TNS client on windows. (MetaLink Note:263489.1 )

This issue is due to the connection string being large enough that the connection packet is being split into two packets and then sent to the listener. There are several workarounds for the issue.
a. Install the exe in a shorter named directory.
b. Modify the TNS Names entry so that it is shorter.
c. Replace domain names with IP Addresses if that shortens and vice versa.
d. Remove any parameters from the entry that are not needed.
e. Patch the Database Listener to the most recent version.
5. Oracle security is enables (for example in Oracle Apps). Solution either:
a) Edit sqlnet.ora file and add your client-ip to tcp.invited_nodes.
b) Remove secutity by editing sqlnet.ora and comment out parameter tcp.validnode_checking = yes by adding # at the beginning of the line.

Social Bookmark These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Faves
  • LinkedIn
  • MisterWong
  • MySpace
  • Reddit
  • Technorati
  • Wikio
  • YahooBuzz
  • Ask
  • Google Bookmarks
  • Linkarena
  • Live-MSN
  • Newstube
  • seekXL
  • TwitThis
  • Webnews
  • Webride
  • Wikio DE
  • Y!GG
  • YahooMyWeb

Topics: Oracle | 1 Comment »

Trackback URL for this post: http://www.bearparc.info/2010/08/30/ora-12537-tns-connection-closed-error/trackback/

One Response to “ORA-12537: TNS: connection closed error”

  1. Tweets that mention ORA-12537: TNS: connection closed error | bearparc – Softwareentwicklung und Projektmanagement -- Topsy.com Says:
    August 31st, 2010 at 1:29 am

    [...] This post was mentioned on Twitter by Brokerbase, Brokerbase. Brokerbase said: ORA-12537: TNS: connection closed error http://is.gd/eMbwM [...]

Comments

You must be logged in to post a comment.