Today I am going to give little insight about Opatch and CPU patch.Opatch is a tool is used to patch all oracle homes for oracle applications. CPU is stands for Critical patch updates, in other way its a security patches for Apps. Is Apps DBA responsibility to keep CPU patches up-to-date to avoid security vulnerabilities.
In Apps we need to use Opatch and adpatch for patching oracle apps. Why we need to use two utility to patch oracle apps.opatch is used to patch all oracle homes (for R12..10.1.2,10.1.3 and 10.2.0.2 oracle homes). Apps patches we need to use to adpatch.
How to use Opatch?
Opatch is one of the easiest and safest for patching oracle apps because you can rollback opatch if you find any issues applying the patches
- From the opatch read me make sure which oracle home you want to patch
- Shutdown the instance related to particular oracle home.
- Set the oracle home in the env .Set the opatch in the path.
- Follow the readme whether opatch needs up gradation.
- cd to the patch area and opatch apply
- Proceed the post install steps
- Run cpu_root.sh to give some permissions to the executables.
- For rollback use opath rollback –id
- “opatch lsinventory “ is used to list all the patches
- “opatch lsinventory –details” is used to find the version belongs to particular oracle home.
CPU patch
CPU patch has to keep uptodate. Use opatch to apply CPU patches. Follow the opatch steps to apply the CPU patch. As part of post installation step run catcpu.sql and utlrp.sql
Issues will face
- When you are applying CPU patch you will get conflict with some patches .Report to Oracle Corporation they will provide a new merged patch if its actually a conflict.