Syed Raheel – Oracle Core & EBS Apps DBA

ISSUE:

While migrating one of my client’s Core Oracle Database from an on-premises environment to Google Cloud VM Instance. I encountered an issue while transferring files via SCP from the source Linux server to the target and was unable to connect to Google Cloud VM’s Linux terminal with password using SSH?

ERROR:

[oraprd@core-db-prd ~]$ scp abc oradev@155.199.299.187:/u01/core_db/db/
The authenticity of host ‘155.199.299.187 (155.199.299.187)’ can’t be established.
ECDSA key fingerprint is SHA256:weCNN1YK6jubMLYRfRs2QVhJ5wPNZc7G8SWp/J+0tJ0.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added ‘155.199.299.187’ (ECDSA) to the list of known hosts.
oraprd@155.199.299.187: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
lost connection
[oraprd@core-db-prd ~]$

SOLUTION:

Steps to Transfer a Folder or File Between GCP VMs

1. Enable Password Authentication on the Target DR Server
   • Open the SSH configuration file:
     vi /etc/ssh/sshd_config
   • Update the following line:
     From: PasswordAuthentication no
     To: PasswordAuthentication yes
   • Restart the SSH service:
     systemctl restart sshd
   • Verify the SSH service status:
     systemctl status sshd
2. Transfer Files
   • Use a secure copy command (scp) to transfer the folder or file from the source (Prod Server) to the target (DR Server). You will be prompted to enter the password.
3. Revert Password Authentication Setting on the Target DR Server
   • Edit the SSH configuration file again:
     vi /etc/ssh/sshd_config
   • Change the line back:
     From: PasswordAuthentication yes
     To: PasswordAuthentication no
   • Restart the SSH service:
     systemctl restart sshd
   • Verify the SSH service status:
     systemctl status sshd

IMPORTANT ! : Always ensure you revert the PasswordAuthentication setting after the transfer to maintain server security.

ISSUE:

While running perl adcfgclone.pl dbTechStack, Cloning EBS integerated 19c Database TechStack Fails on supported OS Check with Red Hat Linux 8.10

CAUSE:

19c does not contain Pre-req checks specific to Oracle Linux 8 / Red Hat Linux 8.10
Silent Installer will fail with below Error,as there are no Pre-req checks specific to Linux 8.

SHOW STOPPER ERROR:

[WARNING] [INS-08101] Unexpected error while executing the action at state:’supportedOSCheck’
CAUSE: No additional information available.
ACTION: Contact Oracle Support Services or refer to the software manual.
SUMMARY:
– java.lang.NullPointerException

SOLUTION:

Hence,there is a need to direct the Installer to assume the installed OS to be OL 7 & perform related checks.
Therefore,the below Variable needs to be set,prior to launching Installer-

export CV_ASSUME_DISTID=OEL7.8

NOTE: As per Oracle Pre-req check file for OL/RHEL 8 is provided by 19c PSU 19.6 + but I faced this same issue in 19.22 still !

ISSUE:

After Adcfgclone appsTier for a newly cloned ebs 12.2.13 environment from an SSL-enabled ebs precloned stage backup prevents me from logging in to non-SSL EBS login URL, despite it was completed 100% successfully without any error.

CAUSE:

EBS Context file variable s_enable_sslterminator was empty and was required to be changed as shown below:

It was discovered that the EBS App Context file was having below entry only and
Even after changing the required parameters in the context file, Switching all https to http did not disable SSL and the URL still rerouted to https.

From – >>> http://ebsclone.aot.sa:8010/OA_HTML/AppsLogin
Redirecting to –>> https://ebsclone.aot.sa:4443/OA_HTML/AppsLocalLogin.jsp

SOLUTION:

The ssl_terminator variable value in the context value tags needs to be included as shown below:

From:
<sslterminator oa_var=”s_enable_sslterminator”/>
to
<sslterminator oa_var=”<s_enable_terminator”>#</sslterminator>

After updating Context file, stopped EBS App Services, run autoconfig and restart the App Services Resolved the NON SSL URL redirection.

—————————————

Official interrelated Oracle EBS SSL Documents:
Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID 1367293.1)
How to Completely Disable the SSL Listener for E-Business Suite R12.2 Using Fusion Middleware Control (Doc ID 2203482.1)03482.1)

Issue faced: Sudden Power shutdown of EBS 12.2 Application Server / Machine

cd $ADMIN_SCRIPTS_HOME
./adapcctl.sh status
Noticed that the http service shows STOP

SOLUTION:

cd /u01/ebiz_APRIL_2018/fs1/FMW_Home/webtier/instances/web_GEAPROD_OHS1/config/OPMN/opmn/states

ls -lrta

-rw-r—–. 1 applprod dba 14 Oct 26 10:58 .locale
-rw-r—–. 1 applprod dba 579 Oct 26 10:59 p1505039354
-rw-r—–. 1 applprod dba 20 Oct 26 11:00 .opmndat

rename this file “p1505039354” and started opmn and adapcctl
mv p1505039354 XX_OFF_p1505039354

ls -lrt
-rw-r—–. 1 applprod dba 578 Oct 26 10:53 XX_OFF_p1505039354

cd $ADMIN_SCRIPTS_HOME
./adapcctl.sh start

Symptoms/Problem Details :

Unable to connect apps user from a Recently cloned and EBS RUP 12.2.12 applied Application node
sqlplus apps/*****
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.[oracle@clone admin]$ sqlplus apps/****
SQL*Plus: Release 10.1.0.5.0 – Production on Mon Sep 2 11:25:55 2024
Copyright (c) 1982, 2005, Oracle.  All rights reserved.

ERROR:

ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

================================
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:53:30 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>  Select name from v$active_services;
NAME
—————————————————————-
cdbclone
cdbcloneXDB
SYS$BACKGROUND
SYS$USERS
clone_ebs_patch
clone
7 rows selected.
SQL> exit
ebs_<PDB_SID> found missing in the above result
==================
root cause identified as below:
service name :      ebs_<PDB_SID> was not up and running
NOTE:  ebs_clone  :  is the service name in our case
====================

SOLUTION:

========

1. open a linux terminal
2. Source CDB env
Our pdb sid is: clone
3. export ORACLE_PDB_SID=clone     ( set the PDB env temporarily) 
4-a. sqlplus / as sysdba
4-b. Start the PDB service – ebs_clone
BEGIN
DBMS_SERVICE.START_SERVICE(
service_name => ‘ebs_clone’
);
END;
/
5. connect EBS node, source run fs environment and test now
sqlplus apps/*** OR sqlplus apps/***
connected to apps user successfully now.
===================================
Recorded session below:
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=clone   (Having sourced CDB env)[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:52:49 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>
BEGIN
DBMS_SERVICE.START_SERVICE(
service_name => ‘ebs_clone’
);
END;
/SQL>   2    3    4    5    6
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
[oracle@clone clone_clone]$
===================================
Now Make sure to save the PDB State with above ebs_clone service configured and running.
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=clone
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:54:12 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL> alter pluggable database “clone” save state;
Pluggable database altered.
SQL>
SQL>
================
Verify the service ebs_clone is now coming as active and running.
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=””
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:53:30 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>  Select name from v$active_services;
NAME
——————-
cdbclone
ebs_clone   <<<— service ebs_clone is now coming as active and running.
cdbcloneXDB
SYS$BACKGROUND
SYS$USERS
clone_ebs_patch
clone
7 rows selected.
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
[oracle@clone clone_clone]$
======================================

ISSUE:

In this Blog we are going to learn about How To Find a Particular Database Session ID From the SQLID.
One of my customer informed me I have query running since 10 hours and He
already confirmed with Business user that this query session is safe to be
terminated.

Here we will not discuss about invetigating if that is really applicable to
be terminated

Instead this is a just to share the method on:

GOAL: How to find particular Database session ID from the SQLID we could
see from Oracle 19c Enterprise Manager Database Express console

Note that we could not see the session id from same console.

SOLUTION:

1. select * from V$SESSION where SQL_ID = ‘7upkztdrajyay’

better to see the detailed row data returned from above select statement.

then check the sid in below sql which will generate kill statement to be run
from database superuser account ( sysdba )

2. select ‘alter system kill session ‘||””||
   vs.sid||’,’||vs.serial#||””|| ‘ immediate;’ from v$session vs, v$process
   vp where vs.paddr = vp.addr and vs.sid in ();

OR merge both queries for one shot result

select ‘alter system kill session ‘||”|| vs.sid ||’,’ || vs.serial# || ” || ‘ immediate;’ from v$session vs, v$process vp where vs.paddr=vp.addr and vs.sid in (select sid from v$session where sql_id =’7upkztdrajyay’);

sqlplus / as sysdba

SQL> ALTER SYSTEM KILL SESSION ‘275,44741’ immediate;
SQL> ALTER SYSTEM KILL SESSION ‘279,44749’ immediate;

Done and EM does not show it anymore.

Issue:
While accessing the EBS 12.2.13 Weblogic Console to check health status of EBS managed server the browser redirects to below error as a security restriction:
The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException: [Security:090220]rule 2

Solution:
Connect to application from OS/Linux terminal/putty

Source EBS 12.2 Run File system environment

Last login: Mon Apr 15 09:35:16 2024

E-Business Suite Environment Information

File System Type: SINGLE
RUN File System : /d01/UAT/ebiz/fs1/EBSapps/appl
PATCH File System : NOT APPLICABLE
Non-Editioned File System : /d01/UAT/ebiz/fs_ne

DB Host: ebsuat.erp.com Service/SID: UAT

Sourcing the RUN File System …

[appluat@ebsuat ~]$ echo $FMW_HOME
/d01/UAT/ebiz/fs1/FMW_Home
[appluat@ebsuat ~]$

[appluat@ebsuat ~]$ cd /d01/UAT/ebiz/fs1/FMW_Home
[appluat@ebsuat FMW_Home]$ cd wlserver_10.3/common/bin/
[appluat@ebsuat bin]$
[appluat@ebsuat bin]$ pwd
/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/common/bin
[appluat@ebsuat bin]$ ls -lrt
total 112
-rwxr-x—. 1 appluat dba 31219 Oct 7 2023 wlscontrol.sh
-rwxr-x—. 1 appluat dba 2089 Oct 7 2023 unpack.sh
-rwxr-x—. 1 appluat dba 2276 Oct 7 2023 config.sh
-rwxr-x—. 1 appluat dba 786 Oct 7 2023 wlst.sh
-rwxr-x—. 1 appluat dba 13854 Oct 7 2023 wlsifconfig.sh
-rwxr-x—. 1 appluat dba 3300 Oct 7 2023 upgrade.sh
-rwxr-x—. 1 appluat dba 1450 Oct 7 2023 stopDerby.sh
-rwxr-x—. 1 appluat dba 4090 Oct 7 2023 startManagedWebLogic.sh
-rwxr-x—. 1 appluat dba 4084 Oct 7 2023 startDerby.sh
-rwxr-x—. 1 appluat dba 2581 Oct 7 2023 pack.sh
-rwxr-x—. 1 appluat dba 2124 Oct 7 2023 config_builder.sh
-rwxr-x—. 1 appluat dba 22785 Oct 7 2023 commEnv.sh
-rwxr-x—. 1 appluat dba 1586 Oct 7 2023 setPatchEnv.sh

[appluat@ebsuat bin]$
[appluat@ebsuat bin]$ hostname
[appluat@ebsuat bin]$ ebsuat.erp.com
[appluat@ebsuat bin]$
[appluat@ebsuat bin]$ cat $CONTEXT_FILE | grep s_wls_adminport
[appluat@ebsuat bin]$ cat $CONTEXT_FILE | grep s_wls_adminport
7011
[appluat@ebsuat ~]$

===============================================
$FMW_HOME/common/bin/wlst.sh

[appluat@ebsuat bin]$ ./wlst.sh

CLASSPATH=/d01/UAT/ebiz/fs1/FMW_Home/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/util/jdk64/lib/tools.jar:/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic_sp.jar:/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/d01/UAT/ebiz/fs1/FMW_Home/modules/features/weblogic.server.modules_10.3.6.0.jar:/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/server/lib/webservices.jar:/d01/UAT/ebiz/fs1/FMW_Home/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/d01/UAT/ebiz/fs1/FMW_Home/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/util/jdk32/lib/dt.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/util/jdk32/lib/tools.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/util/jdk32/jre/lib/rt.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/shared-libs/ebs-3rdparty/WEB-INF/lib/ebs3rdpartyManifest.jar:/d01/UAT/ebiz/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-fmw/WEB-INF/lib/ebsFMWManifest.jar:/d01/UAT/ebiz/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/d01/UAT/ebiz/fs1/FMW_Home/oracle_common/modules/oracle.uix_11.1.1/uix2.jar:/d01/UAT/ebiz/fs1/EBSapps/comn/java/classes:/d01/UAT/ebiz/fs1/EBSapps/10.1.2/forms/java:/d01/UAT/ebiz/fs1/EBSapps/10.1.2/forms/java/frmall.jar:/d01/UAT/ebiz/fs1/EBSapps/10.1.2/jlib/ewt3.jar:/d01/UAT/ebiz/fs1/EBSapps/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-INF/lib/frmsrv.jar:/d01/UAT/ebiz/fs1/FMW_Home/utils/config/10.3/config-launch.jar::/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbynet.jar:/d01/PROD/ebiz/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbyclient.jar:/d01/UAT/ebiz/fs1/FMW_Home/wlserver_10.3/common/derby/lib/derbytools.jar::

Initializing WebLogic Scripting Tool (WLST) …

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands
wls:/offline>

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

You will be arrived to this Prompt –> wls:/offline>

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

Use the respective values from the commands: hostname and grep s_wls_adminport above and below

wls:/offline> connect(“weblogic”,”wlscslpwd”,”ebsuat.erp.com:7011″)

Connecting to t3://ebsuat.erp.com:7011 with userid weblogic …
Successfully connected to Admin Server ‘AdminServer’ that belongs to domain ‘EBS_domain’.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or Admin port should be used instead

wls:/EBS_domain/serverConfig> x=ls(‘Servers’,returnMap=’true’)
dr– AdminServer
dr– forms-c4ws_server1
dr– forms_server1
dr– oacore_server1
dr– oafm_server1

wls:/EBS_domain/serverConfig>

=======================================================
wls:/EBS_domain/serverConfig> x
[AdminServer, forms-c4ws_server1, forms_server1, oacore_server1, oafm_server1]
wls:/EBS_domain/serverConfig>

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

wls:/EBS_domain/serverConfig> for i in x: state(i,’Server’)
…
Current state of ‘AdminServer’ : RUNNING
Current state of ‘forms-c4ws_server1’ : SHUTDOWN
Current state of ‘forms_server1’ : RUNNING
Current state of ‘oacore_server1’ : RUNNING
Current state of ‘oafm_server1’ : RUNNING
wls:/EBS_domain/serverConfig>
wls:/EBS_domain/serverConfig>
…
wls:/EBS_domain/serverConfig> exit

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

Environment: Oracle EBS Release that is 12.2.13 with 19c that is 19.22 which is Running on Red Hat Enterprise Linux release 8.9 (Ootpa)

Issue:

After Applying :

1. R12.AD.C.delta.15 -> 34695811
2. R12.TXK.C.delta.15 -> 34785677
3. Oracle E-Business Suite 12.2.13 Release Update Pack -> 34776655
   
   We started facing problem i.e Concurrent Request Output and Log output displays Blank Page in the Browser.

SOLUTION:

Make sure to shutdown EBS Services including Weblogic

Then Run the following commands to unzip the container and WLS patch respectively and then Apply below Weblogic Server Patch ( for OL8/RHEL8 customers only ):

1. cd /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/cache_dir/

2-a. unzip -o /u01/EBS_UPDATE_12_2_13/CONC_LOG_NO_OUTPUT/p32931976_R12_GENERIC.zip
2-b. unzip -o /u01/EBS_UPDATE_12_2_13/CONC_LOG_NO_OUTPUT/p31090393_1036_Linux-x86-64.zip —-> EG54.jar delivered by this patch is actually going to fix.

[appluat@ebsappuat CONC_LOG_NO_OUTPUT]$ ls -lrt
total 213624
-rw-r–r–. 1 appluat dba 196680280 Dec 9 2020 patch-catalog_27387.xml
-rw-r–r–. 1 appluat dba 449 Dec 9 2020 README.txt
-rw-r–r–. 1 appluat dba 4088 Dec 9 2020 EG54.jar
-rw-r–r–. 1 appluat dba 673 May 27 2021 Readme.txt
-rw-r–r–. 1 appluat dba 11081624 May 27 2021 p31090393_1036_Linux-x86-64.zip
-rw-r–r–. 1 appluat dba 10970736 Feb 21 16:09 p32931976_R12_GENERIC.zip
[appluat@ebsappuat CONC_LOG_NO_OUTPUT]$

3. cd /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu

. /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/bsu.sh -prod_dir=/u01/8005_uat_app/ebiz/fs1/FMW_Home/wlserver_10.3/ -patch_download_dir=/u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/cache_dir/ -patchlist=EG54 -verbose -install >> /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/cache_dir/Apply_WLS_EG54_1.log

4. cat /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/cache_dir/Apply_WLS_EG54_1.log

Checking for conflicts..
No conflict(s) detected

Starting installation of Patch ID: EG54
Installing /u01/8005_uat_app/ebiz/fs1/FMW_Home/utils/bsu/cache_dir/EG54.jar
Backing up /u01/8005_uat_app/ebiz/fs1/FMW_Home/wlserver_10.3/server/native/linux/x86_64/libwlenv.so into /u01/8005_uat_app/ebiz/fs1/FMW_Home/patch_wls1036/backup/backup.jar
Extracting /u01/8005_uat_app/ebiz/fs1/FMW_Home/wlserver_10.3/server/native/linux/x86_64/libwlenv.so
Result: Success <<<<<<— Successfully Applied

Issue resolved after this patch.

OS level error while starting WebLogic Admin adadminsrvctl.sh service in EBS 12.2 on Redhat and or Oracle Linux 8.9 :

You are running adadminsrvctl.sh version 120.10.12020000.11

Starting WLS Admin Server…
Refer /u01/8005_uat_app/ebiz/fs1/inst/apps/PREUPG_ebsappuat/logs/appl/admin/log/adadminsrvctl.txt for details

AdminServer logs are located at /u01/8005_uat_app/ebiz/fs1/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs

adadminsrvctl.sh: exiting with status 0

adadminsrvctl.sh: check the logfile /u01/8005_uat_app/ebiz/fs1/inst/apps/PREUPG_ebsappuat/logs/appl/admin/log/adadminsrvctl.txt for more information …

.end std out.

sh: scl: line 1: syntax error: unexpected end of file
sh: error importing function definition for scl’ sh: ml: line 1: syntax error: unexpected end of file sh: error importing function definition forml’
sh: switchml: line 1: syntax error: unexpected end of file
sh: error importing function definition for switchml’ sh: which: line 1: syntax error: unexpected end of file sh: error importing function definition forwhich’
sh: ml: line 1: syntax error: unexpected end of file
sh: error importing function definition for ml’ sh: _module_raw: line 1: syntax error: unexpected end of file sh: error importing function definition for_module_raw’
sh: scl: line 1: syntax error: unexpected end of file

.end err out.

To solve the error while starting weblogic admin server, follow the given below

Solution:

1. vi .bash_profile of your EBS Application OS user
   unset which
   unset scl
2. Login via root user and rename below file :
3. mv /etc/profile.d/modules.sh /etc/profile.d/modules.sh.bkup
4. Take a fresh putty session on Linux
   now Log out, log back in, and set the application environment.

Goal:

Extraction of EBS 12.1.x or EBS 12.2.x Workflow Mailer logs having Error, Exception or UNEXPECTED Keywords in your target logfiles.

By following the given below steps you will easily extract EBS 12.1.x or EBS 12.2.x Workflow Mailer logs having Error, Exception or UNEXPECTED Keywords in your target logfiles.

Steps:

1. Source EBS Run file system/
2. cd $APPLCSF/logs
3. Generate the subject logs with the following commands:

grep “:ERROR:” $APPLCSF/$APPLLOG/FNDCPGSC*.txt > WFMailer_ERRORS.log

grep “Exception:” $APPLCSF/$APPLLOG/FNDCPGSC*.txt > WFMailer_EXCEPTIONS.log

grep “:UNEXPECTED:” $APPLCSF/$APPLLOG/FNDCPGSC*.txt > WFMailer_UNEXPECTED.log