CA Directory .db data file timestamps do not update on Windows

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite
• CA Directory

Issue/Introduction

CA Directory installed on Windows server may show .db file timestamps ("Created", "Modified", and "Accessed") that do not change after the Initial DSA creation, even when data has been modified. This occurs when the disable-transaction-log parameter is set to true in the DSA configuration.

Symptoms

• DSA data is actively changing, but .db file timestamps remain static.
• Timestamps reflect the date/time of DSA creation only.
• Uncertainty regarding the necessity of disaster recovery after an abnormal DSA exit.

Environment

• Release: 14.x
• Component: CA Directory
• OS: Windows

Cause

The created/modified/accessed timestamps of .db files in CA Directory on Windows do not change after DSA creation. Assumptions cannot be made about the state of data in a DSA based on these OS-level file values.

Resolution

Disaster recovery is required after an abnormal DSA exit if the disable-transaction-log is enabled, regardless of the .db file timestamps.

For technical assistance or specific recovery steps, see Contact Broadcom Support.

To download the latest releases or patches, see Download Broadcom Products and Software.