Skip to content

Best Practices for Minimizing Oracle E-Business Suite Release 12.2.n Upgrade Downtime


Best Practices for Minimizing Oracle E-Business Suite Release 12.2.n Upgrade Downtime (Doc ID 1581549.1)

Oracle Linux 7.4 harddisk partition

You have two HDD and need to make two partition with separate during installation














When we’re trying to post the data using REST service after we add some parameter in existing package, we’re getting the error while post


“ISGServiceFault”: {
“Message”: “Error while executing service”,
“Resolution”: “System error, please see service log trace for details”,
“ServiceDetails”: {
“ServiceName”: “XXACE_AP_INV_CMS_SOA_PKG”,
“OperationName”: “xxace_main”,
“InstanceId”: “0”


Log in error while deploy REST service

PLS-00306: wrong number or types of arguments in call to ‘HAS_DEFAULT’
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored


Solution :

Functional Administrator –> clear cache

restart service

undeploy and deploy the service again

Now we can able to post data


EBS 12.2 Only Allow Access to Oracle WebLogic Server Administration Ports from Trusted Hosts

When i am trying to access the weblogic server console from one of client machine, I am getting the below error



Solution :


If you have applied the Critical Patch Update (CPU) released in April 2019, then you can use the context variable s_wls_admin_console_access_nodes to specify the trusted hosts used by administrators that require access to the Oracle WebLogic Server Administration Console and Fusion Middleware Control. Set this context variable to a list of trusted hosts that are allowed to access the consoles using the Oracle WebLogic Server Administration ports.


Run file system, we need to add the client ip or hostname lists in context file

<s_wls_admin_console_access_nodes oa_var=”s_wls_admin_console_access_nodes”>10.0.XX.XX</s_wls_admin_console_access_nodes>

run autoconfig

stop and start service

Now we can able to reach the weblogic server console URL

adop phase=fs_clone

yum install package compilation issue

I created a local repository in redhat 7.6 and then i am trying to install the package but i am getting the dependency issue.

Error :

[root@ebs-117-41 Packages]# yum install glibc-2.17-222.el7.i686
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Resolving Dependencies
–> Running transaction check
—> Package glibc.i686 0:2.17-222.el7 will be installed
–> Processing Dependency: glibc-common = 2.17-222.el7 for package: glibc-2.17-222.el7.i686
–> Processing Dependency: for package: glibc-2.17-222.el7.i686
–> Processing Dependency: for package: glibc-2.17-222.el7.i686
–> Running transaction check
—> Package glibc.i686 0:2.17-222.el7 will be installed
–> Processing Dependency: glibc-common = 2.17-222.el7 for package: glibc-2.17-222.el7.i686
—> Package nss-softokn-freebl.i686 0:3.34.0-2.el7 will be installed
–> Finished Dependency Resolution
Error: Package: glibc-2.17-222.el7.i686 (customrepo)
Requires: glibc-common = 2.17-222.el7
Installed: glibc-common-2.17-260.el7.x86_64 (@anaconda/7.6)
glibc-common = 2.17-260.el7
Available: glibc-common-2.17-222.el7.x86_64 (customrepo)
glibc-common = 2.17-222.el7
You could try using –skip-broken to work around the problem
You could try running: rpm -Va –nofiles –nodigest


Solution :

By mistake I created a local repository with lower version of redhat. so that it’s not compatible when i try to install rpm packages. After i corrected the repository version, it’s okay to install.

In case, If you still continue to see the error after you created the repository with correct version, you need to clean.


yum clean all

then execute

yum repolist

Now We can able to install rpm packages on the server using local repository.




New OA Framework 12.2.9 Bundle 2 Available

Please refer


Extended Support Fee Waiver for Oracle Database 12.1 and 11.2 for Oracle E-Business Suite

refer :


List of users with responsibilities

decode(a.END_DATE,NULL,’ACTIVE’,’INACTIVE’) Status,a.start_date,a.end_date,a.last_logon_date,d.internal_location
FROM apps.fnd_responsibility_vl frv,apps.FND_USER a,apps.FND_USER_RESP_GROUPS_all b,apps. per_all_people_f d,apps.FND_RESPONSIBILITY_TL res,PER_JOBS_VL e,
per_all_assignments_f f
d.person_id=f.person_id and
b.responsibility_id = res.responsibility_id
and a.USER_ID=b.USER_ID and b.RESPONSIBILITY_ID=frv.RESPONSIBILITY_ID and a.employee_id=d.person_id
and sysdate between d.effective_start_date and d.effective_end_Date
and sysdate between nvl(frv.start_date,sysdate) and nvl(frv.end_date,sysdate)
AND f.job_id = e.job_id
group by d.employee_number,a.USER_NAME,frv.responsibility_name, d.full_name,b.START_DATE,b.end_date,decode(a.END_DATE,NULL,’ACTIVE’,’INACTIVE’),
ORDER BY d.full_name

Java webstart at EBS 12.2.9

I upgraded EBS Version from 12.1.3 to 12.2.9. After upgraded, i planned to setup the Java webstart for EBS 12.2.9 version. As such, i review the document (Doc ID 2188898.1), this document clearly explained about how to setup the java webstart on EBS.


There was many patches noted to apply on EBS version for java webstart. But my case, I have already upgraded to latest version. so all the patches are included whichever required.


Section : 4.2.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2

the document noted to apply the patch Patch 25441839 but Patch 26825525 already applied during upgrade activity. so no need to apply the patch 25441839 (Doc ID 2554599.1).

you need to follow further steps for Java webstart setup.

New JRE 1.8.0 & 1.7.0 Certification with EBS Releases 12.2 and 12.1