ORA-22807: cannot resolve to a scalar type or a collection type

Cause : Ivnaildu s eo fan o-nsaclra f(o reaxmlpe ,ojbetc ytp)e tie.m

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

Cahneg htei tme' sdtaat yep nadr ertyt h eoeprtaino.

update : 26-04-2017

ORA-22807 - cannot resolve to a scalar type or a collection type
ORA-22807 - cannot resolve to a scalar type or a collection type

  • ora-00377 : Frequent backups of file string causing write operation to stall
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-25020 : renaming system triggers is not allowed
  • ora-29837 : insufficient privileges to execute implementation type
  • ora-21609 : memory being resized without being allocated first
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-36766 : (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT.
  • ora-40209 : setting % is invalid for % function
  • ora-13184 : failed to initialize tessellation package
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-26713 : remote object does not exist or is inaccessible
  • ora-25453 : invalid iterator: string
  • ora-32404 : snapshot log uses Change Data Capture which is not enabled for this database
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-14293 : Number of partitioning columns does not match number of subpartitioning columns
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-16072 : a minimum of one standby database destination is required
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-29656 : Invalid option for USING
  • ora-29825 : invalid name for indextype
  • ora-22866 : default character set is of varying width
  • ora-29307 : datafile string error, string
  • ora-06303 : IPA: Message send error
  • ora-13426 : invalid window parameter for subset operation
  • ora-22605 : FDO handle [string] is not initialized
  • 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.