2 Answers
- Newest
- Most votes
- Most comments
0
Hello,
Try running with:
@with_norecovery = 0
and see if that works for you. Setting it to 1 leaves it in a state where you can then restore additional transaction logs etc, or set up replication. If you want the database usable, you need to leave it in an online state, which setting it to 0 should do.
0
I found the cause. In the source database from which the backup was taken, there was a user "admin"@"localhost". When I was choosing the DB create parameters, I accepted the default master user name which was: "admin"@"localhost". This conflict caused the restore to fail on creating the master user and then retry, apparently in an infinite loop. I solved the problem simply by choosing a different name for the master user.
answered 2 years ago
Relevant content
- Accepted Answerasked 4 years ago
- asked 9 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
I don't think MySQL has an equivalent parameter to SQL Server's @with_norecovery.