Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
parthiTA
Contributor II
Contributor II

How to resolve error 1000123 ( undefined symbol: db2ReadLog)?

Can you please help us understand why we see erro 100123 (undefined symbol: db2ReadLog?

Trying to replicate from on-prem DB2-LUW to DB2-LUW on cloud, using user credentials that has read access on the source database, and full permission on the target database.

Is this error related to user privileges or the client driver? If related to user privileges, what additional privileges are needed?

Appreciate your help.

 

00008036: 2022-03-03T12:47:54 [TASK_MANAGER ]I: All stream components were initialized (replicationtask.c:3609)
00008039: 2022-03-03T12:47:54 [AT_GLOBAL ]I: Dynamic loading 'libdb2o.so' (db2luw_endpoint_util.c:1949)
00008041: 2022-03-03T12:47:54 [SORTER ]I: Sorter last run state: confirmed_record_id = 0, confirmed_stream_position = '' (sorter_transaction.c:3251)
00008036: 2022-03-03T12:47:54 [TASK_MANAGER ]I: Task error notification received from subtask 0, thread 0, status 1000123 (replicationtask.c:3433)
00008036: 2022-03-03T12:47:54 [TASK_MANAGER ]W: Task 'DDOLT onprem - DDOLD AWS' encountered a recoverable error (repository.c:5795)
00008041: 2022-03-03T12:47:54 [SORTER ]I: Final saved task state. Stream position , Source id 0, next Target id 1, confirmed Target id 0, last source timestamp 0 (sorter.c:770)
00008039: 2022-03-03T12:47:54 [INFRASTRUCTURE ]E: Failed to get symbol <db2ReadLog>: /apps/db2/odbc_cli/clidriver/lib/libdb2o.so: undefined symbol: db2ReadLog [1000124] (at_loader.c:223)
00008039: 2022-03-03T12:47:54 [INFRASTRUCTURE ]E: <Failed to get symbol <db2ReadLog>: No such file or directory> and the dll name: <libdb2o.so> [1000123] (at_loader.c:484)
00008039: 2022-03-03T12:47:54 [AT_GLOBAL ]E: Error Initializing endpoint. Failed to load libdb2o.so [1000123] (db2luw_endpoint_util.c:1954)
00008039: 2022-03-03T12:47:54 [SOURCE_CAPTURE ]E: Error loading DB2 CLI library [1000123] (db2luw_endpoint_capture.c:2709)
00008039: 2022-03-03T12:47:54 [SOURCE_CAPTURE ]E: capture_start: in agent_setup [1000123] (db2luw_endpoint_capture.c:3064)
00008039: 2022-03-03T12:47:54 [SOURCE_CAPTURE ]E: Error executing command [1000123] (streamcomponent.c:2024)

11 Replies
parthiTA
Contributor II
Contributor II
Author

Just to update on this topic: We cleaned up the Full load tasks and the full load also works. Thanks to everyone of you for your support.

Regards

Parthiban

john_wang
Support
Support

Hello @parthiTA , 

Agree with @Heinvandenheuvel that a new topic or support case is much better - just keeps a topic simple and easy to understand. 

Before we close this article I'd like to share an observation... not sure how you created the task, the task name exceeds the max length limitation, 32 chars. Seems your task name is 43 chars? "DB2LUWSourceDBDB - DB2LUWTargetDB Full Load" (looks like by modifying-json-then-importing?). Maybe this is not the root reason but shorten it to avoid other potential issues.

thank you,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!