Object Compare - No Sync Script Generated

Toad for Oracle
1

When comparing objects across databases, the Sync Script and Dependent Objects tabs do not populate when you run the compare.

However, there is a workaround I have noticed.

  1. Choose an object to compare and select your target connection object
  2. Click the "Text File" radio button
  3. Switch back to "Live Object" radio button
  4. Click Run and the tabs will be present

Obviously this is not a show stopper, but everyone within our organization is running into this issue on the latest release.

Edition and Add-Ons:

Toad for Oracle Professional Edition (64-bit)
Add-Ons: DB Admin Module
17.1.717.3711

1 Like
2

This has been reported before but so far I have been unable to reproduce it. I think there is some relevant detail here that I am missing.

Can you post a screen shot for me, right after you've selected your objects (but not clicked "Text File" yet in your step 2 above)?

Thanks.

3

Thank you for your response John.

Here is a screenshot of before I select Text File:

1_Before_Selecting_Text_File
1_Before_Selecting_Text_File1390×916 29.3 KB

Here is a screenshot of after I select Text File. You will notice that in the lower left hand corner, the "Switch Source and Target" gets activated and the "Compare Data" button appears.

2_After_Selecting_Text_File
2_After_Selecting_Text_File2288×1146 94.8 KB

4

Thanks Nick.

One more question - are you activating the window from main menu, or right-click in schema browser, or somewhere else?

5

I almost always activate the window by right clicking on objects.

However, I just verified the same issue occurs when I use the dropdown menu. Database -> Compare -> Single Objects and then defining source and target.

EDIT: I also want to add that we have been using Toad for many years and have not experienced this issue until this current version.

7

Hi Nick,

Well it seems that I've fixed this already but forgot that I fixed it. :smiley:

You can get the most recent beta here and give it a try. I There is a change log at the bottom of that page. It was fixed in the beta released on June 24.

Thanks

John

8

Thank you for the update John. I guess I should check that thread next time I find an issue. I will give the Beta a look soon!