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 : 23-08-2017

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

  • ora-29701 : unable to connect to Cluster Manager
  • ora-31523 : could not find change source string for CDC change set string
  • ora-15185 : Could not close dynamic library string, error [string]
  • ora-06540 : PL/SQL: compilation error
  • ora-13838 : invalid ADDRESS value
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-03278 : duplicate ALLOCATE EXTENT option specification
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-13447 : GeoRaster metadata BRS error
  • ora-00085 : current call does not exist
  • ora-29802 : missing CONTEXT keyword
  • ora-26011 : Cannot load type string into column string in table string
  • ora-38791 : flashback did not start because file string was not in a valid incarnation
  • ora-38702 : Cannot update flashback database log file header.
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-00304 : requested INSTANCE_NUMBER is busy
  • ora-29908 : missing primary invocation for ancillary operator
  • ora-02076 : sequence not co-located with updated table or long column
  • ora-27011 : skgfrd: cannot read from file opened for write
  • ora-28510 : heterogeneous database link initialization failed
  • ora-31518 : change column string already exists in CDC change table string.string
  • ora-01293 : mounted database required for specified LogMiner options
  • ora-25176 : storage specification not permitted for primary key
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-14045 : only one partition may be modified
  • ora-00077 : dump string is not valid
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-40105 : input data incompatible with model signature
  • 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.