Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2013
    Posts
    31

    Unanswered: How to determine our version of Q Apply

    Does anyone know how to determine which version of Q Apply we're running? we have a Test DB2 replication server that's been offline for some time, and I'm trying to resurrect it. When I try to start the Q Apply service though I'm getting this error:

    2013-05-09-09.57.00.165000 <browser::verifyMsgVersion> ASN7515E "Q Apply" : "ASN" : "BR00000" : The Q Apply program cannot process message type "ASNMQ_HEARTBEAT" of version "4".
    2013-05-09-09.57.00.259000 <browser::readNextMsg> ASN0589I "Q Apply" : "ASN" : "BR00000" The program received an unexpected return code "6004" from routine "browser::verifyMsgVersion".
    2013-05-09-09.57.00.275000 <browser::readNextDenseMsg> ASN0589I "Q Apply" : "ASN" : "BR00000" The program received an unexpected return code "6004" from routine "browser::readNextMsg".
    2013-05-09-09.57.00.275000 <brwzMain> ASN0589I "Q Apply" : "ASN" : "BR00000" The program received an unexpected return code "6004" from routine "browser:rocessRecvQ".

    Per IBM our version of Q Capture and Q Apply aren't compatible, but I'm unsure how to determine what versions we're running so I can upgrade it if needed.

    Thanks.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    When you run the corresponding control commands (asnqccmd and asnqacmd) they print out their respective versions. I'm guessing they should match the version of the installed capture and apply programs.
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Feb 2013
    Posts
    31

    SQL Apply not connecting

    Quote Originally Posted by n_i View Post
    When you run the corresponding control commands (asnqccmd and asnqacmd) they print out their respective versions. I'm guessing they should match the version of the installed capture and apply programs.
    Thanks, and actaully running the command through db2cmd is returning a more verbose error anyway so maybe you or someone else can help with this. It was giving a user login error, so I used asnpwd to define the password and alias then ran it again with the Replication path to get this result:


    asnqapp apply_server=DB2_Test_DB apply_schema=TestSchema apply_path="D:\replication"

    2013-05-09-12.02.29.038000 ASN0600I "Q Apply" : "" : "Initial" : Program "mqapply 9.1.0" is starting.

    2013-05-09-12.02.29.178000 ASN0552E "Q Apply" : "TestSchema" : "Initial" : The program encountered an SQL error. The server name is "DB2_Test_DB". The SQL request is "sqlmonss". The table name is "N/A". The SQLCODE is "-1013". The SQLSTATE is "42705". The SQLERRMC is "". The SQLERRP is "SQLMAGN1".

    2013-05-09-12.02.29.178000 SQL1013N "Q Apply" : "TestSchema" : "Initial" : The database alias name or database name "" could not be found. SQLSTATE=42705

    2013-05-09-12.02.29.178000 ASN0534E "Q Apply" : "TestSchema" : "Initial" : DB2 "DB2_Test_DB" cannot be used, because it is in the "UNDETERMINED" state.

    2013-05-09-12.02.29.210000 SQL1442N "Q Apply" : "TestSchema" : "Initial" : The context is not in use or is not in use by the current thread. Reason code "2".

    2013-05-09-12.02.29.210000 SQL1444N "Q Apply" : "TestSchema" : "Initial" : The application context cannot be destroyed because it is in use.
    I'm scowering the DB2 docs and Red Books looking for a solution, but it's acting like it can't connect to the database given it's saying UNDETERMINED state. I can ping the database server, and I can browse to it with no problems in Control Center. I also verified the connection and password in Connection Assistant. What else can I check?

    Thanks.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    SQLCODE -1013 means you are trying to connect to a database that does not exist, and the database name or alias is shown as an empty string. I'm not very familiar with replication so I cannot tell you where to check that you have specified a valid database alias.
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •