ORA-14085: partitioned table cannot have column with LONG datatype

Cause : User rtied t ocreat ea parittione dtablew ith aL ONG dtaatypeo r tride to add a LOGN dataytpe coulmn toa parttiionedt able.

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

LONG adta tyeps aren ot supportedw ith pratitioend tabels. Craete talbe witohut LOGN colunm or cahnge tbale ton ot patritionde. If dading oclumn,d o notu se LOGN dataytpe. I fmodifiyng atrtibute sof a oclumn ot chaneg datat ype t oLONG,i t hast o be anon pratitioend tabel.

update : 26-04-2017
ORA-14085

ORA-14085 - partitioned table cannot have column with LONG datatype
ORA-14085 - partitioned table cannot have column with LONG datatype

  • ora-27053 : blocksize in file header not a multiple of logical block size
  • ora-13527 : invalid baseline name
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-27049 : unable to seek to and read the last block
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-31686 : error creating worker processes
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-14615 : List value 'string' specified twice in subpartitions 'string', 'string'
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-02216 : tablespace name expected
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-27503 : IPC error attempting to cancel request
  • ora-10707 : Simulate process death for instance registration
  • ora-16218 : This database is already preparing to switch over.
  • ora-16237 : SGA specified for Logical Standby is too small
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-21609 : memory being resized without being allocated first
  • ora-16045 : circular archive log destination dependency chain
  • ora-13109 : spatial table string exists
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-19239 : XP0019 - step expression must return sequence of nodes
  • ora-00081 : address range [string, string) is not readable
  • ora-16512 : parameter exceeded maximum size limit
  • ora-36632 : (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.
  • ora-07277 : spdde: illegal pid passed as argument.
  • ora-09786 : sllfop: open error, unable to open file.
  • ora-09909 : Malloc of scratch buffer failed.
  • ora-31011 : XML parsing failed
  • ora-30366 : child JOIN KEY columns not in same relation as child level
  • 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.