ORA-25225: invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED

Cause : An invalid parameter has been specified for DEQUEUE_MODE.

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

Specify either REMOVE, BROWSE or LOCKED.

update : 16-08-2017

ORA-25225 - invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
ORA-25225 - invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED

  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-01907 : TABLESPACE keyword expected
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-28001 : the password has expired
  • ora-25507 : resource manager has not been continuously on
  • ora-13757 : "SQL Tuning Set" "string" owned by user "string" is active.
  • ora-19040 : Element string does not match expected string.
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-16072 : a minimum of one standby database destination is required
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-31404 : all input parameters are null
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-32503 : Mapping SGA from file failed
  • ora-22609 : error string during initialization of FDO
  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-01413 : illegal value in packed decimal number buffer
  • ora-00964 : table name not in FROM list
  • ora-14178 : STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-31642 : the following SQL statement fails: string
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-25210 : invalid value for RELATIVE_MSGID, no message in queue with that msgid
  • ora-00063 : maximum number of log files exceeded string
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • 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.