While launching R12.2.x installer in RHEL/OEL encountered issue

Error

This is a very common issue when running Oracle EBS 12.2.x Rapid Install (RapidWiz) on newer Linux servers.

[applmgr@proderpappl rapidwiz]$ Exception in thread "main" java.lang.UnsatisfiedLinkError: 
/apps/stage122/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at sun.security.action.LoadLibraryAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
at sun.awt.DebugHelper.<clinit>(Unknown Source)
at java.awt.Component.<clinit>(Unknown Source)
Could not find the main class: oracle.apps.ad.rapidwiz.RIWizard.  Program will exit.

Root Cause

RapidWiz is trying to load the X11 library libXtst.so.6, but the package is not installed on the OS:

libXtst.so.6: cannot open shared object file: No such file or directory

Because the Java GUI libraries cannot load, RapidWiz fails to start:

Could not find the main class: oracle.apps.ad.rapidwiz.RIWizard

Solution
RapidWiz is trying to load a 32-bit library.

If using OL7/OL8 x86_64, install 32-bit compatibility packages:

Step 1: Verify Missing Library
$ locate libXtst.so.6
or
$ find /usr -name "libXtst.so*"
If nothing is returned, install the package.
Step 2: Install Required Package
RHEL/OEL 7
Install below missing two rpms in the same order.

[root@proderpappl ~]# rpm -ivh libXi-1.3-3.el6.i686.rpm
warning: libXi-1.3-3.el6.i686.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Preparing...                ########################################### [100%]
   1:libXi                  ########################################### [100%]

[root@proderpappl ~]# rpm -ivh libXtst-1.0.99.2-3.el6.i686.rpm
warning: libXtst-1.0.99.2-3.el6.i686.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Preparing...                ########################################### [100%]
   1:libXtst                ########################################### [100%]

Verify:
[root@proderpappl ~]# rpm -qa | grep Xtst
[root@proderpappl ~]# ln -s /usr/lib64/libXtst.so.6 /usr/lib/libXtst.so.6

Flexfield View Generation Failure during Oracle EBS Upgradation

In Oracle E-Business Suite, the view MTL_SYSTEM_ITEMS_B_KFV is normally a Key Flexfield View generated automatically by the Application Object Library (FND).

When Oracle cannot generate the actual KFV view successfully, it creates this dummy view instead. This indicates:

• Key Flexfield compilation failed.
• One or more dependent objects are invalid.
• Flexfield definition is corrupted or incomplete.
• APPS schema compilation encountered errors.

Common causes in Oracle EBS

For MTL_SYSTEM_ITEMS_B_KFV, the object is the Inventory Item Key Flexfield (System Items KFF). The upgrade worker or post-upgrade compilation typically fails because of one of the following:

• Invalid Item Flexfield definition.
• Invalid Item Flexfield (MSTK) metadata
• Missing grants/synonyms on underlying tables.
• Invalid APPS packages or dependent objects.
• Failed execution of Flexfield View Generator.
• Incomplete post-upgrade compilation. 
• Failed AutoConfig or AD utilities execution
• During EBS upgrade, KFF views were not regenerated
• Worker failure during the upgrade that was skipped and not fully resolved.

Usually indicates that the Inventory Item Key Flexfield (MSTK) failed to compile during the upgrade or post-upgrade object generation phase. Oracle EBS generates these KFV views automatically from the flexfield metadata; when generation fails, Oracle replaces the intended view with this placeholder.

Upgrade-specific logs to inspect

For 12.2.x, the actual ORA error is usually in:

• adwork*.log
• u*.log worker logs
• adadmin compile logs
• Flexfield generation logs (FNDFFMDC/FDFVGN related)

The placeholder view itself does not contain the root cause; the worker log contains the actual ORA- error.

Note: The relevant adworkxxx.log snippet, I can identify the exact root cause and tell you whether it is a flexfield metadata issue, invalid package issue, or a known 12.2.x upgrade problem like this.

CREATE OR REPLACE FORCE VIEW APPS.MTL_SYSTEM_ITEMS_B_KFV
(
VIEW_HAS_FAILED_CHECK_LOG_FILE
)
AS
SELECT 'View generation has failed. Check log file for error messages'
VIEW_HAS_FAILED_CHECK_LOG_FILE
FROM SYS.DUAL;

Verify the issue

Check the current view definition:

SELECT text
FROM dba_views
WHERE owner='APPS'
AND view_name='MTL_SYSTEM_ITEMS_B_KFV';

Check object status:

SELECT owner,
       object_name,
       object_type,
       status
FROM dba_objects
WHERE object_name='MTL_SYSTEM_ITEMS_B_KFV';

Check errors

SELECT line,
       position,
       text
FROM dba_errors
WHERE owner='APPS'
AND name='MTL_SYSTEM_ITEMS_B_KFV'
ORDER BY sequence;

Find invalid flexfield views / Verify Item Flexfield (MSTK)
select application_table_name,
       id_flex_code,
       concatenated_segs_view_name
from applsys.fnd_id_flexs
where concatenated_segs_view_name is not null;

Regenerate the Key Flexfield View

From EBS responsibility:

System Administrator
→ Application
→ Flexfield
→ Key
→ Segments

Query:

Application : Inventory
Flexfield Title : System Items

Then:

Compile

or use concurrent program:

Compile Key Flexfield Segments

Recompile invalid objects / Mandatory post-upgrade checks for 12.2.x

EXEC UTL_RECOMP.RECOMP_SERIAL();

or

@?/rdbms/admin/utlrp.sql

For Oracle EBS 12.2.x

If this occurred after clone, patching, or upgrade:

1. Run AutoConfig on both tiers.
2. Run adadmin → Compile APPS schema.
3. Run "Compile Key Flexfield Segments".
4. Verify that MTL_SYSTEM_ITEMS_B_KFV gets recreated with the actual item flexfield columns rather than the single message column.

                                                                     OR

Create MTL_SYSTEM_ITEMS_B_KFV view from MTL_SYSTEM_ITEMS_B table.