Another sample where PLSD messes with

Maxmix

Member³
Compare User Objects, connected as DBA1 both to source db and to destination db.
We compare table TDET in schema SCHEMA_A to the same table schema_a.TDET on destination db, which (table) does not exist there yet.

On source db, the table TDET has a foreign key (FK_XRIS_RIS) pointing to some table in another schema SCHEMA_B.

PLSD creates a sync statement, which suddenly "has forgotten" that we reference to schema_b, like this:

-- Create/Recreate primary, unique and foreign key constraints
alter table SCHEMA_A.TDET
add constraint FK_XRIS_RIS foreign key (XRIS_REF)
references SCHEMA_A.TMASTER (RIS_NAME);

The last line should read
references SCHEMA_B.TMASTER (RIS_NAME);

Magically, if tables SCHEMA_A.TDET are synced on source and destination, PLSD correctly identifies that:

Code:
----------------------------
--  No differences found  --
----------------------------
 
Last edited:
Back
Top