ORA-19229: XP0009 - schema import not supported

Cause : A schema import was encountered in the query.

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

remove the schema import.

update : 25-04-2017
ORA-19229

ORA-19229 - XP0009 - schema import not supported
ORA-19229 - XP0009 - schema import not supported

  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-13226 : interface not supported without a spatial index
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-40305 : invalid impurity metric specified
  • ora-07756 : slemcf: fread failure
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-39006 : internal error
  • ora-00488 : RBAL process terminated with error
  • ora-22288 : file or LOB operation string failed string
  • ora-13109 : spatial table string exists
  • ora-40216 : feature not supported
  • ora-30742 : cannot grant SELECT privilege WITH HIERARCHY OPTION on this object
  • ora-15198 : operation string is not yet available
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-16224 : Database Guard is enabled
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-28546 : connection initialization failed, probable Net8 admin error
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-14293 : Number of partitioning columns does not match number of subpartitioning columns
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-00290 : operating system archival error occurred. See error below
  • ora-32817 : message system link string is not configured with a log queue for string
  • ora-19588 : %s recid string stamp string is no longer valid
  • ora-07755 : slemcf: fseek before read failure
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-07442 : function address must be in the range string to string
  • 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.