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 : 25-04-2017
ORA-14114

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-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-01999 : password file cannot be updated in SHARED mode
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-02761 : File number to be canceled is negative.
  • ora-38498 : invalid stored attribute for the index object : string
  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-27007 : failed to open file
  • ora-27148 : spawn wait error
  • ora-38777 : database must not be started in any other instance.
  • ora-06323 : IPA: Cause event error
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-06774 : TLI Driver: error sending break mode
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-27146 : post/wait initialization failed
  • ora-16116 : no work available
  • ora-02035 : illegal bundled operation combination
  • ora-02040 : remote database string does not support two-phase commit
  • ora-14185 : incorrect physical attribute specified for this index partition
  • ora-09985 : SGA definition file could not be read
  • ora-06915 : CMX: unknown t_event in datarq
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-12531 : TNS:cannot allocate memory
  • ora-02049 : timeout: distributed transaction waiting for lock
  • 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.