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-04-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-28152 : proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
  • ora-06039 : NETDNT: connect failed
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-29536 : badly formed source: string
  • ora-01776 : cannot modify more than one base table through a join view
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-24418 : Cannot open further sessions.
  • ora-29656 : Invalid option for USING
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-06421 : NETCMN: Error detected in the read-in data
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-29353 : The transportable list is too long.
  • ora-19622 : archivelog thread string sequence string not restored due to string
  • ora-02377 : invalid resource limit
  • ora-39000 : bad dump file specification
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-24770 : cannot forget a prepared transaction
  • ora-03132 : two-task default value overflow
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-09366 : Windows 3.1 Two-Task driver unable to allocate shared memory
  • ora-02202 : no more tables permitted in this cluster
  • ora-03203 : concurrent update activity makes space analysis impossible
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-28037 : Cannot Get Session Key for RACF Authentication
  • ora-02141 : invalid OFFLINE option
  • ora-00358 : Too many file members specified, the maximum is string
  • ora-01900 : LOGFILE keyword expected
  • ora-02086 : database (link) name is too long
  • ora-29365 : parameters string and string cannot both be set
  • 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.