ORA-25966: join index cannot be based on an index organized table

Cause : An attempt to create a join index was made, which failed because one of the tables was an index organized table.

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

Ensure no underlying tables are index organized.

update : 18-08-2017

ORA-25966 - join index cannot be based on an index organized table
ORA-25966 - join index cannot be based on an index organized table

  • ora-13061 : topology with the name string does not exist
  • ora-22337 : the type of accessed object has been evolved
  • ora-14167 : only one subpartition may be moved
  • ora-12321 : database (link name string) is not open and AUTO_MOUNTING=FALSE
  • ora-06792 : TLI Driver: server cannot exec oracle
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-19762 : invalid file type string
  • ora-27476 : "string.string" does not exist
  • ora-29926 : association already defined for the object
  • ora-13236 : internal error in R-tree processing: [string]
  • ora-16953 : Type of SQL statement not supported.
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-07742 : slemop: $CONNECT failure
  • ora-16237 : SGA specified for Logical Standby is too small
  • ora-37070 : You may not execute OLAP DML programs in a parallel query session.
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-22920 : row containing the LOB value is not locked
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-38955 : Source platform string not cross platform compliant
  • ora-02261 : such unique or primary key already exists in the table
  • ora-15100 : invalid or missing diskgroup name
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-19617 : file string contains different resetlogs data
  • ora-06810 : TLI Driver: could not set the IPX ethernet SAP at init
  • ora-19117 : invalid redefinition of predefined namespace prefix 'string'
  • ora-29357 : object string already exists
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • 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.