ORA-39600: Queue keys needs to be a suffix of cluster key.

Cause : Attempt to specify queue key columns that don't form a suffix of the cluster key.

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

Only specify queue key columns as a suffix of cluster key.

update : 26-07-2017

ORA-39600 - Queue keys needs to be a suffix of cluster key.
ORA-39600 - Queue keys needs to be a suffix of cluster key.

  • ora-16160 : Cannot change protected standby database configuration
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-12531 : TNS:cannot allocate memory
  • ora-31644 : unable to position to block number string in dump file "string"
  • ora-06907 : CMX: error during connect confirmation
  • ora-07744 : slemcl: invalid error message file handle
  • ora-07755 : slemcf: fseek before read failure
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-24098 : invalid value string for string
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-03002 : operator not implemented
  • ora-13621 : The task_or object string is marked as a template and cannot perform the requested operation.
  • ora-13140 : invalid target type
  • ora-02167 : LOGFILE clause specified more than once
  • ora-39006 : internal error
  • ora-01183 : cannot mount database in SHARED mode
  • ora-02277 : invalid sequence name
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-13631 : The task string contains no execution results.
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-29552 : verification warning: string
  • ora-25103 : NOPARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-06573 : Function string modifies package state, cannot be used here
  • ora-32578 : password for SYS already specified
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • 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.