EBS 12.2.10 Upgrade (Patch 30399999) error

 While applying EBS 12.2.10 patch 30399999 got the below error.

ATTENTION: All workers either have failed or are waiting:

FAILED: file fnd_web_resource.xdf on worker 1.

FAILED: file fnd_web_product_family.xdf on worker 4.

FAILED: file fnd_web_used_resource.xdf on worker 5.

FAILED: file fnd_web_product_family_tl.xdf on worker 7.

FAILED: file fnd_web_application.xdf on worker 8.

Fix:

Login to sqlplus as apps user and execute below :

exec AD_ZD_SEED.UPGRADE('FND_WEB_PRODUCT_FAMILY');

exec AD_ZD_SEED.UPGRADE('FND_WEB_APPLICATION');

exec AD_ZD_SEED.UPGRADE('FND_WEB_RESOURCE');

exec AD_ZD_SEED.UPGRADE('FND_WEB_PRODUCT_FAMILY_TL');

exec AD_ZD_SEED.UPGRADE('FND_WEB_USED_RESOURCE');

Once you applied the fix, restart all failed workers and the patch got completed successfully. 

How to check online patching is enabled from backend ?

 If you wanted to check online patching is enabled or not from backend, run the below query as apps user.

sqlplus apps/apps

SQL> select decode(editions_enabled, 'Y','Yes','No') "Online Patching Enabled?"

from fnd_oracle_userid au, dba_users du

where au.oracle_username = du.username and au.read_only_flag = 'U';  

Onl

---

Yes

DB Startup issue after memory change in the server level

Faced an issue after changing the DB memory parameters (SGA and PGA) and got the below error while startup.

ORA-27106: System Pages Not Available To Allocate Memory

Issue: Found that the "USE_LARGE_PAGES" setting to "ONLY"

Fix: Parameter USE_LARGE_PAGES set to "TRUE" and started database, DB came up. 

How to check who logged in Oracle Apps(EBS) Front End ?

 It is very common for DBA to check who logged into EBS application in order to take application down for some maintenance ... etc and make sure the system is idle.

Here is the query to see who is there on the system from backend, connect to database as APPS user and run the query.

I ran this query to see who logged in last one day, based on your requirement you can change it for hours as well.

 col user_name for a40

 select USER_NAME, to_char(LAST_LOGON_DATE, 'DD-MON-YYYY HH24:MI:SS') from fnd_user where last_logon_date > sysdate -1 order by USER_NAME;

USER_NAME        TO_CHAR(LAST_LOGON_DATE,'D

-----------      --------------------------

ABC.DEF          21-JUN-2021 09:48:28

GHI.JKL          21-JUN-2021 08:51:31

MNO.PQR          21-JUN-2021 10:18:14

Workflow Override Email Address

It is very common requirement to stop workflow notifications going out of the system, particularly from Development instances and Test instances. Oracle have given a functionality “workflow override email address” to achieve this requirement.

In many companies this task is done by Database Administrators (DBA) but incase you need to do it yourself you follow the below steps.  There are two ways to setup this: 

1. Login to Oracle Apps preferably with a user who is "Workflow System Administrator".

Navigate to “Workflow Administrator Web Applications” Responsibility
Expand "Oracle Applications Manager"

Click "Workflow Manager"

Click "Service Components"

Click “Workflow Notification Mailer”

Click "Set Override Address"

Once you provide the email address you will receive a verification code for the first time which you need to enter it back in the above page to complete the process. Verification field will be enabled after you provide the email address.
2.  From backend, connect to the database using apps user and run below update statement.

update fnd_svc_comp_param_valsset    parameter_value = '<email address>'where  parameter_value = 'NONE'and    parameter_id =( select parameter_idfrom   fnd_svc_comp_params_tlwhere  display_name = 'Test Address');
commit;