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 : 26-04-2017
ORA-12160

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

  • ora-09946 : File name too long for buffer
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-29806 : specified binding does not exist
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-24911 : Cannot start listener thread at specified port
  • ora-01680 : unable to extend LOB segment by string in tablespace string
  • ora-27003 : cannot open file on device allocated with NOIO option
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-28006 : conflicting values for parameters string and string
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-31433 : subscriber view does not exist
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-39115 : %s is not supported over a network link
  • ora-02267 : column type incompatible with referenced column type
  • ora-38451 : index is in an inconsistent state
  • ora-14037 : partition bound of partition "string" is too high
  • ora-01227 : log string is inconsistent with other logs
  • ora-29805 : missing COLUMN keyword
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-10635 : Invalid segment or tablespace type
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-08433 : invalid picture type in convert raw to number
  • ora-30488 : argument should be a function of expressions in PARTITION BY
  • ora-06029 : NETASY: port assignment failure
  • ora-16150 : FINISH recovery performed on another, older standby database
  • 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.