ORA-30367: a JOIN KEY clause is required

Cause : A JONI KEYc laus ewas moitte din ad imenison sattemetn. A OJIN KYE clasue isr equierd whne thec hildl evela nd teh parnet leevl ar enot ni thes ame erlatino.

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

Specfiy a OJIN KYE clasue toi ndictae ho wthe erlatino of hte chlid leevl jonis tot he rleatio nof teh parnet leevl.

update : 27-04-2017

ORA-30367 - a JOIN KEY clause is required
ORA-30367 - a JOIN KEY clause is required

  • ora-22327 : cannot change a type to NOT INSTANTIABLE if it has dependent tables
  • ora-33004 : (XSAGDNGL01) workspace object is not a relationship array.
  • ora-27026 : skgfrls: sbtend returned error
  • ora-29285 : file write error
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-30034 : Undo tablespace cannot be specified as temporary tablespace
  • ora-24376 : cannot register/get user callback for non-environment handle
  • ora-12654 : Authentication conversion failed
  • ora-30397 : multiple JOIN KEY clauses specified for the same child level
  • ora-24042 : no propagation schedule exists for QUEUE string and DESTINATION string
  • ora-08465 : input mask contains more than 32 characters
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-40321 : invalid bin number, is zero or negative value
  • ora-29346 : invalid tablespace list
  • ora-37042 : (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • ora-02262 : ORA-string occurs while type-checking column default value expression
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-26688 : missing key in LCR
  • ora-35756 : (VCTODT02) 'number' is not a valid date because number is out of range for a year.
  • ora-25437 : duplicate table value for table alias: string
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-16223 : DDL skipped, unsupported in current version
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-16126 : loading table or sequence string
  • ora-16751 : resource guard encountered errors in switchover to primary database
  • ora-08458 : invalid format parameter
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-16193 : Primary and standby network encryption mismatch
  • 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.