ORA-24014: invalid value string, RETENTION_TIME should be FOREVER or non-negative

Cause : Queue retention was specified, but the retention time was specified to be less than zero.

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

Specify the retention time to be non-negative or FOREVER. Alternately don't specify retention.

update : 25-09-2017

ORA-24014 - invalid value string, RETENTION_TIME should be FOREVER or non-negative
ORA-24014 - invalid value string, RETENTION_TIME should be FOREVER or non-negative

  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-02320 : failure in creating storage table for nested table column string
  • ora-24365 : error in character conversion
  • ora-28590 : agent control utility: illegal or badly formed command
  • ora-31022 : Element not found
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-00981 : cannot mix table and system auditing options
  • ora-28539 : gateway does not support result sets
  • ora-10663 : Object has rowid based materialized views
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-29956 : warning in the execution of ODCIINDEXEXCHANGEPARTITION routine
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-40203 : model string does not exist
  • ora-19038 : Invalid opertions on query context
  • ora-31614 : routine string received this error from string: string
  • ora-16584 : illegal operation on a standby site
  • ora-13214 : failed to compute supercell for window object
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-04940 : unsupported optimization of Oracle binary, check alert log for more info
  • ora-01974 : Illegal archive option
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-24763 : transaction operation cannot be completed now
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-19511 : Error received from media manager layer, error text: string
  • ora-30730 : referential constraint not allowed on nested table column
  • ora-01036 : illegal variable name/number
  • ora-32516 : cannot wait for ORADEBUG command completion; waited number ms for process string
  • ora-19500 : device block size string is invalid
  • ora-25952 : join index must only contain inner equi-joins
  • 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.