Q-replication for 3 tables

Gopalan Venkatramani

Q-replication for 3 tables

I was able to start the capture without any issue and also apply program but the table is not getting replicated I'm seeing this all time in my apply logs
DB2 LUW - 10.5 - Linux. Can anyone please help me ?

 

2017-07-27-18.13.28.703656 <browser::browser> ASN8999D MQOPEN(Exclusive) for queue 'ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA' was successful. Browser will MQCLOSE and do MQOPEN(Shared).
2017-07-27-18.13.28.731998 <browser::cleanDoneMsg> ASN8999D Browser for queue 'ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA' will start cleaning the DONEMSG table.
2017-07-27-18.13.28.734554 <browser::browser> ASN8999D browser for queue 'ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA' did not find any msgID after cleaning IBMQREP_DONEMSG table on startup.
2017-07-27-18.13.28.735036 <brwzMain> ASN7526I "Q Apply" : "ASNTGT" : "BR00000" : The Q Apply program has started processing the receive queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA" for replication queue map "ASNSRC_TO_ASNTGT".
2017-07-27-18.13.28.735146 <brwzMain> ASN8999D Browser('ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA') uses MEMORY_LIMIT=64 MB, AGENTS=16, MAXAGENTS_CORRELID=0, PARALLEL_SENDQS=N, AGENT_STMT_CACHE_SZ=300, MRI_MEMORY_LIMIT=1024.
2017-07-27-18.13.28.736883 <appAgntMain> ASN8999D agent 004 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.736952 <appAgntMain> ASN8999D agent 001 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.737489 <appAgntMain> ASN8999D agent 007 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.737502 <appAgntMain> ASN8999D agent 003 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.738263 <appAgntMain> ASN8999D agent 005 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.739142 <appAgntMain> ASN8999D agent 006 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.740158 <appAgntMain> ASN8999D agent 002 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.742241 <appAgntMain> ASN8999D agent 009 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"
2017-07-27-18.13.28.742542 <appAgntMain> ASN8999D agent 008 started for queue "ASNSRC.CMSDB_TO_ASNTGT.DB2OC_1.DATA"

 

 

Gopalan Venkatramani

DB2 LUW

J&#248;rn Thyssen

RE: Q-replication for 3 tables
(in response to Gopalan Venkatramani)

Hi,

Troubleshooting item #1 when working with Q replication: 

Check that all MQ channels are up and running, and that there are not messages queued up anywhere in the system  

 

Best regards,

Jørn Thyssen

Rocket Software
77 Fourth Avenue • Waltham, MA • 02451 • USA
E: [login to unmask email] • W: www.rocketsoftware.com 

Views are personal. 

Gopalan Venkatramani

RE: Q-replication for 3 tables
(in response to Jørn Thyssen)


 

 Hi Thyssen - Thanks for your response. I was running two MQ server on the same machine with same port. So as soon as I shutdown the other mqm service the other started replicating. All good.

 

I've question in schema replication. Does schema replication supports generated always column ? Because I started schema replication for 600+ tables on a particular schema but none of the generated always tables were able to replicate. But I was able to replicate 250+ tables. 

I'm planning to go back to create subscription for each and every table instead of doing a full schema subscribed replication per discussion with other Q-Replication dba outside my company.

Anyone has any suggestion on replicating 600+ tables?

 

Gopalan Venkatramani

DB2 LUW