Introduction: After upgrading our Oracle E-Business Suite environment to AD-TXK Delta 15, we encountered a front-end access issue the application URLs were not opening even though all services were up…
Read MoreWhen running the ADOP fs_clone command during an Oracle E‑Business Suite patch upgrade, you might encounter an error related to a missing PATCH FS CONTEXT FILE in the FND_OAM_CONTEXT_FILES table.…
Read MoreIntroduction: Managing EBS environments effectively requires attention to detail, especially after upgrades like AD-TXK 15. One critical aspect is ensuring password synchronization for seamless ADOP cycles. Understanding the Issue :…
Read MoreIntroduction: Oracle E-Business Suite (EBS) Rapid Clone is a critical tool for creating copies of an EBS environment. However, issues may arise during the cloning process due to system configuration…
Read MoreIn this blog, we will explore the common OACore issues, their potential causes, and step-by-step troubleshooting techniques to resolve them. Whether you’re an Oracle DBA, application administrator, or IT professional,…
Read MoreThe purpose of this blog is to assist DBAs in resolving issues encountered while applying or rolling back OPatch in an Oracle database. , we faced the issue “OPatch Unable…
Read MoreThis blog aims to support DBAs who encounter issues during the EBS application R12.2 ADOP phase=cleanup, specifically when it fails with the ORA-20001 error message: ‘Error while calling ad_zd.cleanupORA-01555: snapshot too old.’ The steps provided here offer guidance in identifying and addressing the challenges associated with the ADOP phase=Cleanup problem. Below Step: Issue: We encountered the following issue during the application of the adpatch ADOP patching cycle when executing the adop phase=cleanup [applmgr@r122 ~]$ adop phase=cleanup Enter the APPS password: Enter the SYSTEM password: Enter the WLSADMIN password: Please wait. Validating credentials… RUN file system context file: /u01/applmgr/UAT_TEST/fs2/inst/apps/UAT_TEST_r122/appl/admin/UAT_TEST_r122.xml PATCH file system context file: /u01/applmgr/UAT_TEST/fs1/inst/apps/UAT_TEST_r122/appl/admin/UAT_TEST_r122.xml ************* Start of session ************* version: 12.2.0 started at: Wed May 24 2021 03:34:53 APPL_TOP is set to /u01/applmgr/UAT_TEST/fs2/EBSapps/appl [STATEMENT] Using 4 workers (Default: 4, Recommended maximum limit: 62) Cleanup is not done in earlier session [START 2021/05/24 03:35:27] adzdoptl.pl run ADOP Session ID: 4 Phase: cleanup Log file: /u01/applmgr/UAT_TEST/fs_ne/EBSapps/log/adop/4/adop_20210524_033421.log [START 2021/05/24 03:35:48] cleanup phase [EVENT] [START 2021/05/24 03:35:52] Performing Cleanup steps [EVENT] [START 2021/05/24 03:35:57] Running CLEANUP ddls in ddl handler table Calling: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/u01/applmgr/UAT_TEST/fs2/EBSapps/appl/admin/UAT_TEST/adalldefaults.txt patchtop=/u01/applmgr/UAT_TEST/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=cleanup.log driver=ucleanup.drv ADPATCH Log directory: /u01/applmgr/UAT_TEST/fs_ne/EBSapps/log/adop/4/cleanup_20210524_033421/UAT_TEST_r122/log [EVENT] [END 2021/05/24 03:39:43] Running CLEANUP ddls in ddl handler table [EVENT] Cleaning up ABORT DDL from DDL Handler Table [START 2021/05/24 03:39:54] Generating All DDL Report [EVENT] Report: /u01/applmgr/UAT_TEST/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDALLDDLS.sql…
Read MoreThis blog is intended for DBA’s who have error while using a database links.Let’s work on a journey to decode, troubleshoot, and over the challenge posed by the ORA-02020 error. Issue: Error While Fetching data against a database link, got below error.ORA-02020: Too Many Database Links In Use Sql>select sysdate from dual@Daatbase_link5; * ERROR at line 1: ORA-02020: too many database links in use CAUSE & SOLUTION: n open_links parameter control, the number of database links each session can use without closing it. n If you access a database link in a session, then the link remains open until you close the session. Check the below parameter: SQL> show parameter open_link NAME TYPE VALUE ———————————— ———– —————————— open_links integer 4 open_links_per_instance integer 4 Here open_links is set to a session can access only 4 open database links in that session.When the open db_link connection reaches the limit(open_links), it throws ORA-02020: too many database links in use. Solution:1 n Close the open db_link connections n Increase the open_links parameter (bounce required) Let’s reproduce this error. SQL> select sysdate from dual@Database_link1; SYSDATE ——— 30-JUL-17 SQL> select sysdate from dual@Database_link2; SYSDATE ——— 30-JUL-17 SQL> select sysdate from dual@Database_link3;…
Read MoreThe purpose of this blog is to assist DBAs encountering ebs database custom table column missing while running adpatching cycle. The steps shared here will help to identify the table…
Read MoreThis blog is intended for DBA’s who have error while running a fsclone phase run patching cycle error, we have solution for fsclone phase error. Issue: We are facing issue…
Read More