If you have used PWXUCDCT to derive a backup CDCT, and then used PWXUCDCT to restore that backup to the actual CDCT, then you don't need SEQUENCE_TOKEN and RESTART_TOKEN overrides.
All you need to do is warm start PWXCCL.
If you do want to use those token values for a special start or cold start, just use the tokens from the PWX-33256 message. "Sequence" is the SEQUENCE_TOKEN, and "Restart" is the RESTART_TOKEN
220114 152811 LNX64 3 PWX-33256 CCLWTR File switch complete. Current restart tokens: Sequence
Thanks for the quick reply,
So even though there is a lapse between the time the logger went down, and the new logger is running, rebuilding the CDCT from CND will tell the logger to begin reading in Oracle REDO? Much simpler than I was making this out to be. And to special start from the messages in the PWX message log, I don't need to convert anything to decimal from HEX, just put the tokens in exactly as I see them in the messages?
If that is the case, you have made my job so much easier,
PWXCCL writes checkpoints to CDCT when each CND file is closed.
On a warmstart, PWXCCL restarts as of the most recent checkpoint in the CDCT.
When you rebuild the CDCT using PWXUCDCT, that includes the relevant checkpoints.
So after that, a warm start of PWXCCL will restart as of the tokens/checkpoint corresponding to last closed CND file.
Most likely, that will be somewhere in Archive Logs.