This article aims to give basic information on how to read a Qlik Replicate log.
Let's begin by identifying error messages based on their severity (Information, Warning, etc.). For more detailed information on how to analyze the logs, see How to analyze a Qlik Replicate log.
Information is identified with ]I:
Example:
00007928: 2022-03-02T13:23:08 [TASK_MANAGER ]I:
00011964: 2022-03-02T13:23:08 [SERVER ]I:
Warnings are identified with ]W:
Example:
00013992: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]W: mssql_always_on_is_healthy(...) No data passed back upon querying for AlwaysOn HEALTH state. State is assumed as NOT HEALTHY. (sqlserver_log_queries.c:7653)
Errors are identified with ]E:
00013992: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]E:
00013992: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]E:
When logging is set to trace, the lines are identified with ]T:
00005892: 2022-03-01T14:55:09 [TASK_MANAGER ]T: Sending control record to component st_0_filet1. Command
00005892: 2022-03-01T14:55:09 [TASK_MANAGER ]T: Wait for termination of the thread of 'st_0_logstrem1SQL_S_79 1' component (subtask.c:1608)
00006320: 2022-03-01T14:55:09 [UTILITIES ]E: File 'd:\logpurge\sql2logstream1\LOG_STREAM\audit_service\20211008084234948556\3' already purged, position does not exist [1002510] (at_audit_reader.c:799)
Logging set to verbose can be identified with ]V:
This is a breakdown of a Qlik Replicate log on Windows:
00009012: 2022-03-01T14:55:08 [AT_GLOBAL ]I: Task Server Log - sql2file2 (V2021.11.0.140 SGU-Win2019-SQL Microsoft Windows Server 2012 (build 9200) 64-bit, Revision:3ccf18c35dc3321f2471ba46adbe4485d60c2515, PID: 7948) started at Tue Mar 01 14:55:08 2022 (at_logger.c:2680)
sql2file2: The task name.
V2021.11.0.140: Qlik Replicate version
PID: 7948: The Windows PID. If you open windows task manager, you would see this PID, and the process is repctl.exe.
00009012: 2022-03-01T14:55:08 [AT_GLOBAL ]I: Licensed to QLIK CUSTOMER, evaluation license (0 days remaining), all sources, all targets, all hosts (at_logger.c:2683)
This is the Qlik Replicate license information.
00009012: 2022-03-01T14:55:08 [INFRASTRUCTURE ]I: The log level for 'TASK_MANAGER' has been changed from 'INFO' to 'TRACE'. (at_logger.c:2927)
This indicates to what level the logging information is set (example: trace, verbose, etc..) as well as on which component it has been set.
NOTE: If you have example source_capture trace / verbose, but in the log, it shows just info, then you have to enable: Store trace/verbose logging in memory, but if an error occurs write to the logs - turn this off, if you want trace/verbose logging.
00009012: 2022-03-01T14:55:08 [TASK_MANAGER ]I: Task 'sql2file2' running full load and CDC in resume mode (replicationtask.c:1690)
This records if a task is full load only or full load and CDC. It will also record if this is a fresh start, resume mode, recoverable error, or resumed from timestamp.
00007928: 2022-03-02T13:22:58 [METADATA_MANAGE ]I: Target endpoint 'SQL Server' is using provider syntax 'SQLServer' (provider_syntax_manager.c:875)
This identifies the target endpoint. Example: SQL Server
00013992: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]I: Source endpoint 'SQL Server' is using provider syntax 'SQLServer' (provider_syntax_manager.c:869)
This identifies the source endpoint. Example: SQL Server
00010460: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]I: Source endpoint 'SQL Server' is using provider syntax 'SQLServer' (provider_syntax_manager.c:869)
00010460: 2022-03-02T13:22:58 [SOURCE_CAPTURE ]I: ODBC driver version: '11.00.7001'
This identifies the ODBC driver version.
00007928: 2022-03-02T13:23:08 [SERVER ]I: Stop server request received internally (server.c:2338)
00007928: 2022-03-02T13:23:08 [TASK_MANAGER ]I: Task management thread terminated (replicationtask.c:4155)
This identifies if someone (or the scheduler) has stopped a task: Stop server request received internally
Related Content
How to analyze a Qlik Replicate log
Qlik Replicate: Example error codes sent by data sources in
