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 : 28-04-2017

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

  • ora-28151 : more than one user name specified for command
  • ora-21612 : key is already being used
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-22288 : file or LOB operation string failed string
  • ora-01676 : standby file name convert of 'string' exceeds maximum length of string
  • ora-07707 : error in archive text: need tape label name
  • ora-30066 : test support - drop rollback segment wait
  • ora-06303 : IPA: Message send error
  • ora-06800 : TLI Driver: SQL*Net SPX client went away during reconnect
  • ora-25236 : buffer too small for user data
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-12728 : invalid range in regular expression
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-23441 : object does not exist for refresh group template
  • ora-01312 : Specified table/column does not exist
  • ora-01193 : file string is not the same file seen at start of recovery
  • ora-01022 : database operation not supported in this configuration
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-01059 : parse expected before a bind or execute
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-13015 : the window definition is not valid
  • ora-13905 : Critical or warning threshold have incorrect values
  • ora-25440 : invalid table alias: string
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-19575 : expected string blocks in file string, found string
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • 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.