16
Apr

Login to internal node gets redirected to external node after adding new DMZ node in EBS R12.2.x

Symptoms:

For some users, login to internal node gets redirected to external node.

 

Cause:

In $IAS_ORACLE_HOME/instances/EBS_web_SID_OHS1/config/OHS/EBS_web_SID/mod_wl_ohs.conf and apps.conf files, the cluster includes the external node external.domain.com.

 

Solution:

 

To fix this issue, make the following changes to the run file system of the internal node:
Remove any reference to external.domain.com from both the files i.e. mod_wl_ohs.conf and apps.conf.

 
Node 1: /u02/oracle/EBSPROD/fs1/FMW_Home/webtier/instances/EBS_web_EBSPROD_OHS1/config/OHS/EBS_web_EBSPROD
 
Node 2: /u02/oracle/EBSPROD/fs1/FMW_Home/webtier/instances/EBS_web_EBSPROD_OHS3/config/OHS/EBS_web_EBSPROD
 
DMZ Node: /u02/oracle/EBSPROD/fs2/FMW_Home/webtier/instances/EBS_web_EBSPROD_OHS2/config/OHS/EBS_web_EBSPROD
 
Read more...

18
Feb

Applying AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2

The latest RUPs while writing this post are R12.AD.C.Delta.10 (Patch 25820806) and R12.TXK.C.Delta.10 (Patch 25828573).

Apply Required Database Patches

 
AD-TXK Delta 10 requires a number of database bug fixes to install and operate correctly.
 
NOTE: Take Central Inventory backups on the database and application tiers.
 
Before you apply the AD and TXK Delta 10 release update packs (RUPs), you must run the latest version (available via Patch 17537119) of the EBS Technology Codelevel Checker (ETCC). Use the command checkDBpatch.sh (on UNIX) or checkDBpatch.cmd (on Windows).

Check the OPatch utility version.

/u01/oracle/product/dbhome1/OPatch/opatch version
OPatch Version: 11.2.0.3.16

OPatch succeeded.

Upgrade to the latest OPatch Utility.

[oracle@ebsdb01 OPatch]$ ./opatch version
OPatch Version: 11.2.0.3.18

OPatch succeeded.

Read more...

24
Jan

After Upgrading From 12.2.0 to 12.2.x Apache Does Not Start And Errors With Could not open configuration file

Error:

/u02/oracle/ERPPROD/fs1/FMW_Home/webtier/ohs/bin/apachectl startssl: execing httpd
 
Killedworker: Syntax error on line 1039 of /u02/oracle/ERPPROD/fs1/FMW_Home/webtier/instances/EBS_web_ERPPROD_OHS1/config/OHS/EBS_web_ERPPROD/httpd.conf: Syntax error on line 115 of /u02/oracle/EBS_web_ERPPROD_OHS1/config/OHS/EBS_web_ERPPROD/ssl.conf: Could not open configuration file
You have new mail in /var/spool/mail/applprod
 

[applprod@erpapp01 ~]$ ls -ltr
/u02/oracle/ERPPROD/fs1/FMW_Home/webtier/instances/EBS_web_ERPPROD_OHS1/OHS/EBS_web_ERPPROD/oracle_apache_ssl.conf: No such file or directory

Cause:

In the runfilesystem xml file the value of variable s_ohs_installed is set to False.
This will stop the configuration file from getting generated.

Hence the file oracle_apache_ssl.conf was not created and the services are not starting.


[applprod@erpapp01 ~]$ grep -i s_ohs_installed $CONTEXT_FILE
false

Read more...

8
Nov

Error occurred while Executing txkADOPValidation script when running fs_clone

While running fs_clone, it fails with the following error:


[applprod@erpapp01 ~]$ adop phase=fs_clone

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Initializing.
Run Edition context : /u01/oracle/ERPPROD/fs1/inst/apps/ERPPROD_erpapp01/appl/admin/ERPPROD_erpapp01.xml
Patch edition context: /u01/oracle/ERPPROD/fs2/inst/apps/ERPPROD_erpapp01/appl/admin/ERPPROD_erpapp01.xml
Patch file system free space: 355.97 GB

Validating system setup.
Node registry is valid.
[WARNING] ETCC: The following required database fixes have not been applied to node dx
12608451
21286665
Refer to My Oracle Support Knowledge Document 1594274.1 for instructions.

Checking for existing adop sessions.
No pending session exists.
Starting new adop session.

===========================================================================
ADOP (C.Delta.8)
Session ID: 3
Node: erpapp01
Phase: fs_clone
Log: /u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/3/20170807_123036/adop.log
===========================================================================
Read more...

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...

Back to Top