GoldenGate: Initialization when Table has Clob

Question

I have been testing Goldengate and I have performed schema initialization successfully when
all tables have scalar data types.
I have a problem when I include a table with a clob column in this test.
My clob table is simply:
desc johns_clob
Name Null? Type
ID NOT NULL NUMBER
MYCLOB CLOB
I've loaded the clob column with a character string that is 30000 characters long.
When I try to start the initial load, I get the following information in my ggserr.log file and the
process abends:
2010-11-10 16:47:40 INFO OGG-00963 Oracle GoldenGate Manager for Oracle, mgr.prm: Command received from GGSCI on host 10.143.204.77 (START EXTRACT INITLOAD ).
2010-11-10 16:47:40 INFO OGG-00975 Oracle GoldenGate Manager for Oracle, mgr.prm: EXTRACT INITLOAD starting.
2010-11-10 16:47:40 INFO OGG-01017 Oracle GoldenGate Capture for Oracle, initload.prm: Wildcard resolution set to IMMEDIATE because SOURCEISTABLE is used.
2010-11-10 16:47:40 INFO OGG-00992 Oracle GoldenGate Capture for Oracle, initload.prm: EXTRACT INITLOAD starting.
2010-11-10 16:47:41 ERROR OGG-01192 Oracle GoldenGate Capture for Oracle, initload.prm: Trying to use RMTTASK on data types which may be written as LOB chunks (Table: 'JOHNB.JOHNS_CLOB').
2010-11-10 16:47:41 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, initload.prm: PROCESS ABENDING.
Trying to use RMTTASK on data types which may be written as LOB chunks
I cannot find any reference to the message "Trying to use RMTTASK on data types which may be written as LOB chunks".
Any help is appreciated.
Thanks,
John

Answer 1

Hi,
Did you check this Metalink Doc?
Does GoldenGate Extract Support Oracle Spatial? [ID 971719.1]
Modified 07-JAN-2010 Type HOWTO Status PUBLISHED
In this Document
Solution
Applies to:
Oracle GoldenGate - Version: 4.0.0 - Release: 4.0.0
Information in this document applies to any platform.
Solution
Issue:
Does GoldenGate Extract support Oracle Spatial?
Solution Overview:
Oracle Spatial is supported with limitations.
Solution Details:
Spatial is supported:
1.Like-to-like only.
ASSUMETARGETDEFS is required in the Replicat parameter file.
SOURCEDEFS is not supported currently.
2. XMLType embedded in Spatial (and other UDT and system-DT) is not supported currently. (OS-7065)
3. The Spatial types that includes LOB are not supported currently. (OS-7134)
--------------------------------- example --------------------------------
NOTE: The 'SDO' indicates a spatial type object.
--------------------------------- example --------------------------------
--- create source table----
CREATE TABLE cities (
city VARCHAR2 (30) primary key,
state VARCHAR2 (30),
geom mdsys.SDO_GEOMETRY
--- create target table----
CREATE TABLE cities_t (
city VARCHAR2 (30) primary key,
state VARCHAR2 (30),
geom mdsys.SDO_GEOMETRY
INSERT into cities values ('SF','CA',
mdsys.sdo_geometry (2008, null, null,
mdsys.sdo_elem_info_array (1,1003,3),
mdsys.sdo_ordinate_array (-109,37,-102,40)
commit;
SQL >select * from cities; <======================= source table
CITY STATE
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SF CA
SDO_GEOMETRY(2008, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 3), SDO_ORDINATE_ARR
AY(-109, 37, -102, 40))
SQL >select * from cities_t; <======================target table
CITY STATE
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SF CA
SDO_GEOMETRY(2008, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 3), SDO_ORDINATE_ARR
AY(-109, 37, -102, 40))
Thanks.