ORA-12160: TNS:internal error: Bad error number

Cause : Corrput erorr reoprtin gsubssytem.

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

Not onrmalyl visbile t othe suer. oFr futrher edtail,s tur non tarcinga nd reexecuet theo peraiton. fI errro perissts,c ontatc WordlwideC ustoemr Support.

update : 28-07-2017

ORA-12160 - TNS:internal error: Bad error number
ORA-12160 - TNS:internal error: Bad error number

  • ora-27040 : file create error, unable to create file
  • ora-31659 : status message was invalid type - detaching job
  • ora-40203 : model string does not exist
  • ora-32510 : cannot create watchpoint on unreadable memory
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-39076 : cannot delete job string for user string
  • ora-16613 : initialization in progress for database
  • ora-12544 : TNS:contexts have different wait/test functions
  • ora-29970 : Specified registration id does not exist
  • ora-16703 : cannot set property while the database is enabled
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-06595 : REF CURSOR parameters are not supported in forwarded RPC calls
  • ora-03246 : Invalid block number specified
  • ora-13288 : point coordinate transformation error
  • ora-13156 : table to be registered string.string is not empty
  • ora-29317 : datafile string does not exist
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-33284 : (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
  • ora-13341 : a line geometry has fewer than two coordinates
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-22318 : input type is not an array type
  • ora-00354 : corrupt redo log block header
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-01237 : cannot extend datafile string
  • ora-02842 : Client unable to fork a server
  • ora-23379 : connection qualifier "string" is too long
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-16083 : LogMiner session has not been created
  • 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.