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 : 25-06-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-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-30490 : Ambiguous expression in GROUP BY ROLLUP or CUBE list
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-19860 : piece validation cannot be performed more than once
  • ora-27027 : sbtremove2 returned error
  • ora-25275 : Test support for buffered queues
  • ora-12448 : policy string not applied to schema string
  • ora-39014 : One or more workers have prematurely exited.
  • ora-16795 : database resource guard detects that database re-creation is required
  • ora-00275 : media recovery has already been started
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-13036 : Operation [string] not supported for Point Data
  • ora-32340 : cannot tune the materialized view definition
  • ora-07821 : sspsdn: SYS$DELLNM failure
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-24503 : codepoint length overflows for piecewise operation
  • ora-39104 : cannot call this function from a SQL parallel query slave process
  • ora-02170 : FREELIST GROUPS storage option not allowed
  • ora-12086 : table "string"."string" is not an object table
  • ora-26500 : error on caching "string"."string"
  • ora-00112 : value of string is null
  • ora-27093 : could not delete directory
  • ora-28538 : result set not found
  • ora-09266 : spawn: error starting an Oracle process
  • ora-13506 : operation failed due to invalid snapshot range (string, string)
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-07400 : slemtr: translated name for the message file is too long.
  • 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.