Error messages in SQL log when SQLClone used

RandyBCDRandyBCD Posts: 4 New member

We are seeing the following errors on a newly created clone server on a regular basis, the second error is the most important as the databases constantly restart.  Let me know if you need two separate questions/cases or will just one suffice:

1)
Message
Process ID 89 was killed by hostname USCDC01CWSQS012, host process ID 3744.

ProcessID is RedGate.SqlClone.Agent.Service.exe


2)
Message
Starting up database 'ODSConfigs'.

When the second message occurs the database owner reverts back to non SA which then causes additional issues from the app/web tier.  Why would the databases stop and then start up again?


The clones reside on the same server/disks as the Image so this is not a network related issue.


Thanks

Tagged:

Answers

  • Usually the reason that this would occur would be because the Clone Agent believes that it can no longer access the image (at which point the clones would become invalid to access, so we attempt to kill connections and detach the clone database until the image is availabl). Given that you say that the image is on the same machine, it sounds like this is something worth investigating, since the image shouldn't be intermittently unavailable.

    Could you share your agent logs with us as described in https://documentation.red-gate.com/clone2/troubleshooting/log-locations? It may be preferable to open a ticket by emailing [email protected] rather than posting them on the forums.
  • RandyBCDRandyBCD Posts: 4 New member
    Chris, thanks we will collect the logs as requested and open a ticket as outlined.
  • Usually the reason that this would occur would be because the Clone Agent believes that it can no longer access the image (at which point accessing clone databases causes file system errors, so we attempt to kill connections and detach the clone database until the image is available again). Given that you say that the image is on the same machine, it sounds like this is something worth investigating, since the image shouldn't be intermittently unavailable.

    Could you share your agent logs with us as described in https://documentation.red-gate.com/clone2/troubleshooting/log-locations? It may be preferable to open a ticket by emailing [email protected] rather than posting them on the forums.
  • Usually the reason that this would occur would be because the Clone Agent believes that it can no longer access the image (at which point accessing clone databases causes file system errors, so we attempt to kill connections and detach the clone database until the image is available again). Given that you say that the image is on the same machine, it sounds like this is something worth investigating, since the image shouldn't be intermittently unavailable.

    Could you share your agent logs with us as described in https://documentation.red-gate.com/clone2/troubleshooting/log-locations? It may be preferable to open a ticket by emailing [email protected] rather than posting them on the forums.
Sign In or Register to comment.