Please make it easier for a customer to determine which "patch application" that they think that they have applied. Now that patches are being released on an almost monthly basis, it can be very challenging for a client to determine which patch that they think that they have been applied AND if all entities have been patched (DB, Stat Central Agent, Windows Clients, Oracle EBS Agents).
This is my suggestion...
1) Add a script that would write against the STAT_DBSCRIPT_TBL for all patches even if the repository has not been updated with any schema or table updates.
ID: next sequential ID
Script Name: Stat <x.x.x> HotFix <a> -- this shows the patch that all entities SHOULD be on
Stat Version: Stat <x.x.x> HotFix <x>
Run Dt: <execution date of script>
*Run DB User Info: <keep what is currently recorded -- this is not really helpful info though>
2) Add the following information in the Stat Release Notes at the very beginning (optionally -- also place this in the <Run DB User Info>:
HotFix: <a>
Client: <x.x.x.x> -- this is in the version that shows in the "Details" tab of the "Properties" file of STAT.EXE
Stat Central Agent: <99999> -- identify the size of a file or a version # in some file -- something that people can use to identify the patch file of the agent
Oracle EBS Agent: <99999> -- identify the size of a file or a version # in some file -- something that people can use to identify the patch file of the agent
With so many moving pieces (multiple clients + multiple EBS Agents) it can be really challenging to:
- Determine the HotFix that the client should be on.
- Validate that the Stat Central Agent is on the correct patch that matches the Stat Repository.
- Validate that all Stat Clients match the Stat Repository.
- Validate that all Oracle EBS match the Stat Repository.
