The system has encountered an error when servicing the request, Please try again. If the error persists, please contact the system administrator.

Please contact the system administrator

Error: While accessing the EBS application getting below error while all the application tier services are up and running, Listener is active and Database is up.

Cause:

Java process is running still the application tier services are down. Shutdown all the application Tier services and check.

Solution:

Shudown all the application Tier services and check whether java service is running or not

[applvis@test ~]$ netstat -ntpl|grep java(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)tcp6       0      0 172.16.10.110:12425     :::*   LISTEN      8840    java

[applvis@test ~]$ netstat -ntpl|grep 12425(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)tcp6       0      0 172.16.10.110:12425     :::* LISTEN      8840/    java

[applvis@test ~]$ ps -ef|grep 8840applvis   8840     1  0 08:14 ?        00:00:34 /backups/appsvision/fs1/EBSapps/comn/util/jdk64/bin/java -DCLIENT_PROCESSID=8840 -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts= -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -Ddbcfile=/backups/appsvision/fs1/inst/apps/VIS_test/appl/fnd/12.0.0/secure/VIS.dbc -Dcpid=2729529 -Dconc_queue_id=31528 -Dqueue_appl_id=0 -Dlogfile=/backups/appsvision/fs_ne/inst/VIS_test/logs/appl/conc/log/IEMDPDEV2729529.txt -DLONG_RUNNING_JVM=true -DEBS_HOSTNAME=test -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.iem.emta.gsm.IEMDPCARTapplvis  27246 27063  0 13:50 pts/1    00:00:00 grep --color=auto 8840You have new mail in /var/spool/mail/applvis

[applvis@test ~]$ kill -9 8840

[applvis@test ~]$ ps -ef|grep 8840
applvis  27256 27063  0 13:51 pts/1    00:00:00 grep --color=auto 8840


Now start all the application Tier services (Follw link https://anilbandiodba.blogspot.com/2019/01/how-to-startup-database-and-ebs.html to start and stop services) and Check Application will work fine now.

PL/SQL: numeric or value error: character string buffer too small | package body "APPS.AD_ZD_ADOP" has errors

package body "APPS.AD_ZD_ADOP" has error

Error:

echo $FILE_EDITION

run

echo $TWO_TASK

test

adop phase=apply patches=27949145 apply_mode=downtime

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Validating credentials.

Initializing.

    Run Edition context  : /u01/UAT/fs1/inst/UAT_saniel/appl/admin/UAT_saniel.xml

    Patch file system free space: 89.80 GB

Validating system setup.

    [ERROR]     Failed to execute SQL statement:

 select AD_ZD_ADOP.GET_INVALID_NODES() from dual

    [ERROR]     Error Message:

    [ERROR]     ORA-04063: package body "APPS.AD_ZD_ADOP" has errors (DBD ERROR: OCIStmtExecute)

    [UNEXPECTED]Error determining whether this is a multi-node instance

[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 = 2 (Fail)

Cause :

Package “APPS.AD_ZD_ADOP” is not valid since this package became invalid due to incorrect execution of adgrants.sql script.

Solution:

SQL> alter package APPS.AD_ZD_ADOP compile body;

Warning: Package Body altered with compilation errors.

SQL> show error

Errors for PACKAGE BODY APPS.AD_ZD_ADOP:

LINE/COL ERROR

-------- -----------------------------------------------------------------

2686/3   PL/SQL: Statement ignored

2686/7   PLS-00201: identifier 'SYS.DBMS_METADATA_UTIL' must be declared

SQL> conn / as sysdba

Connected.

SQL> grant execute on DBMS_METADATA_UTIL to apps;

Grant succeeded.

SQL> conn apps

Enter password:

Connected.

SQL> alter package APPS.AD_ZD_ADOP compile body;

Package body altered.

adop phase=apply patches=27949145 apply_mode=downtime

ADOP cycle completed without errors.

Oracle Home inventory is corrupted

While running ETCC on Oracle EBS 12.2 we may get following error if Inventory is Corrupted

Error: 
 Oracle Fusion Middleware (FMW) - oracle_common
=======================================================================
Now examining product Oracle Fusion Middleware (FMW) - oracle_common.
Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
Possible causes are:
   Oracle Home dir. path does not exist in Central Inventory
   Oracle Home is a symbolic link
   Oracle Home inventory is corrupted
LsInventorySession failed: OracleHomeInventory gets null oracleHomeInfo

Cannot confirm bugfixes applied to /u02/ebsappl/PTEST1/fs1/FMW_Home/oracle_common

Inventory could not be checked. Error code: 73.


Exiting.

Solution:

[appltest@test u02]$ cd /u02/ebsappl/PTEST1/fs1/FMW_Home/oracle_common/oui/bin

[appltest@test bin]$ ./attachHome.sh

Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 63999 MB    Passed

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2019-02-21_03-46-38PM. Please wait ...[appltest@test bin]$ The inventory pointer is located at /etc/oraInst.loc

The inventory is located at /u01/oraInventory

'AttachHome' was successful.

How to know the Database Size

We can know the DB size by following queries:

Which version of TXK Delta patch

How can we know Which version of TXK Delta patch we have currently ?

To find which version of ADc Delta and TXKc Delta patches we have query with the following command..

SELECT codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');

In the above screenshot the version of TXK and AD are Delta 8

How to startup Database and EBS application

Oracle EBS Apps R12 Application Startup Notes

• Open Putty with the hostname and enter Database username and password.
• Start the listener

• Open the Database as sysdba 

• Exit the user or take another putty session and enter application username and password.
• After login enter into the Admin Scripts Home and run the adstrtal.sh script with the apps and weblogic credentials.

• Finally You have to get all the services are started. If the status is 1 troubleshoot according to the issue.

How to check if a Patch is applied or not

Oracle EBS R12: Check if the patch is applied or not.