ORA-25261: JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation

Cause : AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.

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

Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation.

update : 25-06-2017

ORA-25261 - JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
ORA-25261 - JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation

  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-28554 : pass-through SQL: out of cursors
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-14072 : fixed table may not be truncated
  • ora-16243 : paging out string bytes of memory to disk
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-36280 : (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model.
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-38750 : FLASHBACK DATABASE may not be performed using a dispatcher.
  • ora-32014 : error processing parameter "string" from the SPFILE restore image
  • ora-08275 : Environment variable unset
  • ora-03279 : invalid INSTANCE specified
  • ora-04095 : trigger 'string' already exists on another table, cannot replace it
  • ora-32578 : password for SYS already specified
  • ora-13287 : can't transform unknown gtype
  • ora-39777 : data saves are not allowed when loading lob columns
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-39082 : Object type string created with compilation warnings
  • ora-24776 : cannot start a new transaction
  • ora-07670 : $IDTOASC failed translating a secrecy category
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-24143 : invalid evaluation context name
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-39315 : call to DBMS_SCHEMA_COPY.SWAP is not legal
  • ora-14606 : Tablespace was specified for previous subpartitions in template but is not specified for string
  • ora-00063 : maximum number of log files exceeded string
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • 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.