cancel
Showing results for 
Search instead for 
Did you mean: 

Smart Data Integration - DB2LogReader (initial + realtime) - Failed Init.

Helle everyone,

currently I face an issue which i can't solve myself. Maybe I will find a solution by posting my challenge.

Scenario:

  • DB2 is connected via DB2LogReader Adapter to XSA using Smart Data Integration
  • Created a replication task which loads one single table
  • Load mode is "intial + realtime" and preserve all

Note: The scenario described above worked pretty fine for about two hours. We captured every single data change coming from the DB2 source system. At one point we truncated the table we had in use for testing directly within DB2. Since then I am no longer able to get a replication task mode "initial + realtime" running although "initial only" works as fine as before.

So the moment I execute the replication task in "initial + realtime" i receive the following error message:

Could not execute 'CALL "DELTA_XXX"."DataWareHouse.Database.Replication ...'
Error: (dberror) [686]: start task error: "DELTA_XXX"."DataWareHouse.Database.Replication Tasks::XXX_DELTA.START_REPLICATION": line 27 col 6 (at pos 1110): [140038] Error executing SQL command in task.;Error executing ALTER_REMOTE_SUBSCRIPTION_QUEUE with command: 'ALTER REMOTE SUBSCRIPTION "DELTA_XXX"."SUB_XXX" QUEUE'. ,exception 71000129: SQLException
exception 71000256: QUEUE: SUB_XXX: Failed to add subscription for remote subscription SUB_XXX[id = 16579466] in remote source XXX_LogReader[id = 14918173]. Error: exception 151050: CDC add subscription failed: RS[XXX_LogReader]: Failed to add the first subscription. Error: Failed to subscribe table ["SCHEMA"."XXX"]. Error: Initialization for replication of database <XXX> has not been done.

Maybe you guys have a working solution for me. Thanks in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi Denys,

yes, we already worked through the provided documents. At the moment we are looking at the following note

- Verify the Current Archive Setting of the Transaction Log (LINK)

Scenario:

Standard approach recommended by SAP: Using LOGARCHMETH1

Currently in use due to safety reasons: Using a copy of LOGARCHMETH1 as LOGARCHMETH2 since LOGARCHMETH1 is used as backup. But the path to that is currently set to "Off" so we have no access to that logs (and we don't know why it has been set to "Off" since it was working fine for a while)

Solution: Restart DB2

dvankempen
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Sunny,

Thanks for posting your question on the forum.

I am not familiar with the configuraiton with DB2 but from the documentation and notes, I understand the database (server) needs to initialized. The steps to perform are different for each RDBMS but for DB2 are documented here:

Did you go through these steps and does the issue still persists?

Thanks