Consider posting the full capture log here (or the lines that get appended when capture tries to begin), or at least selected columns/rows that get added in asn.ibmsnp_captrace when capture tries to begin from the replication-centre. If the database-name is mangled in the log file and ibmsnap_captrace then all bets are off as to the real cause.
Secondly, suggest you manually start asncap, taking care to specify all the arguments correctly on the command-line, simply to compare the behaviour and results. By doing it that way, you are temporarily eliminating any differences that might be caused by the GUI using unintended startup arguments for capture, due to misconfiguration.
------------------------------
Mike O'Reilly
------------------------------
Original Message:
Sent: Thu April 11, 2024 04:54 PM
From: Alex Kogan
Subject: SQL Replication complaining about LOGRETAIN1
Hi,
Setting up SQL Replication between 2 database. Both are on DB2 v10.5.0.8. Both set up with (LOGARCHMETH1) = LOGRETAIN and yet when I try to Start Capture Program via Replication Center it is giving me this error.
Database [Ljava.lang.String;@aa50d18a needs to be configured with LOGARCHMETH1=LOGRETAIN. Use the Enable Database for Replication window to set the LOGARCHMETH1 value.
Also, not sure why it is changing source db name to "[Ljava.lang.String;@aa50d18a"
Thank you
Alex
------------------------------
Alex Kogan
------------------------------