Skip to main content

tnsping and sqlplus takes long time event though TNSPING response time is great

This time I faced this scenario,
One of my client called me and tell me that his application server faces difficulties to create the connection pool against the DB.

first I have checked the DB server side and I saw everything is ok
I tried to connect from my laptop - again OK
from the application server things were getting weird..
once every few tnsping commands or sqlplus command using tnsnames.ora sqlnet.ora the command tooks more than 10 seconds to return to prompt...

I did these changes to isolate the problem

sqlnet.ora

I've changed -
SQLNET.AUTHENTICATION_SERVICES= (NTS)
to:
SQLNET.AUTHENTICATION_SERVICES= (NONE)
and  in the tnsnames.ora - I've used IP instead of the DB hostname.
but still - same behavior as above.

then I've started to drill down and found these amazing finding:

* in the registry key called TNS_ADMIN
under LOCAL MACHINE -> SOFTWARE -> ORACLE
I found out that the value is pointing to a centralized Oracle client server which the response time to reach him is not always good!!

Solution ->
I've changed this registry value to point the local network/admin folder and is works like a magic!

 I hope it helps you :-)

Comments

Post a Comment

Popular posts from this blog

ORA-27104: system-defined limits for shared memory was misconfigured

I faced this error while trying to restore & recover of a PDB (pluggable database) part of the log file and the solution is described here below: log: initialization parameters used for automatic instance: db_name=CDB db_unique_name=gbux_pitr_PDB1_CDB compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/oracle/app/oracle _system_trig_enabled=FALSE sga_target=1888M processes=200 db_create_file_dest=/oracle/auxilary log_archive_dest_1='location=/oracle/auxilary' enable_pluggable_database=true _clone_one_pdb_recovery=true #No auxiliary parameter file used starting up automatic instance CDB RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 07/31/2016 16:22:20 RMAN-04014: startup failed: ORA-27104: system-defined limits for shared...
6 comments
Read more

ora-65035 while create pluggable database from another one

or : ORA-21000: error number argument to raise_application_error of -65035 is out of range Cause: this error caused because of an unrecoverable transaction in the source DB. Solution: 1. either stop and start your pluggable source DB 2. identify the open transaction and kill it if you can. use this query to do so: select * from v$transaction t,v$session  s where t.ses_addr = s.saddr;
Post a Comment
Read more

KUP-04074: no write access to directory when trying to query EXTERNAL table

Hi All, You may think that in order to query external table you should have only read permission on the Directory Object which sounds very reasonable.... but in some external table the definition include this part of code: ACCESS PARAMETERS         ( records delimited by newline           LOGFILE   "EXTERNAL_FILES" : 'faults.txt'       FIELDS TERMINATED BY ';'             missing FIELD values are null this definition force a write permission on the directory object.  else you will run into this error: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-29400: data cartridge error KUP-04074: no write access to directory object EXTERNAL_FILES 29913. 00000 -  "error in executing %s callout" *Cause:    The execution of the specified callout caused an error. *Acti...
Post a Comment
Read more