Comparison with index names of the primary constraint type SYS_C009252288

Toad for Oracle - Beta
1

I do not have the comparison with index names of the primary constraint type SYS_C009252288.
Database / compare / schema / multiple
Source : TADMX
Target : TYADMX (Shareplex replication)
Schema LSM. Object type to compare : tables + constraints + index

image
image327×224 29.6 KB

Exemple TADMX table LSM.TYPE_LOG: index name SYS_C009252288
Exemple TYADMX table LSM.TYPE_LOG: index name SYS_C009199454
In an older version of TOAD, I had this differentiation and a proposed script.
Also, operations on indexes of this type fail in SharePlex replication because the index names differ. And TOAD does not help me.

2

Are the constraints different besides the name? Toad isn't going to sync those names. It shouldn't. Those are system generated constraint/index names. If you want Toad to sync the names, you should name the one in the source database (like TYPE_LOG_PK or whatever makes sense to you). Then Toad should provide a script to give the one in the target the same name.

If the constraints are actually different in some other way, please provide details so i can attempt to reproduce the problem.

Thanks.

3

Also, unrelated to your question, but I noticed you have it set on <Multiple Schemas> even though you are only comparing one pair of schemas.

The Schema Compare will be easier to use if you choose the source and target schemas at the top instead of <Multiple Schemas>. <Multiple Schemas> is really for when you want to compare multiple pairs of schemas. Like, compare schema A with schema A, B with B, C with C, etc.

Maybe you are really comparing multiple and just wanted to filter it for the screen shot.

4

The table is :
CREATE TABLE TYPE_LOG
(
ID_TYPE_LOG INTEGER NOT NULL,
DESCRIPTION VARCHAR2(250 BYTE) NOT NULL,
DT_MAJ DATE DEFAULT SYSDATE,
DT_SYNCHRO DATE
)
;

ALTER TABLE TYPE_LOG ADD (
PRIMARY KEY
(ID_TYPE_LOG) USING INDEX
ENABLE VALIDATE);
The index name was generated like SYS_C006937098.
Shareplex replicates on the target database, and the index name is different SYS_C006937123. But TOAD compare does not provide the alter to rename to SYS_C006937098 on the target. I remember that an older version of TOAD detected it.

5

How much older? I vaguely remember that very old versions of Toads would rename indexes/constraints like this, but I would call that a bug since these objects are named by Oracle.

If you want to keep the object names in sync, you should name them and not rely on names like SYS_Cnnnnnnnnn.