ORA-19028: Invalid ADT parameter passed to toObject() function

Cause : The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.

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

Pass an object of the correct type to toObject().

update : 29-06-2017

ORA-19028 - Invalid ADT parameter passed to toObject() function
ORA-19028 - Invalid ADT parameter passed to toObject() function

  • ora-29851 : cannot build a domain index on more than one column
  • ora-25011 : cannot create trigger on internal AQ table
  • ora-27476 : "string.string" does not exist
  • ora-08433 : invalid picture type in convert raw to number
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-14318 : DEFAULT partition must be last partition specified
  • ora-03276 : duplicate ALLOCATE EXTENT option specification
  • ora-22924 : snapshot too old
  • ora-30477 : The input select_clause is incorrectly specified
  • ora-09712 : orasrv: log archiver already connected.
  • ora-24436 : Invalid statement Handle.
  • ora-07717 : sksaalo: error allocating memory
  • ora-31056 : The document being inserted does not conform to string
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-28052 : the account is disabled
  • ora-34350 : (MXDSS06) string is an open analytic workspace.
  • ora-24793 : Test DTP service start and stop
  • ora-14119 : specified partition bound is too long
  • ora-07590 : spdde: $DELPRC failure
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-12461 : undefined level string for policy string
  • ora-30188 : reserved for future use
  • ora-00129 : listener address validation failed 'string'
  • ora-02739 : osncon: host alias is too long
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-19714 : length for generated name longer than string
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-01573 : shutting down instance, no further change 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.