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 : 23-09-2017
ORA-39600

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-04085 : cannot change the value of an OLD reference variable
  • ora-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-15031 : disk specification 'string' matches no disks
  • ora-16212 : number processes specified for APPLY is too great
  • ora-31649 : Master process string violated startup protocol.
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-32732 : Parallel Oradebug session is aborted
  • ora-02287 : sequence number not allowed here
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-10627 : Dump the content of the index leaf block
  • ora-26563 : renaming this table is not allowed
  • ora-01136 : specified size of file string (string blocks) is less than original size of string blocks
  • ora-13860 : Invalid service name
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-31079 : unable to resolve reference to string "string"
  • ora-06761 : TLI Driver: error sending orderly release
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-22808 : REF dereferencing not allowed
  • ora-23471 : template not authorized for user
  • ora-24030 : Only one of rule or rule-set must be specified
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-36830 : (XSLMGEN00) AW name cannot be NA
  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-28556 : authorization insufficient to access table
  • ora-36266 : (XSCGMDLAGG00) Invalid context for the AGGREGATION function
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-27200 : skgfpgo: sbtpcstart returned error
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-02201 : sequence not allowed here
  • 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.