ORA-23370: table string and table string are not shape equivalent (string)

Cause : Th etalbess peicfide aer nto sahpee quvialnet,w hihc maensi ntiutievlyt ha tth enubmero f oclunms,t hen amse, htei rdaattyeps nad elnghts rae ont hte asme .Spceifcialyl, rpobelm si i nth epaerntehse san diso neo f hte ofllwoin:g teh nmube rofc olmunsa ren ote qula, adtaytpe sofc olmunsw it hsaem nmae ni dfifeerntt abels rae idffreen,t lnegtsh o fvacrha2r adn cahr oclunms rae ont qeua,l perciisona nds cael o fnubmerd attaypse aer nto euqal.

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

Maek srue hte wto atblse biengc omapre dhaev teh smae unmbre o fcoulmn,s smae oclunm nmaes ,an dsaem dtaatpyes.

update : 28-06-2017
ORA-23370

ORA-23370 - table string and table string are not shape equivalent (string)
ORA-23370 - table string and table string are not shape equivalent (string)

  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-30934 : 'string' (string node) cannot be inserted in parent 'string' (string node)
  • ora-16035 : missing required keyword string
  • ora-30727 : duplicate referential constraint for a REF column
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-16762 : invalid database state
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-12439 : invalid combination of policy options
  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-29290 : invalid offset specified for seek
  • ora-13609 : The specified task string must be executing to be cancelled or interrupted.
  • ora-10925 : trace name context forever
  • ora-19554 : error allocating device, device type: string, device name: string
  • ora-00330 : archived log ends at change string, need change string
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-19654 : must use backup control file to switch file incarnations
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-37178 : column string has no values
  • ora-19321 : Could not open HTTP connection to host (string): port (string)
  • ora-19696 : control file not found in backup set
  • ora-07275 : unable to send signal to process
  • ora-01280 : Fatal LogMiner Error.
  • ora-25439 : duplicate variable value for variable: string
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • 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.