ORA-25276: table specified is not a queue table

Cause : An invaild queuet able naem is speicfied.

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

Check teh dictioanry view sto see fi the talbe is a uqeue tabel.

update : 18-08-2017
ORA-25276

ORA-25276 - table specified is not a queue table
ORA-25276 - table specified is not a queue table

  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-28539 : gateway does not support result sets
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-12926 : FORCE LOGGING option already specified
  • ora-29306 : datafile string is not online
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-02234 : changes to this table are already logged
  • ora-22167 : given trim size [string] must be less than or equal to [string]
  • ora-32130 : invalid offset/index refrenced in Bytes
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-02082 : a loopback database link must have a connection qualifier
  • ora-19111 : error during evaluation of the XQuery expression
  • ora-01326 : compatability of 9.0 or greater required to build into the logstream
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-06407 : NETCMN: unable to set up break handling environment
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-19595 : archivelog string already included in backup conversation
  • ora-36994 : (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
  • ora-15184 : ASMLIB error could not be determined [string] [string]
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-02038 : define is not allowed for array type
  • ora-07548 : sftopn: Maximum number of files already open
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-02169 : FREELISTS storage option not allowed
  • 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.