GoldenGate DBMS_SCHEDULER replication

Hi guyz,
Do you know the optimal way to replicate jobs of DBMS_SCHEDULER in the GoldenGate replication?
Thank you beforehand.

You can create extra supplemental log groups for capturing changes. In one log group, do columns 1-32, in the second, 33-64, and in the third, the remainder. If you do ADD TRANDATA and go beyond 32 columns, you will get an ORA-02257 error (plus an OGG error).

Similar Messages

  • Oracle Standard Edition and GoldenGate for replication?

    The Question:
    Can GoldenGate run in a Standard Edition RAC ==> Enterprise Edition standalone environment and perform the required rule-based replication without requiring an upgrade of our RAC Standard Edition to RAC Enterprise Edition?
    The environment:
    Source System: 2-node RAC running Standard Edition 10.2.0.5 (RHEL5 x86-64)
    Target System: 1-node running Enterprise Edition 11.2.0.1 (RHEL5 x86-64)
    The requirement:
    Lossless one-way replication in "real time" of selected schema while excluding selected DDL/DML based on multiple rules.
    Present solution:
    LogMiner, but there is a known LogMiner bug (p8977287) that causes data loss when one RAC node goes down or is evicted from the cluster. The bug is reportedly patched in 11.2.0.2 and is slated to be fixed in 12.x.
    Thx.

    Yes. Simple enough, it can extract from SE, even XE!

  • Goldengate: DML replication is not syncing data

    Hi,
    I have followed the below steps for DML replication. No error found and all processes are running fine but data is not syncing. I am using ASM, db version:10.2.0.4,goldengate version:Version 11.1.1.0.0. Please check-
    Steps:
    @source
    Create folders
    Shell> ggsci
    GGSCI> CREATE SUBDIRS
    GGSCI> EXIT
    SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    SQL> EXIT
    GGSCI> EDIT PARAMS MGR
    PORT 7808
    GGSCI> START MGR
    GGSCI> INFO MGR
    @source
    create user source identified by source;
    grant create session,resource to source;
    grant select any dictionary to source;
    @target
    create user target identified by target;
    grant create session,resource to target;
    grant select any dictionary to target;
    sqlplus source@db01
    SQL> @demo_ora_create
    SQL> @demo_ora_insert
    Verify the results:
    SQL> select * from tcustmer;
    SQL> select * from tcustord;
    SQL> exit
    @source
    Shell> ggsci
    GGSCI> DBLOGIN USERID source, PASSWORD source sysdba
    GGSCI> ADD TRANDATA source.TCUSTMER
    GGSCI> ADD TRANDATA source.TCUSTORD
    @target
    GGSCI> CREATE SUBDIRS
    GGSCI> EDIT PARAMS MGR
    PORT 7809
    Start Manager
    GGSCI> START MANAGER
    Verify the results:
    GGSCI> INFO MANAGER
    sqlplus target@db02
    SQL> @demo_ora_create
    Verify the results:
    SQL> desc tcustmer;
    SQL> desc tcustord;
    SQL> exit
    @source
    GGSCI>ADD EXTRACT EIEXSL, TRANLOG, BEGIN NOW
    GGSCI>edit params EIEXSL
    -- TCUSTMER and TCUSTORD changes
    EXTRACT EIEXSL
    userid source,password source
    tranlogoptions asmuser sys@+ASM,asmpassword gpdba123
    EXTTRAIL ./dirdat/lt
    discardfile ./dirrpt/eiexsl.dsc,purge
    table source.tcust*;
    GGSCI>ADD EXTTRAIL ./dirdat/lt, EXTRACT EIEXSL,MEGABYTES 5
    GGSCI> START EXTRACT EIEXSL
    INFO EXTRACT EIEXSL
    @target
    GGSCI> EDIT PARAMS ./GLOBALS
    checkpointtable target.ggschkpt
    GGSCI> exit
    ggsci
    GGSCI> DBLOGIN USERID target, PASSWORD target
    GGSCI> ADD CHECKPOINTTABLE
    GGSCI> ADD REPLICAT RORASL, EXTTRAIL ./dirdat/lt
    GGSCI> EDIT PARAM RORASL
    -- Change Delivery parameter file to apply
    -- TCUSTMER and TCUSTORD Changes
    REPLICAT RORASL
    USERID target, PASSWORD target
    HANDLECOLLISIONS
    ASSUMETARGETDEFS
    DISCARDFILE ./dirrpt/RORASL.DSC, PURGE
    MAP source.tcustmer, TARGET target.tcustmer;
    MAP source.tcustord, TARGET target.tcustord;
    GGSCI> START REPLICAT RORASL
    GGSCI> INFO REPLICAT RORASL
    GGSCI> INFO ALL
    @source
    Shell> sqlplus source@db01
    SQL> @demo_ora_misc
    Verify results on the source system
    @source
    SQL> select * from tcustmer;
    SQL> select * from tcustord;
    SQL> exit
    @target
    SQL> select * from tcustmer;
    SQL> select * from tcustord;
    SQL> exit
    Thanks
    baju

    Source Log
    GGSCI (dbatest01) 1> info all
    Program Status Group Lag Time Since Chkpt
    MANAGER RUNNING
    EXTRACT RUNNING EIEXSL 00:00:00 00:00:02
    GGSCI (dbatest01) 2> info MANAGER,detail
    Manager is running (IP port dbatest01.7808).
    GGSCI (dbatest01) 3> info EXTRACT EIEXSL,detail
    EXTRACT EIEXSL Last Started 2011-04-06 17:53 Status RUNNING
    Checkpoint Lag 00:00:00 (updated 00:00:06 ago)
    Log Read Checkpoint Oracle Redo Logs
    2011-04-07 10:24:48 Seqno 489, RBA 8982016
    Target Extract Trails:
    Remote Trail Name Seqno RBA Max MB
    ./dirdat/lt 0 2966 5
    Extract Source Begin End
    +DG01/db01/onlinelog/group_3.311.736337327  2011-04-06 17:52  2011-04-07 10:24
    Not Available * Initialized * 2011-04-06 17:52
    Current directory /u01/oracle/goldengate
    Report file /u01/oracle/goldengate/dirrpt/EIEXSL.rpt
    Parameter file /u01/oracle/goldengate/dirprm/eiexsl.prm
    Checkpoint file /u01/oracle/goldengate/dirchk/EIEXSL.cpe
    Process file /u01/oracle/goldengate/dirpcs/EIEXSL.pce
    Stdout file /u01/oracle/goldengate/dirout/EIEXSL.out
    Error log /u01/oracle/goldengate/ggserr.log
    GGSCI (dbatest01) 5> view report EIEXSL
    Oracle GoldenGate Capture for Oracle
    Version 11.1.1.0.0 Build 078
    Solaris, sparc, 64bit (optimized), Oracle 10 on Jul 28 2010 17:02:45
    Copyright (C) 1995, 2010, Oracle and/or its affiliates. All rights reserved.
    Starting at 2011-04-06 17:53:32
    Operating System Version:
    SunOS
    Version Generic_138888-01, Release 5.10
    Node: dbatest01
    Machine: sun4u
    soft limit hard limit
    Address Space Size : unlimited unlimited
    Heap Size : unlimited unlimited
    File Size : unlimited unlimited
    CPU Time : unlimited unlimited
    Process id: 1709
    Description:
    ** Running with the following parameters **
    -- TCUSTMER and TCUSTORD changes
    EXTRACT EIEXSL
    userid source,password ******
    tranlogoptions asmuser sys@+ASM,asmpassword ********
    EXTTRAIL ./dirdat/lt
    discardfile ./dirrpt/eiexsl.dsc,purge
    table source.tcust*;
    2011-04-06 17:53:32 INFO OGG-01635 BOUNDED RECOVERY: reset to initial or altered checkpoint.
    Bounded Recovery Parameter:
    Options = BRRESET
    BRINTERVAL = 4HOURS
    BRDIR = /u01/oracle/goldengate
    CACHEMGR virtual memory values (may have been adjusted)
    CACHEBUFFERSIZE: 1M
    CACHESIZE: 8G
    CACHEBUFFERSIZE (soft max): 4M
    CACHEPAGEOUTSIZE (normal): 4M
    PROCESS VM AVAIL FROM OS (min): 16G
    CACHESIZEMAX (strict force to disk): 13.99G
    Database Version:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for Solaris: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Database Language and Character Set:
    NLS_LANG environment variable specified has invalid format, default value will be used.
    NLS_LANG environment variable not set, using default value AMERICAN_AMERICA.US7ASCII.
    NLS_LANGUAGE = "AMERICAN"
    NLS_TERRITORY = "AMERICA"
    NLS_CHARACTERSET = "WE8ISO8859P1"
    Warning: your NLS_LANG setting does not match database server language setting.
    Please refer to user manual for more information.
    Maximum supported ASM read buffer size is 28 KB
    2011-04-06 17:53:32 INFO OGG-01515 Positioning to begin time Apr 6, 2011 5:52:51 PM.
    2011-04-06 17:53:33 INFO OGG-01516 Positioned to Sequence 488, RBA 166416, Apr 6, 2011 5:52:51 PM.
    2011-04-06 17:53:33 INFO OGG-01052 No recovery is required for target file ./dirdat/lt000000, at RBA 0 (file not opened).
    2011-04-06 17:53:33 INFO OGG-01478 Output file ./dirdat/lt is using format RELEASE 10.4/11.1.
    ** Run Time Messages **
    2011-04-06 17:53:33 INFO OGG-01517 Position of first record processed Sequence 488, RBA 166416, SCN 0.5638566, Apr 6, 2011 5:52:54 PM.
    TABLEWildcard resolved (entry SOURCE.TCUST*):
    table SOURCE.TCUSTMER;
    Using the following key columns for source table SOURCE.TCUSTMER: CUST_CODE.
    TABLEWildcard resolved (entry SOURCE.TCUST*):
    table SOURCE.TCUSTORD;
    Using the following key columns for source table SOURCE.TCUSTORD: CUST_CODE, ORDER_DATE, PRODUCT_CODE, ORDER_ID.
    Destination Log
    GGSCI (dbatest02) 1> info all
    Program Status Group Lag Time Since Chkpt
    MANAGER RUNNING
    REPLICAT RUNNING RORASL 00:00:00 00:00:06
    GGSCI (dbatest02) 2> info mgr
    Manager is running (IP port dbatest02.7809).
    GGSCI (dbatest02) 3> info REPLICAT RORASL,detail
    REPLICAT RORASL Last Started 2011-04-06 17:55 Status RUNNING
    Checkpoint Lag 00:00:00 (updated 00:00:01 ago)
    Log Read Checkpoint File ./dirdat/lt000000
    First Record RBA 0
    Extract Source Begin End
    ./dirdat/lt000000 * Initialized * First Record
    ./dirdat/lt000000 * Initialized * First Record
    Current directory /u01/oracle/goldengate
    Report file /u01/oracle/goldengate/dirrpt/RORASL.rpt
    Parameter file /u01/oracle/goldengate/dirprm/rorasl.prm
    Checkpoint file /u01/oracle/goldengate/dirchk/RORASL.cpr
    Checkpoint table TARGET.GGSCHKPT
    Process file /u01/oracle/goldengate/dirpcs/RORASL.pcr
    Stdout file /u01/oracle/goldengate/dirout/RORASL.out
    Error log /u01/oracle/goldengate/ggserr.log
    GGSCI (dbatest02) 4> view report RORASL
    Oracle GoldenGate Delivery for Oracle
    Version 11.1.1.0.0 Build 078
    Solaris, sparc, 64bit (optimized), Oracle 10 on Jul 28 2010 17:08:59
    Copyright (C) 1995, 2010, Oracle and/or its affiliates. All rights reserved.
    Starting at 2011-04-06 17:55:15
    Operating System Version:
    SunOS
    Version Generic_138888-01, Release 5.10
    Node: dbatest02
    Machine: sun4u
    soft limit hard limit
    Address Space Size : unlimited unlimited
    Heap Size : unlimited unlimited
    File Size : unlimited unlimited
    CPU Time : unlimited unlimited
    Process id: 2178
    Description:
    ** Running with the following parameters **
    -- Change Delivery parameter file to apply
    -- TCUSTMER and TCUSTORD Changes
    REPLICAT RORASL
    USERID target, PASSWORD ******
    HANDLECOLLISIONS
    ASSUMETARGETDEFS
    DISCARDFILE ./dirrpt/RORASL.DSC, PURGE
    MAP source.tcustmer, TARGET target.tcustmer;
    MAP source.tcustord, TARGET target.tcustord;
    CACHEMGR virtual memory values (may have been adjusted)
    CACHEBUFFERSIZE: 1M
    CACHESIZE: 512M
    CACHEBUFFERSIZE (soft max): 4M
    CACHEPAGEOUTSIZE (normal): 4M
    PROCESS VM AVAIL FROM OS (min): 1G
    CACHESIZEMAX (strict force to disk): 881M
    Database Version:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for Solaris: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Database Language and Character Set:
    NLS_LANG environment variable specified has invalid format, default value will be used.
    NLS_LANG environment variable not set, using default value AMERICAN_AMERICA.US7ASCII.
    NLS_LANGUAGE = "AMERICAN"
    NLS_TERRITORY = "AMERICA"
    NLS_CHARACTERSET = "WE8ISO8859P1"
    Warning: your NLS_LANG setting does not match database server language setting.
    Please refer to user manual for more information.
    ** Run Time Messages **
    Thanks

  • Goldengate - DDL replication on MSSQL Server

    GOldengate 11g - IS there any way we can replicate DDL replication on MS SQL Server

    Hi
    Oracle GoldenGate (OGG) supports DDL capture and apply for the Oracle and Teradata databases only.
    check this may help you.
    http://www.ateam-oracle.com/oracle-goldengate-capture-and-apply-of-microsoft-sql-server-ddl-operations/

  • Converting goldengate database into production.

    Hi
    I m using 10g SE and cannot configure DG, if i configure goldengate data replication tool then can it be converted to production DB, if PDB crashes.
    Appreciate suggestions

    You cannot configure Data Guard on Standard Edition because it is a licensed option under the Enterprise Edition (in case you didn't know why, or for others reading this).
    http://docs.oracle.com/cd/E11882_01/license.112/e10594/editions.htm#BABDJGGI
    Otherwise, you can use another application - such as GoldenGate, or something from TOAD, etc. - to perform replication. You can also use Oracle Streams. Chances are that if you didn't buy EE, you're not going to like the price of GoldenGate, so you will be looking at poor man's replication, such as Streams (or even materialized views).

  • Schema level and table level supplemental logging

    Hello,
    I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command-
    SQL>alter database add supplemental log data (primary key) columns;
    Database altered.
    SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;
    SUPPLEME SUP SUP
    IMPLICIT YES NO
    -My question is should I enable supplemental logging table level also(for DML replication only)? should I run the below command also?
    GGSCI (db1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
    Successfully logged into database.
    GGSCI (db1) 2> ADD TRANDATA schema.<table-name>
    what is the deference between schema level and table level supplemental logging?

    For Oracle, ADD TRANDATA by default enables table-level supplemental logging. The supplemental log group includes one of the following sets of columns, in the listed order of priority, depending on what is defined on the table:
    1. Primary key
    2. First unique key alphanumerically with no virtual columns, no UDTs, no functionbased
    columns, and no nullable columns
    3. First unique key alphanumerically with no virtual columns, no UDTs, or no functionbased
    columns, but can include nullable columns
    4. If none of the preceding key types exist (even though there might be other types of keys
    defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
    the database allows to be used in a unique key, excluding virtual columns, UDTs,
    function-based columns, and any columns that are explicitly excluded from the Oracle
    GoldenGate configuration.
    The command issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA clause that
    is appropriate for the type of unique constraint (or lack of one) that is defined for the table.
    When to use ADD TRANDATA for an Oracle source database
    Use ADD TRANDATA only if you are not using the Oracle GoldenGate DDL replication feature.
    If you are using the Oracle GoldenGate DDL replication feature, use the ADD SCHEMATRANDATA command to log the required supplemental data. It is possible to use ADD
    TRANDATA when DDL support is enabled, but only if you can guarantee one of the following:
    ● You can stop DML activity on any and all tables before users or applications perform DDL on them.
    ● You cannot stop DML activity before the DDL occurs, but you can guarantee that:
    ❍ There is no possibility that users or applications will issue DDL that adds new tables whose names satisfy an explicit or wildcarded specification in a TABLE or MAP
    statement.
    ❍ There is no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.
    ADD SCHEMATRANDATA ensures replication continuity should DML ever occur on an object for which DDL has just been performed.
    You can use ADD TRANDATA even when using ADD SCHEMATRANDATA if you need to use the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters.
    Additional requirements when using ADD TRANDATA
    Besides table-level logging, minimal supplemental logging must be enabled at the database level in order for Oracle GoldenGate to process updates to primary keys and
    chained rows. This must be done through the database interface, not through Oracle GoldenGate. You can enable minimal supplemental logging by issuing the following DDL
    statement:
    SQL> alter database add supplemental log data;
    To verify that supplemental logging is enabled at the database level, issue the following statement:
    SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
    The output of the query must be YES or IMPLICIT. LOG_DATA_MIN must be explicitly set, because it is not enabled automatically when other LOG_DATA options are set.
    If you required more details refer Oracle® GoldenGate Windows and UNIX Reference Guide 11g Release 2 (11.2.1.0.0)

  • Support for NVARCHAR2 and/or CHARACTER semantics

    Does streams support replication of NVARCHAR2 between databases whose char set is ISO8859-1?
    Same question for char fields declared with CHARACTER semantics.
    Same questions as above but for GoldenGate.
    Does GoldenGate support replication of NVARCHAR2 between databases whose char set is ISO8859-1?
    Same question for GoldenGate for char fields declared with CHARACTER semantics.

    No, we have consolidated on the Apache XML/XSL stuff. You are free to use
    whatever other parser you would like however. The Sun XML pkg should work
    fine.
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc
    "Boris Tabenkin" <[email protected]> wrote in message
    news:[email protected]..
    Are you still including the sun XML package, and if so which version?
    "Toby Allsopp" <[email protected]> wrote in message
    news:[email protected]..
    Hi, Craig.
    Craig Macha wrote:
    Our company typically does NOT use Open Source products. We can't
    risk
    not having support.
    I think you're a little confused about what "Open Source" means. Itdoesn't mean "unsupported." If you want support then you need to pay forit,
    just like any software. One of the advantages of open source software is
    that you aren't tied to a single vendor for your support - anyone with the
    appropriate skills can take the source code and
    provide support, as BEA have chosen to do in this case.
    Regards,
    Toby Allsopp.

  • How to Turn Off Recyclebin?

    Hi,
    We are in a process of installing the Oracle Golden Gate software, wherein we need to stopp RECYCLEBIN to install DDL objects. The errormessage is as shown below.
    ERROR at line 1:
    ORA-20783:
    GoldenGate DDL Replication setup:
    *** RECYCLEBIN must be turned off.
    *** For 10gr2 and up, set RECYCLEBIN in parameter file to OFF. For 10gr1, set
    _RECYCLEBIN in parameter file to FALSE. Then restart database and installation.
    ORA-06512: at line 19
    Any help on this will be much appreciated.
    Thanks,
    Avadhut
    Email : [email protected]
    Mob# 9223504348

    Hi,
    ERROR at line 1:
    ORA-20783:
    GoldenGate DDL Replication setup:
    *** RECYCLEBIN must be turned off.
    *** For 10gr2 and up, set RECYCLEBIN in parameter file to OFF. For 10gr1, set
    _RECYCLEBIN in parameter file to FALSE. Then restart database and installation.
    ORA-06512: at line 19Change parameter RECYCLEBIN=FALSE* in Initialization parameter file under $ORACLEHOME/dbs/init<sid>.ora. and restart your database and start your Installation.
    If its using spfile use command *alter system set  _RECYCLEBIN=FALSE;*
    Hope helps
    Regards,
    X A H E E R

  • Oracle Gldengate Extract Issue

    Hi All:
    can we ignore perticulare database replicated data from extract process.
    exp: A database having two replicate one from B and one from C databases, which replicate data from B and C database server. i want extract process on A database which ignores those data, which comes from B database (through replicat). please help me out. i am using OGG 11.1.1.0 version
    is there any way to do this thing.
    Regards,
    Abhishek

    No, I meant what I posted: filter out/ignore based on the source database.
    Some examples:
    DBUSERID = @GETENV ("ORAENVIRONMENT","DBLOGINUSER")
    TK-OSUSER = @GETENV ("GGENVIRONMENT" , "OSUSERNAME"),
    TK-GROUP = @GETENV ("GGENVIRONMENT" , "GROUPNAME")
    TK-HOST = @GETENV ("GGENVIRONMENT" , "HOSTNAME")
    See page 406 in the 11.1.1. reference guide
    Not sure what you mean by "Can we create two GOLDENGATE DDL REPLICATION user's in a 1 schema of 1 database." If you have two replicat processes, you can have each process logging on as a different user, but you still have the issue of ignoring operations by those users back on the source when the changes get replicated there.

  • Goldengate replication performance

    Hi ,
    This is about Goldengate replication performance.
    Have configured Goldengate replication between OLTP and Reporting  and the business peak hours occurs only for a one hour.
    at that time I can see a LAG on the replicat side of around 10-15 minutes.
    Rest of all the time there is no LAG.
    I reviewed the AWR report of the target and I could see all the replicat process are executing with a elapsed time of 0.02 or 0.01 seconds.
    However I could see a major wait event DB sequential read of 65%-71% of DB time  and it is having the maximum Waits. apart from this there are no major wait event contributing to % DB time.(21% od DB CPU which I believe is normal )
    and I can also see few queries are being hit at that peak time since it is a reporting server. and they are using select query which executes more than 15-20 minutes specially on the High transaction table.
    Can you please advise where I should look on to resolve the LAG during the Peak hours.
    I believe the select operation/wait event is causing the LAG during that peak hours. Am I correct.
    can you please advise from your experience.
    Thanks
    Surendran

    Hi Bobby,
    Thanks for your response.
    Please find my response as below,
    Environment details as below.
    1. Source and target DB - oracle database enterprise edition v 11.2.0.4
    2. Goldengate version. 12.1.2.0.0  (Same Golden-gate version installed on source and target)
    3  Classic CDC process is configured between source and target Goldengate.
    Queries and response
    Is there any long running transactions on the extract side?
    No, long running transaction is seen, I can see a huge volume of transaction getting populated  (over 0.3M records in 30 minutes)
    Target environment information
    High transaction DML activities is seen only on 3 tables.
    As the target is reporting environment I can see many sql's querying those 3 high transaction populating tables and I can see DB sequential read wait event spiking up to 65%-71%.
    I can also see in the AWR report that the GG session are executing the insert/update transaction is less than 0.01/2 sec.
    Have to set the report for every 10 min. I will update to 1 min and share the report.
    My query is : Is the select operation executed on that high transaction table on the reporting server during that high transaction window is causing the bottleneck and causes the LAG during that peak hours ?
    or Do I need to look on other area's ?
    Based on above information If you any further comments/advise  please share.
    Thanks
    Surendran.

  • GoldenGate - Oracle to MSSQL - handling DDL replication abends on replicat

    Sorry for the cross-post. I clearly failed to actually read the "there's a GoldenGate forum" sticky...
    Hello -
    Very much a GoldenGate noob here, so please excuse me if I fumble on the terms / explanations - still learning.
    We've recently been lucky enough to have a GoldenGate pump put into our campus environment to support our data warehouse. We don't manage the pump or source systems - just the target.
    Pump: GoldenGate 11.1.1.1
    Source: Oracle 11g
    Target: MSSQL 2008R2
    ~5,000 tables of hugely varying sizes
    The extract is apparently configured to push DDL changes, which is clearly not going to work with a MSSQL 2008 R2 target. We're getting abend messages on the replicat and I'd like to know if we can bypass them on the replicat or need to ask that the extract process be modified to exclude DDL operations.
    The replicat error logs show exception:
    OGG-00453: DDL Replication is not supported for this database
    On the replicat I've tried including:
    DDL EXCLUDE ALL
    DDLERROR DEFAULT DISCARD (or DDLERROR DEFAULT IGNORE - neither let the process continue)
    The replicat just abends with the same OGG-00453 exception.
    My question: Can I gracefully handle these abends on the replicat? Or do I need to request the extract be updated with "DDL EXCLUDE ALL." Ideally, we can handle this on the replicat - I'm trying to be considerate of the main GoldenGate admin's time and also avoid any disruption of the extract.
    Any direction / info / ideas much appreciated.
    Thank you,
    Eric

    924681 wrote:
    Sorry for the cross-post. I clearly failed to actually read the "there's a GoldenGate forum" sticky...
    Hello -
    Very much a GoldenGate noob here, so please excuse me if I fumble on the terms / explanations - still learning.
    We've recently been lucky enough to have a GoldenGate pump put into our campus environment to support our data warehouse. We don't manage the pump or source systems - just the target.
    Pump: GoldenGate 11.1.1.1
    Source: Oracle 11g
    Target: MSSQL 2008R2
    ~5,000 tables of hugely varying sizes
    The extract is apparently configured to push DDL changes, which is clearly not going to work with a MSSQL 2008 R2 target. We're getting abend messages on the replicat and I'd like to know if we can bypass them on the replicat or need to ask that the extract process be modified to exclude DDL operations.
    The replicat error logs show exception:
    OGG-00453: DDL Replication is not supported for this database
    On the replicat I've tried including:
    DDL EXCLUDE ALL
    DDLERROR DEFAULT DISCARD (or DDLERROR DEFAULT IGNORE - neither let the process continue)
    The replicat just abends with the same OGG-00453 exception.
    My question: Can I gracefully handle these abends on the replicat? Or do I need to request the extract be updated with "DDL EXCLUDE ALL." Ideally, we can handle this on the replicat - I'm trying to be considerate of the main GoldenGate admin's time and also avoid any disruption of the extract.
    Any direction / info / ideas much appreciated.
    Thank you,
    EricI find strange that DDLERROR DEFAULT IGNORE does not work, are you sure you placed it properly? did you restarted the replicats after doing the change?
    Why dont you try specifying the error like:
    DDLERROR <error> IGNORE

  • How can we find if an oracle database is involved in GoldenGate replication

    Just by connecting to an oracle database using sqlplus, is there anyway to know if a database is involved in GoldenGate replication?
    i think dba_feature_usage_statistics is one option.
    Thanks
    Sarayu

    Hi,
    The best way that comes to mind is to make a grid where you have the entity and value dimensions on the rows and years and periods on the columns.
    For entities you select the parent and the child you want to look at, value dimension members <Entity Currency> and [Proportion]. For years you select those which you want to look at and all the periods.
    On the grid the [Proportion] should turn from green to red on one of the year/periods and that's the moment your entity became inactive to that parent.
    Hope this helps.

  • Install oracle goldengate at ASM  for data replication in RAC system?

    Hi Experts,
    We have 2 RAC server and each server have a 4 nodes RAC with 10R2 database in linux.
    We will install oracle goldengate as data replication between two RAC servers.
    Our database install on ASM in SAN box in linux
    Based on Goldengate install requirement, 16.     Set a shared driver that is accessed by each RAC nodes
    and install goldebgate on shared driver.
    As I understand, can we install goldengate on ASM that is shared by each node?
    Or we MUST set up other shared driver ( NO ASM) for installation of goldengate.
    Please advise me?
    Thanks
    Jim

    http://www.oracle.com/technology/products/goldengate/10/whitepapers/ha-goldengate-whitepaper.pdf
    This will answer your questions.

  • GoldenGate replication of creating users, roles

    System Specs:
    O/S : RHEL 5 (Tikanga)
    RDBMS: 11.2.0.3 (Standalone, ASM, Archivelog)
    GoldenGate v:11.1.1.0 (getting ready to upgrade to v11.1.1.2 (want to utilize the ADD SCHEMATRANDATA and updated sequence support)
    I have read the documentation in GG that says that DDL support Oracle restricted schemas is not supported (including sys and system). From this document a create statement is considered DDL.
    However, I have to think that when a user or role is created on the Source that you want that action replicated to the Targets? So you don't have to rerun the action on the number of targets you have. This is the benefit of replication, correct?
    Without this ability replication is somewhat restrictive.
    Please someone shed some light on how a user/role statement could be replicated?
    Thanks!
    Jason

    Okay, so I reviewed the documentation and need some help in replicating DDL for 2 schemas.
    Here is my Extract and Replicat modules
    EXTRACT EXT1
    USERID ggs_owner, PASSWORD ggs_owner
    RMTHOST db2, MGRPORT 7809
    RMTTRAIL /home/oracle/goldengate/dirdat/gg
    ---ddl---
    DDL INCLUDE MAPPED
    ---dml---
    table schema1.*;
    table exclude schema1.*_sq;
    REPLICAT REP1
    ASSUMETARGETDEFS
    USERID ggs_owner, PASSWORD ggs_owner
    DDL INCLUDE MAPPED
    DDLERROR DEFAULT IGNORE RETRYOP
    REPERROR (1403, DISCARD)
    MAP schema1.*, TARGET schema1.* ;
    MAP schema2.*, TARGET schema2.*;
    My issue is that ddl replication is only working for schema1. No ddl is being replicated with schema2. I know there must be a something small I am overlooking.
    I was successful with
    DDL INCLUDE ALL, EXCLUDE "schema3.*, EXCLUDE "schema4.*", EXCLUDE "schema5.*", etc...
    However, I don't want to list out every schema that could potentially perform ddl. I would think the DDL INCLUDE MAPPED and then include those schemas that you want mapped.
    Any ideas?

  • Goldengate replication of CLOBs in Linux

    Hi All,
    I'm facing a weird problem using GoldenGate to replicate CLOBs in a Linux environment. I have configured GG for a simple one-way replication of no more than 10 tables from Oracle to Oracle databases.
    Most of these tables have CLOB columns and during my testing, in a Linux box, I detected that the CLOB data is replicated to the target db adding an extra space between each character. For example:
    In the source:
    Text (CLOB): Testing replication of CLOB using Goldengate
    In the target, the replicat is saving the data in this way:
    Text (CLOB): T e s t i n g r e p l i c a t i o n o f C L O B u s i n g G o l d e n g a t e
    Have you seen this problen before? Is there any problem with my GG installation? I tested this in a Windows platform and there, the CLOBs are being replicated fine.
    The details of my Linux and GG env:
    SO: Oracle's Enterprise Linux 32bit
    Database: 11GR2
    GG (I’ve tried both 11G and 10G versions):
    For 10G:
    [orgolden@naciprdell209 golden]$ ./ggsci
    Oracle GoldenGate Command Interpreter for Oracle
    Version 10.4.0.19 Build 002
    Linux, x86, 32bit (optimized), Oracle 10 on Sep 17 2009 23:49:42
    Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.
    For 11G:
    [orgolden@naciprdell209 golden_11g]$ ./ggsci
    Oracle GoldenGate Command Interpreter for Oracle
    Version 10.4.0.19 Build 002
    Linux, x86, 32bit (optimized), Oracle 11 on Sep 17 2009 23:49:42
    Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.
    Thanks and regards,
    Harvey

    Okay, so I reviewed the documentation and need some help in replicating DDL for 2 schemas.
    Here is my Extract and Replicat modules
    EXTRACT EXT1
    USERID ggs_owner, PASSWORD ggs_owner
    RMTHOST db2, MGRPORT 7809
    RMTTRAIL /home/oracle/goldengate/dirdat/gg
    ---ddl---
    DDL INCLUDE MAPPED
    ---dml---
    table schema1.*;
    table exclude schema1.*_sq;
    REPLICAT REP1
    ASSUMETARGETDEFS
    USERID ggs_owner, PASSWORD ggs_owner
    DDL INCLUDE MAPPED
    DDLERROR DEFAULT IGNORE RETRYOP
    REPERROR (1403, DISCARD)
    MAP schema1.*, TARGET schema1.* ;
    MAP schema2.*, TARGET schema2.*;
    My issue is that ddl replication is only working for schema1. No ddl is being replicated with schema2. I know there must be a something small I am overlooking.
    I was successful with
    DDL INCLUDE ALL, EXCLUDE "schema3.*, EXCLUDE "schema4.*", EXCLUDE "schema5.*", etc...
    However, I don't want to list out every schema that could potentially perform ddl. I would think the DDL INCLUDE MAPPED and then include those schemas that you want mapped.
    Any ideas?

Maybe you are looking for