DDL on plsql objects in run edition while patch edition exists-R12.2

[tanweer]

Hello erman,

Please clarify

From Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)

Section 2.2.3: PL/SQL Package

Dynamic DDL Standards

If the running application creates, replaces, or drops package  while a patch edition exists, then the same action must be executed in the patch edition. [minimal]

Our concern is,if we create a view or package in run edition while a patch edition exists,then do we need to create the same view/package in patch edition as well?

Thank you

[tanweer]

hello erman,

further tested and below is the finding

I tried to create a view in run edition while a patch edition exists and here is the status of view from run and patch editions

A simple view-create or replace view XXXANAND as select * from ap_suppliers;

 
from run edition:status is valid

SQL> select OBJECT_NAME,OBJECT_TYPE,STATUS,actual from ad_objects where OBJECT_NAME='ABCANAND';

OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE        STATUS  A
------------------ ------- -
ABCANAND
VIEW               VALID   Y

 

But from patch edition,it is invalid...is this normal?

 

SQL> select OBJECT_NAME,OBJECT_TYPE,STATUS,actual from ad_objects where OBJECT_NAME='ABCANAND';

OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE        STATUS  A
------------------ ------- -
ABCANAND
VIEW               INVALID N

 

Is this the reason,they are asking to create in patch edition as well?please clarify

[ErmanArslansOracleBlog]

What happens when you try to recompile it?

[satish]

Hi erman,

When we tried to compile,it became valid in patch edition.But is it really required to create view in patch edition as well?Or my understanding is wrong

Thank you

[ErmanArslansOracleBlog]

According to the documentation yes. But the documentation about this is very limited.
So, we need to understand why.

Please reproduce the problem and check the reason behind that view being invalid in the patch edition and update me.

In order to understand the error, first (before compiling), execute a query from that view in the patch edition... What do you see ? What is the error reported?