Setup Menus in Admin Panel

DBATalent

In R12.2.4 WARNING: Entry oracle/apps .. (may indicate corrupt metadata or concurrent modification)

Introduction: While running adop phase=prepare, it was failing with the error similar to this below:

WARNING: Entry oracle/apps/per/selfservice/appraisals/server/AssessmentsAMImpl.class in the archive /apps/fs2/EBSapps/comn/java/classes does not have expected size of 23892 bytes (may indicate corrupt metadata or concurrent modification)

ERROR: I/O or zip error while attempting to read entry oracle/apps/per/selfservice/appraisals/server/CompetenceElementsVORowImpl.class in zip file /apps/fs2/EBSapps/comn/java/classes

This error is not only 12.2 specific but also can occur in any release of R12.

Cause:

The main reason of this is the difference in the Java Class files/sizes in metadata and the ones present in the file system. We need to Synchronize the sizes/files in the metadata with the ones actually present in the File System to resolve this issue.\

Solution:

In R12 (12.1.X):

1. Set the enviroment
2. Run the below command as applmgr (or Equivalent) user:

adjava -mx512m oracle.apps.ad.jri.adjcopy -masterArchive $JAVA_TOP -sync -mode APPLY

In R12 (12.2.X):

1. Set the RUN File System enviroment

cd <Base Directory>
. EBSapps.env run
adjava -mx512m oracle.apps.ad.jri.adjcopy -masterArchive $JAVA_TOP -sync -mode APPLY

2. Set the PATCH File System enviroment

cd <Base Directory>
. EBSapps.env patch
adjava -mx512m oracle.apps.ad.jri.adjcopy -masterArchive $JAVA_TOP -sync -mode APPLY

May 7, 2015

2 Responses on In R12.2.4 WARNING: Entry oracle/apps .. (may indicate corrupt metadata or concurrent modification)"

Leave a Message