ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns

Cause : The two tables specified in the EXCHANGE have different number of columns

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

Ensure that the two tables have the same number of columns with the same type and size.

update : 23-08-2017
ORA-14096

ORA-14096 - tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
ORA-14096 - tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns

  • ora-22888 : duplicate SCOPE clauses for a REF column
  • ora-19923 : the session for row with id string is not active
  • ora-08322 : scnmin: open/convert of bias lock failed
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-13751 : "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
  • ora-16704 : cannot modify a read-only property
  • ora-40101 : Data Mining System Error string-string-string
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-10924 : import storage parse error ignore event
  • ora-09350 : Windows 32-bit Two-Task driver unable to allocate context area
  • ora-19595 : archivelog string already included in backup conversation
  • ora-06950 : No error
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-27434 : cannot alter chain step job string.string.string
  • ora-19803 : Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)
  • ora-36874 : (XSTFDSC04) Expression string cannot be used to define a column in a LIMITMAP.
  • ora-28542 : Error in reading HS init file
  • ora-12646 : Invalid value specified for boolean parameter
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-29364 : plan directive string, string already exists
  • ora-13790 : invalid value for time limit
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-29277 : invalid SMTP operation
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-02252 : check constraint condition not properly ended
  • ora-12806 : could not get background process to hold enqueue
  • ora-36672 : (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
  • ora-02347 : cannot grant privileges on columns of an object table
  • 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.