Information on Custom packages

[satish]

Hi Erman,

Prepare phase was completed,later we have connected to run edition and created 2 packages but after cutover we are not able to view them.

Is this normal,pls suggest

Thank you

[ErmanArslansOracleBlog]

What do you mean by inherited?

If you ask for the stub objects.
Here is an sql for you:

ADZDSHOWOBJS - Show Object Summary per edition. Counts of actual and stub (inherited) editioned object per edition.

Use this sql to monitor the inherited objects

[ErmanArslansOracleBlog]

AD_OBJECTS can also be used to check the object status to see whether the object is “actual” (a real object) in the current edition, or a "stub" object (the object definition was inherited from a previous edition).

[ErmanArslansOracleBlog]

You can read Oracle E-Business Suite Developer's Guide, Part No. E22961, as well.

[ErmanArslansOracleBlog]

Oracle says:

If yo apply customizations as an online patch, the custom code is patched into the patch edition when an online patching cycle is open. The patch must follow Online Patching Development Standards.
"In this case, the custom patch acts like any other Oracle E-Business Suite online patch and receives the same benefits (no additional downtime, ability to review patching results before cutover, ability to abort the patch if there is trouble)"

This means, the custom db objects (when deployes as online patches) are maintained in the same manner as the standard db objects..

[satish]

Yes i agree erman and thanks for the update.is it mandatory to follow any naming convention for custom packages.

Will we loose custom packages if we create in in run edition during an online patching cycle?

Thank you

[ErmanArslansOracleBlog]

1)Read -> Oracle® E-Business Suite Developer's Guide Release 12.2  Part No. E22961-15

Overview of Naming Standards ............................................................................................ 38-1
Naming Standards and Definitions........................................................................................38-1
Database Objects................................................................................................................38-1
Form Objects......................................................................................................................38-5
File Standards.................................................................................................................... 38-8
PL/SQL Packages, Procedures and Source Files.................................................................38-9
Reserved Words...............................................................................................................38-10


2)No you won't lose.

[satish]

Thanks erman

[Sri]

Myself tried this and able to view the package after cutover.
 Ran prepare phase
Created package by connecting to run edition
Ran finalize and cutover
Able to view the package in new run edition

Need to understand how this package got synced when we created this package in run edition after prepare phase

[ErmanArslansOracleBlog]

In this example, you don't do EBR related deployment in the database.
So it is normal what you are seeing.

You can think like that, during creating the new db edition, adop takes the current db edition "as is". So your package automatically taken from run to patch edition.
So, when your patch edition becomes the new run edition, your package normally and automatically be in your new run edition.

[Sri]

Thanks erman,

I agree with "during creating the new db edition, adop takes the current db edition "as is".But the package was created after running the prepare phase in run edition(i mean after db edition is prepared).How sync happens in this case?

Thank you

[ErmanArslansOracleBlog]

Afaik, there is no such synch for packages.

Is this package owned by a a non editions-enabled user? I guess not.
I guess this package is noneditioned. that s why it is visible to all editions. (even if it was created after preparing)


INFO:

*A noneditioned object has either a schema object type that is noneditionable in its owner or the NONEDITIONABLE property. An edition cannot have its own copy of a noneditioned object. A noneditioned object is visible to all editions.

*An editions-enabled user could not own a noneditioned object of an editionable type

*package creation syntax:
[ EDITIONABLE | NONEDITIONABLE ]

*"Specifies whether the package is an editioned or noneditioned object "if editioning is enabled for the schema object" type PACKAGE in schema."

[Sri]

Thanks for the update erman.

Finally what i understood was,if we create packages/functions in run edition after prepare phase is completed(i mean after db is prepared),you will loose those packages after cutover.Please correct me if this is wrong

Thank you

[ErmanArslansOracleBlog]

If you are that much curios about it, why dont you test? and update?

[Sri]

Hi Erman,

I have tested in 2 instances,but behaving differently

In our test instance 1
=============
Ran prepare phase and created packages in run edition
able to view them in run edition
not able to view in patch edition

Test instance 2
==========
Ran prepare phase and created packages in run edition
able to view them in run edition
able to view in patch edition as well but with invalid status and actual='N'

RUN
===

SQL> select OBJECT_NAME,OBJECT_TYPE,ACTUAL,STATUS,CTIME,MTIME from ad_objects where OBJECT_NAME='TESTPKG';

OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE        A STATUS  CTIME              MTIME
------------------ - ------- ------------------ ------------------
TESTPKG
PACKAGE BODY       Y VALID   20-OCT-17          20-OCT-17

TESTPKG
PACKAGE            Y VALID   20-OCT-17          20-OCT-17


Patch
===
SQL> select OBJECT_NAME,OBJECT_TYPE,ACTUAL,STATUS,CTIME,MTIME from ad_objects where OBJECT_NAME='TESTPKG';

OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE        A STATUS  CTIME              MTIME
------------------ - ------- ------------------ ------------------
TESTPKG
PACKAGE            N INVALID 20-OCT-17          20-OCT-17

TESTPKG
PACKAGE BODY       N INVALID 20-OCT-17          20-OCT-17


please note i am creating package under apps schema
This is very big confusion to me and requested your help

[ErmanArslansOracleBlog]

It can be invalid in patch edition, if the object/objects that it is dependent on, is/are not present in patch edition. So , what you see in your test instance 2 can be normal.

However, in test instance 1, you say, you cannot see the package in patch edition..
May this package already present in test instance 1? I mean before running prepare.. An old object with the same name, maybe?

What are the differences between those 2 instances? They are identical in terms of technology levels (AD and TXK)

[Sri]

Thanks erman,

I could see in test instance1,the same package is created and dropped in patch instance just for testing purpose.

[Sri]

You are right erman,there is one old object with same name.how this will make my query to not return any rows for the package

[Sri]

Hi Erman,

I have done a test and concluded that we will not loose any custom objects even if we create them in run edition(after the db is prepared)

Initially the packages showed as invalid in patch edition but after some time they became valid.Not sure what is the logic behind this

Initially in patch edition

SQL> select object_name,status from ad_objects where object_name=upper('TEST');

OBJECT_NAME
--------------------------------------------------------------------------------
STATUS
-------
TEST
INVALID

TEST
INVALID

Later after some time

SQL> select object_name,status from ad_objects where object_name=upper('TEST');

OBJECT_NAME
--------------------------------------------------------------------------------
STATUS
-------
TEST
VALID

TEST
VALID

Any idea?

Thanks,
sri

[ErmanArslansOracleBlog]

Did you check the reason behind this invalidation?
Did you see the error causing this invalidation?  (by comping them in the patch edition manually?)