ORA-14114: partitioned table cannot have column with object, REF, nested table, array datatype

Cause : User tried to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table.

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

object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non partitioned table.

update : 26-05-2017

ORA-14114 - partitioned table cannot have column with object, REF, nested table, array datatype
ORA-14114 - partitioned table cannot have column with object, REF, nested table, array datatype

  • ora-27369 : job of type EXECUTABLE failed with exit code: string
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-01607 : cannot add logfile to the specified instance
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-19651 : cannot apply offline-range record to datafile string: SCN mismatch
  • ora-02251 : subquery not allowed here
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • ora-32830 : result code string returned by Messaging Gateway agent
  • ora-04061 : existing state of string has been invalidated
  • ora-10620 : Operation not allowed on this segment
  • ora-32580 : both SYS and SYSTEM passwords must be provided
  • ora-12652 : String truncated
  • ora-29741 : IMR active for some, but not all members of cluster
  • ora-19735 : wrong creation SCN - control file expects initial plugged-in datafile
  • ora-24332 : invalid object type
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-01684 : max # extents (string) reached in table string.string partition string
  • ora-19682 : file string not in block media recovery context
  • ora-19913 : unable to decrypt backup
  • ora-02353 : files not from the same unload operation
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-28120 : driving context already exists
  • ora-12423 : invalid position specified
  • ora-29885 : domain index is defined on the column to be modified
  • ora-32818 : AQ queue string does not exist
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • 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.