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-07-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-15079 : ASM file is closed
  • ora-23607 : invalid column "string"
  • ora-01620 : no public threads are available for mounting
  • ora-13448 : GeoRaster metadata BRS error
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-12054 : cannot set the ON COMMIT refresh attribute for the materialized view
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-00827 : could not shrink sga_target to specified value
  • ora-15019 : discovered duplicate path 'string' for 'string'
  • ora-02737 : osnpcl: cannot tell orapop to exit
  • ora-01591 : lock held by in-doubt distributed transaction string
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-01170 : file not found 'string'
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-12027 : duplicate filter column
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-38444 : statistics do not exist for the expression set
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-19261 : XQ0041 - non empty URI in QName
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • ora-01769 : duplicate CLUSTER option specifications
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-02088 : distributed database option not installed
  • ora-23615 : Block number string does not exist for script string
  • ora-13517 : Baseline (id = string) does not exist
  • 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.