Schema Compare crashes when comparing large number of objects in a schema

finchom

We're evaluating Schema Compare and it is very impressive. But we have an issue.

We're hoping to use Schema Compare on a large Oracle EBS database and there are many, many objects in one particular schema - APPS.

We're comparing the database to a scripts folder and the compare process runs for about 16 minutes. After it finishes it presents a list of 204,459 objects that exist in the database but not in the folder.

I can scroll through the list and I check off a handful of objects (12), and press the Deployment Wizard button. I select the option to 'Update the scripts folder' and the process starts. I see a 'Calculating dependencies' screen for about 1 or 2 seconds and then the application crashes.

What should we do? Our goal is to move a bunch of these objects out of APPS and into another schema so it is easier to compare, but are we not able to use Schema Compare against a schema with a high number of objects?

Schema Compare 5.6

Eddie D

Hi, thank you for your forum post.

Sadly there is insufficient information to accurately identify the cause of the problem.  Is there any error message on screen that helps to identify the cause?

One common problem is insufficient memory for Schema Compare for Oracle (SCO) to generate the temporary files it creates.  By default, our tools create tmp files in the user's Windows profile temp folder.

If you have another disk drive on the machine running the Oracle tools with plenty of free disk space, the user can create the RGTEMP environment variable whose data value is to a folder that has plenty of free disk space.

If you wish to try out the RGTEMP environment variable, please follow the steps below.

1.  On another disk drive, create a folder called RGTEMP.  For example, 'D:\RGTEMP'

2.  Right click 'MyComputer' or 'This PC' and select properties.

3.  Select 'Advanced system settings'.

4.  Click the 'Environment Variables' button.

5.  In the 'System variables' section, click the new button.

6.  For the 'Variable name' enter RGTEMP.

7.  For the 'Variable value' enter the path specified in Step 1, for example 'D:\RGTEMP'

8.  Click the 'OK' button total of 3 times, to close the dialog windows that opened.

In some case you may need to restart the machine for the change to take effect.

Once the RGTEMP Environment Variable is in place, the Redgate tools will create their temporary files in the (using my example) 'D:\RGTEMP folder', which may prevent any issues occurring from using the default Windows Temp directories.

Also using the 'Ignore Rules Filter' you can reduce the number of objects to be compared.  This means you can compare and deploy the objects of interest.  Further reading on the Ignore Rules filter can be found in this help article, plus syntax and examples in this second help article. 

Many Thanks

Eddie

finchom

I was running my testing in a virtual machine. So in light of the insufficient memory possibility, I ran on a physical machine with 32G of memory and plenty of disk storage and was able to complete the compare (even without filters). Thank you.

finchom

To answer your question -- there was no error message on the screen. After pressing the deployment wizard button, I briefly saw a dialog window and then the entire application just disappears.