Data Replication 2
Results 1 to 2 of 2

Thread: How to modify cdcTimeout property with default value of 600?

  1. #1
    anwark is offline Junior Member
    Join Date
    May 2015
    Posts
    3
    Rep Power
    0

    How to modify cdcTimeout property with default value of 600?

    I am getting an error in a replicattion task after exactly 10 mins (600 sec). Attunity is trying to process a big (+10GB) SQL Server t-log and this is taking more than 600 seconds. The connection to the source db (SQL Server) is dropped after 600 seconds and some errors appears in the log though.

    Source connection string (SQL), looks similar to this:

    database=DB1;username=attunityusr;safeguardPolicy= RELY_ON_SQL_SERVER_REPLICATION_AGENT;alternateBack upFolder=\\fileshare\log_db1;server=SERVER_NAME;Pr eferBackupScan=N;readBackupOnly=N;useWindowsAuthen tication=N;

    Can anyone know why this happens? is the value for cdcTimeout property related with this issue?

    Thanks in advance for your assistance.

    00002276: 2016-03-23T00:22:15 [SERVER ]I: Task Server Log - PRD_DB (V4.0.8.31 PILOTATTUNITY.db1.local Microsoft Windows 64-bit, PID: 2964) started at Wed Mar 23 00:22:15 2016 (logger.c:448)
    00002276: 2016-03-23T00:22:15 [INFRASTRUCTURE ]I: Product license was not found. (license.c:799)
    00002276: 2016-03-23T00:22:15 [SERVER ]I: Client session (ID 8101) allocated (dispatcher.c:237)
    00002276: 2016-03-23T00:22:15 [TASK_MANAGER ]I: Task 'PRD_DB' running full load and CDC in resume mode (replicationtask.c:773)
    00002276: 2016-03-23T00:22:15 [METADATA_MANAGER]I: ODBC driver 'SQL Server' found as installed. (sqlserver_endpoint_util.c:334)
    00002276: 2016-03-23T00:22:15 [METADATA_MANAGER]I: NLS configuration sampled: Associated code page=1252 (sqlserver_endpoint_imp.c:1823)
    00002276: 2016-03-23T00:22:15 [METADATA_MANAGER]I: Going to connect to server redshift.amazonaws.com database db1 (redshift_imp.c:726)
    00002276: 2016-03-23T00:22:15 [METADATA_MANAGER]I: Connected to server redshift.amazonaws.com database db1 successfully. (redshift_imp.c:745)
    00002276: 2016-03-23T00:22:15 [UTILITIES ]I: The state is restored from file 'C:\Program Files\Attunity\Replicate\data\tasks\PRD_DB/StateManager/ars_saved_state_000002.sts' saved at Tue, 22 Mar 2016 08:41:03 GMT (1458636063781930) (statemanager.c:1065)
    00000960: 2016-03-23T00:22:15 [TASK_MANAGER ]I: Creating threads for all components (replicationtask.c:1235)
    00000960: 2016-03-23T00:22:15 [TASK_MANAGER ]I: Threads for all components were created (replicationtask.c:1381)
    00000960: 2016-03-23T00:22:15 [TASK_MANAGER ]I: Task initialization completed successfully (replicationtask.c:2186)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: The MS SQL Server instance is set up for Replication. (sqlserver_log_queries.c:2438)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: MS-Replication is properly set up on the database instance. (sqlserver_log_queries.c:2514)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: Access to TLOG is permitted. (sqlserver_log_queries.c:2536)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: Database 'BULK-LOGGED' recovery model fitness approved. (sqlserver_log_queries.c:2578)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: Database 'FULL' backup fitness approved. (sqlserver_log_queries.c:2628)
    00003144: 2016-03-23T00:22:15 [SOURCE_CAPTURE ]I: NLS configuration sampled: Associated code page=1252 (sqlserver_endpoint_imp.c:1823)
    00001592: 2016-03-23T00:22:15 [SORTER ]I: Start the task using saved state. Start source from stream position 000003df:001eff96:0004 and id 4490227. Confirmed target id is 17006549, next target id is 17006553 (sorter.c:386)
    00001592: 2016-03-23T00:22:15 [SORTER_STORAGE ]I: Swap files were loaded. Next target id to be assigned is 17006553. Next swap file id is 26915 (transaction_storage.c:178)
    00002744: 2016-03-23T00:22:15 [STREAM_COMPONENT]I: Target last committed record id from the previous run is '17006549' (streamcomponent.c:1241)
    00002744: 2016-03-23T00:22:15 [TARGET_APPLY ]I: Going to connect to server redshift.amazonaws.com database db1 (redshift_imp.c:726)
    00002744: 2016-03-23T00:22:15 [TARGET_APPLY ]I: Connected to server redshift.amazonaws.com database db1 successfully. (redshift_imp.c:745)
    00002744: 2016-03-23T00:22:16 [TARGET_APPLY ]I: Restore bulk state. Last bulk last record id - '0', last applyed record id - '0', target confirmed record id - '17006549' (endpointshell.c:867)
    00002744: 2016-03-23T00:22:16 [TARGET_APPLY ]I: Target endpoint does not support direct insert in batch apply mode (bulk_apply.c:459)
    00002744: 2016-03-23T00:22:16 [TARGET_APPLY ]I: Working in bulk apply mode (endpointshell.c:874)
    00002744: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: NLS configuration sampled: Associated code page=1252 (sqlserver_endpoint_imp.c:1823)
    00000960: 2016-03-23T00:22:16 [TASK_MANAGER ]I: All stream components were initialized (replicationtask.c:2032)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: Mapping partition id's for all tables has finished. (sqlserver_log_utils.c:433)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: partition id's catchup is set to true (sqlserver_log_utils.c:435)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: Start to approve full logging setup for all tables (7) (sqlserver_log_utils.c:1800)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: Approve full logging setup for all tables has finished (sqlserver_log_utils.c:1867)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: Positioning token value upon start is: '000003df:001eff96:0004' (sqlserver_log_utils.c:1933)
    00001592: 2016-03-23T00:22:16 [SORTER ]I: Transaction consistency reached (sorter_transaction.c:212)
    00000960: 2016-03-23T00:22:16 [TASK_MANAGER ]I: Starting replication now (replicationtask.c:1797)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: SAFEGUARD_POLICY: RELY_ON_SQL_SERVER_REPLICATION_AGENT: A/B latches (sqlserver_endpoint_capture.c:466)
    00003144: 2016-03-23T00:22:16 [SOURCE_CAPTURE ]I: cdcTimeout property is set to 600 (sqlserver_log_processor.c:5040)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]E: SqlStat: HYT00 NativeError:0 [Microsoft][SQL Server Native Client 11.0]Query timeout expired (PcbMsg: 63) [120102] Stream Component recoverable error. (sqlserver_log_processor.c:3660)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]E: Unknown '0' native error detected while SQL_ERROR is flagged / SQLSTATE is not empty. [120102] Stream Component recoverable error. (sqlserver_log_processor.c:3661)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]I: Throughput monitor: Last DB time scanned: N/A. Last LSN scanned: 000003df:001eff96:0004. #scanned events: 0. (sqlserver_log_utils.c:4282)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]E: sqlserver_capture_source_loop(...) encountered an unexpeceted error. [120102] Stream Component recoverable error. (sqlserver_endpoint_capture.c:740)
    00000960: 2016-03-23T00:32:27 [TASK_MANAGER ]E: Task error notification received from subtask 0, thread 0 [120102] Stream Component recoverable error. (replicationtask.c:1872)
    00000960: 2016-03-23T00:32:27 [TASK_MANAGER ]I: Task 'PRD_DB' encountered a recoverable error (repository.c:4005)
    00001592: 2016-03-23T00:32:27 [SORTER ]I: Final saved task state. Stream position 000003df:001eff96:0004, Source id 4490227, next Target id 17006553, confirmed Target id 17006549 (sorter.c:536)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]E: Error executing source loop [120102] Stream Component recoverable error. (streamcomponent.c:1465)
    00003144: 2016-03-23T00:32:27 [TASK_MANAGER ]E: Stream component failed at subtask 0, component st_0_PRD_DB [120102] Stream Component recoverable error. (subtask.c:1344)
    00003144: 2016-03-23T00:32:27 [SOURCE_CAPTURE ]E: Stream component 'st_0_PRD_DB' terminated [120102] Stream Component recoverable error. (subtask.c:1509)
    00000960: 2016-03-23T00:32:31 [TASK_MANAGER ]I: Subtask #0 ended (replicationtask_util.c:925)
    00000960: 2016-03-23T00:32:31 [SERVER ]I: Stop server request received internally (server.c:2077)
    00000960: 2016-03-23T00:32:31 [TASK_MANAGER ]I: Task management thread terminated (replicationtask.c:2575)
    00002276: 2016-03-23T00:32:32 [SERVER ]I: Client session (ID 8101) closed (dispatcher.c:190)
    00002276: 2016-03-23T00:32:32 [UTILITIES ]I: The last state is saved to file 'C:\Program Files\Attunity\Replicate\data\tasks\PRD_DB/StateManager/ars_saved_state_000002.sts' at Wed, 23 Mar 2016 06:32:27 GMT (1458714747960990) (statemanager.c:674)
    00003752: 2016-03-23T00:32:32 [SERVER ]I: The process stopped (server.c:2184)
    00003752: 2016-03-23T00:32:32 [SERVER ]I: Closing log file at Wed Mar 23 00:32:32 2016 (logger.c:1915)

  2. #2
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    151
    Rep Power
    12

    set cdctimeout=xxxx in the connection_string

    Yes, you can set the parameter cdctimeout to a larger value like 5000 in the connection_string to allow it to wait more than 10 minutes, if you know there could be a good reason to have to wait that long, due to re-positioning in a large ( > 5GB ) Tlog backup.

    I suspect you will find one thread in the SQLserver nearly 100% CPU busy while this is repositioning is happening.

    FWIW.... this is really a SQLserver topic best place (in the future) un that section.
    It has nothing to do with Redshift.

    Cheers,
    Hein

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •