GoldenGate

Guys,

I am a Golden Gate novice just trying to setup sync between two 11.2.0.1 databases on Linux 64 Bit servers. The process I am trying to follow, in a nutshell, is as under:-

1. Setup extract process on node rac1, DB gg1
2. Setup data pump on node rac1
3. Start manager, extract and datapump on node rac1
4. Clone database gg1(node rac1) to gg1dup(node rac2) using duplicate database command
5. Start replicate on node rac2 using afterscn from Ser# 4

The extract and data pump processes get into an ABEND state due to probably unsupported data types including TIMESTAMP WITH TZ datatype (supported per documentation). I have included all schemas in the extract parameter file - not sure if I need to exclude some of them for full database sync ! Relevant extract of error log and extract parameter files are as under:-

2010-09-30 17:09:33 ERROR OGG-01418 Oracle GoldenGate Capture for Oracle, ext_db.prm: Unsupported datatype SYS.TIMESTAMP WITH TZ (188) found in UDT attribute TIMESTAMP_ORIGINATING (type: ALERT_TYPE).
2010-09-30 17:09:33 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, ext_db.prm: PROCESS ABENDING.

2010-10-04 12:39:32 INFO OGG-01517 Oracle GoldenGate Capture for Oracle, ext_db.prm: Position of first record processed Sequence 6, RBA 6449168, SCN 0.1029802, Sep 30, 2010 4:13:49 PM.
2010-10-04 12:39:53 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_CAPTURE_SQL. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:39:53 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_CAPTURE. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:39:54 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_LATEST_SQL. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:39:54 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_LATEST. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:39:56 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_SYSTEM_PERFORMANCE_LOG. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:39:59 WARNING OGG-00869 Oracle GoldenGate Capture for Oracle, ext_db.prm: No unique key is defined for table MGMT_OMS_PARAMETERS. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2010-10-04 12:40:00 ERROR OGG-00665 Oracle GoldenGate Capture for Oracle, ext_db.prm: OCI Error getting OCI_ATTR_NAME for UDT (status = 24328-ORA-24328: illegal attribute value), SQL<Not available>.
2010-10-04 12:40:00 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, ext_db.prm: PROCESS ABENDING.

# ext_db.prm
EXTRACT ext_db
USERID ggate@gg1, PASSWORD xxx
EXTTRAIL ./dirdat/lt
--DDL support
--DDL INCLUDE MAPPED OBJNAME sender.*;
TABLE ANONYMOUS.*;
TABLE APEX_030200.*;
TABLE APEX_PUBLIC_USER.*;
TABLE APPQOSSYS.*;
TABLE BI.*;
TABLE CTXSYS.*;
TABLE DBSNMP.*;
TABLE DIP.*;
TABLE EXFSYS.*;
TABLE FLOWS_FILES.*;
TABLE GGATE.*;
TABLE HR.*;
TABLE IX.*;
TABLE MDDATA.*;
TABLE MDSYS.*;
TABLE MGMT_VIEW.*;
TABLE OE.*;
TABLE OLAPSYS.*;
TABLE ORACLE_OCM.*;
TABLE ORDDATA.*;
TABLE ORDPLUGINS.*;
TABLE ORDSYS.*;
TABLE OUTLN.*;
TABLE OWBSYS.*;
TABLE OWBSYS_AUDIT.*;
TABLE PM.*;
TABLE SCOTT.*;
TABLE SH.*;
TABLE SI_INFORMTN_SCHEMA.*;
TABLE SPATIAL_CSW_ADMIN_USR.*;
TABLE SPATIAL_WFS_ADMIN_USR.*;
TABLE SYS.*;
TABLE SYSMAN.*;
TABLE SYSTEM.*;
TABLE WMSYS.*;
TABLE XDB.*;
TABLE XS$NULL.*;

Will appreciate any pointers to help debug and resolve the above situation. Also, is there a way to bump up the log/trace level for ggserr.log ?

Thanks,

Satish