Averify Critical Sequence Error AGIL-00025060/AGIL-00025056 Disappeared Even Though Fix Script Was Not Applied
(Doc ID 2942489.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Any of the below Averify critical sequence error reported in the earlier Averify run has disappeared even though fix script for the test case was not applied.
AGIL-00025060 : C : CHANGE_HISTORY table has bad data (Table ID:{ID1} is greater than the Sequence ID {ID2})
AGIL-00025056 : C : PROPERTYTABLE : table has bad data at id = {ID1} (Table ID is greater than the Sequence ID {ID2})
The issue can be reproduced at will with the following steps:
- Stop Agile Application Server
- Configure %Averify_Home%\config\averify.properties file. For RAC database instance, make sure that it is configured to connect to single database node.
- Run Averify by running averify.bat/averify.sh from %Averify_Home%\bin
- Check oracle_averify_report.log generated under %Averify_Home%\logs. See any of below error generated:
AGIL-00025060 : C : CHANGE_HISTORY table has bad data (Table ID:{ID1} is greater than the Sequence ID {ID2})
AGIL-00025056 : C : PROPERTYTABLE : table has bad data at id = {ID1} (Table ID is greater than the Sequence ID {ID2}) - Run Averify again.
- Check oracle_averify_report.log, and see the error is no longer reported.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |