fix_cache_key.php suddenly broken?

[zcnb]

1. Login to the admin console of the DUPLICATE store
2. Take that DUPLICATE store out of DOWN_FOR_MAINTENANCE mode (remember, the database was duplicated while the original store was in DOWN_FOR_MAINTENANCE, otherwise duplication could have unpredictable results).
3. Run fix_cache_key.php

OK - I have just confirmed (for the Nth time) that the above sequence is mandatory for my store.

I accept what DrByte said about this not being a requirement but apparently there is some uniqueness to my environment or duplication procedure.

Perhaps this has to do with the fact that I don't create a new dbuser for the newly duplicated database but rather re-assign the existing dbuser to the newly duplicated database?

At the moment I have no definite explanations.