Relink After Platform Migration Fails With Error: wrong ELF Machine Type: EM_386

APPLIES TO:

Oracle Applications DBA - Version 12.2 and later
Information in this document applies to any platform.

SYMPTOMS

After Platform migration, relink is failing with the following error:

wrong ELF machine type: EM_386

/u01/oracle/CLONE/fs1/EBSapps/appl/po/12.0.0/lib/libpo.a(xitpox.o): wrong ELF machine type: EM_386
ld: warning: file
/u01/oracle/CLONE/fs1/EBSapps/appl/gl/12.0.0/lib/libgl.a(xitsqlgl.o): wrong ELF machine type: EM_386
ld: warning: file
/u01/oracle/CLONE/fs1/EBSapps/appl/alr/12.0.0/lib/libalr.a(xitalr.o): wrong ELF machine type: EM_386
ld: fatal: file /u01/oracle/CLONE/fs1/EBSapps/appl/alr/12.0.0/lib/alstub.o: wrong ELF machine type: EM_386
*** Error code 1
make: Fatal error: Command failed for target

SOLUTION

To implement the solution, execute the following steps:

1. Run Adadmin > Maintain Snapshots Information at the source;

2. Regenerate the Manifest File for the source environment;

3. Upload it and generate the Customer Specific Patch;

4. Remove all the *.a and *.o files from the Product tops at the target using the following syntax:

  rm -f $APPL_TOP/*/12.0.0/lib/*.a
  rm -f $APPL_TOP/*/12.0.0/lib/*.o

  - rename the following log files:

  adrelink.log

  adlibout.log

  adlibin.log

  adpatch.log

5. Apply the new customer specific patch generated on step 3.
6. Retest the issue.
7. Migrate the solution as appropriate to other environments.