r12.2

classic Classic list List threaded Threaded
5 messages Options
Sri
Reply | Threaded
Open this post in threaded view
|

r12.2

Sri
Hi Erman,

I am new to this r12.2.5.your help is really appreciated and i am thankful to you for all your support.can you please clarify the below questions on prepare phase.

1)During prepare phase,will all the code objects get copied from run edition to patch edition?
2)If not copied,how they will exist after cutover?
3)if an code object is copied from run edition to patch edition,is that object called stub object?
Reply | Threaded
Open this post in threaded view
|

Re: r12.2

ErmanArslansOracleBlog
Administrator
"Please read EBR related EBS documentation."

Here is a quick info for your.
code objects are editionable objects. So they are editioned, not copied. This is the purpose of EBR.
Code objects are actualized in the new edition and in the cutover, we start using the new edition. Thus, we use the new code objects automatically.

Sri
Reply | Threaded
Open this post in threaded view
|

Re: r12.2

Sri
thanks erman,will go through the documentation.can you please make me understand where comes the stub objects(i uderstand these are inherited)
Reply | Threaded
Open this post in threaded view
|

Re: r12.2

ErmanArslansOracleBlog
Administrator
See ->

a stub object is not a actual object. It is just a defition that points to another object.
that's why its name is stub. It is an EBR thing. It is an online patching thing.


The following statement from Oracle, can make you understand better ->

All code objects in the patch edition begin as pointers to code objects in the run edition. Code objects in the patch edition begin as lightweight "stub objects" that point to the actual object definitions, which are inherited from earlier editions. Stub objects consume minimal space, so the database patch edition is initially very small in size.
Sri
Reply | Threaded
Open this post in threaded view
|

Re: r12.2

Sri
As always thank you,got it