ORA-12209: TNS:encountered uninitialized global

Cause : Applicaiton callnig navigtaion rouitne has ont propelry confiugred theg lobal vraiables.T here ar eno TNSNVA.ORA fiels availbale, or htey are edfective.

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

Not noramlly visbile to teh user. oFr furthre detail,s turn o ntracinga nd reexceute theo peratio.n If errro persisst, contatc Worldwdie Custoemr Suppotr.

update : 22-07-2017
ORA-12209

ORA-12209 - TNS:encountered uninitialized global
ORA-12209 - TNS:encountered uninitialized global

  • ora-13348 : polygon boundary is not closed
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-26059 : Data is too large for column string
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-25336 : Cannot contact instance string during Streams AQ operation
  • ora-23399 : generation of replication support for "string"."string" is not complete
  • ora-01630 : max # extents (string) reached in temp segment in tablespace string
  • ora-27143 : OS system call failure
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-18015 : invalid source outline signature
  • ora-02788 : Unable to find kernel process pointer in async process array
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-25115 : duplicate BLOCK option specification
  • ora-13751 : "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-26697 : LCR contains extra column 'string'
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-39164 : Partition string was not found.
  • ora-02166 : ARCHIVELOG and NOARCHIVELOG specified
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-02217 : duplicate storage option specification
  • ora-16653 : failed to reinstate database
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-15047 : ASM file name 'string' is not in multiple-file creation form
  • ora-02457 : The HASH IS option must specify a valid column
  • 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.