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 : 22-08-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-29256 : Cursor contains both regular and array defines which is illegal
  • ora-02032 : clustered tables cannot be used before the cluster index is built
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-12664 : Services required by server not available on the client
  • ora-09989 : attempt to use invalid skgmsdef struct pointer
  • ora-32333 : disable table scn update for Materialized view
  • ora-14312 : Value string already exists in partition string
  • ora-24079 : invalid name string, names with AQ$_ prefix are not valid for string
  • ora-02041 : client database did not begin a transaction
  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-01743 : only pure functions can be indexed
  • ora-31674 : worker process interrupt for unhandled exception in master process
  • ora-19110 : unsupported XQuery expression
  • ora-26508 : null materialized view connection
  • ora-02038 : define is not allowed for array type
  • ora-28593 : agent control utility: command terminated with error
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-30368 : ATTRIBUTE cannot determine column in a different relation
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-19701 : device name exceeds maximum length of string
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-30065 : test support for row dependencies
  • ora-02785 : Invalid shared memory buffer size
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-09759 : osnsbt: bad message received.
  • ora-28367 : wallet does not exist
  • ora-25466 : data not specified for variable name: string
  • ora-19764 : database id string does not match database id string in control file
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • 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.