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 : 24-09-2017

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-01219 : database not open: queries allowed on fixed tables/views only
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-12153 : TNS:not connected
  • ora-26505 : unexpected internal null
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-16521 : unable to create generic template id
  • ora-06002 : NETASY: port read failure
  • ora-07211 : slgcs: gettimeofday error, unable to get wall clock.
  • ora-24906 : invalid recepient attribute passed into OCI call
  • ora-12055 : materialized view definition contains cyclic dependencies with existing materialized views
  • ora-28513 : internal error in heterogeneous remote agent
  • ora-02238 : filename lists have different numbers of files
  • ora-40209 : setting % is invalid for % function
  • ora-29283 : invalid file operation
  • ora-01625 : rollback segment 'string' does not belong to this instance
  • ora-13485 : error occurred during compression or decompression: string
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-01917 : user or role 'string' does not exist
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-13145 : failed to generate range list
  • ora-13784 : cannot accept SQL profiles for all statements in the "SQL Tuning Set"
  • ora-16618 : response document of size "string" bytes is too large
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-25205 : the QUEUE string.string does not exist
  • ora-12227 : TNS:syntax error
  • ora-13453 : GeoRaster metadata layer error
  • ora-30944 : Error during rollback for XML schema 'string' table string column '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.