Skip to content
← Oracle

How can we improve our Oracle solution?

Oracle: Schema Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Schema Compare should be able to ignore system generated names for supplemental log groups

Schema Compare should be able to ignore names for supplemental log groups. I have many differences on tables that I do not care about like this (the names were generated by GoldenGate):
ALTER TABLE schemaname.tablename ADD SUPPLEMENTAL LOG GROUP ggs_84245 (columnname) ALWAYS;

6 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Mark Little shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminRichard Mitchell (Admin, Redgate) commented  ·   ·  Report

    Annoyingly I think you could do this via a filter mechanism I've added into Source Control for Oracle lately. I am planning on back-porting it into Schema Compare at some point in the future. This would allow you set a textual object filter to exclude objects with names containing "ggs_" - would that be enough?

    I'm trying to avoid option proliferation, although it's no great problem for most users.

  • Mark Little commented  ·   ·  Report

    In the GoldenGate command line interface (ggsci), I run the "add trandata schemaname.*" command and it creates supplemental log groups for each table that does not already have one. For most tables, dba_log_groups will be populated as follows:
    1. log_group_name will start with GGS_ (for "GoldenGate Software", which was once a stand-alone company and was later acquired by Oracle) and then have a sequential number which I have no control over.
    2. log_group_type = 'USER LOG GROUP'
    3. always = 'ALWAYS'
    4. generated = 'USER NAME'

    I have one table with no primary key defined and has a column having a datatype of raw, which has these values:
    1. log_group_name starts with SYS_C and then has a sequential number which I have no control over.
    2. log_group_type = 'ALL COLUMN LOGGING'
    3. always = 'ALWAYS'
    4. generated = 'GENERATED NAME'

    Perhaps this request should be renamed to "Schema Compare should be able to ignore names for supplemental log groups". I only care if there is not an exact match on owner + log_group_type + always + generated.

  • AdminRichard Mitchell (Admin, Redgate) commented  ·   ·  Report

    In the DBA_LOG_GROUPS table what is the value of the GENERATED column? I'm expecting 'GENERATED NAME' for system generated names. The name prefix 'ggs_' doesn't seem like a system generated name as these normally start with 'sys_'