OGG-01028 : Formatting error on: table name schema_name.table_name, rowi d AACjvQAFtAAAFYrAAA, XID 1155.38.90011, position (Seqno 125631, RBA 1673159256). Error converting timestamp with timezone from Oracle to ASCII format for column xxx.

One of the extract group failed with the above error today on 10g database:

Formatting error on: table name SCHEMA_NAME.TABLE_NAME, rowi
d AACjvQAFtAAAFYrAAA, XID 1155.38.90011, position (Seqno 125631, RBA 1673159256). Error converting timestamp with timezone from Oracle to ASCII format for column COLUMN_NAME.

Metalink Note: 1558791.1 says that this is db bug and apply a patch 15947884.

The other Note: 1350728.1 (OGG Extract support for Data Type TIMESTAMP WITH TIME ZONE, Oracle to ASCII) says that:
Extract requires the TRANLOGOPTIONS INCLUDEREGIONID or INCLUDEREGIONIDWITHOFFSET to support this data type correctly.

For now, added below to extract parameter and started the extract and it's running fine:
TRANLOGOPTIONS INCLUDEREGIONID

The other option might be considered is by adding below right before userid:
setenv (nls_lang="AMERICAN_AMERICA.US7ASCII")

ORA-01418: specified index does not exist

Very simple issue :)
There was this table which we were back loading about 14 billion rows while disabling the PK and when all is done, the next step was to start GoldenGating to replicate the live data and fun started.

As mentioned this table has about 14 billion records with about 700GB. So, enabling PK is not going to be fun (dont want to use novalidate) - took about close to 12 hours but didn't finish.

Best and the fasted way is to create an index first (unique or non-unique) with parallel and nologging and then enable the Primary Key using that index.

So, tried to create an index and see that there is already one index created on the very same column.

Well then lets use that index, so issued below:
alter table schema_name.table_name enable constraint table_name_pk using index index_name;
*
ERROR at line 1:
ORA-01418: specified index does not exist

What??? That index exists so what's the issue?

I was trying to enable that constrain by logging as my user and figured it got to be something to do with privs. So, logged in as the schema owner and ran the script and it runs fine.