Schema Comparison Results Lockup

chazamania · February 10, 2014, 7:36pm

I just 12.1.0.22 (32bit)/Win7(64bit) loaded and I’m consistently freezing the entire app when comparing (double-clicking) certain objects on the results from a db-to-db schema comparison. I just did it with a object difference whee a PK has an extra column included on the destination and separately double-clicking a constraint that was only in the destination. Toad shows Not Responding in task manager with no additional CPU activity. I never had this issue in 11.6.

JohnDorlon · February 11, 2014, 6:34am

I’ve been trying to reproduce this but I’m not having much luck. I compared the SYS schemas from two different versioned databases, so I’m getting a good number of differences. The rt-click and toolbar options seem to work fine for me. Double clicking shouldn’t do much of anything (just possibly change toolbar button enablement, if you changed nodes in your click)

alancounihan · February 11, 2014, 7:36am

I’m pretty sure I experienced the same issue as this when comparing check constraints.

It was displaying differences when there should not have been differences and I think this is what caused the locking cause Toad got confused

I then tested it on the beta and it worked. Can you try it on the Beta?

Might not be the same issue but it sounds similar

chazamania · February 11, 2014, 7:49am

Here’s my repeatable test case. I can’t touch this network with the beta. I have it on a laptop elsewhere, but VirtualBox upgrades is killing me.

–comparsions done as SYS Only tables and constraints checked for comparison

–always locks (2 separate tests) on double-click “Objects which differ|Constraints - PK| TABLE_JOINS_PK”

–DB1

CREATE TABLE nwps.table_joins

(

menu_opt VARCHAR2 (30),

table1 VARCHAR2 (40),

field1 VARCHAR2 (40),

table2 VARCHAR2 (40),

field2 VARCHAR2 (40),

mandatory_flg CHAR (1)

);

CREATE UNIQUE INDEX nwps.table_joins_pk

ON nwps.table_joins (menu_opt,

table1,

field1,

table2,

field2);

ALTER TABLE nwps.table_joins ADD (

CONSTRAINT table_joins_pk

PRIMARY KEY

(menu_opt, table1, field1, table2, field2)

USING INDEX nwps.table_joins_pk

ENABLE VALIDATE);

– DB2

CREATE TABLE nwps.table_joins

(

menu_opt VARCHAR2 (30),

table1 VARCHAR2 (40),

field1 VARCHAR2 (40),

table2 VARCHAR2 (40),

field2 VARCHAR2 (40),

mandatory_flg CHAR (1),

data_source VARCHAR2 (1) NOT NULL

);

CREATE UNIQUE INDEX nwps.table_joins_pk

ON nwps.table_joins (menu_opt,

table1,

field1,

table2,

field2,

data_source);

ALTER TABLE nwps.table_joins ADD (

CONSTRAINT table_joins_pk

PRIMARY KEY

(menu_opt, table1, field1, table2, field2, data_source)

USING INDEX nwps.table_joins_pk

ENABLE VALIDATE);

alancounihan · February 11, 2014, 8:16am

I tried this out and Toad 12.1 comes back with the error below

Works fine in Beta V12.5.0.21

EurekaLog 7.0.3.0

Application:

1.1 Start Date : Tue, 11 Feb 2014 15:49:06 +0

1.2 Name/Description: Toad.exe - (Toad for Oracle)

1.3 Version Number : 12.1.0.22

1.4 Parameters :

1.6 Up Time : 22 minute(s), 11 second(s)

Exception:

2.1 Date : Tue, 11 Feb 2014 16:11:18 +0

2.2 Address : 04199888

2.3 Module Name: Toad.exe - (Toad for Oracle)

2.5 Type : EAccessViolation

2.6 Message : Access violation at address 04199888 in module ‘Toad.exe’. Read of address FFFFFFF9

2.7 ID : B9AB0000

2.8 Count : 1

2.11 Sent : 0

JohnDorlon · February 11, 2014, 8:28am

I found the same as Alan - I was able to repeat it in 12.1, but it is fixed in the beta.

Looking in our source control comments, I see that it was fixed on 12/5.

chazamania · February 11, 2014, 8:40am

What’s the best path to get this as a 12.1 patch? I’ve been working for 3 months to get it added to DADMS and this functionality is my lifeblood for the next 3-4 months.

JohnDorlon · February 11, 2014, 8:54am

Unfortunately, it’s too late to add this to a 12.1 patch. 12.5 will be out in the spring.

That bug is only going to happen with constraints. Hopefully that helps.

As a workaround, you could uncheck all, check only the object you are interested, then go to the sync script tab. It’s not exactly the same thing, but it’s
better than nothing. Or, if it doesn’t happen in 11.6, you could keep that version for constraints.

Sorry I don’t have better news for you.

From: chazamania [mailto:bounce-chazamania@toadworld.com]

Sent: Tuesday, February 11, 2014 10:40 AM

To: toadoracle@toadworld.com

Subject: RE: [Toad for Oracle - Discussion Forum] Schema Comparison Results Lockup

RE: Schema Comparison Results Lockup

Reply by chazamania

What’s the best path to get this as a 12.1 patch? I’ve been working for 3 months to get it added to DADMS and this functionality is my lifeblood for the next 3-4 months.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.

chazamania · February 11, 2014, 9:36am

Thanks and good to know. I’ll try to get to some of the other false positives I saw earlier in 11.6 like column level grants and USING INDEX clauses and see if they persist in 12.1.

JohnDorlon · February 11, 2014, 9:41am

Ok…if you find any problems, do let me know and I’ll make sure they are fixed for 12.5.