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 : 26-06-2017

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

  • ora-24763 : transaction operation cannot be completed now
  • ora-38772 : cannot add datafile 'string' - file could not be created
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-10941 : trace name context forever
  • ora-30551 : The index depends on a package/type body which does not exist
  • ora-02420 : missing schema authorization clause
  • ora-32006 : %s initialization parameter has been deprecated
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-30185 : output too large to fit in the buffer
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-13065 : cannot delete a child layer with a parent layer
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-13630 : The task string contains execution results and cannot be executed.
  • ora-03234 : unable to extend index string.string subpartition string by string in tablespace string
  • ora-16089 : archive log has already been registered
  • ora-16403 : shutdown in progress - remote connection is not permitted
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-13386 : commit/rollback operation error: [string]
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-30342 : referenced level is not defined in this dimension
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-01241 : an external cache has died
  • ora-02852 : Invalid critical-section time out value
  • ora-21527 : internal OMS driver error
  • ora-25015 : cannot perform DML on this nested table view column
  • ora-37176 : argument string is not valid for the sparsity advisor
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-02330 : datatype specification not allowed
  • 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.