Packaging Internals - IPS Finalize Package
(Doc ID 797160.1)
Last updated on APRIL 06, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.1.0 [Release 11.1 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
Why do we have "IPS FINALIZE PACKAGE" command?
Documentation library describe it as:
"Finalizing means adding to the package any additional trace files", but FINALIZE PACKAGE command has no argument as a file name, but only a number of package.
This note should solve this apparent antagonism and clarify about purpose of "IPS FINALIZE PACKAGE" and explain about packaging internals in general. It turns out that this command is available for compatibilty reasons only and there is NO NEED to run this command manually through ADRCI at any time while standard package creation.
End-Users should better ignore IPS FINALIZE option, because it's an internal functionality that will always trigger automatically at IPS GENERATE if not already run before. Contrary IPS finalize doesn't generate a physical package.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Why do we have "IPS FINALIZE PACKAGE" command? |
| Solution |
| Concepts |
| Logical packaging |
| Physical packaging |
| Additional Note IPS: run all in one |
| References |