Checkpoint to CDCT synchronization not done for time stamp "
time_stamp
" tag "
registration_tag
" number
record_count
reason
.
After a PowerExchange Condense warm start, PowerExchange tried to synchronize the current checkpoint file to the CDCT file. However, the checkpoint file record that includes the specified time stamp and registration tag does not match a record with the same key fields in the CDCT file. This mismatch might occur because of differing time stamps or condense file names in the records or because the checkpoint file record is a compressed RET record. RET records contain only the instance, registration tag, condense file name, retention information fields and cannot be used to add a corresponding record to the CDCT file. This warning message is issued for each checkpoint file record that cannot be synchronized with the CDCT file records.
Typically, these mismatches do not occur. They can be caused by deleting the current checkpoint file or by restoring the CDCT file to a point in time older than the retention limit recorded in the RET records. If a mismatch occurs because of differing time stamps or condense file names, the CDCT file can be restored based on the DCT records in the checkpoint file. However, if the mismatch occurs because of RET records in the checkpoint file, synchronization processing cannot be done and some records will be missing from the CDCT file.
In the message text, the variables are:
time_stamp
is the timestamp of the checkpoint record that could not be synchronized with the CDCT file.
registration_tag
is the registration identifier for the source object associated with the record that is missing from the CDCT file.
record_count
is the total number of records that are missing from the CDCT file after a checkpoint-to-CDCT file synchronization process. A separate PWX-06446 message is issued for each missing record. This variable reports the cumulative total up to the current message issuance.
reason
is the reason for the mismatch:
Different times: checkpoint=
timestamp_in_checkpoint_file_record
file=
timestamp_in_CDCT_record
Different filenames: checkpoint=
condense_file_name_in_checkpoint_file
file=
condense_file_name_in_CDCT
Only in checkpoint RET item
If the PowerExchange Condense OPER_WTOR_ENABLED parameter is set to Y, a PWX-06449 message is issued as a Operator Reply message for each record that is missing from CDCT file after a checkpoint-to-CDCT synchronization process. The system waits for you to reply Y or N to the message. If you reply Y, PowerExchange Condense processing continues. In this case, extraction processes might not find the condense files associated with the missing records, causing some change data to not be extracted. If you reply N, PowerExchange Condense processing ends.
If the OPER_WTO_ENABLED parameter is set to N, PowerExchange does not display the PWX-06449 Operator Reply message. PowerExchange Condense processing continues without notification of the missing records in the CDCT file. In this case, some change data might not be extracted.
Perform one or more the following actions:
Use the time stamp that this message reports to determine if the checkpoint record points to a condense file with old data or a condense file that has been processed by the CDC workflow.
Determine if the reported registration tag identifies a source object for which change data loss can be tolerated.
Examine the contents of the CDCT file to determine if it has been restored from an older backup.
Cold start the CDC workflow from an earlier point in time to prevent change data loss.
If you need assistance, contact Informatica Global Customer Support.
ASK BOLOPreview
