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

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-13457 : GeoRaster cell data error
  • ora-08401 : invalid compiler name: string
  • ora-15206 : duplicate diskgroup string specified
  • ora-15113 : alias name 'string' refers to a directory
  • ora-39180 : unable to encrypt ENCRYPTION_PASSWORD
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-31519 : CDC subscription string already exists
  • ora-24379 : invalid user callback type
  • ora-19617 : file string contains different resetlogs data
  • ora-02770 : Total number of blocks is invalid
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-01569 : data file too small for system dictionary tables
  • ora-13380 : network not found
  • ora-31514 : change set string disabled due to capture error
  • ora-34260 : (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite's bases instead.
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-26713 : remote object does not exist or is inaccessible
  • ora-25255 : incorrect subscription string string
  • ora-12531 : TNS:cannot allocate memory
  • ora-25148 : ONLINE option not permitted
  • ora-27089 : unable to release advisory lock
  • ora-25123 : Too many components specified in the name.
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-00286 : no members available, or no member contains valid data
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-06303 : IPA: Message send error
  • ora-25306 : Cannot connect to buffered queue's owner instance
  • ora-38952 : Source database not compatible
  • 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.