My Oracle Support Banner

Streams Apply stops with ORA-55610 when destination tables are in a flash data archive (Doc ID 801134.1)

Last updated on DECEMBER 09, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


DDL statement was captured on the source database and propagated to destination database but the apply fails with ORA-55610
When we use print_errors procedure for the failing transaction we see the error ORA-55610 for that transaction.

SQL> exec print_errors
----- ERROR #1
----- Local Transaction ID: 5.20.7503
----- Source Database: TEST1
----Error in Message: 1
----Error Number: 55610
----Message Text: ORA-55610: Invalid DDL statement on history-tracked table

--message: 1
type name: SYS.LCR$_DDL_RECORD
source database: TEST1
owner: TEST1
object: TABLE1
is tag null: Y
ddl: alter table TABLE1 modify NEWVALUE varchar2(400)

PL/SQL procedure successfully completed.


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.