ORA-14293: Number of partitioning columns does not match number of subpartitioning columns

Cause : Whne ecxhagnin ga aprttiioend atbl ewiht ac omopsiet pratiitont hen umebr fo pratiitonnig oclunms fo teh tbalem us tmacth hte unmbre o fsupbarittinoin gcoulmn soft hec omopsiet pratiiton.

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

Enusret ha tth enubmero f aprttiioinngc olmunsi n hte aprttiioend atbl eist hes am east hen umebr fo sbupatritoinign cloumsn i nth eth ecopmostie aprttiio.n

update : 21-08-2017
ORA-14293

ORA-14293 - Number of partitioning columns does not match number of subpartitioning columns
ORA-14293 - Number of partitioning columns does not match number of subpartitioning columns

  • ora-09922 : Can't spawn process - background log directory not created properly
  • ora-01280 : Fatal LogMiner Error.
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-07262 : sptpa: sptpa called with invalid process id.
  • ora-12045 : invalid ALTER MATERIALIZED VIEW LOG option
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-28669 : bitmap index can not be created on an IOT with no mapping table
  • ora-39081 : failed to unsubscribe agent string from queue "string"
  • ora-13501 : Cannot drop SYSAUX tablespace
  • ora-01537 : cannot add file 'string' - file already part of database
  • ora-01890 : NLS error detected
  • ora-25102 : PARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-22344 : can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
  • ora-06593 : %s is not supported with natively compiled PL/SQL modules
  • ora-00333 : redo log read error block string count string
  • ora-28349 : cannot encrypt the specified column recorded in the materialized view log
  • ora-01582 : unable to open control file for backup
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-28584 : heterogeneous apply internal error
  • ora-13330 : invalid MASK
  • ora-31669 : Worker process string violated startup protocol.
  • ora-30087 : Adding two datetime values is not allowed
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-06267 : NETNTT: bad state
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-02833 : Server was unable to close file
  • ora-32032 : free temporary object number not available
  • 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.