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-05-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-14451 : unsupported feature with temporary table
  • ora-02721 : osnseminit: cannot create semaphore set
  • ora-30371 : column cannot define a level in more than one dimension
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-25141 : invalid EXTENT MANAGEMENT clause
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-09265 : spwat: error temporarily suspending process
  • ora-38104 : Columns referenced in the ON Clause cannot be updated: string
  • ora-23404 : refresh group "string"."string" does not exist
  • ora-14082 : new partition name must differ from that of any other partition of the object
  • ora-27208 : syntax error in device PARMS - environment variable value missing
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-32612 : invalid use of FOR loop
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-08231 : smscre: unable to attach to SGA
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-40271 : no statistically significant features were found
  • ora-37603 : (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-12681 : Login failed: the SecurID card does not have a pincode yet
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-22800 : invalid user-defined type
  • ora-36806 : (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
  • ora-01116 : error in opening database file string
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-29665 : Java thread deadlock detected
  • ora-28669 : bitmap index can not be created on an IOT with no mapping table
  • ora-16001 : database already open for read-only access by another instance
  • 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.