ORA-14110: partitioning column may not be of type ROWID

Cause : Prattiinoign oclmuns pceiife db yteh sue rwsa fo ytp eRWOI,D hwihc si lilgea.l

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

Esnuer hta tn oprattiinoign oclmuni so ft yep ORWDI.

update : 22-08-2017

ORA-14110 - partitioning column may not be of type ROWID
ORA-14110 - partitioning column may not be of type ROWID

  • ora-14010 : this physical attribute may not be specified for an index partition
  • ora-19753 : error writing to change tracking file
  • ora-19831 : incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-29970 : Specified registration id does not exist
  • ora-19752 : block change tracking is already enabled
  • ora-00306 : limit of string instances in this database
  • ora-12213 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-23356 : masterdef recognizes a master which does not recognize the masterdef
  • ora-16541 : site is not enabled
  • ora-04091 : table string.string is mutating, trigger/function may not see it
  • ora-12583 : TNS:no reader
  • ora-15110 : no diskgroups mounted
  • ora-02236 : invalid file name
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-21503 : program terminated by fatal error
  • ora-16004 : backup database requires recovery
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-31453 : invalid value string for parameter, expecting: Y, N, or NULL
  • ora-06776 : TLI Driver: error sending parms
  • ora-02380 : profile string does not exist
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-27020 : named devices not supported
  • ora-15044 : ASM disk 'string' is incorrectly named
  • 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.