In the sync portion of the Compare and Sync schemas, the tool generates the ALTER statements for columns in the wrong order; thus not really making them equal.
For example:
Actual DDL in Schema 1:
CREATE TABLE "IMDBA"."TEST_TOAD_A" (
"A" INTEGER,
"B" INTEGER,
"C" INTEGER
)
Actual DDL in Schema 2: (Notice this has columns Z, Y, X order)
CREATE TABLE "O5Z"."TEST_TOAD_A" (
"A" INTEGER,
"B" INTEGER,
"C" INTEGER,
"Z" INTEGER,
"Y" INTEGER,
"X" INTEGER
)
In Schema Compare it shows the right order for the columns:
CREATE TABLE "O5Z"."TEST_TOAD_A" (
"A" INTEGER,
"B" INTEGER,
"C" INTEGER,
"Z" INTEGER,
"Y" INTEGER,
"X" INTEGER
)
However, the sync script generated is as follows:
ALTER TABLE "IMDBA"."TEST_TOAD_A"
ADD COLUMN "X" INTEGER;
ALTER TABLE "IMDBA"."TEST_TOAD_A"
ADD COLUMN "Y" INTEGER;
ALTER TABLE "IMDBA"."TEST_TOAD_A"
ADD COLUMN "Z" INTEGER;
Thus it creates the table with the wrong order of columns. Thus running the compare again indicates they are different.
WORKAROUND:
Run the sync one more time where it has to drop the entire table and recreate it in the right order is where it will match.
STATUS:
Waiting for fix in a future release of Toad for DB2.
Toad for DB2 Beta 5.1.0.627 has a fix in place. Visit http://toadfordb2.com/beta.jspa for more information.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center