MySQL Bugs: #66246: 'original schema not found' when sync'ing.

Bug #66246	'original schema not found' when sync'ing.
Submitted:	7 Aug 2012 15:39	Modified:	4 Mar 2013 16:56
Reporter:	Robert Cesaric	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.41	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
When trying synchronize to a remote DB, kept getting "original schema not found".  I can continue and 'Force Synchronization with [schema]' but this isn't convenient as it happens every time regardless if I'm sync'ing to an existing schema or creating a new one in the process.

How to repeat:
Here's the exact steps I did to repeat:

1. Saved a new schema with the default name 'mydb'.  
2. I then added a couple tables & saved.
3. Changed the schema name to 'demo_shop' & saved.
3. Then I did a 'Synchronize Model' to an empty remote DB named 'demo_shop'.

Suggested fix:
The only way I could fix it was by unzipping the MWB file and adding 'demo_shop' to he 'oldName' attribute (it was blank) in the xml.

I'm also seeing an old redundant FK 'drop and recreate' issue that I haven't seen in a while but I'll try to add that to another ticket later as I had to downgrade back to 5.2.40 to get some work done.  ...Thanks.

Are you saving the model after synchronization?

Yes. I saved, closed, re-opened, rinsed and repeated.  Tried everything I could think of before actually editing the MWB xml source.

Are the servers you synchronize with different each time or always the same one?

Same one.  It's a local instance on my computer:

➜  ~  mysql5 -v
Server version: 5.1.63 Source distribution

Please try version 5.2.43. Thanks.

Sorry, I missed testing this in 5.2.43 but I just tested this in 5.2.44.  Still getting the same issue.  Here's the message when I try to synchronize:

The schema 'demo_shop2' seems to have been renamed from '' in the model,
but the original '' was not found in the RDBMS.
However a schema called 'demo_shop2' seems to exist there, would you like to force synchronization with it?

The schemata from your model are missing from the target RDBMS server.
If you are creating them for the first time use the Forward Engineer function.

I wanted to make sure my Mac upgrade to Mountain Lion had nothing to do with it so I've reverted back to 5.2.40 and repeated the test with no issue.

Also, I just downloaded 5.2.43 and tested.  Still same issue as with my 5.2.44 tests above.

Just wanted to chime in and say that I'm experiencing this issue on 5.2.44 as well, but on Windows 7 x64 for a remote database.

I can't repeat with Mountain Lion on MacBook Pro and remote server on Windows 7. Please provide the Workbench project file. Thanks.

MWB file that reproduces force sync message.

Attachment: MySQL_Bug.mwb (application/octet-stream, text), 5.19 KiB.

A few things:
- if you're creating a new DB on a server, you should use Forward Engineer, not Synchronize
- after the 1st time I synchronize by forcing it (which would not be necessary if you use Forward Engineer), any new synchronizations I do afterwards to the same DB work just fine

So it looks like this is not a bug.