This blog post tackles common questions regarding code objects and the prepare phase in Oracle EBS R12.2. Note that, this is derived from my forum.. Based on a real question. It's especially helpful for those new to EBS 12.2 and want to understand how code objects are handled during patching. The Questions: Are all code objects copied from the run edition to the patch edition during the prepare phase? If not copied, how do they exist after the cutover? Are the objects copied during the prepare phase called stub objects? Understanding Editioning and EBR: We clarify that code objects are editionable. This means they are managed through Oracle's Edition Based Redefinition (EBR) feature, rather than simply being copied. EBR allows for maintaining different versions of code objects within the same database. Code Objects in the Patch Edition: During the prepare phase, code objects aren't physically copied. Instead, they are editioned in the patch edition. This essentially creates new versions of the code objects specific to the patch. Cutover and Using New Code Objects: The cutover phase activates the patch edition. As a result, the newly editioned code objects become active, and you automatically start using them. Stub Objects Explained: These aren't actual code objects but rather placeholders. They act as pointers referencing the original code objects in the run edition. Why Stub Objects? Stub objects are lightweight, minimizing the initial size of the patch edition. This efficiency is crucial for online patching, where downtime is minimized. A Clearer Picture: Imagine the run edition as your main codebase. The prepare phase creates a new edition (patch edition) with pointers (stub objects) to the run edition's code objects. These pointers are lightweight, keeping the patch edition initially small. Finally, during cutover, the patch edition becomes active, and you start using the editioned code objects.

View Entire Post