Commit_timestamp$ displays 1/1/1988 in CDC Publisher Table
(Doc ID 729373.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.2 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
For few tables of publisher, Column COMMIT_TIMESTAMP$ displays 1/1/1988
Due to other issues with CDC, when executing errors like ORA-1858 or
ORA-1461 apply errors using DBMS_APPLY_ADM.EXECUTE_ERROR or EXECUTE_ALL_ERRORS, the COMMIT_TIMESTAMP$
column is set to '1/1/1988 0:0:0' in the change table.
Also seen in 10046 event trace:
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |