Cloning issues ?

[Gaurav Kumar15]

HI Team,

Could anyone please help me in knowing the reason of clone failure.

1. We scheduled an clone at around 9am IST, it was successful.

2. Now on next day, when we again scheduled clone for same instance by scheduling a request around 7am IST, it got failed with the following error :-

Clone was not in ready state, exiting without running clone (state: Error)

Does anyone knows why this error comes. And on the previous day, we havn't done much development to instance that will result in schema changes. Still it got failed.

Don't know the exact reason why it got failed.

If anyone had faced this situation earlier, can guide us through why it failed ?

TIA,

Gaurav

[Pradeep Sharma]

Hi Gaurav,

I think this error comes if the clone request is put on hold. I would recommend you to contact support if you are still facing this issue.

[Gaurav Kumar15]

Thanks for the reply.

Yes i had raised an incident with HI, now i amgetting in touch with them to know it better. I thought maybe someone had already faced this and tell us the reasons, if any.

[donaldbates]

Just ran into this today, so documenting the answer for future Googlers.

After the scheduled kickoff of the instance don't touch anything on the source.

If a table that is being cloned is modified between the time the backup kicks off, and the clone starts, the clone will fail.

That required four hour delay is when the backup is taken that will be used for the clone. If you're cloning even further into the future I don't exactly when the backup is taken.