FRM-92101: There was a failure in the Forms Server during startup.

After I recently cloned a TEST Instance, I faced the issue while the forms are opening. 

So I decided to check forms log and out files and found the below issue.

So from forms_server1.out file I found out the actual cause for the issue. Some mandatory RPM's are missing and hence the issue. So inorder to fix the issue, I googled and found some sites which provides solutions for the exact issue. At that point I learned this error is generic and this issue could be by multiple reasons.

So I decided to install the missing RPM's(as per the blogs I referred) in order to solve the issue. Below are the steps I followed.

Now I've installed all the required RPM and now I need to relink the forms before starting the APPS service to check whether the issue is fixed or not.

Once the forms compilation is completed, I started the APPS services and opened a form and ended up with the same issue.

Now on further drill-down, I found out some of the library files are missing which are mandate and to be in place for the forms to open.

Under /usr directory a directory named X11R6 is missing. So I created a directory manually and copied the libraries from another server and created the required soft links as below.

But still no luck and ended up with the same issue.

So finally I decided to run a RDA check on my instance to find what are all the pre-requisites I missed for an EBS R12.2 environment.

After I ran RDA check I found the RPM's which I need badly to fix this issue. Below are the steps I followed.

Now I know what are all the RPM's I need to install to fix this issue. So I installed all the RPM's(some 32 bit RPM as well[mandate]) and the issue is fixed.

Again I ran a RDA check and still it shows openmotif21 is missing, but actually openmotif22 is installed. Issue is fixed and the forms are opening properly. 

Reference:

1. R12 E-Business Suite Applications Technology Stack Forms Access Fails For Any Form Responsibility Fails With Error "FRM-92101: Forms Server"After EBS Fresh Install (Doc ID 1192205.1)
2. R12 Clone Instance Fails While Opening Forms With Error FRM-92101, and formsstd.out Shows Error frmweb: error while loading shared libraries: libXt.so.6: cannot open shared object file: No such file or directory (Doc ID 2170634.1)
3. R12: "FRM-92101:There was a failure in the Forms Server during startup" Error When Attempting to Launch Forms (Doc ID 454427.1)
4. Remote Diagnostic Agent (RDA) - Getting Started (Doc ID 314422.1)
5. How To Install 32-bit RPMs On A 64-bit OS (Doc ID 2166149.1)
6. RPM Download Link -- https://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/

                           ****************************நன்றி****************************

Target node/queue unavailable in R12.2

After creating a clone instance in R12.2, faced the below error.

There was no problem in starting or stopping the concurrent manager.

So to fix this issue, I tried running CM Recovery wizard.

Press on Next button to complete all the steps.

But this CM recovery wizard ends in vain.

So after these steps, decided to update the CM related tables manually from backend to resolve this stated error.

In the place of NODENAME replace your nodename and omit the angular brackets. You can find the nodename from fnd_nodes table.

select node_name,target_node,control_code from fnd_concurrent_queues;

update apps.fnd_concurrent_queues set node_name = '<NODENAME>' where node_name is null;

select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;

select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;

UPDATE fnd_concurrent_queues set control_code = null;

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where node_name = '<NODENAME>';

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE is null;

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE = '<NODENAME>';

update fnd_concurrent_queues set NODE_NAME='<NODENAME>' where NODE_NAME='<NODENAME>';

update fnd_concurrent_queues set TARGET_NODE='<NODENAME>' where TARGET_NODE is null;

UPDATE fnd_concurrent_queues set target_node = '<NODENAME>';

UPDATE fnd_concurrent_queues set node_name = '<NODENAME>';

commit;

Once you updated the table. Try start the concurrent manager. This time the issue was fixed and everything is fine.

****************************நன்றி****************************