Skip to content

Settings and activity

1 result found

  1. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Mark Little commented  · 

    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.

    Mark Little shared this idea  ·