11
Dec

APPS.AD_ZD_ADOP Package invalid after applying Database Bundle Patch

Issue:

After applying Exadata or Super Cluster Bundle Patch on the RDBMS HOME of an EBS R12.2 database, the APPS.AD_ZD_ADOP Package becomes invalid and all ADOP sessions fail.

Error:

Check ADOP status:

applprod@ebsapp01:~$ adop -status

Enter the APPS password:

==============================================================
ADOP (C.Delta.7)
Session Id: 55
Command: status
Output: /u01/PROD/fs_ne/EBSapps/log/status_20161115_112514/adzdshowstatus.out
===================================wo============================

File System Synchronization Type: Full
declare
*
ERROR at line 1:
ORA-04063: package body "APPS.AD_ZD_ADOP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.AD_ZD_ADOP"
ORA-06512: at line 6

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 1 (Fail)

=====================

Read more...

13
Nov

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.

Read more...

1
Nov

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.

Download Java

Java version already installed
Read more...

23
Aug

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

Read more...

1
May

ORACLE error 20100 in FDPSTP

Error :

ORACLE error 20100 in FDPSTP
FDPSTP failed due to ORA-20100: ORA-20100: Temporary file creation for FND_FILE failed.
Directory &FILE_DIR is invalid, contact your system administrator.

Action:

Check that the directory is a valid directory with wri06-APR-2016 14:48:29

Cause:

The concurrent program was unable to write to the specified temporary file because the virtual path assigned to the APPLPTMP environment variable is not referenced in the UTL_FILE_DIR
Read more...

Back to Top