Load Ingest Data
Results 1 to 7 of 7

Thread: Replication failed to start (SQL Server Database)

  1. #1
    Domenm is offline Junior Member
    Join Date
    Jan 2019
    Posts
    7
    Rep Power
    0

    Attunity Replication fail to start between SQL Server Databases

    Hi all!
    I have started an evaluation of Attunity Replication Express between 2 SQL Server 2017 databases. When I try to run the replication task for initial load (e.g. 'Reload target' option), I immediately get an error. For the sake of simplicity I only selected 1 table for replication. Both, source and target servers are connectable from the console (Test connection is OK). I tried with SQL and Windows authentication options.

    Here's the error I get:
    Name:  repl_error.jpg
Views: 480
Size:  92.8 KB

    I'm also attaching the whole error log.
    From the log I couldn't find any useful hints why replication task refuses to work, so I would like to ask for some help to find out what's causing these errors.

    Any ideas appreciated!
    Regards,
    Domen
    Attached Files Attached Files
    Last edited by Domenm; 01-25-2019 at 09:24 AM.

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

    The error is detected by - sqlserver_capture_source_loop
    The error handling is not complete.
    That function be executing a statement like 'select top 5000 from fn_dblog(null,null...)
    Perhaps you can isolate that and run manually, using the same account used by Attunity Replicate
    >>Task Server Log (V6.1.0.407
    >> Microsoft SQL Server 2017
    I think I've seen this message before (yesterday :-), also for a Microsoft SQL Server 2017 source.
    I'm pretty sure SQLserver 2017 was not formally supported in Replicate 6.1
    You may want to try to download a more recent version.
    Our licensed customers are using 6.3.0.320 or even more recent.


    >> Task 'GENINGSQLTEST01--737' running full load and CDC in resume mode after recoverable error, retry #3
    It has retries a few times. Maybe time to re-run 'fresh' with just the RELOAD.
    Before you do, switch LOGGING for SOURCE_CAPTURE to VERBOSE

    And even before you do that, may just do a quick full-load only test.
    That will rule out any surprises in that phase.

    Good luck!
    Hein

  3. #3
    Domenm is offline Junior Member
    Join Date
    Jan 2019
    Posts
    7
    Rep Power
    0
    Hello Hein,

    thank you for your reply. First I have to apologize for late reply.
    I haven't tried yet your other suggestions, but this one looks promising : "I think I've seen this message before (yesterday :-), also for a Microsoft SQL Server 2017 source.
    I'm pretty sure SQLserver 2017 was not formally supported in Replicate 6.1". As a part of evaluation, we have downloaded the 6.1 version. We get this by default by clicking the link on your page (https://discover.attunity.com/replicate-express-download.html...). We are testing this on Windows, so we got AttunityReplicate_6.1.0.407_X64.exe. To eleminate other reasons, would it be possible to download an test on more recent version (6.3) ?

    Thank you.
    Best Regards,
    Domen

  4. #4
    Domenm is offline Junior Member
    Join Date
    Jan 2019
    Posts
    7
    Rep Power
    0
    Hello Hein,

    I apologize for late reply and thank you for your answer.
    I haven't tried yet your other suggestions, but this one looks promising: "I'm pretty sure SQLserver 2017 was not formally supported in Replicate 6.1". We use SQL Server 2017 and we have 6.1 version we got from download link on "https://discover.attunity.com/replicate-express-download.html". To eliminate other reasons, would it be possible to get more recent version (6.3) for evaluation?

    Thank you.
    Best Regards,
    Domen


    Quote Originally Posted by Domenm View Post
    Hi all!
    I have started an evaluation of Attunity Replication Express between 2 SQL Server 2017 databases. When I try to run the replication task for initial load (e.g. 'Reload target' option), I immediately get an error. For the sake of simplicity I only selected 1 table for replication. Both, source and target servers are connectable from the console (Test connection is OK). I tried with SQL and Windows authentication options.

    Here's the error I get:
    Name:  repl_error.jpg
Views: 480
Size:  92.8 KB

    I'm also attaching the whole error log.
    From the log I couldn't find any useful hints why replication task refuses to work, so I would like to ask for some help to find out what's causing these errors.

    Any ideas appreciated!
    Regards,
    Domen

  5. #5
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    152
    Rep Power
    12
    I'll send a link in a private message. Hein.

  6. #6
    Domenm is offline Junior Member
    Join Date
    Jan 2019
    Posts
    7
    Rep Power
    0
    Thank you Hein, I'll install this version and reply the results.
    Regards,
    Domen

    Quote Originally Posted by Hein View Post
    I'll send a link in a private message. Hein.

  7. #7
    Domenm is offline Junior Member
    Join Date
    Jan 2019
    Posts
    7
    Rep Power
    0
    Quote Originally Posted by Domenm View Post
    Thank you Hein, I'll install this version and reply the results.
    Regards,
    Domen

    Hello Hein,
    I've installed the version you sent and the first results are good! The replication seems to work now with SQL Server 2017.
    I'll continue with tests and report any problems.

    Thanks again.
    Regards,
    Domen

Tags for this Thread

Posting Permissions

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