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 : 24-08-2017
ORA-25337

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-00329 : archived log begins at change string, need change string
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-13447 : GeoRaster metadata BRS error
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-25156 : old style outer join (+) cannot be used with ANSI joins
  • ora-23468 : missing string string
  • ora-27459 : A program of type EXECUTABLE must have character-only arguments.
  • ora-16029 : cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-04060 : insufficient privileges to execute string
  • ora-13191 : failed to read SDO_ORDCNT value
  • ora-00034 : cannot string in current PL/SQL session
  • ora-16722 : unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-07706 : error in archive text: need disk file name
  • ora-25531 : MTTR specified is too small: string
  • ora-21527 : internal OMS driver error
  • ora-08309 : sllfop: Cannot fstat file
  • ora-29829 : implementation type does not exist
  • ora-01345 : must be a LogMiner coordinator process
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-02820 : Unable to write the requested number of blocks
  • ora-16653 : failed to reinstate database
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-12323 : unable to open database (link name string)
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • 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.