ORA-12547: TNS :lost contact when try to connect to Oracle
ERROR: ORA-12547: TNS :lost contact when try to connect to Oracle There could be many reasons for the above error, but one of the common issue is due to incorrect…
Read MoreGet any Apps User Password from Backend
In this steps we can find any user name’s password in oracle apps. STEP 1: login to Database through Command Prompt #sqlplus / as sysdba STEP 2 : Create Function…
Read More11i: “APP-FND-01542” Error When Logging Directly Into Forms Via the f60cgi in 11.5.10
Applies to: Oracle E-Business Suite Technology Stack – Version 11.5.10.0 to 11.5.10.0 [Release 11.5] Information in this document applies to any platform. Checked for relevance on 25-SEP-2013 Goal How to…
Read MoreAdcfgclone AppsTier Failing During Clone Into When Source And Target Are On Same Host
Applies to: Oracle Applications Manager – Version 12.2.4 and later Information in this document applies to any platform. Symptoms E-Business Suite 12.2 Applications Manager, Rapidclone related issues Cloning the applications…
Read MoreORA-01422: Exact Fetch Returns More Than Requested Number Of Rows (Doc ID 2212698.1)
Applies to: Oracle Applications Manager – Version 12.2.4 and later Information in this document applies to any platform. Symptoms On : 12.2.4 version, Rapidclone While running autoconfig the following error…
Read MoreUnable To Login into EBS With SYSADMIN User After Migrating To New Machine
Applies to: Oracle Application Object Library – Version 12.1.1 to 12.1.3 [Release 12.1] Information in this document applies to any platform. Symptoms Unable to login R12 Applications with Sysadmin user…
Read MoreReorganizing FND_LOBS table in Oracle EBS R12.1.3
Reorganizing FND_LOBS table in Oracle EBS R12.1.3 FND_LOBS is usually one of the top 10 table in an EBS environment. It stores all the attachments that have been uploaded to Oracle Applications. There is a LOB field within this table called FILE_DATA, the corresponding LOB segment (e.g., APPLSYS.SYS_LOB000******04$$) is where the actual attachment data is stored, and is usually very large. The size of FND_LOBS table and its LOB_SEGMENT SYS_LOB******$$ was around 3GB and 1.5 TB in our environment. There were over 40 lakhs record in the FND_LOBS table each pertaining to its own Application Module. Our Client had recently decided to migrate the EBS environment to OCI (IAAS). The OC team had decided to follow expdp/impdp to migrate the EBS database from on-prem to cloud. When they tried to perform the export the EBS database they had faced an issue with the FND_LOBS table. They had faced the following error, ORA-31693: Table data object “APPLSYS”.”FND_LOBS” failed to load/unload and is being skipped due to error: ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout ORA-01555: snapshot too old: rollback segment number with name “” too small ORA-22924: snapshot too old This error occurred while the expdp is trying to export the FND_LOBS table. This issue is occurring due to corruption in the FND_LOBS table. Reference – SRDC – ORA-22924 or ORA-1555 on LOB data: Checklist of Evidence to Supply (Doc ID 1682707.1) As suspected there were logical corruptions in the FND_LOBS table and 26 rows were identified as corrupted records in FND_LOBS table by the validation scripts in Doc ID 1682707.1. We had opened a SR with Oracle Support to resolve the corruptions, Oracle Support had suggested to follow action plan mentioned in Doc ID 1950896.1 to remove corruptions. As per Doc ID 1950896.1 we had performed the following, Section a – Identifying and removing logical corruptions Create a temporary dummy table for storing the rowids of the corrupted LOBs. here the dummy table name is “corrupt_lobs”. SQL> create table corrupt_lobs (corrupt_rowid rowid, err_num number); Create this table as a user who has necessary provilege to scan the target table for corruptions. Execute the following PL/SQL block to identify the corrupted rows. Provide the <lob Column name> and <Table name> with the respective LOB column and table name. SQL> declare error_1578 exception; error_1555 exception; error_22922 exception; pragma exception_init(error_1578,-1578); pragma exception_init(error_1555,-1555); pragma exception_init(error_22922,-22922); num number; begin for cursor_lob in (select rowid r, &&lob_column from &table_owner..&table_with_lob) loop begin num := dbms_lob.instr (cursor_lob.&&lob_column, hextoraw (‘889911’)) ;…
Read MoreAdop failed in fs_clone phase “ERROR: Update Moveplan Fail”
Issue: On : 12.2.4 version, ISSUES WITH FUNCTIONALITY OF AD UTILITIES When attempting to run fs_clone after a successful clone the following error occurs. FSCloneApplyAppsTier_08081620.log shows +++++++++++++++++++++++++ configProperty id =…
Read MoreAfter 12.2 upgrade adop failed ORACLE error 6550 in FDPSTP Cause: FDPSTP
Issue: [STATEMENT] This request finished with an error and produced the following completion message: ORACLE error 6550 in FDPSTP Cause: FDPSTP failed due to ORA-06550: line 1, column 18: PLS-00802:…
Read MoreIntegration of IDCS with EBS Failed with “No resources currently available in pool to allocate to applications”
Issue: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool <POOL_NAME> to allocate to applications, please increase the size of the pool and retry.. Cause: This issue is due to leaked…
Read More