Oracle Forms: Newly Created Runtime Process Has Terminated Abnormally

After applying a Critical Patch Update (CPU) or a specific bundle patch to an Oracle Forms 12c environment, you might find that the application fails to launch.

This is a "post-patching headache" in the Oracle Middleware world. The undefined symbol: naesha512_compare_checksums error specifically points to a library mismatch—where the frmweb executable is looking for a function in the shared libraries that it can’t find.

When checking the formsapp-diagnostic.log, you encounter the following frustrating error:

==> /u01/oracle/middleware/user_projects/domains/fmw_forms_domain/servers/WLS_FORMS/logs/formsapp-diagnostic.log <==
[WLS_FORMS] [ERROR] [FRM-93546] [oracle.forms.servlet] [tid: 50] [userId: <anonymous>] [ecid: 006IXBXufKWDScX_Ptt1id001SJJ00000F,0:1] [APP: formsapp#12.2.1] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FORMS_SESSION_ID: WLS_FORMS.formsapp.7] [SRC_CLASS: oracle.forms.servlet.RunformProcess] [SRC_METHOD: getPidAndPort] external message from runtime process: /u01/oracle/middleware/bin/frmweb: symbol lookup error: /u01/oracle/middleware/bin/frmweb: undefined symbol: naesha512_compare_checksums
[WLS_FORMS] [ERROR] [FRM-93552] [oracle.forms.servlet] [tid: 50] [userId: <anonymous>] [ecid: 006IXBXufKWDScX_Ptt1id001SJJ00000F,0:1] [APP: formsapp#12.2.1] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FORMS_SESSION_ID: WLS_FORMS.formsapp.7] [SRC_CLASS: oracle.forms.servlet.BaseServlet] [SRC_METHOD: logConnectionException] cannot connect to runtime process:  Newly created runtime process has terminated abnormally.

The Solution: Manual Relinking

While most patches attempt to relink automatically, environment variables or locked files can cause this step to fail. To fix this, you must manually relink the Forms executables.

Step 1: Preparation

Before starting, ensure all services utilizing the Forms executables are completely shut down. This includes:

• The AdminServer
• The WLS_FORMS Managed Server
• The Node Manager
• The HTTP Server (OHS)

Step 2: Set Your Environment

Ensure your $ORACLE_HOME is pointing to the correct Middleware home for Forms

export ORACLE_HOME=<FORMS HOME>
cd   $ORACLE_HOME/rdbms/lib

Step 3: Execute the Relink Commands

Run the following commands in sequence. These use the Oracle make utilities to rebuild the links between the executables and the shared libraries.

1. Relink RDBMS Client Libraries:

cd $ORACLE_HOME/procbuilder/lib
make -f ins_rdbms.mk client_sharedlib

2. Relink Procbuilder and dejvm Components:

cd $ORACLE_HOME/procbuilder/lib
make -f ins_procbuilder.mk sharedlibs dejvm_install

3. Relink Forms Executables: This is the most critical step for fixing the frmweb error.

make -f ins_procbuilder.mk sharedlibs dejvm_install
cd $ORACLE_HOME/forms/lib
make -f ins_forms.mk sharedlib frmopmn_wrp_install frmctrl_install frmweb_install frmcmpb_install frmcmp_install frmbld_install

Step 4: Verification and Restart

Once the make commands finish without errors, restart your stack:

1. Start Node Manager and Admin Server.
2. Start the WLS_FORMS Managed Server.
3. Test the application URL.

Always check the patch README file. While these steps are standard, some specific security patches may require additional flags or specific library paths to be set during the relinking process.