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 : 24-05-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-15032 : not all alterations performed
  • ora-23316 : the masterdef is string
  • ora-07232 : slemcc: fclose error.
  • ora-06115 : NETTCP: unable to create ORACLE logicals
  • ora-36991 : (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
  • ora-02420 : missing schema authorization clause
  • ora-22910 : cannot specify schema name for nested tables
  • ora-30088 : datetime/interval precision is out of range
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-24795 : Illegal string attempt made
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-00278 : log file 'string' no longer needed for this recovery
  • ora-07760 : slemtr: $open failure
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-24091 : Destination queue string is the same as the source queue
  • ora-01338 : Other process is attached to LogMiner session
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-31649 : Master process string violated startup protocol.
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-25289 : Buffer Already Exists
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-12910 : cannot specify temporary tablespace as default tablespace
  • ora-23437 : template authorization already exists for user
  • ora-00293 : control file out of sync with redo log
  • ora-25351 : transaction is currently in use
  • ora-09213 : slgfn: error fabricating file name
  • 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.