EBS 12.2 - On Sourcing Patch FS env, connection to database from Apps Tier is still going to Run edition - when there is no active ADOP cycle
(Doc ID 2956399.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Applications DBA - Version 12.2.3 to 12.2.12 [Release 12.2Cloud to 12.2]Information in this document applies to any platform.
Symptoms
On : 12.2.x, AD Utilities,
When the following conditions meet -
1) There is no active ADOP cycle at the moment. That is ADOP prepare is not run yet (which will create a new Patch edition).
2) From the Primary Application node, source the Patch File System and try to make a sqlplus connection to database from APPS user.
. ./EBSapps.env P
$echo $FILE_EDITION
patch
EXPECTED BEHAVIOUR
=====================
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On the Application Tier node via "applmgr" user and source the Patch FS via -
/EBSapps.env patch
2. Attempt sqlplus connection to the database using -
sqlplus apps/<>
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are able to connect to the Run Edition even after sourcing Patch FS. This will prevent Online Patching tools from
operating correctly, resulting in system corruption.
Changes
Apps schema has been granted 'ADMINISTER DATABASE TRIGGER' privilege and/or 'IMP_FULL_DATABASE' role, either manually or explicitly for some reason by the customer.
Cause
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
Symptoms |
Changes |
Cause |
Solution |