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

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

  • ora-28101 : policy already exists
  • ora-23420 : interval must evaluate to a time in the future
  • ora-14066 : illegal option for a non-partitioned index-organized table
  • ora-19767 : missing TRACKING keyword
  • ora-07706 : error in archive text: need disk file name
  • ora-02058 : no prepared transaction found with ID string
  • ora-19040 : Element string does not match expected string.
  • ora-30163 : The thread safety initialization failed
  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-27010 : skgfwrt: write to file failed
  • ora-29550 : Java session state cleared
  • ora-40104 : invalid training data for model build
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-03240 : User's temporary tablespace same as tablespace being migrated
  • ora-26534 : collision: tranID number ignored and purged
  • ora-16001 : database already open for read-only access by another instance
  • ora-16810 : multiple errors or warnings detected for the database
  • ora-02071 : error initializing capabilities for remote database string
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-06002 : NETASY: port read failure
  • ora-14400 : inserted partition key does not map to any partition
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-12065 : unknown refresh group identifier string
  • ora-22304 : input type is not an object type
  • ora-38306 : this object is not recoverable standalone
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-12412 : policy package string is not installed
  • ora-37181 : expected exactly string columns for dimension string, got 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.