Post by Reed, David A.Is the difference that the target objects are owned by different schemas NOKALG and OLIALG?
Oh, wait....after rereading your email, maybe this is not the problem. I don't think I understand your synonym scenario. Could you work up a script to create the objects so I can reproduce it?
From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of John Dorlon
Sent: Wednesday, April 17, 2013 10:38 AM
To: ***@yahoogroups.com
Subject: [toad] RE: Schema Compare and Synonyms
The schema compare is smart enough to ignore the fact that the schemas have different names. The side by side viewer is not. So don't be fooled by the side by side viewer highlighting the schema names (unless of course the highlighted schema is not one that is being compared, and is a true difference).
If a trigger is created with the schema name, that schema name will make it into the trigger's source. If the trigger is created without the schema name, there will be no schema name in the trigger's source. Toad sometimes has to inject or remove the schema name when building 'create trigger' scripts depending on a) if your options are configured to include schema name, b) if the schema name is present in the source, and c) if your options are configured for Toad to add or remove the schema name (this is the "parse triggers for schema name" option).
Post by Reed, David A.Is the difference that the target objects are owned by different schemas NOKALG and OLIALG?
Yes, I believe that is what is causing the difference.
From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of Reed, David A.
Sent: Wednesday, April 17, 2013 10:20 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] RE: Schema Compare and Synonyms
John/Bert:
I am beginning to know Schema Compare better.
* In the NOKPROK/OLIPROC schemas comparison, I see only 2 triggers with description differences. When I look at the difference details, I see the schema names present in the CREATE OR REPLACE statements causing the difference. But when I go to the source tabs for the triggers in each schema, the schema names are not present. To add to the strangeness none of the other triggers shows description differences.
* None of the synonyms are public. But what you state may be the issue. I am comparing NOKPROC (source) to OLIPROC (target). One of the synonyms is NOKPROC.ALG_ACT_CONFIG. Its target object is NOKALG.ALG_ACT_CONFIG (a table). The corresponding synonym is OLIPROC.ALG_ACT_CONFIG. Its target object is OLIALG.ALG_ACT_CONFIG (a table). Is the difference that the target objects are owned by different schemas NOKALG and OLIALG? I don't see however, the reverse: the same OLIPROC synonyms not being present in NOKPROC.
* The constraint issue is that the comparison uses generating scripts that include the schema names. This results in the difference. It would be nice to have an option to not include the schema names when comparing generating scripts.
Regards,
Dave
From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of John Dorlon
Sent: Wednesday, April 17, 2013 10:08 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] RE: Schema Compare and Synonyms
Yes, in the schema compare window, options tab, object type specific options, in the "PL/SQL Objects and View Source" groupbox, there are all kinds of things like that.
From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of Bert Scalzo
Sent: Wednesday, April 17, 2013 9:04 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] RE: Schema Compare and Synonyms
On #1 is there also not an option to ignore spaces and things when comparing that text ???
From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of John Dorlon
Sent: Wednesday, April 17, 2013 8:59 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] RE: Schema Compare and Synonyms
Hi David,
The word 'description' here refers to the data in the dba_triggers.description column. When you create the trigger, some of your 'create' statement ends up in there. It is basically everything before the body of the trigger. If you rt-click on the trigger in the schema compare results and choose "show difference details", the DDL for the two triggers (one from each schema) will appear in the side-by-side file compare window.
Synonyms: Is the synonym owner or name different between the two schemas? Public in one schema, private in the other?
Constraint: Look in dba_constraints for the rows of the constraints in question, particularly at the r_owner and r_constraint_name columns. Also check the table name that the R_CONSTRAINT_NAME constraint is one. That being different could also raise this.
I hope that helps.
- John
From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of Reed, David A.
Sent: Wednesday, April 17, 2013 8:25 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] Schema Compare and Synonyms
Yesterday I used Schema Compare from 11.6.1.1 to look at the differences between 2 similar schemas and have several issues.
* Schema Compare is showing triggers that differ by the "description". How can I look at it using Toad? We don't assign it a value. Does a default value get assigned?
* Schema Compare is showing synonyms missing between the two schemas, particularly in the source not found in the target. However, when I look at the target, they exist. What are the criteria for synonyms not being present?
* Schema Compare is showing constraints that differ by "foreign key". What does that mean? When I look at the two constraints, I see no differences.
Thanks in advance,
Dave
David Reed
Principal Engineer
Strategy and Project Support
Design Standardization & Process Leadership
CWHQ2 318D
Westinghouse Electric Company
Suite 251
1000 Westinghouse Drive
Cranberry Township PA 16066, USA
Phone: +1 (412) 374-6739
Fax: +1 (412) 374-4575
Email: ***@westinghouse.com<mailto:***@westinghouse.com>
Home Page: www.westinghousenuclear.com