Re-link fails on target "jox_refresh_knlopt ioracle" while applying OJVM PATCH SET UPDATE on Exadata
Issue:
While applying the OJVM patch on Exadata, the patch application fails on relinking.
Error:
OPatch failed: ApplySession failed in system modification phase... 'ApplySession::apply failed: Re-link fails on target "jox_refresh_knlopt ioracle".
OJVM Patch Installation:
Go to the patch directory.
[oracle@exadb01~]$ cd /u01/exadata_patch_apr2016/22738416/Database/11.2.0.4.0/11.2.0.4.160419OJVMPSU/22674697
OPatch Conflict Check
Determine whether any currently installed interim patches conflict with this patch.
[oracle@exadb01 22674697]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/11.2.0.4/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.4.0
Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2016-11-04_13-34-29PM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
Oracle E-Business Suite Forms not opening in Internet Explorer
Issue:
After logging in and clicking on any form, java installation window opens up even though the correct java version is installed on client PC’s.
This issue is seen on all client machines.
Issue occurs for all EBS Users who are using Internet Explorer.
Cause:
Classid is not set properly in $FORMS_WEB_CONFIG_FILE.
EBS looks for classid to launch the form.
Health Check of Oracle E-Business Suite Database
List of tasks to be done as part of the Health Check
- Check database and application availability
- Check status of cluster services
- Monitor space availability in all tablespaces
- Check for errors in Database Alert log files and take appropriate action
- Check Concurrent Managers
- Check /tmp for space constraints
- Check invalid objects and compile if required
- ASM Grid Space Check
- Database and Application Mount points check
- Verify Backups
- Verify Gather Schema Statistics and Purge Concurrent Request and/or Manager Data Concurrent Requests are scheduled and are completing successfully
Oracle E-Business Suite Migration from Linux 5 to Linux 7
Objective:
The objective is to migrate the EBS instance from a server running Linux 5 to a new server running Linux 7.
Environment Details:
EBS R12.1.3, Database 11.2.0.4
Mount points: Database: /ddb02, Application: /dap01
Create Users and Groups on the new server.
[root@ebs01 ~]# groupadd dba
[root@ebs01 ~]# groupadd oinstall
[root@ebs01 ~]# groupadd oper
[root@ebs01 ~]# groupadd asmdba
[root@ebs01 ~]# groupadd asmoper
[root@ebs01 ~]# useradd -g dba -G oinstall,oper,asmdba,asmoper -m oradev
[root@ebs01 ~]# useradd -g dba -G oinstall,oper -m appldev
[root@ebs01 ~]# groups oradev
oradev : dba oinstall oper asmdba asmoper
[root@ebs01 ~]# groups appldev
appldev : dba oinstall oper
Error on libdb Library Starting Oracle EBS Application Services on Linux Platforms
Error :
While starting the application services, Apache services do not start.
Error in the log file:
/dap01/appldev/EBSDEV/apps/tech_st/10.1.3/Apache/Apache/bin/httpd: error while loading shared libraries: libdb-4.3.so: cannot open shared object file: No such file or directory
Cause:
This is caused by having an older Oracle HTTP Server installed on a newer Operating System. For the OPatch issue, Perl is expecting to find the /usr/lib/libdb-3.3.so library, but it is missing.
The following command locates a higher version of the library (for example, /usr/lib/libdb-4.1.so)
/libdb ls -al /usr/lib *.so
Note that the error can be a newer library, depending which is found and used from the operating system. (e.g., libdb-4.2.so, libdb-4.3.so, libdb-4.4.so, etc).
The correct libdb filename to use should depend on output of ldd httpd, for example:
cd $ORACLE_HOME/Apache/Apache/bin
ldd httpd | grep libdb
libdb.so.2 => /usr/lib/libdb.so.2 (0x00868000)
•In this case, libdb.so.2 is expected
•In this case, having libdb-3.3.so will not help