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-06-2017

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

  • ora-24101 : stopped processing the argument list at: string
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-33218 : (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
  • ora-39058 : current object skipped: string of type string
  • ora-00076 : dump string not found
  • ora-14116 : partition bound of partition "string" is too long
  • ora-25115 : duplicate BLOCK option specification
  • ora-22990 : LOB locators cannot span transactions
  • ora-12606 : TNS: Application timeout occurred
  • ora-13384 : error in network schema: string
  • ora-30160 : Unable to access the file
  • ora-12601 : TNS:information flags check failed
  • ora-16208 : Logical standby dictionary build failed to start.
  • ora-22053 : overflow error
  • ora-13214 : failed to compute supercell for window object
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-24336 : invalid result set descriptor
  • ora-02753 : osnfsmmap: cannot close shared memory file
  • ora-10865 : Control tracing of notification operations
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-08315 : sllfrb: Error reading file
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-01202 : wrong incarnation of this file - wrong creation time
  • ora-10579 : Can not modify control file during test recovery
  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-24776 : cannot start a new transaction
  • ora-27250 : OS system call failure
  • ora-00269 : specified log file is part of thread string not string
  • 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.