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 : 22-09-2017

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

  • ora-27058 : file I/O question parameter is invalid
  • ora-02048 : attempt to begin distributed transaction without logging on
  • ora-24336 : invalid result set descriptor
  • ora-02334 : cannot infer type for column
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-30179 : invalid argument index used in a format code
  • ora-04935 : unable to get/convert SCN recovery lock
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-25337 : Cannot propagate in queue-to-queue mode to a database with version lower than 10.2
  • ora-27375 : valid agent name must be specified for secure queues
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-19510 : failed to set size of string blocks for file "string" (blocksize=string)
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-32031 : illegal reference of a query name in WITH clause
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-39154 : Objects from foreign schemas have been removed from import
  • ora-29806 : specified binding does not exist
  • ora-26736 : Data Pump error
  • ora-09794 : szrbuild: length of role name is greater than buffer.
  • ora-24098 : invalid value string for string
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-29534 : referenced object string.string could not be resolved
  • ora-12481 : effective label not within program unit clearance range
  • ora-01947 : TEMPORARY TABLESPACE already specified
  • ora-19276 : XP0005 - XPath step specifies an invalid element/attribute name: (string)
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • 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.