Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 439 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
TNSPING ON LOCALHOST VERY SLOW

Hi there,
I have a question. Last week I had to restart my Oracle Linux 5 server with Oracle DB 11.2.0.1.0 database and since the restart I have problems connecting to the database. The connections gets timedout a lot. It was working perfect before the restart.
I tried tnsping on several clients and the time gets more then 2000 ms in many tries. I tried this directly on the server and got the same results. It's not all the time, it keeps working great for a minute or two, and then it has issues.
I use IP host names in TNSNAMES. not hostnames, so DNS resolving should not be the problem..
Please help, thanks!
Answers
-
user10434575 wrote: Hi there, I have a question. Last week I had to restart my Oracle Linux 5 server with Oracle DB 11.2.0.1.0 database and since the restart I have problems connecting to the database. The connections gets timedout a lot. It was working perfect before the restart. I tried tnsping on several clients and the time gets more then 2000 ms in many tries. I tried this directly on the server and got the same results. It's not all the time, it keeps working great for a minute or two, and then it has issues. I use IP host names in TNSNAMES. not hostnames, so DNS resolving should not be the problem.. Please help, thanks!
Oracle depends upon the OS for any & all packet exchange.
Oracle is the victim; not the culprit.
Root cause is OS/Networking mis-configuration.
problem & fix are external to Oracle
-
Thanks, but how to find out what causes the problem. Nothing was changed, just a simple restart.
The server is a vmware based virtual machine.
If there would be network problems, why is the time so big even local?
tnx!
-
user10434575 wrote: Thanks, but how to find out what causes the problem. Nothing was changed, just a simple restart. The server is a vmware based virtual machine. If there would be network problems, why is the time so big even local? tnx!
>Nothing was changed
If nothing really changed, then behavior would be the same.
Since behavior is different, then by definition SOMETHING has CHANGED!
-
Obviously, if tnsping is 'too slow', you should use ordinary Linux ping to the node.
If you are really using only localhost and you have hardcoded it, response should be immediately.
You could easily have an incorrect IP address as gateway, and/or a wrong network mask, forcing your packet to leave your system.
All of that, of course, has nothing to do with Oracle, and should be addressed in a Linux forum, not here.
-----------
Sybrand Bakker
Senior Oracle DBA
-
Hello,
Please look at DTRACE utility to identify where the performance bottleneck is. Please see the following article and see if that helps you.
How to Get Started Using DTrace on Oracle Linux
regards
Fahd
-
you could try a tnsping trace, add the following lines to your sqlnet file before doing a tnsping.
TNSPING.TRACE_LEVEL = 16
TNSPING.TRACE_DIRECTORY = <some directory>
you may find some clues in the output as to why it's so slow.