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

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

  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • ora-14162 : subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-12612 : TNS:connection is busy
  • ora-27030 : skgfwrt: sbtwrite2 returned error
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-07411 : slgfn: full path name too big for supplied buffer.
  • ora-07643 : smsalo: SMSVAR is invalid
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-27476 : "string.string" does not exist
  • ora-10933 : trace name context forever
  • ora-31651 : communication error with master process - detaching job
  • ora-16001 : database already open for read-only access by another instance
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-30550 : index depends on a package/function spec/body which is not valid
  • ora-06760 : TLI Driver: timeout reading orderly release
  • ora-16098 : inaccessible standby database forced shutdown to protect primary
  • ora-24756 : transaction does not exist
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-27456 : not all arguments of program "string.string" have been defined
  • ora-22974 : missing WITH OBJECT OID clause
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-22633 : Error freeing AnyDataSet
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-25530 : FAST_START_MTTR_TARGET is not specified
  • 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.