How the .dp file under data directory is updated with timestamp in CA Directory?

Products

• CA Identity Manager

Issue/Introduction

The following error occurred and DSA was unable to start.

  "DSA is attempting to start after a long outage, perform a recovery procedure before starting"

 

The .dp file under data directory shows timestamp older than 7 days.

 

How the .dp file under data directory is updated with timestamp in CA Directory in Multiwrite-DISP configured DSAs?
Why did the .dp file contain a timestamp that older than 7 days although the DSAs are running until recently?

Environment

Release : CA Directory 14.1

Resolution

The "DSA is attempting to start after a long outage, perform a recovery procedure before starting" error occurs when the .dp file contains a timestamp older than 7 days.
First of all, to resolve the long outage error, please refer to DSA is unable to start after a long outage

Supposed we have a pair of DSA that are configured to have Multiwrite-DISP configuration, both are running and communicating normally, then the .dp files will be updated in the following manner.
 

  - When there is any data update to any DSA.
  - When the DSA is shutdown gracefully
  - When the DSA is restarted

 

In this kind of condition, even if there is no data update for more than 7 days, the .dp file will be updated upon graceful DSA shutdown. So the next DSA restart will not have the 'DSA is attempting to start after a long outage, perform a recovery procedure before starting' error. In other words, unless the DSA's dxserver process is not terminated/exited abruptly then in this case the above 'long outage' condition won't occur.

So the possible reason that the .dp file contained an old timestamp although it ran until recently is, that there was no data update for a while and DSA's dxserver process was terminated unexpectedly.

 

Assuming the faulty DSA name is dsaname-CADir2, running the command on all nodes

dxdisp <dsaname-CADir2>

should resolve the issue.