Q-Replication

Gopalan Venkatramani

Q-Replication

Hi all - I've a 2 DB2 database servers with one act as a source and other as target.One MQ replication Server.

Server         Database

TESTA          REPL1

TESTB          REPL2

 

MQ Series Server and runtime has been installed.

All 3 servers are Linux on PPC LE machines.

 

While I start the Capture service I get the following error, Has anyone faced such issues while setting you Q-Replication ?

 

>asnqcap capture_server=REPL1 capture_schema=ASNUA
2017-04-06-18.37.44.061813 ASN0600I  "Q Capture" : "" : "Initial" : Program "mqpub 10.2.1 (Build 10.5.0.7 Level s151221, PTF IP23960)" is starting.
2017-04-06-18.37.46.531157 ASN7259W  "Q Capture" : "ASNUA" : "WorkerThread" : The MAXDEPTH attribute for restart queue "ASNUA.RESTARTQ" is greater than the recommended value of 1.
2017-04-06-18.37.46.614075 ASN0575E  "Q Capture" : "ASNUA" : "WorkerThread" : The program encountered a WebSphere MQ error "2085 (MQRC_UNKNOWN_OBJECT_NAME)" while issuing the WebSphere MQ command "MQOPEN" on object "ASNUA.REPL1_TO_ASNUB.REPL2.DATA".
[asnqwk] Leaving the asnqwk thread:
[asnqwk] total database transactions captured = 0
[asnqwk] total MQSeries transactions          = 0
[asnqwk] total DB transactions published      = 0
[asnqwk] total time WAITING for logrd         = 0.000 second(s)
2017-04-06-18.37.47.116279 ASN7109I  "Q Capture" : "ASNUA" : "WorkerThread" : At program termination, the lowest log sequence number of a transaction still to be committed (LSN) is "0000:0000:0000:0000:0000:0000:0000:0000" and the highest log sequence number of a successfully processed transaction (MAXCMTSEQ) is "0000:0000:0000:0000:0000:0000:0000:0000".
2017-04-06-18.37.50.042481 ASN0573I  "Q Capture" : "ASNUA" : "Initial" : The program stopped. Reason: "program error"

Regards

Glenn

 

 

Gopalan Venkatramani

DB2 LUW

Olaf Stephan

RE: Q-Replication
(in response to Gopalan Venkatramani)

Hello,

 

check your configuration either the Replication Queue Maps, the names for the send/receive Queues or the queue definitions in the Q-Managers.

 

 

mqrc 2085

      2085  0x00000825  MQRC_UNKNOWN_OBJECT_NAME

Gopalan Venkatramani

RE: Q-Replication
(in response to Olaf Stephan)

Hi all thanks for pitching into this issue. I fixed the issue.

I dropped the Q-Manager and recreated with as follows,

I cataloged the database with an Alias REPL1 and REPL2 respectively

The command 

MQSERVER 1 NAME TESTA MQHOST "lhqsb1db2db01.com"  MQPORT 2510 QMANAGER QMUA QNAME_QUAL ASNUA,
MQSERVER 2 NAME TESTB  MQHOST "lhqsb1db2db01.com"  MQPORT 2511 QMANAGER QMUB QNAME_QUAL ASNUB;

MQSERVER 1 NAME REPL1 MQHOST "lhqsb1db2db01.com"  MQPORT 2510 QMANAGER QMUA QNAME_QUAL ASNUA,
MQSERVER 2 NAME REPL2 MQHOST "lhqsb1db2db01.com"  MQPORT 2511 QMANAGER QMUB QNAME_QUAL ASNUB;

I changed the TESTA to REPL1 and TESTB to REPL2. 

I was able to start both Capture and Apply program.

Thank.

Regards

Glenn


 

 

Gopalan Venkatramani

DB2 LUW

Charles Brown

Q-Replication
(in response to Gopalan Venkatramani)
Hello Glenn,



Glad to hear you had your Q-Rep issue resolved. Q-rep issue can be a nightmare. I’m wondering though – have you tried the Q-Rep Dashboard. Trust me – this tool makes life much easier supporting Q-rep. It is free – meaning you can download from IBM at no cost. It’s also available for mobile devices – tablets I would recommend.



Thanks

Chas/b

NZ DBA



From: Gopalan Venkatramani [mailto:[login to unmask email]
Sent: Friday, April 07, 2017 11:29 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: Q-Replication



Hi all thanks for pitching into this issue. I fixed the issue.

I dropped the Q-Manager and recreated with as follows,

I cataloged the database with an Alias REPL1 and REPL2 respectively

The command

MQSERVER 1 NAME TESTA MQHOST "lhqsb1db2db01.com" MQPORT 2510 QMANAGER QMUA QNAME_QUAL ASNUA,
MQSERVER 2 NAME TESTB MQHOST "lhqsb1db2db01.com" MQPORT 2511 QMANAGER QMUB QNAME_QUAL ASNUB;

MQSERVER 1 NAME REPL1 MQHOST "lhqsb1db2db01.com" MQPORT 2510 QMANAGER QMUA QNAME_QUAL ASNUA,
MQSERVER 2 NAME REPL2 MQHOST "lhqsb1db2db01.com" MQPORT 2511 QMANAGER QMUB QNAME_QUAL ASNUB;

I changed the TESTA to REPL1 and TESTB to REPL2.

I was able to start both Capture and Apply program.

Thank.

Regards

Glenn







Gopalan Venkatramani

DB2 LUW



-----End Original Message-----

Gopalan Venkatramani

RE: Q-Replication
(in response to Charles Brown)

Hi Thank you so much for the suggestion. I'm running the MQ replication on PPC LE and I don't see a version that supports.

Glenn

DB2 LUW

Jørn Thyssen

RE: Q-Replication
(in response to Gopalan Venkatramani)

Hi,

you can install the dashboard on any other server or your own workstation 

Best regards,

Jørn Thyssen

Works for IBM Denmark. Views are personal. 

Gopalan Venkatramani

Q-Replication
(in response to Jørn Thyssen)
Hi Jorn - I've installed the IIDR Dashboard on my laptop. Its making my
life easier as you said. Thank you.

Regards
Glenn

On 9 April 2017 at 07:51, Jørn Thyssen <[login to unmask email]> wrote:

> Hi,
>
> you can install the dashboard on any other server or your own workstation
>
> Best regards,
>
> Jørn Thyssen
>
> Works for IBM Denmark. Views are personal.
>
> -----End Original Message-----
>

Gopalan Venkatramani

RE: Q-Replication
(in response to Gopalan Venkatramani)


Hi all - With advice of IBM I've installed db2 connect on my laptop to take db2rc to configure Q-Replication. I cataloged the databases in my laptop and the connect is successful however during the Create Q Capture Control Tables Wizard -- > Start -- > Custom : Specify your own settings. --- > Server --- > Pick the server / DB --- > Specify a Q Capture schema --  > ASN after this when I click Next I see an error 

"ASN2023E The database platform "", version "" on server "MQDB" is not supported."

My DB2 connect version is 10.1 FP4 but the db2rc version is I believe 9.

Is it because of the version difference that I'm getting this error ?

 

Regards

Glenn

 

 

Gopalan Venkatramani

DB2 LUW

Gopalan Venkatramani

RE: Q-Replication
(in response to Gopalan Venkatramani)

It was a Version issue between DB2 Connect and database. So I downloaded the db2 luw 11.1 and installed a new db2 connect and I'm all good.

Thank you...

Glenn