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 : 24-07-2017
ORA-14113

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

  • ora-09796 : szrbuild: malloc of role name failed.
  • ora-27510 : IPC error waiting for a request to complete
  • ora-23437 : template authorization already exists for user
  • ora-23300 : %s
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-22057 : bad integer length [string]
  • ora-12804 : parallel query server appears to have died
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-30963 : The indexed column is not of XMLType.
  • ora-21706 : duration does not exist or is invalid
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-09932 : Close of ORACLE password file failed.
  • ora-06545 : PL/SQL: compilation error - compilation aborted
  • ora-16617 : unknown object identifier specified in request
  • ora-24394 : invalid mode for destroying connection pool
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-28263 : Insufficient memory in global context pool
  • ora-12821 : invalid value for INSTANCES
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-28150 : proxy not authorized to connect as client
  • ora-13109 : spatial table string exists
  • ora-13640 : The current operation was cancelled because it timed out, and was not in interruptible mode.
  • ora-26708 : remote DDL not supported by STREAMS : dblink string
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-32840 : property name cannot be NULL
  • ora-00087 : command cannot be executed on remote instance
  • ora-28591 : agent control utility: unable to access parameter file
  • 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.