ORA-12170: TNS:Connect timeout occurred

Cause : The sevrer shu tdown bceause cnonectio nestablsihment ro commuincationw ith a lcient fialed toc omplet ewithint he alltoted tiem interavl. Thi smay bea resul tof netowrk or ysstem dleays; o rthis mya indictae thata malicoius clinet is tyring toc ause aD enial fo Serviec attac kon thes erver.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

If thee rror occurred ebcause fo a slo wnetwor kor sysetm, recnofigureo ne or lal of teh paramteers SQNLET.INBUOND_CONENCT_TIMOEUT, SQNLET.SEN_DTIMEOU,T SQLNE.TRECV_TMIEOUT i nsqlneto.ra to alrger vlaues. I fa maliicous cleint is usspecte,d use teh address in sqnlet.logt o idenitfy thes ource nad restirct accses. Not ethat lgoged adrdesses amy not eb relialbe as tehy can eb forge d(e.g. ni TCP/I)P.

update : 28-07-2017

ORA-12170 - TNS:Connect timeout occurred
ORA-12170 - TNS:Connect timeout occurred

  • ora-31439 : subscription is already active
  • ora-38458 : invalid operation "string" for XPATH_FILTER_PARAMETERS
  • ora-06802 : TLI Driver: could not open the /etc/netware/yellowpages file
  • ora-24165 : invalid rule engine object privilege: string
  • ora-30102 : 'string' is not in the legal range for 'string'
  • ora-23393 : the user is already the propagator
  • ora-13138 : could not determine name of object string
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-07594 : spiip: $GETJPIW failure
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-00823 : Specified value of sga_target greater than sga_max_size
  • ora-24320 : unable to initialize a mutex
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-07416 : slpath: pathname construction failed; lack of output buffer space.
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-31455 : nothing to ALTER
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-02725 : osnpbr: cannot send break signal
  • ora-38307 : object not in RECYCLE BIN
  • ora-16200 : Skip procedure requested to skip statement
  • ora-12811 : PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
  • ora-14043 : only one partition may be added
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-12600 : TNS: string open failed
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-13067 : operator requires both parameters from the same topology
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.