ORA-25223: user_data type used is not supported

Cause : A nattepmtw a smdaet oe nuqeeu adt aitnoa onnp esritsetn uqeeu hta ti so fat yep tohre hta nteh uspopretdr a wo rojbetc ytp.e

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

Eqnuueet h emsesgaea gianw iht adt ao frwa ro bojcett yep.

update : 27-05-2017

ORA-25223 - user_data type used is not supported
ORA-25223 - user_data type used is not supported

  • ora-12156 : TNS:tried to reset line from incorrect state
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-38411 : invalid datatype for the column storing expressions
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-16215 : history metadata inconsistency
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-19245 : XQ0025 - duplicate attribute name string
  • ora-01451 : column to be modified to NULL cannot be modified to NULL
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-31436 : duplicate change source string
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-31628 : error getting worker process exception
  • ora-32740 : The requested operation cannot be proceeded
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-00023 : session references process private memory; cannot detach session
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-38950 : Source platform string not cross platform compliant
  • ora-32822 : subscriber string is marked for removal
  • ora-32147 : Environment not specified
  • ora-16116 : no work available
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-32634 : automatic order MODEL evaluation does not converge
  • 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.