Locking Issues

[WARN]: TDK is unable to obtain a lock.

This error message indicates that TDK has insufficient permissions to create an object in the output database. Please grant the necessary permissions.

For MySQL: Additionally grant create, select, insert, and drop permissions on tdklockholdingschema schema.

grant create, select, insert, drop on tdklockholdingschema.* to "${user}";

For Oracle:

grant
    create any procedure,
    drop any procedure
to ${user}

[FAILED]: Failed to claim sink. TDK is already running.

This happens because TDK is seeing an existing lock in the output database. This can happen if TDK was stopped abruptly or if the lock was not released yet. To resolve this issue, you can either wait for the lock to be released or manually release the lock.

If you are sure that TDK is not running, you can manually release the lock.

You can do it either by specifying flag FORCE_CLAIM_SINK (see configuration flags.) or by manually releasing the lock in the output database:

For MySQL, MSSQL, H2, PostgreSQL:

drop table tdklockholdingschema.tdksinkclaimtable;
drop schema tdklockholdingschema;

For Oracle (execute as TDK user):

drop drop function tdk$claim_function;

If you are using CLI installation, you can use the following command in order to force-release lock:

tdk --output-url <jdbc-url> --output-username <username> --output-password <password> release-lock