Compare Schema Sync Script not populating schema correctly for triggers when the target schema name is different from the reference schema name. Combinations of checking and unacking the options such as "Parse for Schema Name", Include Schema Names yield incorrect result.
Product Defect
WORKAROUND:
1. Use Toad for Oracle 11 Beta.
2. If there is a schema name already in trigger code, it is best to check the ‘parse for schema name’ option. This will ensure that it gets changed to the correct target schema.
3. If there is no schema name in trigger code, and you do not want a schema name to be added to the trigger sync code. That is when this 'parse' option is best left unchecked.
4. These are options which are available for varied scenarios, reviewing of the sync script is necessary.
STATUS:
Waiting for fix in a future release of Toad for Oracle. Target for version 11.
"Compare schema name in description": Checked by default, TOAD compares the description in the trigger for schema name. Select description from user_triggers;
"Parse for Schema Name": If checked, this ensures that the schema name is changed to the correct target name when there is a schema name in the trigger description.
"Include schema names" : Checked by default, the target schema name for the trigger would be used.
