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

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-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-38310 : cannot purge tablespace for other users
  • ora-15206 : duplicate diskgroup string specified
  • ora-12045 : invalid ALTER MATERIALIZED VIEW LOG option
  • ora-39706 : schema 'string' not found
  • ora-27488 : unable to set string because string was/were already set
  • ora-30447 : internal data for run number string is inconsistent
  • ora-16105 : Logical Standby is already running in background
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-10561 : block type 'string', data object# string
  • ora-19604 : conversation file naming phase is over
  • ora-04008 : START WITH cannot be more than MAXVALUE
  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-13288 : point coordinate transformation error
  • ora-12730 : invalid equivalence class in regular expression
  • ora-13115 : [string]_EDGE$ table does not exist
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-02154 : a tablespace with the name 'string' is found
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-29523 : authorization error for unknown referenced name
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-29512 : incorrectly formed name resolver specification
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-02155 : invalid DEFAULT tablespace identifier
  • ora-08205 : ora_addr: $ORACLE_SID not set in environment
  • ora-31193 : This versioning feature isn't supported for resource string
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-23483 : object "string"."string" not allowed in this operation.
  • 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.