Replication Server version 12.5 and later can handle messages larger than 16K only if the site version is also 12.5 or later. If the site version is 12.1 or earlier, messages larger than 16K may cause the stable queue to shut down. Similarly, if a replicate or intermediate site of a route is not set to a site version of 12.5 and later, messages larger than 16K may cause the route to shut down.
If a large messages shuts down a stable queue, you can restart the queue using resume queue. To restart the queue and, optionally, to instruct Replication Server to skip the first large message encountered, enter:
resume queue, q_number, q_type[, skip transaction with large message]
q_number is the number of the queue, and q_type is either “0” for outbound queues or “1” for inbound queues.
To set default behavior for a stable queue encountering a large message, use alter queue. Enter:
alter queue, q_number, q_type,
set sqm_xact_with_large_msg to {skip | shutdown }
If a large message has shut down a route, you can restart the route using resume route. Enter:
resume route to dest_rep_server [skip transaction with large message]
dest_rep_server is the Replication Server to which the message is sent. This command applies only to direct routes.
To set default behavior for a route encountering a large message, use alter route. Enter:
alter route to dest_rep_server
set sqm_xact_with_large_msg to
{ skip | shutdown }
Replication Server marks a replication definition as compatible with Replication Server version 12.5 or later if the replication definition describes columns that contain more than 250 bytes. A 12.5 or later replication definition can only be subscribed by a replicate site if its site and route versions are 12.5 or later.
If you create or alter a replication definition that includes a rawobject or rawobject in row column, only Replication Server version 12.0 or later can subscribe to that replication definition.
You can introduce column-level and class-level datatype translations only between Replication Servers of version 12.0 or later.
If your replication system uses different versions of Replication Server (for example, version 11.0.x and version 11.5 or later), Replication Server version 11.0.x is subject to the following limitations:
You cannot subscribe to a replication definition that specifies any of the following information:
Different source and destination table names
Different source and destination column names
Source or destination table owner names
Such a replication definition is incompatible with and unavailable to Replication Servers earlier than version 11.5.
You can receive information about and subscribe to only one replication definition per table; however, when a Replication Server version 11.5 or later primary table has multiple replication definitions, the first replication definition created for the table can be marked and propagated to a Replication Server of a previous version, if it is compatible; that is, has the same primary and replicate table names, same primary and replicate column names, and does not include table owner name.
If you drop that replication definition, the next oldest 11.0.x-compatible replication definition created for that table is available for Replication Server version 11.0.x.
If subscriptions exist from Replication Server version 11.0.x, you must not alter an 11.0.x-compatible replication definition so that it is no longer compatible with 11.0.x. If you do so, that replication definition is no longer available to 11.0.x Replication Servers and the next oldest 11.0.x-compatible replication definition (if any) is available to the 11.0.x Replication Servers.
You cannot create multiple replication definitions per table or customize them for destination tables.
Unicode datatypes require Replication Server version 12.5 or later. If you are using Unicode datatypes in a mixed-version environment, see the Replication Server Design Guide.
See also“Mixed-version replication systems” for more information.
