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 : 28-05-2017
ORA-24014

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-31114 : XDB configuration has been deleted or is corrupted
  • ora-01080 : error in shutting down ORACLE
  • ora-28263 : Insufficient memory in global context pool
  • ora-13240 : specified dimensionality greater than that of the query mbr
  • ora-07218 : slkhst: could not perform host operation
  • ora-13707 : Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-27369 : job of type EXECUTABLE failed with exit code: string
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-16043 : managed recovery session canceled
  • ora-34358 : (MXDSS14) number other users reading
  • ora-07741 : slemop: $OPEN failure
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-16104 : invalid Logical Standby option requested
  • ora-38401 : synonym string not allowed
  • ora-25960 : join index cannot be based on a temporary table
  • ora-39171 : Job is experiencing a resumable wait. string
  • ora-14616 : table is not subpartitioned by List method
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-02881 : sou2o: Could not revoke access to protected memory
  • ora-12467 : minimum label can contain a level only
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-00205 : error in identifying control file, check alert log for more info
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-26023 : index string.string partition string was made unusable due to:
  • ora-13148 : failed to generate SQL filter
  • ora-27057 : cannot perform async I/O to file
  • 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.