topic Failure upon initial capture fitness checking in Qlik Replicate

Failure upon initial capture fitness checking

Naga_vivek — Mon, 12 Feb 2024 15:46:37 GMT

Hi Team,

We got this error when running replicate from Microsoft SQL server to csv file.

and we set Change processing mode (read changes from): Prioritize Online Logs

Stream component 'st_0_src_end_point' terminated
Stream component failed at subtask 0, component st_0_src_endpoint
Error executing command
Failure upon initial CAPTURE fitness checking
Insufficient permission to perform CDC. User must be granted SYSADMIN or DBOWNER privileges

But when we modified the Change processing mode (read changes from): Online Logs it is working

Can anyone explain what is the difference between those two(Prioritize Online Logs vs Online Logs)

and why is is not running with Prioritize Online Logs.

We tried checking the prerequisites for SQL server for replication but all looks good.

Please help how we can resolve when using Change processing mode (read changes from): Prioritize Online Logs

Thanks

N L N Vivek

Re: Failure upon initial capture fitness checking

Dana_Baldwin — Tue, 30 Jan 2024 16:53:38 GMT

Hi @Naga_vivek

Prioritize online logs means we try to read from the online log but will read from the backup log as needed.

Online log only means we will not attempt to read changes from the backup log.

The error you noted means that the correct permissions have not been assigned to the user defined in the source endpoint. Please assign sysadmin and dbowner to the user or follow the steps in the user guide for configuring a non-sysadmin user:

Required permissions | Qlik Replicate Help

Thanks,

Dana

Re: Failure upon initial capture fitness checking

Naga_vivek — Tue, 30 Jan 2024 17:51:17 GMT

Hi @Dana_Baldwin ,

Thanks for your reply.

When we set the Change processing mode (read changes from): Prioritize Online Logs we are seeing this error.
But when we set Change processing mode (read changes from): Online Logs it is running fine.
so will there be any reason why it is not working there but working here.

We also verified all the permissions for the user sysadmin and dbowner are set for both database level and server level but we are still getting the same issue.

Any inputs on this behavior.

Thanks & regards

N Vivek

Re: Failure upon initial capture fitness checking

Kent_Feng — Tue, 30 Jan 2024 23:51:15 GMT

Hi Naga_vivek,

According to the user's guide https://help.qlik.com/en-US/replicate/May2022/Content/Global_Common/Content/SharedReplicateHDD/SQLServer-Source/SQLServerDBSource_Security.htm,
A member of both the db_owner database role and the sysAdmin fixed server role should be sufficient to perform CDC. If you still have issues, please open a support case and our TSE will help to look into it for you.

Re: Failure upon initial capture fitness checking

DesmondWOO — Wed, 31 Jan 2024 01:20:00 GMT

Hi @Naga_vivek ,

Please enable verbose logging on the SOURCE_CAPTURE. This may provide clues as to why Replicate is encountering a permission issue.

As Kent suggested, please open a support ticket if issue persists.

Regards,
Desmond

Re: Failure upon initial capture fitness checking

SushilKumar — Thu, 01 Feb 2024 08:55:01 GMT

Hello team,

If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.

Regards,

Sushil Kumar

Re: Failure upon initial capture fitness checking

Heinvandenheuvel — Tue, 06 Feb 2024 08:47:52 GMT

>>> User must be granted SYSADMIN or DBOWNER privileges

Replicate does not make this up. You indicated those permissions were in place for the username making the endpoint connection, but I'd urge you to double check that.

The reason for this message is that with Prioritize Tlog, the backed-up log access is implied as opposed to the Tlog only setting. To performance backup log access, Replicate uses the SQL Server fn_dump_dblog function. Because this function is passed a physical fu\ilename, outside the database files, SQL server insists that its user has the right to read any file: sysadmin