Table T_FLOW_STATE not purged

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

The table T_FLOW_STATE is not purged. It is detected in the QA database starting from August 2024, when we launched the Oracle Database. to contain more than 300K expired entries. 

Environment

VIP Authentication (Auth) Hub

Release : 3.4.4

Database: Oracle

Cause

expireTransactionalDataEnabled is not enabled in the environment.

Resolution

It is the responsibility of the Scheduler Job to automatically do the clean-up of the expired artifacts. 

The scheduler is responsible for cleaning up the expired Flow state objects. This process is repeated every ten minutes to clean up the expired flowstate objects. For this process to work it is important that the following setting is enabled in the environment.

expireTransactionalDataEnabled

Global

When this settings is enabled, database artifacts representing a temporary byproduct of an authentication flow get marked as expired. Later these expired data artifacts are removed by the scheduler process, instead of being deleted right away at the end of the authentication flow. This approach enables active/active deployment with data replication across multiple data centers. This helps in preventing data replication conflicts by having a single authoritative source for removing expired data artifacts.

Additional Information

Delete Expired Artifacts from Database

Manage VIP Authentication Hub Settings