ORA-25305: enqueue failed, expiration must be zero for queue string.string

Cause : An attempt was made to enqueue to a buffered queue with expiration greater than zero seconds.

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

Set expiration to zero.

update : 27-06-2017

ORA-25305 - enqueue failed, expiration must be zero for queue string.string
ORA-25305 - enqueue failed, expiration must be zero for queue string.string

  • ora-13032 : Invalid NULL SDO_GEOMETRY object
  • ora-24762 : server failed due to unspecified error
  • ora-28011 : the account will expire soon; change your password now
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-02899 : smscre: Cannot create SGA with Extended Shared Memory feature
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-29906 : indextype string.string does not exist
  • ora-22619 : all collection elements have already been accessed
  • ora-06721 : TLI Driver: spurious client req
  • ora-26733 : timed-out waiting for file group lock
  • ora-36968 : (XSRELTBL11) workspace object must be a relation.
  • ora-36702 : (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1.
  • ora-23464 : flavor lacks column string of "string"."string"
  • ora-08181 : specified number is not a valid system change number
  • ora-16091 : dependent archive log destination already archived
  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-30343 : level name is not unique within this dimension
  • ora-40283 : missing cost matrix
  • ora-07549 : sftopn: $OPEN failure
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-12434 : invalid audit type: string
  • ora-38729 : Not enough flashback database log data to do FLASHBACK.
  • ora-27453 : %s is an invalid job or program argument 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.