My Oracle Support Banner

Mapping DDL statements from one tablespace to another (Doc ID 1335553.1)

Last updated on JULY 17, 2017

Applies to:

Oracle GoldenGate - Version: and later   [Release: 9.5.0 and later ]
Information in this document applies to any platform.


The tablespace names in our target and source databases are different.
On an index create ddl, GG REPLICAT abends because the tablespace in source db does not exist in the target db:

OGG-00495 Oracle GoldenGate Delivery for Oracle, erep5.prm: DDL error ignore for next retry: error code [DEFAULT], filter [include all (default)], error text [Error code [959], ORA-00959: tablespace 'D_724ACCESS' does not exist, SQL CREATE INDEX "OGGADM"."CUSTMER_PK" ON CUSTMER (CUST_ID) TABLESPACE D_724ACCESS /* GOLDENGATE_DDL_REPLICATION */]

Is there a parameter we can set in the REPLICAT to map the target tablespaces?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.