EBS 12.2 Performace tune doc ids for OPP and CM Reuqests

 

Tuning Output Post Processor (OPP) to Improve Performance (Doc ID 1399454.1)

How To Purge FND_AQ Tables (Doc ID 1156523.1)

Thanks,

Srini

Importent EBS R12.2 doc Id;s

 

Oracle E-Business Suite Release 12.2.10 Readme (Doc ID 2666934.1)

Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c (Doc ID 2552181.1)

Thanks,

Srini

MD5 Checksums for R12.2 Rapid Install Media (Doc ID 1505510.1)

 

---

APPLIES TO: Oracle Applications DBA - Version 12.2 to 12.2.7 [Release 12.2Cloud to 12.2] Information in this document applies to any platform. MAIN CONTENT This document provides a method to check the 12.2 stage for any corruption due to incorrect download of the media from edelivery.oracle.com. You should periodically check this Document 1505510.1 on My Oracle Support for Checksum updates, which are made as required. There is a change log at the end of this document. In This Document This document is divided into the following sections: Section 1: Overview Section 2: Download md5 checksum results from Oracle Section 3: Compare md5 checksums Section 4: Disk overview, to be used when corrupted files are found Change log   Section 1: Overview After staging the Rapid Install software with the buildStage.sh script the md5 checksums for the staged directory structure can be used to validate the software integrity. Do this by running the md5sum program against the stage area using the Oracle-created checksum file. Section 2: Download md5  checksum results from Oracle Download the md5 checksum results from Oracle as posted below into a local file, for example <your platform> md5sum_.txt. The attached files contain the md5 checksum results for every R12.2 release. Download the file corresponding to the used release and platform. The md5 checksum has been created without the startCD as it is often being updated, the checksum for the startCD's can be tested separately. Release 12.2 Checksums currently available: R12.2 - Linux 64-bit (EL5/6) (Based on startCD 46 / Based on startCD 47 / Based on startCD 48 / Based on startCD 49 / Based on startCD 50 / Based on startCD 51) R12.2 - Linux 64-bit (EL7) Based on startCD 50 R12.2 - IBM AIX (Based on startCD 46 / Based on startCD 47 / Based on startCD 48 / Based on startCD 49 / Based on startCD 50 / Based on startCD 51) R12.2 - Solaris Sparc 64-Bit (Based on startCD 46 / Based on startCD 47 / Based on startCD 48 / Based on startCD 49 / Based on startCD 50 / Based on startCD 51) R12.2 - HP_UX Itanium (Based on startCD46 / Based on startCD 47 / Based on startCD 48 / Based on startCD 49 / Based on startCD 50 / Based on startCD 51) R12.2 - Windows 64-Bit (based on startCD 47 / Based on startCD 48 / Based on startCD 49 / Based on startCD 50 / Based on startCD 51) Release 12.2.2 StartCD Checksums: R12.2 startCD - version 12.2.0.51 R12.2 startCD - version 12.2.0.50 R12.2 startCD - version 12.2.0.49 R12.2 startCD - version 12.2.0.48 R12.2 startCD - version 12.2.0.47 R12.2 startCD - Version 12.2.0.46   Section 3: Compare md5 checksums Compare the Stage with the md5sums downloaded from Oracle (md5sum_.txt). There should not be any FAILED entry in the output. If a FAILED entrie was found, then the stage area was not created successfully. The stage have to be re-created for every component indicating differences (FAILED). Note: The following example assumes the stage exists in /u01 for UNIX and Linux, or F:\ for Windows customers. Execute the following example commands to check stage using the the md5 checksums On UNIX/Linux: - Install the md5sum utility for your platform if md5sum is not present on your system. If md5sum is not available from your OS Vendor for your OS version (for example HP 11.0), download and install the coreutils package from gnu.org . $ cd /StageR122 $ md5sum --check md5sum_Linux64.txt > md5sum_result.txt   On Windows: - MKS Toolkit or cygwin needs to be installed to be able to use mdm5sum. F:\> cd StageR122 F:\StageR12> md5sum --check md5sum_Windows.txt > md5sum_result.txt If the checksum commands are not working under cygwin please use the following workaround: - Download and install fastsum - place the md5sum_Windows.txt in the root stage where you will find folders:  EBSInstallMedia TechInstallMedia TechPatches - rename md5sum_Windows.txt to md5sum_Windows.md5 - start fastsum - select file >> verification Wizard - Add file md5sum_Windows.md5 - Click next to start validation   Note: The md5 checksum will validate the entire stage area and may take 10 minutes or more depending on hardware resources and system load. When the md5sum command failed for all lines with error: ": FAILED open or read" try to make it a UNIX file using: dos2unix <checksum file> <checksum file>   Section 4: Disk overview, to be used when corrupted files are found  When a corrupted file is found the following can be used to identify which part needs to be re-downloaded from edelivery. Release 12.2 Disk overview: R12.2 - Linux 64-bit R12.2 - IBM AIX R12.2 - Solaris Sparc 64-Bit R12.2 - HP_UX Itanium R12.2 - Microsoft Windows x64 (64-bit) Section 5: References Document 1320300.1,  Oracle E-Business Suite Release Notes, Release 12.2

 

Error: 'ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found in EBS R12

 

On : 12.2.10 version, Patch Application Issues

Upgrade from R12.1.3 to R12.2.10 - Patch 30399999 Error: ORA-01452

 

When attempting to apply patch 30399999, the following error occurs:

ERROR
-----------------------
SQL: create UNIQUE index "GME"."GME~RESOURCE~TXNS~PK" on "GME"."GME_RESOURCE_TXNS" (POC_TRANS_ID#1) tablespace APPS_TS_TX_IDX storage (initial 128K next 128K) online

ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Apply Patch 30399999.
2. Review AD Worker Log.

The issue is caused by the following:

Per Bug: 34130503, issue relates to code issue after upgrading from R12.1.3 to R12.2.10. Additionally, the below query returns count for duplicate records (Count > 0):

Select count(1) from "GME"."GME_RESOURCE_TXNS" where POC_TRANS_ID#1=-1;

o implement the solution, please execute the following steps:

1. Download and review the readme and pre-requisites for the following patches. Apply them in sequence:

a. Patch 22962971:R12.GME.C
b. Patch 31564811:R12.GME.C

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions:

   GMEVRLBB.pls 120.39.12020000.18
   GMEVRLSB.pls 120.15.12020000.10

   GMERTXN.odf 120.2.12020000.8

You can generate a Diagnostic Apps Check for the Process Manufacturing Process Execution module; see Note: 838707.1 - Diagnostics Apps Check.

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.