r12.2

[satish]

Hi erman,

Before applying patch,we will perform impact analysis but it will not show whether it affects any customizations.ofcourse we apply patch first in test instance and later technical team updates us that customisations are lost after applying the patch.Can you give some suggestions on how to avoid this.how to check if a patch was affecting any customisations.


Suppose if a patch delivers 2 packages and 2 fmb's,what all to check if it affects our customisations before applying a patch

[ErmanArslansOracleBlog]

Only the customizations that depend on the standard codes may be affected.
So, in order to understand this, you need to review what the patch is doing..
read "u" drv files of the patches and then check your customizations and decide manually.

[satish]

Thanks for the update,As a dba we can get what all actions patch was going to do but we cannot identifiy if it is customised or not?any ways to identify this or we just need to work this tech team providing all the changes that patch was going to do?

[ErmanArslansOracleBlog]

standard codes should not be customized at all!
However, you can have seperate customizations dependent on standard code and you need to work with your Developer teams for that.

As a dba you can use dba_source and some dependency views for PLSQL customizations, but for forms, oaf , java and reports customizations, I suggest you to make the developer teams review their codes.