How To Interpret the role of ad_file_versions Table
(Doc ID 294947.1)
Last updated on OCTOBER 31, 2019
Applies to:Oracle Applications DBA - Version 11.5.9 to 11.5.9 [Release 11.5]
Information in this document applies to any platform.
You are trying to determine the version of a file by querying ad_file_versions.
This implies your assumption that the most recent "LAST_UPDATE_DATE" would reflect the current version.
But often this will give you an older version of the file because if a patch contains any version of a file, it will write an entry to this table.
(without regard to whether or not that file actually got APPLIED by that patch).
For Example :
Let us consider on a particular instance, patch "A" was applied that delivered a much newer version of a file.
Patch "B" was subsequently applied, it contained an OLDER version of that file
(and, according to the patch log, that OLDER version was NOT applied).
However, AD_FILE_VERSIONS did include a row referencing that OLDER version of the file
(and that row did correspond to the run of patch "B").
Even running the snapshot on this instance several times did not change ad_file_versions.
In this case ad_file_versions DOES contain the correct information for the file in question.
But the problem is there exits another record with a NEWER last_update_date reflecting an OLDER version of the file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!