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 : 26-05-2017

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

  • ora-10361 : check buffer change vector count consistency
  • ora-00295 : datafile/tempfile number string is invalid, must be between 1 and string
  • ora-26718 : transaction limit reached
  • ora-16011 : Archivelog Remote File Server process in Error state
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-13241 : specified dimensionality does not match that of the data
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-25293 : Lob attributes must be null for buffered operations
  • ora-26745 : cursors (string) are not sufficient
  • ora-25247 : %s is not a recipient of specified message
  • ora-12215 : TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA
  • ora-16084 : an apply engine is already running
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-36871 : (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
  • ora-38721 : Invalid file number.
  • ora-04079 : invalid trigger specification
  • ora-12992 : cannot drop parent key column
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-13023 : interior element interacts with exterior element
  • ora-01058 : internal New Upi interface error
  • ora-28053 : the account is inactive
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-30191 : missing argument list
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-04013 : number to CACHE must be less than one cycle
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-29968 : No primary operator bindings found for ancillary binding #string
  • ora-24394 : invalid mode for destroying connection pool
  • ora-24507 : invalid combination of character set ids
  • 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.