RE: GALAXY QA RTM running on server AWSATPNVAL000P with the component logger is not running @ timestamp 25-Mar-2026 12:00:53 EST
EDG logger was restarted. 
 
[rmatsa@AWSATPNVAL000P oraarch]$ ps -ef|grep ccl 
oracle   1533458       1  2 01:56 ?        00:02:33 pwxccl config=/informatica/pwx_install/dbmover_log.cfg cs=/informatica/pwx_install/pwxccl.cfg 
rmatsa   1749650 1520349  0 03:51 pts/1    00:00:00 grep --color=auto ccl 
[rmatsa@AWSATPNVAL000P oraarch]$  
 
mail communicated to EDG /CDC Team. 
 
On 25?Mar?2026 at approximately 16:05, the Informatica PowerExchange logger process on GALAXY QA (RTM) server AWSATPNVAL000P went down unexpectedly. As a result, CDC capture activity was temporarily stopped, leading to replication lag in downstream processes. 
 
The logger failure was caused by a record-level lock contention on the PowerExchange CDC control file: 
The logger was unable to update its internal CDCT (Change Data Capture Tracking) file due to an existing lock, resulting in a DB_UPDATE failure. This lock was likely caused by: 
 
A stale or orphaned PowerExchange process from a previous session, or 
Concurrent access attempt to the CDCT file, or 
File system/NFS-level locking delay 
 
As a safety mechanism, the PowerExchange logger shut itself down to prevent any potential data inconsistency. 
 
 
Corrective Actions Taken 
 
Archive logs were kept on hold to prevent deletion of required redo information during the logger downtime. 
Verified that no active or orphaned PowerExchange processes were holding the CDCT file lock. 
The PowerExchange logger was restarted using a warm start, allowing it to: 
 
Resume from the last valid checkpoint 
Avoid duplicate capture or data gaps 
 
 
Post-restart monitoring confirmed that CDC activity resumed successfully.