Goldengate: XMLType abending replicat

Hi,
we are setting up a GG replication between a Oracle 10g and 11g Db.
Replication is setup and works fine, testing it with simple operations on tables looks fine.
We are using the clasical replications, and we are replicating one complete schema. No strange mappings, just simple replication from one Db, 1 to 1, to the second DB.
But then we run into a problem: We have some tables that contain XMLTYPE. On the extract and Pump side it seems to work, but the Replicat is abending when encountering one of those tables.
Getting the error:
2012-12-19 09:29:02 WARNING OGG-01003 Oracle GoldenGate Delivery for Oracle, rsc_ddl1.prm: Repositioning to rba 37853107 in seqno 0.
2012-12-19 09:29:02 INFO OGG-01020 Oracle GoldenGate Delivery for Oracle, rsc_ddl1.prm: Processed extract process RESTART_ABEND record at seq 0, rba 38014575 (aborted 478 records).
2012-12-19 09:29:03 ERROR OGG-00665 Oracle GoldenGate Delivery for Oracle, rsc_ddl1.prm: OCI Error getting OCI_ATTR_NAME for UDT SYS.XMLTYPE (status = 24328-ORA-24328: UnzulÌssiger Attributwert), SQL<Not available>.
2012-12-19 09:29:03 ERROR OGG-01668 Oracle GoldenGate Delivery for Oracle, rsc_ddl1.prm: PROCESS ABENDING.
This is the table actually causing the error as per logdump:
CREATE TABLE SOMETABLENAME
DATECREATED DATE DEFAULT SYSDATE,
DATECOMPLETED DATE,
CLIENTORDERID NUMBER,
ORDERTYPE VARCHAR2(100 BYTE),
BUSINESSEVENT VARCHAR2(100 BYTE),
CREATEDBY VARCHAR2(100 BYTE),
COMORDERTBLID NUMBER(15,5),
OBJECTID NUMBER(15,5),
OBJECTTYPE VARCHAR2(40 BYTE),
REVISION NUMBER(15,5),
I_XML_PAYLOAD SYS.XMLTYPE,
SUPPLEMENTAL LOG GROUP GGS_2209838 (COMORDERTBLID) ALWAYS
Looks like the issue is with SYS.XMLTYPE.
Any idea how to solve this?
Thank you very much.
manuel

Hi Annamalai,
1.
Source DB:
SQL> select * from v$version;
BANNER
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 HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Dest Db:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE     11.2.0.1.0     Production
TNS for HPUX: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
GG has the same version on both sides:
Oracle GoldenGate Delivery for Oracle
Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230
2:
Source:
VERSION STATUS
Oracle XML Database
10.2.0.4.0 VALID
destination:
this is strange, I do not get any output if I run that command onthe destination Db.
So is this XDb maybe the problem?
regards
manuel

Similar Messages

  • How to get the changes during ABENDED replicat process

    Hi,
    I am working on Oracle GG bi-directional DML replication. I m stuck in one place.
    My target replicat process was ABENDED due to Error :- ORA-01403: no data found. I restarted my replicat process again by runing the below command
    GGSCI (db1) 30> alter replicat rep2 begin now
    GGSCI (db1) 30> start replicat rep2
    After restart the replicat process I can't see the changes on target server which I had applyed on source server during target replicat was ABENED.
    My doubt is.
    1. Is my command is correct for start the ABENDEND replicat process?
    2.How to get the changes on target server which applyed on source during ABNDED of targer replication?
    3.How to avoid the ABENDED replicat process on production server?
    4.how to track the ABENDED process in production server?
    Please HELP:(
    Edited by: NaveenK on Aug 29, 2012 3:32 AM

    NaveenK wrote:
    Hi,
    I am working on Oracle GG bi-directional DML replication. I m stuck in one place.
    My target replicat process was ABENDED due to Error :- ORA-01403: no data found. I restarted my replicat process again by runing the below command
    GGSCI (db1) 30> alter replicat rep2 begin now
    GGSCI (db1) 30> start replicat rep2
    After restart the replicat process I can't see the changes on target server which I had applyed on source server during target replicat was ABENED.
    My doubt is.
    1. Is my command is correct for start the ABENDEND replicat process?
    2.How to get the changes on target server which applyed on source during ABNDED of targer replication?
    3.How to avoid the ABENDED replicat process on production server?
    4.how to track the ABENDED process in production server?
    Please HELP:(
    Edited by: NaveenK on Aug 29, 2012 3:32 AMHi Naveen. SQL Error 1403 means row not found. Your data is out of sync and you should fix this.
    By doing begin now when this happens, you are skipping all the transactions that were "in-line" since the process ABENDED.
    You have more than one way to deal with these things, first of all you should synchronize your data! This should get rid of the 1403 errors.
    Then you can write rules using REPERROR to tell the replicat how to behave in case of errors should come up.
    Using logdump, you can read the exact row which failed and find out the next RBA to skip that specific one if required. You should also configure a DISCARDFILE to get details about errors when they happen.
    Greetings,
    N K

  • GoldenGate Initial Load Replicat

    Initial Load REPLICAT Paramter File
    REPLICAT 1_IRMRI
    SPECIALRUN
    ASSUMETARGETDEFS
    HANDLECOLLISIONS
    DBOPTIONS USEODBC
    SOURCEDB XXX, USERID XXX, PASSWORD XXX
    EXTFILE ./dirdat/INITMRI000000
    EXTFILE ./dirdat/INITMRI000001
    EXTFILE ./dirdat/INITMRI000002
    EXTFILE ./dirdat/INITMRI000003
    EXTFILE ./dirdat/INITMRI000004
    EXTFILE ./dirdat/INITMRI000005
    EXTFILE ./dirdat/INITMRI000006
    EXTFILE ./dirdat/INITMRI000007
    EXTFILE ./dirdat/INITMRI000008
    EXTFILE ./dirdat/INITMRI000009
    EXTFILE ./dirdat/INITMRI000010
    EXTFILE ./dirdat/INITMRI000011
    EXTFILE ./dirdat/INITMRI000012
    EXTFILE ./dirdat/INITMRI000013
    EXTFILE ./dirdat/INITMRI000014
    EXTFILE ./dirdat/INITMRI000015
    EXTFILE ./dirdat/INITMRI000016
    EXTFILE ./dirdat/INITMRI000017
    EXTFILE ./dirdat/INITMRI000018
    EXTFILE ./dirdat/INITMRI000019
    EXTFILE ./dirdat/INITMRI000020
    EXTFILE ./dirdat/INITMRI000021
    EXTFILE ./dirdat/INITMRI000022
    EXTFILE ./dirdat/INITMRI000023
    EXTFILE ./dirdat/INITMRI000024
    EXTFILE ./dirdat/INITMRI000025
    EXTFILE ./dirdat/INITMRI000026
    EXTFILE ./dirdat/INITMRI000027
    EXTFILE ./dirdat/INITMRI000028
    EXTFILE ./dirdat/INITMRI000029
    EXTFILE ./dirdat/INITMRI000030
    EXTFILE ./dirdat/INITMRI000031
    EXTFILE ./dirdat/INITMRI000032
    EXTFILE ./dirdat/INITMRI000033
    EXTFILE ./dirdat/INITMRI000034
    DISCARDFILE ./dirrpt/1_IRMRI.dsc, PURGE
    MAP dbo.*, TARGET dbo.*;
    END RUNTIME
    The above parameter file does not pickup all the EXTFILE only the last file EXTFILE ./dirdat/INITMRI000034 is used by the REPLICAT process. I want to use all the EXTFILE ??
    The Syntax to add REPLICAT with multiple EXTFILE
    GGSCI>> ADD REPLICAT 1_IRMRI, EXTFILE ./dirdat/INITMRI*
    Can I use wildcard character in the above syntax ??

    Have you tried the Metalink Doc regarding that error?
    What Causes The "Bad Column Index(xxxx)" Error In Replicat? [ID 972954.1]
    Applies to:
    Oracle GoldenGate - Version: 4.0.0 - Release: 4.0.0
    Information in this document applies to any platform.
    Solution
    The "Bad Column Index(xxxx)" error in Replicat is caused by a Source Column Index "xxxx" greater than the number of columns in the Source Table Definition File Input to the Replicat process or if the ASSUMETARGETDEFS parameter is used and the Source Table and Target Table do not have the same structure, the Source Table has more columns than the Target Table.
    Example
    GGS ERROR 160 Bad column index(129) specified for table {table name}, max columns = 127
    Explanation
    The Source Table Trail Record has an Index and Data for Column Number 129 but only 127 columns are defined in the Source Table Definition File or when the ASSUMETARGETDEFS parameter is used in the Replicat Parameter File the Target Table contains 127 columns.
    This is generally caused by changes in the Source Table or Target Table(i.e. columns have been added or deleted and a new Source Definition File has not been created to reflect the Source Table structure to match the Trail Records that Replicat is trying to process.
    To resolve this error, run DEFGEN on the Source System for the Table causing the Replicat abend, copy that Definition File to the Target system. Add this SOURCEDEFS file to the Replicat Parameter file and restart the Replicat process.
    Note: This applies to all Open Systems platforms except z/OS(IBM mainframe)

  • Error OGG-01168 abending replicat process

    Hello All,
    Greetings !
    I have tables that do not have any unique key in source and target database. Replicat process work fine in this case for some tables but for certain table it stops. and generates error:
    "ERROR OGG-01168 Encountered an update for target table SAPSR3.BTCCTL, which has no unique key defined. KEYCOLS can be used to define a key. Use ALLOWNOOPUPDATES to process the update without applying it to the target database. Use APPLYNOOPUPDATES to force the update to be applied using all columns in both the SET and WHERE clause."
    What it exactly means ? I am not understanding, since both the tables have same structures. Pleas help.
    Best Regards,
    R.Kapil

    Hi,
    1. how you have added supplemental lod data on database ? database level or table level?
    2.Did you execute ADD TRANDATA <schemaname.*> on source side?
    3. have you used any COLMAP or Tokens in your parameter files?
    4. if you paste the extract and replicat prm files that would be help to check the details.

  • Replicat process abending with no error in logfile

    Hi,
    I m trying to replication from 11g to 10g on the same physical host. Below the replicat abending but unable to find the source of error in view GGSEVT logfile.
    GGSCI (rhel5.4_prod) 8> info all
    Program     Status      Group       Lag at Chkpt  Time Since Chkpt
    MANAGER     RUNNING                                          
    EXTRACT     RUNNING     EXTLOCAL    00:00:00      00:00:07   
    REPLICAT    ABENDED     REPLOCAL    00:00:00      18:12:27
    2013-04-16 09:58:40  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): start mgr.
    2013-04-16 09:58:41  INFO    OGG-00983  Oracle GoldenGate Manager for Oracle, mgr.prm:  Manager started (port 7809).
    2013-04-16 09:58:45  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): start extract extlocal.
    2013-04-16 09:58:45  INFO    OGG-00963  Oracle GoldenGate Manager for Oracle, mgr.prm:  Command received from GGSCI on host rhel5.4_prod (START EXTRACT EXTLOCAL ).
    2013-04-16 09:58:45  INFO    OGG-00975  Oracle GoldenGate Manager for Oracle, mgr.prm:  EXTRACT EXTLOCAL starting.
    2013-04-16 09:58:45  INFO    OGG-00992  Oracle GoldenGate Capture for Oracle, extlocal.prm:  EXTRACT EXTLOCAL starting.
    2013-04-16 09:58:45  INFO    OGG-03035  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Operating system character set identified as UTF-8. Locale: en_US, LC_ALL:.
    2013-04-16 09:58:46  INFO    OGG-03500  Oracle GoldenGate Capture for Oracle, extlocal.prm:  WARNING: NLS_LANG environment variable does not match database character set, or not set. Using database
    character set value of US7ASCII.
    2013-04-16 09:58:46  INFO    OGG-01815  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Virtual Memory Facilities for: BR
        anon alloc: mmap(MAP_ANON)  anon free: munmap
        file alloc: mmap(MAP_SHARED)  file free: munmap
        target directories:
        /u05/GG/BR/EXTLOCAL.
    2013-04-16 09:58:46  INFO    OGG-01815  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Virtual Memory Facilities for: COM
        anon alloc: mmap(MAP_ANON)  anon free: munmap
        file alloc: mmap(MAP_SHARED)  file free: munmap
        target directories:
        /u05/GG/dirtmp.
    2013-04-16 09:58:46  INFO    OGG-01513  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Positioning to Sequence 22, RBA 18459664, SCN 0.1177097.
    2013-04-16 09:58:46  INFO    OGG-01516  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Positioned to Sequence 22, RBA 18459664, SCN 0.1177097, Apr 15, 2013 4:21:50 PM.
    2013-04-16 09:58:46  INFO    OGG-00993  Oracle GoldenGate Capture for Oracle, extlocal.prm:  EXTRACT EXTLOCAL started.
    2013-04-16 09:58:46  INFO    OGG-00963  Oracle GoldenGate Manager for Oracle, mgr.prm:  Command received from EXTRACT on host rhel5.4_prod (START SERVER CPU -1 PRI -1  TIMEOUT 300 PARAMS ).
    2013-04-16 09:58:46  INFO    OGG-01677  Oracle GoldenGate Collector for Oracle:  Waiting for connection (started dynamically).
    2013-04-16 09:58:46  INFO    OGG-00963  Oracle GoldenGate Manager for Oracle, mgr.prm:  Command received from SERVER on host localhost.localdomain (REPORT 4714 7819).
    2013-04-16 09:58:46  INFO    OGG-00974  Oracle GoldenGate Manager for Oracle, mgr.prm:  Manager started collector process (Port 7819).
    2013-04-16 09:58:46  INFO    OGG-01228  Oracle GoldenGate Collector for Oracle:  Timeout in 300 seconds.
    2013-04-16 09:58:51  INFO    OGG-01226  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Socket buffer size set to 27985 (flush size 27985).
    2013-04-16 09:58:51  INFO    OGG-01229  Oracle GoldenGate Collector for Oracle:  Connected to rhel5.4_prod:11890.
    2013-04-16 09:58:51  INFO    OGG-01669  Oracle GoldenGate Collector for Oracle:  Opening /u05/GG/dirdat/aa000000 (byte -1, current EOF 1145).
    2013-04-16 09:58:51  INFO    OGG-01670  Oracle GoldenGate Collector for Oracle:  Closing /u05/GG/dirdat/aa000000.
    2013-04-16 09:58:51  INFO    OGG-01055  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Recovery initialization completed for target file /u05/GG/dirdat/aa000000, at RBA 1145.
    2013-04-16 09:58:51  INFO    OGG-01478  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Output file /u05/GG/dirdat/aa is using format RELEASE 11.2.
    2013-04-16 09:58:51  INFO    OGG-01669  Oracle GoldenGate Collector for Oracle:  Opening /u05/GG/dirdat/aa000000 (byte 1145, current EOF 1145).
    2013-04-16 09:58:51  INFO    OGG-01735  Oracle GoldenGate Collector for Oracle:  Synchronizing /u05/GG/dirdat/aa000000 to disk.
    2013-04-16 09:58:51  INFO    OGG-01735  Oracle GoldenGate Collector for Oracle:  Synchronizing /u05/GG/dirdat/aa000000 to disk.
    2013-04-16 09:58:51  INFO    OGG-01670  Oracle GoldenGate Collector for Oracle:  Closing /u05/GG/dirdat/aa000000.
    2013-04-16 09:58:51  INFO    OGG-01026  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Rolling over remote file /u05/GG/dirdat/aa000001.
    2013-04-16 09:58:51  INFO    OGG-01669  Oracle GoldenGate Collector for Oracle:  Opening /u05/GG/dirdat/aa000001 (byte -1, current EOF 0).
    2013-04-16 09:58:51  INFO    OGG-01053  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Recovery completed for target file /u05/GG/dirdat/aa000001, at RBA 1018.
    2013-04-16 09:58:51  INFO    OGG-01057  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Recovery completed for all targets.
    2013-04-16 09:58:51  INFO    OGG-01517  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Position of first record processed Sequence 22, RBA 18459664, SCN 0.1177097, Apr 15, 2013 4:21:50 PM.
    2013-04-16 09:58:51  INFO    OGG-00732  Oracle GoldenGate Capture for Oracle, extlocal.prm:  Found crash recovery marker from thread #1 on sequence 23 at RBA 1040. Aborting uncommitted transactions
    2013-04-16 09:58:56  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): start replicat replocal.
    2013-04-16 09:58:56  INFO    OGG-00963  Oracle GoldenGate Manager for Oracle, mgr.prm:  Command received from GGSCI on host rhel5.4_prod (START REPLICAT REPLOCAL ).
    2013-04-16 09:58:56  INFO    OGG-00975  Oracle GoldenGate Manager for Oracle, mgr.prm:  REPLICAT REPLOCAL starting.
    2013-04-16 09:58:56  INFO    OGG-00995  Oracle GoldenGate Delivery for Oracle, replocal.prm:  REPLICAT REPLOCAL starting.
    2013-04-16 09:58:56  INFO    OGG-03035  Oracle GoldenGate Delivery for Oracle, replocal.prm:  Operating system character set identified as UTF-8. Locale: en_US, LC_ALL:.
    2013-04-16 09:58:56  INFO    OGG-01815  Oracle GoldenGate Delivery for Oracle, replocal.prm:  Virtual Memory Facilities for: COM
        anon alloc: mmap(MAP_ANON)  anon free: munmap
        file alloc: mmap(MAP_SHARED)  file free: munmap
        target directories:
        /u05/GG/dirtmp.
    2013-04-16 09:58:56  INFO    OGG-00996  Oracle GoldenGate Delivery for Oracle, replocal.prm:  REPLICAT REPLOCAL started.Configuration
    GGSCI (rhel5.4_prod) 9> view params mgr
    PORT 7809
    USERID ggs_owner, PASSWORD ggs_owner
    PURGEOLDEXTRACTS /u05/GG/dirdat/ex, USECHECKPOINTS
    GGSCI (rhel5.4_prod) 10> view params extlocal
    extract extlocal
    userid ggs_owner, password ggs_owner
    setenv (ORACLE_HOME="/u03/app/oracle/product/11.2.0/db_1")
    setenv (ORACLE_SID="PROD11G")
    rmthost 192.168.1.9, mgrport 7809
    rmttrail /u05/GG/dirdat/aa
    TABLE TESTUSER.*;
    GGSCI (rhel5.4_prod) 11> view params replocal
    REPLICAT replocal
    SETENV (ORACLE_HOME="/u02/app10g/oracle10g/product/10.2.0/db_1")
    SETENV (ORACLE_SID="PROD10G")
    SETENV (NLS_LANG="AMERICAN_AMERICA.US7ASCII")
    ASSUMETARGETDEFS
    USERID ggs_owner, PASSWORD ggs_owner
    MAP TESTUSER.*, TARGET TESTUSER.*;

    Hi,
    Not sure if you have created a definition file. Try if your source and target has a mismatch. Also, find below some additional parameters which will help in sorting out the issue:
    DISCARDFILE :
    Valid for Extract and Replicat
    Use the DISCARDFILE parameter to generate a discard file to which GoldenGate can log records that it cannot process. Records can be discarded for several reasons. For example,
    a record is discarded if the underlying table structure changed since the record was written to the trail. You can use the discard file to help you identify the cause of processing errors. Each entry in the discard file contains the discarded record buffer and an error code indicating the reason. GoldenGate creates the specified discard file in the dirrpt subdirectory of the GoldenGate installation directory. You can view it with a text editor or by using the following command in GGSCI.
    VIEW REPORT
    Where: is the fully qualified name of the discard file.
    To prevent having to perform manual maintenance of discard files, use either the PURGE or APPEND option. Otherwise, you must specify a different discard file name before starting
    each process run, because GoldenGate will not write to an existing discard file. To set an upper limit for the size of the file, use either the MAXBYTES or MEGABYTES option. If
    the specified size is exceeded, the process will abend. Default By default, GoldenGate does not generate a discard file.
    DISCARDROLLOVER:
    Valid for Extract and Replicat
    Use the DISCARDROLLOVER parameter to set a schedule for aging discard files. For long or continuous runs, setting an aging schedule prevents the discard file from filling up and
    causing the process to abend, and it provides a predictable set of archives that can be included in your archiving routine.
    When the DISCARDROLLOVER age point is reached, a new discard file is created, and old files are renamed in the format of ., where:
    ? is the name of the Extract or Replicat group
    ? is a number that gets incremented by one each time a new file is created, for
    example: myext0.dsc, myext1.dsc, myext2.dsc, and so forth.
    You can specify a time of day, a day of the week, or both. Specifying just a time of day (AT option) without a day of the week (ON option) generates a discard file at the specified time every day.
    Default Disabled. No rules specified.
    REPERROR:
    Use REPERROR to specify an error and a response that together control how Replicat responds to the error when executing the MAP statement. You can use REPERROR at the MAP level to override and supplement global error handling rules set with the REPERROR parameter. Multiple REPERROR statements can be applied to the same MAP statement to
    enable automatic, comprehensive management of errors and interruption-free replication processing.
    DEFAULT Sets a global response to all errors except those for which explicit REPERROR statements are specified.
    GETDELETES | IGNOREDELETES:
    Valid for Extract and Replicat
    Use the GETDELETES and IGNOREDELETES parameters to control whether or not GoldenGate processes delete operations. These parameters are table-specific. One parameter remains in effect for all subsequent TABLE or MAP statements, until the other parameter is encountered.
    GETUPDATES | IGNOREUPDATES:
    Valid for Extract and Replicat
    Use the GETUPDATES and IGNOREUPDATES parameters to control whether or not GoldenGate processes update operations. The parameters are table-specific. One parameter remains in effect for all subsequent TABLE or MAP statements, until the other parameter is encountered.
    GETINSERTS | IGNOREINSERTS:
    Valid for Extract and Replicat
    Use the GETINSERTS and IGNOREINSERTS parameters to control whether or not insert operations are processed by GoldenGate. The parameters are table-specific. One parameter remains in effect for all subsequent TABLE or MAP statements, until the other parameter is encountered.
    Update the parameter file on target as
    edit params <TARGET PARAM FILE>
    REPLICAT rcreator
    SOURCEDEFS /u01/app/oracle/product/goldengate/dirdat/defecreator
    DISCARDFILE /u01/app/oracle/product/goldengate/dirdat/creator_err, purge
    DISCARDROLLOVER ON saturday
    USERID goldengate, PASSWORD AACAAAAAAAAAAAKAPATACEHBIGQGCFZCCDIGAEMCQFFBZHVC, ENCRYPTKEY default
    REPERROR (DEFAULT, DISCARD)
    IGNOREDELETES
    IGNOREUPDATES
    GETINSERTS
    MAP meditate.life, TARGET CONSCIOUSNESS.tenure, &
    COLMAP (PERSON_ID=HUMAN_ID, &
    INITIALNAME=FIRSTNAME, &
    ENDNAME=LASTNAME, &
    BIRTH_DATE=DATE_OF_BITH, &
    AGE_AT_DEATH=AGE_AT_TIME_OF_DEATH, &
    DEED_ID_AT_DEATH=DEED_ID_AT_TIME_OF_DEATH), &
    KEYCOLS (PERSON_ID, INITIALNAME,ENDNAME);
    Now stop and start the replicat on target as:
    GGSCI (goldengate) 9> stop replicat RCREATOR
    Sending STOP request to REPLICAT RCREATOR ...
    Request processed.
    GGSCI (goldengate) 10> info all

  • Common GoldenGate errors

    GG version 11.2.1.0.3
    OS: Unix/Unix-like
    For a typical Unidirectional configuration where only DML is replicated , what are the most common errors you usually encounter with GoldenGate ? Just name a few.

    N.Page wrote:
    Thank you NK. This particular error 1203 means that an UPDATE or DELETE was performed at source and when the replicat tried to replicate that change in the target table, it couldn't find that row. Right ?
    Network outage or server outage could be one of the reason for the Target not to be in sync. But once the network/server issues are fixed the 'pending' changes will be applied . So, how could the target become out of sync ?1403*
    Right. Other errors you could face with data out of sync are constraints errors for DML operations.
    Network or server outage could break the communication but goldengate should resume from where it left off.
    There are not many ways of target becoming out of sync, and they are mostly through human intervention. e.g. dml applied to target and not comming from a transaction applied by goldengate, or your replicat abends on target for some reason and they decide to skip a transaction that they shouldnt have, that kind of thing.
    As I said, if the initial load is successfull you should be fine and no errors should arise if your configuration is correct.
    If you happen to configure 2 replicats due to high transactions make sure tables who belong to a same transaction are configured to replicate through the same replication stream, else you could be in trouble aswell
    Edited by: N K on Jan 11, 2013 6:36 AM

  • Golden Gate: Replicate replicated data

    Hi,
    We have 3 Oracle 11GR2 database servers, A, B and C. At the moment we have GoldenGate replicating from A to B. We want to set up another GoldenGate process to replicate from B to C. Database server A cannot reach C, so the replication must come from B to C. Is there a way of replicating the replicated data in B to C? Can the second GoldenGate process (between B and C) be configured to pickup the replicated data in B from the first GoldenGate process (from A to B)?
    Rgs,
    Rob

    What I did to achieve this was to create the same GG process on B, but using a different OGGADMIN user (OGGADMIN2). Server B GG was configured to ignore data from OGGADMIN2 but not from OGGADMIN (from server A). This way I was able to replicate the replicated data from A to B and C while also maintaining a GG user between B and C.
    Thanks,
    Rob

  • HS : Connecting from 9.2.0.8 database on AIX to  MS SQL 2008R2

    Hello ,
    We have a requirement to connect from 9.2.0.8 database on AIX to MS SQL 2008R2 .
    Source :
    Oracle : 9.2.0.8 (64 bit)
    OS : AIX - 4.3.3.0/5.3.0.0 (64-bit)
    Target :
    MS SQL : 2008R2
    OS : Windows 2008 (64-bit)
    1] Can we use - Database Gateway for SQL Server for the above set up ? If so , does this require a separate license ?
    2] Where Do we need to install the "Database Gateway for SQL Server " -- soruce or target server ?
    3] Is there any other solution apart from using "Database Gateway for SQL Server " ?
    THanks,
    shashi

    Shashi,
    To answer your questions -
    1] Can we use - Database Gateway for SQL Server for the above set up ? If so , does this require a separate license ?
    Yes, you can use DG4MSQL and it does require a separate license.
    Your best option would be to use the latest version which is 11.2.0.3 but this requires you to apply patch 5965763 to your 9.2.0.8 RDBMS. See this note in My Oracle Support -
    Note.549796.1 Desupport of Oracle Transparent Gateways (Doc ID 549796.1)
    You also need to be on a particularAIX version as shown in the certification matrix -
    http://www.oracle.com/technetwork/database/gateways/certmatrix-168347.pdf
    if you install the gateway on AIX.
    2] Where Do we need to install the "Database Gateway for SQL Server " -- soruce or target server ?
    You can install DG4MSQL on any machine and connect to it from the RDBMS on AIX using database links. So, you can install on either AIX or Windows where SQL*Server is running. There is no difference in the performance.
    3] Is there any other solution apart from using "Database Gateway for SQL Server " ?
    You could also use the Database Gateway for ODBC (DG4ODBC) which uses a third party ODBC driver to make the connection between the gateway and the non-Oracle database. This is included with your RDBMS license but you need to supply the ODBC driver
    The following notes on My Orcle Support have further details and information -
    Master Note for Oracle Gateway Products (Doc ID 1083703.1)
    Options for Connecting to Foreign Data Stores and Non-Oracle Databases (Doc ID 233876.1)
    Functional Differences Between DG4ODBC and Specific Database Gateways (Doc ID 252364.1)
    Gateway and Generic Connectivity Licensing Considerations (Doc ID 232482.1)
    Depending what you want to do you could also use the GoldenGate product to replicate between Oracle and SQL*Server -
    http://www.oracle.com/technetwork/middleware/goldengate/overview/index.html
    This also requires aa separate license.
    Regards,
    Mike

  • Stop/Start OGG

    hi,
    I am using OGG and is working well (two-way replication)
    Every night, my databases are stopped and started (for snapshot backup)
    my question:
    is it better to stop/start OGG with the database
    or let OGG running all the time ?
    Thanks for your help

    Ideally, it would be better to stop GoldenGate and here is why:
    1. You know for sure that all transactions in the source have been replicated/applied to the target. You won't have source at SCN 123 and the target at SCN 119. You won't induce a synchronization problem.
    2. What if scenario - suppose while the databases are closed, something happens to the trails?
    3. What happens to a long-running transaction? Do you want to deal with bounded recovery issues? (answer: no)
    4. You won't be adding/generating irrelevant errors to GoldenGate processes, those about not being able to connect to the database. It just adds clutter to detail reports, and if you have any monitoring built-in, you can avoid generating irrelevant alerts.
    You can use the event marker infrastructure (i.e., send a message to GoldenGate to stop replicat or other processes), or if using regular scripting, check for lag being 0 after extract is stopped.

  • Import in already existing Streams environment

    Relatively new to streams and have my streams environment setup with mutidirectional schema level DML streaming done between two seperate RAC environments and a unidirectional streaming configured between each RAC environment and its reporting databases. Question is DEVELOPERS need to import data only from SQL SERVER into ORACLE while streaming in oracle is turned on. Is there a prefered method to this? I guess i am asking if there is anything wrong with this and if there is anything i need to do to make the process work or would it break streams? I appreciate your feedback.
    Regards,
    - Richard.

    Hi,
    Thanks for your response. I already have oracle replication configured but we now have a need too load 150gb there about data from sql server ad we were hoping to this by using 'GOLDENGATE'. I am told the process would involve initial load using an import into oracle and then GOLDENGATE would then replicate to ORACLE but we want the job to also replicate accross oracle 4 database databases involved in the streams so we were going to leave streams turned on. I have since looked over the process and consider the amount of log that would be generated and amount of work i would be putting on the system and i am thinking to stop apply, propagation and capture then do my load from SQL SERVER and only after that should ii turn replication back on and reinitialize streaming. Wondering what the better/best approach ought to be :)
    Thanks,
    - Richard.

  • Golden Gate Process to be monitored

    Hi Expoerts,
    We are evaluating an opportunity to monitor golden gate processes using 3rd party tool, would like to know what the process that we can monitor? and what is the best way to have monitoring implemented.
    - Any Doc or implementation guide for monitoring will be very helpful.
    Regards,
    MS

    You mean like re-invent the wheel with respect to what the management pack provides? Look at what Director does, and then emulate that. You know what goes on in GoldenGate (manager, extract, replicat), so that's what you monitor. More specific question = more specific answer.

  • 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

  • Replicat abend

    Hi
    i new with goldengate and i'm sorry if my english is bad.
    i'm trying to do active-active replicat from oracle 10gr2 to oracle 10gr2 using goldengate
    source n target have been running
    when i create table in source, target will recognize that
    but i have a problem
    this is what i do.
    source :
    drop table a
    target :
    select * from table a -> the result is table a not found (extract and replicat still running)
    then i do : select * from table a at source, then my replicat at target abend.
    cannot find table sender.a
    how can i handle this?
    can anyone help me about sqlexec too?
    how i use commit by using sqlexec? i put it on extract or replicat?
    i need to do the extract n replicat commit the dml automatically.
    therefore, i don't need to do commit everytime i do insert at source.
    thanks for helllpppp.. really need this.
    Edited by: 826012 on Jan 6, 2011 2:17 AM
    Edited by: 826012 on Jan 6, 2011 2:18 AM

    Source :
    extract ext_1
    userid oraclegg, password oracle
    rmthost 192.168.111.129, mgrport 7809
    rmttrail /u01/app/oracle/ggs/dirdat/aa
    ddl include mapped objname sender.*
    table sender.*;
    replicat rep_2
    assumetargetdefs
    userid oraclegg, password oracle
    map receiver.*, target sender.*;
    Target :
    extract ext_2
    userid oraclegg, password oracle
    rmthost 192.168.111.182, mgrport 7809
    rmttrail /u01/app/oracle/ggs/dirdat/bb
    ddl include mapped objname receiver.*
    table receiver.*;
    replicat rep_1
    assumetargetdefs
    userid oraclegg, password oracle
    map sender.*, target receiver.*;
    this is the error for rep_2 :
    2011-01-06 15:45:00 ERROR OGG-01296 Error mapping from RECEIVER.A to SENDER.A.
    next case is this :
    before i run my extract and replicat at source and target, i drop table A from schema receiver and sender, then when i start extract and replicat, the replicat (rep_1 and rep_2) are abended.
    error at rep_1 :
    2011-01-07 07:16:19 ERROR OGG-00519 Fatal error executing DDL replication: error [Error code [942], ORA-00942: table or view does not exist, SQL drop table "SENDER"."A" /* GOLDENGATE_DDL_REPLICATION */], no error handler present.
    error at rep_2 :
    2011-01-07 07:25:00 ERROR OGG-00199 Table RECEIVER.A does not exist in target database.
    what error handler to handle this? how can i use ignore?
    thanks for help......

  • Replicat is abending

    This is what i have on source and target:
    Source db: oracle 10.2.0.4 block size 8K
    target :db: oracle 10.2.0.4 block size 32K
    Souce configuration:
    MGR.prm
    PORT 7820
    USERID ggs_user, PASSWORD ggs_user
    PURGEOLDEXTRACTS /u01/oracle/ggs/dirdat/ex, USECHECKPOINTS
    extract load1.prm
    EXTRACT load1
    USERID ggs_user, PASSWORD ggs_user
    RMTHOST targetserver , MGRPORT 7820
    rmttrail /u01/oracle/ggs/dirdat/lt
    --RMTTASK replicat, GROUP load2
    TABLE usachclic.username_test;
    enabled supplemental logging.
    logged in as gss user and ran add trandata usachclic.username_test.
    On TARGET
    mgr.prm
    PORT 7820
    USERID ggs_user, PASSWORD ggs_user
    load2.prm
    REPLICAT load2
    ASSUMETARGETDEFS
    USERID ggs_user, PASSWORD ggs_user
    discardfile /u01/oracle/ggs/discard/rep1_discard.txt, append, megabytes 10
    MAP usachclic.username_test, TARGET usachclic.username_test;
    ./GLOBAL
    GGSCHEMA ggs_user
    CHECKPOINTTABLE ggs_user.checkpoint
    When i start intial load every thing looks goon on extarct load1
    This is the snapshot of GGSEVT
    2010-12-30 14:59:38 GGS INFO 302 Oracle GoldenGate Manager for Oracle, mgr.prm: EXTRACT LOAD1 starting.
    2010-12-30 14:59:38 GGS INFO 310 Oracle GoldenGate Capture for Oracle, load1.prm: EXTRACT LOAD1 starting.
    2010-12-30 14:59:38 GGS WARNING Z1-078 Oracle GoldenGate Capture for Oracle, load1.prm: No valid default archive log destination directory found for thre
    ad 1.
    2010-12-30 14:59:38 GGS INFO 310 Oracle GoldenGate Capture for Oracle, load1.prm: EXTRACT LOAD1 started.
    2010-12-30 14:59:43 GGS INFO 406 Oracle GoldenGate Capture for Oracle, load1.prm: Socket buffer size set to 27985 (flush size 27985).
    2010-12-30 14:59:43 GGS INFO 112 Oracle GoldenGate Capture for Oracle, load1.prm: Recovery initialization completed for target file /u01/oracle/ggs
    /dirdat/lt000002, at RBA 1682.
    2010-12-30 14:59:43 GGS INFO Z0-05M Oracle GoldenGate Capture for Oracle, load1.prm: Output file /u01/oracle/ggs/dirdat/lt is using format RELEASE 10.
    4.
    2010-12-30 14:59:43 GGS INFO 224 Oracle GoldenGate Capture for Oracle, load1.prm: Rolling over remote file /u01/oracle/ggs/dirdat/lt000003.
    2010-12-30 14:59:43 GGS INFO 112 Oracle GoldenGate Capture for Oracle, load1.prm: Recovery completed for target file /u01/oracle/ggs/dirdat/lt00000
    3, at RBA 969.
    2010-12-30 14:59:43 GGS INFO 112 Oracle GoldenGate Capture for Oracle, load1.prm: Recovery completed for all targets.
    But on target when i run:
    infol all command
    I get mamager is running and replicat load2 is abending.
    when i do info replicat load2 i get this
    REPLICAT LOAD2 Last Started 2010-12-30 14:36 Status ABENDED
    Checkpoint Lag 23:28:32 (updated 01:16:18 ago)
    Log Read Checkpoint File /u01/oracle/ggs/dirdat/lt000000
    2010-12-29 15:08:21.059469 RBA 969
    This is the snapshop of GGSEVT on target.
    2010-12-30 14:36:53 GGS ERROR 190 Oracle GoldenGate Delivery for Oracle, load2.prm: PROCESS ABENDING.
    2010-12-30 14:46:26 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params mgr.
    2010-12-30 14:46:48 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params ./GLOBAL.
    2010-12-30 14:47:17 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params load2.
    2010-12-30 14:49:10 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params load2.
    2010-12-30 14:58:22 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): stop replicat load2.
    2010-12-30 14:59:09 GGS INFO 371 Oracle GoldenGate Collector, port 7840: Closing /u01/oracle/ggs/dirdat/lt000002.
    2010-12-30 14:59:09 GGS INFO 372 Oracle GoldenGate Collector, port 7840: Terminating after client disconnect.
    2010-12-30 14:59:26 GGS INFO 301 Oracle GoldenGate Manager for Oracle, mgr.prm: Command received from EXTRACT on host 172.30.130.31 (START SERVER C
    PU -1 PRI -1 PARAMS ).
    2010-12-30 14:59:26 GGS INFO 302 Oracle GoldenGate Manager for Oracle, mgr.prm: Manager started collector process (Port 7840).
    2010-12-30 14:59:26 GGS INFO 373 Oracle GoldenGate Collector, port 7840: Waiting for connection (started dynamically).
    2010-12-30 14:59:31 GGS INFO 373 Oracle GoldenGate Collector: Connected to hcli-stag1101.hcli.usac.loc:55726.
    2010-12-30 14:59:31 GGS INFO 370 Oracle GoldenGate Collector, port 7840: Opening /u01/oracle/ggs/dirdat/lt000002 (byte 1682, current EOF 1682).
    2010-12-30 14:59:31 GGS INFO 371 Oracle GoldenGate Collector, port 7840: Closing /u01/oracle/ggs/dirdat/lt000002.
    2010-12-30 14:59:31 GGS INFO 370 Oracle GoldenGate Collector, port 7840: Opening /u01/oracle/ggs/dirdat/lt000003 (byte -1, current EOF 0).
    2010-12-30 15:26:27 GGS ERROR 190 Oracle GoldenGate Command Interpreter for Oracle: Received signal: Program interrupt (2).
    2010-12-30 15:26:27 GGS ERROR 190 Oracle GoldenGate Command Interpreter for Oracle: PROCESS ABENDING.
    2010-12-30 15:46:06 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params mgr.
    2010-12-30 15:47:40 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params load2.
    2010-12-30 15:48:24 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params ./GLOBAL.
    2010-12-30 15:53:22 GGS ERROR 190 Oracle GoldenGate Command Interpreter for Oracle: Received signal: Program interrupt (2).
    2010-12-30 15:53:22 GGS ERROR 190 Oracle GoldenGate Command Interpreter for Oracle: PROCESS ABENDING.
    Please HELP

    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 Linux: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Database Language and Character Set:
    NLS_LANG environment variable not set, using default value AMERICAN_AMERICA.US7ASCII.
    NLS_LANGUAGE = "AMERICAN"
    NLS_TERRITORY = "AMERICA"
    NLS_CHARACTERSET = "WE8ISO8859P1"
    Warning: NLS_LANG is not set. Please refer to user manual for more information.
    ** Run Time Messages **
    Opened trail file /u01/oracle/ggs/dirdat/lt000002 at 2010-12-30 19:16:19
    MAP resolved (entry USACHCLIC.USERNAME_TEST):
    MAP USACHCLIC.USERNAME_TEST, TARGET usachclic.username_test;
    Using following columns in default map by name:
    USERNAMEID, USERNAME, PASSWORD, FIRSTNAME, LASTNAME, EMAIL,
    DISABLEDFLAG, USERID, CREATIONDATE, LASTEDITDATE
    Using the following key columns for target table USACHCLIC.USERNAME_TEST: USERNAMEID.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000003 at 2010-12-30 19:16:19 due to EOF, with current RBA 1682
    Opened trail file /u01/oracle/ggs/dirdat/lt000003 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 3, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000004 at 2010-12-30 19:16:19 due to EOF, with current RBA 1362
    Opened trail file /u01/oracle/ggs/dirdat/lt000004 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 4, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000005 at 2010-12-30 19:16:19 due to EOF, with current RBA 1167
    Opened trail file /u01/oracle/ggs/dirdat/lt000005 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 5, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000006 at 2010-12-30 19:16:19 due to EOF, with current RBA 1029
    Opened trail file /u01/oracle/ggs/dirdat/lt000006 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 6, rba 969.
    2010-12-30 19:16:19 GGS WARNING 218 Aborted grouped transaction on 'USACHCLIC.USERNAME_TEST', Database error 1 (ORA-00001: unique constraint (USACHCLIC
    .SYS_C0036809) violated).
    2010-12-30 19:16:19 GGS WARNING 218 Repositioning to rba 1345 in seqno 2.
    Opened trail file /u01/oracle/ggs/dirdat/lt000002 at 2010-12-30 19:16:19
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000003 at 2010-12-30 19:16:19 due to EOF, with current RBA 1682
    Opened trail file /u01/oracle/ggs/dirdat/lt000003 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 3, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000004 at 2010-12-30 19:16:19 due to EOF, with current RBA 1362
    Opened trail file /u01/oracle/ggs/dirdat/lt000004 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 4, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000005 at 2010-12-30 19:16:19 due to EOF, with current RBA 1167
    Opened trail file /u01/oracle/ggs/dirdat/lt000005 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 5, rba 969.
    Switching to next trail file /u01/oracle/ggs/dirdat/lt000006 at 2010-12-30 19:16:19 due to EOF, with current RBA 1029
    Opened trail file /u01/oracle/ggs/dirdat/lt000006 at 2010-12-30 19:16:19
    Processed extract process graceful restart record at seq 6, rba 969.
    2010-12-30 19:16:19 GGS WARNING 218 SQL error 1 mapping USACHCLIC.USERNAME_TEST to USACHCLIC.USERNAME_TEST OCI Error ORA-00001: unique constraint (USAC
    HCLIC.SYS_C0036809) violated (status = 1), SQL <INSERT INTO "USACHCLIC"."USERNAME_TEST" ("USERNAMEID","USERNAME","PASSWORD","FIRSTNAME","LASTNAME","EMAIL","D
    ISABLEDFLAG","USERID","CREATIONDATE","LASTEDITDATE") VALUES (:a0,:a1,:a2,:a3,:a4,:a5,:a6,:a>.
    2010-12-30 19:16:19 GGS WARNING 218 Repositioning to rba 1029 in seqno 6.
    Source Context :
    SourceModule : [er.main]
    SourceID : [$Id: //depot/releases/OpenSys/v10.4.0/src/app/er/rep.c#19 $]
    SourceFunction : [take_rep_err_action]
    SourceLine : [14904]
    ThreadBacktrace : [7] elements
    : [u01/oracle/ggs/replicat(_ZN15CMessageContext16AddThreadContextEv+0x26) [0x5b1b46]]
    : [u01/oracle/ggs/replicat(_ZN15CMessageFactory13CreateMessageEP14CSourceContextjz+0x383) [0x5aa483]]
    : [u01/oracle/ggs/replicat [0x4ba31d]]
    : [u01/oracle/ggs/replicat [0x4c1687]]
    : [u01/oracle/ggs/replicat(main+0x4ee) [0x4d337e]]
    : [lib64/libc.so.6(__libc_start_main+0xf4) [0x3f18e1d994]]
    : [u01/oracle/ggs/replicat(__gxx_personality_v0+0x172) [0x45adea]]
    2010-12-30 19:16:19 GGS ERROR 218 Error mapping from USACHCLIC.USERNAME_TEST to USACHCLIC.USERNAME_TEST.
    * ** Run Time Statistics ** *
    Last record for the last committed transaction is the following:
    Trail name : /u01/oracle/ggs/dirdat/lt000004
    Hdr-Ind : E (x45) Partition : . (x04)
    UndoFlag : . (x00) BeforeAfter: B (x42)
    RecLength : 9 (x0009) IO Time : 2010-12-30 18:44:52.031077
    IOType : 3 (x03) OrigNode : 255 (xff)
    TransInd : . (x03) FormatType : R (x52)
    SyskeyLen : 0 (x00) Incomplete : . (x00)
    AuditRBA : 181 AuditPos : 126247440
    Continued : N (x00) RecCount : 1 (x01)
    2010-12-30 18:44:52.031077 Delete Len 9 RBA 1029
    Name: USACHCLIC.USERNAME_TEST
    Reading /u01/oracle/ggs/dirdat/lt000006, current RBA 1029, 3 records
    Report at 2010-12-30 19:16:19 (activity since 2010-12-30 19:16:19)
    From Table USACHCLIC.USERNAME_TEST to USACHCLIC.USERNAME_TEST:
    # inserts: 2
    # updates: 0
    # deletes: 1
    # discards: 1
    Last log location read:
    FILE: /u01/oracle/ggs/dirdat/lt000006
    SEQNO: 6
    RBA: 1029
    TIMESTAMP: 2010-12-30 19:09:24.032634
    EOF: NO
    READERR: 0
    CACHE OBJECT MANAGER statistics
    CACHE MANAGER VM USAGE
    vm current = 0 vm cached = 0
    vm anon = 0 vm file = 0
    vm used max = 0 ==> CACHE BALANCED
    CACHE CONFIGURATION
    cache size = 512M cache force paging = 881M
    buffer min = 64K buffer highwater = 4M
    pageout eligible size = 4M
    CACHE Transaction Stats
    trans active = 0 max concurrent = 0
    non-zero total = 0 trans total = 0
    CACHE File Caching
    disk current = 0 disk total = 0
    disk caching = 0 file cached = 0
    file retrieves = 0
    CACHE MANAGEMENT
    buffer links = 0 anon gets = 0
    forced unmaps = 0 cnnbl try = 0
    cached out = 0 force out = 0
    Allocation Request Distribution
    < 128B: 0
    128B: 0 0 | 512B: 0 0
    2K: 0 0 | 8K: 0 0
    32K: 0 0 | 128K: 0 0
    512K: 0 0 | 2M: 0 0
    8M: 0 0 | 32M: 0 0
    128M: 0 0 | 512M: 0 0
    2G: 0 0 | 8G: 0
    Cached Transaction Size Distribution
    0: 0
    < 4K: 0
    4K: 0 0 | 16K: 0 0
    64K: 0 0 | 256K: 0 0
    1M: 0 0 | 4M: 0 0
    16M: 0 0 | 64M: 0 0
    256M: 0 0 | 1G: 0 0
    4G: 0 0 | 16G: 0 0
    64G: 0 0 | 256G: 0 0
    1T: 0 0 | 4T: 0 0
    16T: 0 0 | 64T: 0 0
    256T: 0 0 |1024T: 0 0
    QUEUE Statistics:
    num queues = 15 default index = 0
    cur len = 0 max len = 0
    q vm current = 0 vm max = 0
    q hits = 0 q misses = 0
    queue size q hits curlen maxlen cannibalized
    0 64K 0 0 0 0
    1 128K 0 0 0 0
    2 256K 0 0 0 0
    3 512K 0 0 0 0
    4 1M 0 0 0 0
    5 2M 0 0 0 0
    6 4M 0 0 0 0
    7 8M 0 0 0 0
    8 16M 0 0 0 0
    9 32M 0 0 0 0
    10 64M 0 0 0 0
    11 128M 0 0 0 0
    12 256M 0 0 0 0
    13 512M 0 0 0 0
    14 1G 0 0 0 0
    ================================================================================
    CACHE POOL #0
    POOL INFO group: load2 id: p344_BLOB
    trans active = 0 trans concurrent (max) = 0
    trans total = 0 (0 )
    flag = 0x00000003
    highestCSN = (wrap=0, base=0) valid = 0
    last error = (0=<none>)
    Allocation Request Distribution
    < 128B: 0
    128B: 0 0 | 512B: 0 0
    2K: 0 0 | 8K: 0 0
    32K: 0 0 | 128K: 0 0
    512K: 0 0 | 2M: 0 0
    8M: 0 0 | 32M: 0 0
    128M: 0 0 | 512M: 0 0
    2G: 0 0 | 8G: 0

  • Replicat abended

    Hi,
    im my active -active replication setup, today i'm getting the below error message , can you please help me to resolve this ,
    2011-06-15 13:30:09 GGS ERROR 101 Oracle GoldenGate Delivery for Oracle,
    REP_TAR2.prm: Must be IGNORE, DISCARD, ABEND, EXCEPTION, TRANSABORT or RETRYOP
    Where i need to set the above parameters, please find below the map statements which is configured in both replicat prm files
    MAP replica.test, TARGET replica.item_descr, &
    REPERROR ( DEFAULT , EXCEPTION ) , &
    SQLEXEC ( ID detect_conflict, &
    ON UPDATE, &
    QUERY "SELECT 0 conflict FROM replica.test WHERE batch_id=:p_batch_id AND total=:p_total_before", &
    PARAMS(p_batch_id=batch_id,p_total_before=BEFORE.total), &
    ALLPARAMS REQUIRED , &
    BEFOREFILTER, &
    EXEC MAP, &
    TRACE ALL, &
    ERROR RAISE );
    also i have written a procedure on both side for mismatch,
    create or replace PROCEDURE ggadmin.h (
    p_batch_id IN NUMBER
    , p_total_after IN NUMBER
    , p_total_before IN NUMBER)
    IS
    BEGIN
    UPDATE replica.test
    SET total = total + (p_total_after - p_total_before)
    WHERE batch_id = p_batch_id;
    END h;
    Please help to resolve the 2011-06-15 13:30:09 GGS ERROR 101 Oracle GoldenGate Delivery for Oracle,
    REP_TAR2.prm: Must be IGNORE, DISCARD, ABEND, EXCEPTION, TRANSABORT or RETRYOP
    when i start the replicat process both side it goes ABENDED status... below are the full replicat process entries please advice...
    -- Replicat process
    REPLICAT REP_SRC1
    -- Environment Settings
    USERID ggadmin, PASSWORD ggadmin
    -- Discard file path
    DISCARDFILE E:\ggs\dirrpt\rep1_dsc.rpt, append
    -- Grneral Parameters
    ASSUMETARGETDEFS
    -- Truncate parameter
    --GETTRUNCATES
    DDL INCLUDE ALL
    DDLERROR DEFAULT IGNORE RETRYOP
    --HANDLECOLLISIONS
    APPLYNOOPUPDATES
    -- Mapping parameters
    GETAPPLOPS
    IGNOREREPLICATES
    -- This starts the macro
    --MAP replica.*, target replica.*;
    MAP replica.test , TARGET replica.test, &
    REPERROR ( DEFAULT, EXCEPTION ), &
    SQLEXEC ( ID detect_conflict, &
    ON UPDATE, &
    QUERY "SELECT 0 conflict FROM replica.test WHERE batch_id=:p_batch_id AND total=:p_total_before", &
    PARAMS(p_batch_id=batch_id,p_total_before=BEFORE.total), &
    ALLPARAMS REQUIRED, &
    BEFOREFILTER, &
    EXEC MAP, &
    TRACE ALL, &
    ERROR RAISE );
    MACRO #exception_handler
    BEGIN
    , TARGET ggadmin.exceptions
    , EXCEPTIONSONLY
    , SQLEXEC ( SPNAME ggadmin.h, &
    PARAMS(p_batch_id = batch_id, &
    p_total_after = total, &
    p_total_before = BEFORE.total)
    , EXEC MAP
    , TRACE ALL
    , COLMAP ( rep_name = "rep_src1"
    , table_name = @GETENV ("GGHEADER", "TABLENAME")
    , errno = @GETENV ("LASTERR", "DBERRNUM")
    , dberrmsg = @GETENV ("LASTERR", "DBERRMSG")
    , optype = @GETENV ("LASTERR", "OPTYPE")
    , errtype = @GETENV ("LASTERR", "ERRTYPE")
    , logrba = @GETENV ("GGHEADER", "LOGRBA")
    , logposition = @GETENV ("GGHEADER", "LOGPOSITION")
    , committimestamp = @GETENV ("GGHEADER", "COMMITTIMESTAMP")
    , batch_id=batch_id
    , batch_id_before = BEFORE.batch_id
    --, total_after = total
    , total_before = BEFORE.total
    , record_image = @GETENV ("GGHEADER", "BEFOREAFTERINDICATOR"))
    , INSERTALLRECORDS
    END;
    -- This ends the macro
    Edited by: Atp on Jun 15, 2011 5:49 PM

    Hi Steven,
    Thanks for your reply,
    the problem is space between ( and DEFAULT also between EXCEPTION and ) after removing the space its working fine....
    REPERROR (DEFAULT, EXCEPTION), &

Maybe you are looking for