CA Advanced Authentication Release Notes › Known Issues › Strong Authentication Known Issues › Old Values set for CA Risk Authentication, CA Strong Authentication, Case Management Instance-specific Configurations cannot be Preserved Post Upgrade on Upgrade to New Server Machine

Old Values set for CA Risk Authentication, CA Strong Authentication, Case Management Instance-specific Configurations cannot be Preserved Post Upgrade on Upgrade to New Server Machine

Symptom:

The new CA Risk Authentication,CA Strong Authentication and Case Management instance-specific configurations, transport (ssl) and the other protocol information are set to default values for the new instance, that is created after upgrade. The old values that are set before upgrade are not preserved for the new instance, post upgrade.

Solution:

The new upgrade to 8.0 creates new instance that draws values from the default settings. Reconfigure all CA Risk Authentication, CA Strong Authentication and Case Management server instance-specific configurations and transport (ssl) and the other protocol information.

Sequence Number Running Out of Range

Symptom:

The transaction ids are limited to 2^32-1. After a certain number of transactions by the system, unique Ids can run out of range and cause transactional failure.

Solution:

To prevent the sequence number running out of range, archive and trim audit logs from the transactional database at a regular intervals, as part of regular maintenance. The amount of data to keep in transactional database is governed by reporting requirements.

Perform the monitoring as outlined here at regular intervals:

1. Execute the query,

   SELECT count(*)   FROM    ARWFAUTHAUDITLOG A; 
   

   1. If the count is above 1 billion, archive older records.

   Reason: If this number reaches the limit, then the system encounters unique constraint failed error, causing transaction failure. Keep the records well below the highest range till next scheduled date for monitoring.

2. Execute the query,

   Select USEDVALUE FROM ARWFSEQUENCE WHERE SEQUENCENAME = 'ARWFTXNIDSEQ';
   

   1. If this value is larger than 2.1 billion then,
   • Archive and trim older records from the database. Verify that Step 1 is executed.
   • Shut down the server.
   • Execute the queries.

   Update ARWFSEQUENCE SET STARTINGVALUE=1 , WHERE SEQUENCENAME = 'ARWFTXNIDSEQ';

   Update ARWFSEQUENCE SET USEDVALUE=1 , WHERE SEQUENCENAME = 'ARWFTXNIDSEQ';

   • Restart the servers.

   Reason: If this number reaches the maximum value, then transaction fails as new sequence number is out of range. Keep the usedvalue below the maximum, till next scheduled monitoring date.

The transaction rate governs the interval at which to monitor the database. Revise the recommended numbers of 1 billion and 2.1 billion in the above guidelines, based on transaction volume and monitoring frequency.