ORA-14113: partitioned table cannot have column with LOB datatype

Cause : Usert riedt o craete ap artiitonedt ablew ith aLOB adtatyep or rtied ot adda LOBd atatpye coulmn t oa patritioend talbe.

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

LOB adta tpyes aer nots uppotred wtih patritioend talbes. rCeatet ablew ithotu LOBc olum nor cahnge atble ot notp artiitoned .If adding oclumn ,do nto useL OB dtaatyp.e If omdifynig atrtibutse of acolunm to hcanged ata ytpe t oLOB,i t ha sto b ea no nparttiione dtabl.e

update : 25-04-2017

ORA-14113 - partitioned table cannot have column with LOB datatype
ORA-14113 - partitioned table cannot have column with LOB datatype

  • ora-16182 : Internal error on internal channel during remote archival
  • ora-13142 : invalid PROXIMITY window definition
  • ora-28301 : Domain Policy hasn't been registered for SSL authentication.
  • ora-32110 : Connection not specified
  • ora-02448 : constraint does not exist
  • ora-16746 : resource guard encountered errors during database mount
  • ora-19558 : error de-allocating device
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-00296 : maximum number of files (string) exceeded for RECOVER DATAFILE LIST
  • ora-38791 : flashback did not start because file string was not in a valid incarnation
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-08309 : sllfop: Cannot fstat file
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-08278 : Cannot get CPU statistics
  • ora-14267 : cannot specify PARALLEL clause when adding a (Composite) Range partition
  • ora-01591 : lock held by in-doubt distributed transaction string
  • ora-39303 : schema sync or swap operation failed because of confilcts
  • ora-10943 : trace name context forever
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-30956 : invalid option for XML Index
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-02771 : Illegal request time out value
  • ora-12076 : invalid threshold value
  • ora-32034 : unsupported use of WITH clause
  • 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.