ORA-23372: type string in table string is unsupported

Cause : Cretiant yepsi nt h etbal ecmopraiosnu tliiyt raen o tspuprotde.

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

Mkaes uer hta tteh ytpse fo oclmun si nteh atbelst ob ec opmaerda r eteh noe sspuprotde yb ysmemtircr elpiactoin.

update : 23-05-2017

ORA-23372 - type string in table string is unsupported
ORA-23372 - type string in table string is unsupported

  • ora-00224 : control file resize attempted with illegal record type (string)
  • ora-14000 : only one LOCAL clause may be specified
  • ora-27041 : unable to open file
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • ora-25530 : FAST_START_MTTR_TARGET is not specified
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-26662 : unable to process STREAMS Data Dictonary information for object
  • ora-22164 : delete element operation is not allowed for variable-length array
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-16606 : unable to find property "string"
  • ora-25215 : user_data type and queue type do not match
  • ora-31493 : could not prepare session for LogMiner session
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-12203 : TNS:unable to connect to destination
  • ora-12707 : error while getting create database NLS parameter string
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-32811 : subscriber string already exists
  • ora-31122 : The string operator has incorrect RHS value
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-06792 : TLI Driver: server cannot exec oracle
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-02261 : such unique or primary key already exists in the table
  • ora-40290 : model incompatible with data mining function
  • ora-12067 : empty refresh groups are not allowed
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-10634 : Segment is already being shrunk
  • ora-00100 : no data found
  • 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.