ORA-25337: Cannot propagate in queue-to-queue mode to a database with version lower than 10.2

Cause : Remote subscriber with queue_to_queue mode set to TRUE was added. The remote subscriber is on a database version lower than 10.2. Propagation was scheduled to a destination database with version lower than 10.2.

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

Remove the remote subscriber with queue_to_queue mode and add the subscriber back with queue_to_queue set to FALSE. Unschedule the queue-to-queue propagation and schedule propagation in queue-to-dblink mode.

update : 27-04-2017

ORA-25337 - Cannot propagate in queue-to-queue mode to a database with version lower than 10.2
ORA-25337 - Cannot propagate in queue-to-queue mode to a database with version lower than 10.2

  • ora-15008 : cannot drop system template
  • ora-13616 : The current user string has not been granted the ADVISOR privilege.
  • ora-22280 : no more buffers available for operation
  • ora-01140 : cannot end online backup - all files are offline or readonly
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-09200 : sfccf: error creating file
  • ora-02444 : Cannot resolve referenced object in referential constraints
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-01336 : specified dictionary file cannot be opened
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-02161 : invalid value for MAXLOGFILES
  • ora-31054 : The string operator cannot have an ancillary operator
  • ora-07601 : spguno: $GETJPIW failure
  • ora-08190 : restore point string is from a different incarnation of the database
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-01509 : specified name 'string' does not match actual 'string'
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-29506 : invalid query derived from USING clause
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-07685 : sou2os: supervisor stack set error
  • ora-39033 : Data cannot be filtered under the direct path access method.
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-23347 : datatype string for column string table string not supported
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-32806 : value for string is too long, maximum length is string
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-38451 : index is in an inconsistent state
  • ora-12092 : cannot online redefine replicated table "string"."string"
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-19247 : XQ0027 - validation error
  • 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.