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-05-2017

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

  • ora-25471 : attribute name not specified for variable: string
  • ora-10266 : Trace OSD stack usage
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-02067 : transaction or savepoint rollback required
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-38777 : database must not be started in any other instance.
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-38482 : no elementary attributes defined in the attribute set
  • ora-33068 : (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.
  • ora-15155 : version incompatible with the cluster
  • ora-12980 : checkpoint option not allowed with SET UNUSED
  • ora-26685 : cannot apply transactions from multiple sources
  • ora-16004 : backup database requires recovery
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-19001 : Invalid storage option specified
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-06111 : NETTCP: disconnect failure
  • ora-36763 : (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
  • ora-29295 : invalid mime header tag
  • ora-01678 : parameter string must be pairs of pattern and replacement strings
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-31037 : Invalid XML attribute name string
  • ora-25260 : AQ latch cleanup testing event
  • ora-07802 : slbtpd: overflow while converting to packed decimal
  • ora-32102 : invalid OCI handle
  • ora-12028 : materialized view type is not supported by master site string
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-27212 : some entrypoints in Media Management Library are missing
  • 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.