Replication Agent for DB2 UDB 15.0 for z/OS supports extensible limits through use of the new Long_varchar configuration parameter for replication to Replication Server 15.0. If you attempt to replicate to a Replication Server 12.6 or earlier using Long_varchar=Y, you might receive the following LTM for MVS error message:
01133: “Long_varchar
forced to ‘N’ - Rep Server does not support Long_varchar.”
If you encounter this error message for Replication Server 12.5 and later, use the following procedure.
Executing the rs_del_locater
stored procedure (12.5 and later)
On the Adaptive Server containing the primary Replication Server RSSD, execute the rs_del_locater stored procedure using the following example syntax:
rs_del_locater RS_source_ds, RS_source_db
where the values for RS_source_ds and RS_source_db match the values you recorded on the Replication Agent Installation Worksheet.
The rs_del_locater stored procedure deletes some rows from the rs_locater table for the specified database connection. For more information on this and other stored procedures, see the Replication Server Reference Manual.
Restart the Replication Server.
If you encounter this error message for Replication Server 12w.1 and earlier, use this procedure.
Executing the rs_del_locater
stored procedure (12.1 and earlier)
Use isql to access the Adaptive Server containing the primary Replication Server RSSD.
Obtain the dbid for the connection using the following command:
select dbid from rs_databases where dsname = "RS_source_ds" and dbname = "RS_source_db"
RS_source_ds and RS_source_db are from the LTM configuration file.
Using the dbid obtained in step 3, ensure there is an "upgrade" record for this connection:
select * from rs_locater where sender = dbid and type = "U"
If the record exists, delete it using the following:
delete from rs_locater where sender = dbid and type = "U"
Restart the Replication Server.
