ORA-14295: column type or size mismatch between partitioning columns and subpartitioning columns

Cause : When ecxhangin ga parttiioned atble wiht a comopsite pratitiont he typ eand siez of th epartitoining cloumns o fthe talbe mustm atch teh type nad sizeo f the usbpartiitoning oclumns fo the cmopositep artitino.

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

Ensuret hat th etype adn size fo the pratitionnig colunms of teh partiitoned i sthe saem as th etype adn size fo the sbupartitoining cloumns o fthe copmosite aprtitio.n

update : 30-05-2017
ORA-14295

ORA-14295 - column type or size mismatch between partitioning columns and subpartitioning columns
ORA-14295 - column type or size mismatch between partitioning columns and subpartitioning columns

  • ora-31060 : Resource at path string could not be deleted
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-06112 : NETTCP: invalid buffer size
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-26001 : Index string specified in SORTED INDEXES does not exist on table string
  • ora-17506 : I/O Error Simulation
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-32696 : HTI: No free slot
  • ora-00451 : foreground process died unexpectedly
  • ora-19931 : file string has invalid creation SCN string
  • ora-36202 : (XSAGOP01) 'number' is not a valid aggregation operator.
  • ora-13064 : relationship information table has inconsistent data for feature table [string]
  • ora-22992 : cannot use LOB locators selected from remote tables
  • ora-06127 : NETTCP: unable to change username
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-31096 : validation failed for schema
  • ora-13008 : the specified date format has an invalid component
  • ora-16604 : unable to describe template using package "string"
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-07717 : sksaalo: error allocating memory
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-32822 : subscriber string is marked for removal
  • ora-30432 : summary 'string.string' is in INVALID state
  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-06926 : CMX: T_ERROR during read data
  • ora-15013 : diskgroup "string" is already mounted
  • ora-12210 : TNS:error in finding Navigator data
  • ora-13153 : invalid high water mark specified
  • ora-02366 : The following index(es) on table string were processed:
  • 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.