the data synchronization script is displayed on a new window within the comparison tab. the new window is named with the [Oracle connection],[schema] for which the script was generated.
If the data synchronization script exceeds 32MB, Data Compare displays only the first 32MB-size block of the script in order to preserve the memory. If you want to view the whole script, you can save it to a file, and then open the file using a text editor.
A handy context menu allows you to save, copy, print, and add line numbers to the script as well as jump to a certain line in the script.
Here you can review the script to ensure that it is doing what you intend it to do. You may want to start the review from the Synchronization Log so that you can quickly identify the areas of the script that may require a closer look. You can access the synchronization log from the ribbon by clicking View Sync Log or from the action links on the right panel. The synchronization log contains a summary of the actions that you want to perform on the target database.
Refreshing the comparison and regenerating the script
While reviewing the script, you may discover that you should have done something different during the preparation phase before running the compare. IDERA Data Compare for Oracle Database allows you to change the options at any point during the process, and the simply click Refresh Result on the ribbon to redo the comparison without having to go through the whole exercise of selecting columns and keys etc. Note that this refresh action does not affect the previously generated synchronization script. To refresh the script window, simply generate the script again.
If the synchronization script contains LOB fields (CLOB, NCLOB or BLOB) whose size exceeds the maximum inline size supported by Oracle (4000 bytes), IDERA Data Compare for Oracle Database adds some additional steps to the core synchronization script to overcome this limitation. An Oracle package is created before the data script begins the execution and it is dropped after the execution. The package allows the LOB fields to be updated in chunk of approximately 4000 bytes in size.