Recently Updated Records in Custom Table on Source Instance are Skipped During Import on Target
Last updated on JULY 31, 2017
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Recently updated records in custom table on source instance (i.e., contribution) are skipped during import on target (i.e., consumption). The following systemdatabase and archiver tracing is found in the target instance.
The SELECT statement above is used to validate the changed record, but it's only referencing the primary key value to see if the record exists. In a working environment, it is expected to see the modify timestamp field used.
The table replication was working in UCM 10g and WCC 188.8.131.52, but started occurring with WCC 184.108.40.206.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms