ORA-25955: all tables must be joined in the where clause

Cause : An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.

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

Ensure that the where clause contains all from clause tables.

update : 25-04-2017

ORA-25955 - all tables must be joined in the where clause
ORA-25955 - all tables must be joined in the where clause

  • ora-06916 : CMX: error in data read (t_datain)
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-36678 : (XSDPART16) workspace object is missing from one or more partition dimension lists.
  • ora-19635 : input and output filenames are identical: string
  • ora-02438 : Column check constraint cannot reference other columns
  • ora-07486 : scg_get_inst: cannot convert(get) instance number lock.
  • ora-19670 : file string already being restored
  • ora-28521 : no heterogeneous capability information available
  • ora-14401 : inserted partition key is outside specified partition
  • ora-01603 : illegal grouping size in clause "string" of string
  • ora-16753 : resource guard could not open standby database
  • ora-03128 : connection is in blocking mode
  • ora-16089 : archive log has already been registered
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-32167 : No payload set on the Message
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-29287 : invalid maximum line size
  • ora-36704 : (XSRELTBL06) workspace object should be dimensioned by workspace object.
  • ora-12670 : Incorrect role password
  • ora-38732 : Expected file size string does not match string.
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-12203 : TNS:unable to connect to destination
  • ora-39022 : Database version string is not supported.
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-19270 : XP0050 - treat failed - expected string got string
  • ora-01626 : rollback segment number 'string' cannot handle more transactions
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-01898 : too many precision specifiers
  • 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.