AIX 系统 EBS form 打开报错FRM-92101: FORM server在启动过程中失败

克隆或者安装好系统后,发现form打不开,报错截图:

根据oracle 官方文档:R12: "FRM-92101:There was a failure in the Forms Server during startup" Error When Attempting to Launch Forms [ID 454427.1]

Oracle Applications Technology Stack - Version 12.0.4 to 12.2 [Release 12.0 to 12.2]
IBM AIX on POWER Systems (64-bit)
AIX5L Based Systems (64-bit)
Checked for relevance on 16-JUL-2013

SYMPTOMS

After a successful login, attempts to launch forms based responsibilities fail with the following errors within the Java Console:

proxyHost=null
proxyPort=0
connectMode=HTTP, native.
oracle.forms.net.ConnectionException: Forms session <1> failed during startup: no response from runtime process
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.HTTPConnection.connect(Unknown Source)
at oracle.forms.engine.FormsDispatcher.initConnection(Unknown Source)
at oracle.forms.engine.FormsDispatcher.init(Unknown Source)
at oracle.forms.engine.Runform.initConnection(Unknown Source)
at oracle.forms.engine.Runform.startRunform(Unknown Source)
at oracle.forms.engine.Main.createRunform(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Additionally, users may see:

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

This could happen due to invalid configuration. Please look into the web-server log file for details.
Details...

Java Exception:
oracle.forms.net.ConnectionException: Forms session <3> failed during startup: no response from runtime process
at oracle.forms.net.ConnectionException.CreateConnectionException(Unknown Source)

The underlying cause is revealed by the $LOG_HOME/ora/10.1.3/j2ee/forms_default_group_1/application.log:

formsweb: Forms session <3> aborted: runtime process failed during startup with errors exec(): 0509-036 Cannot load program .../apps/tech_st/10.1.2/bin/frmweb because of the following errors:

rtld: 0712-001 Symbol nnftboot was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnfoboot was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnfhboot was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnflboot was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nttini was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ntusini was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ntpini was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ntzini was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnflgav was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnflrne was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnflfrm was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol nnflgapc was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ldap_search_s was referenced
from module frmweb(), but a runtime definition
of the symbol was not found.
....

CHANGES

The problem of forms not launching is typically seen after a fresh installation or clone.

CAUSE

The forms executable was not relinked successfully.   The "failed during startup: no response from runtime process" error message occurs when first trying to initialize the forms process versus actually performing a forms function.

The most common cause for the failed relink is that the file "ldflags" in $ORACLE_HOME/lib32 is missing or pointing to an incorrect location.

SOLUTION

1. In several customer instances, $ORACLE_HOME/lib32/ldflags was a symbolic link that pointed to a location that did not exist.  This was resolved by performing the following UNIX commands to point the $ORACLE_HOME/lib32/ldflags to the $ORACLE_HOME/lib/ldflags:

$ cd $ORACLE_HOME/lib32

$ rm ldflags

$ ln -s $ORACLE_HOME/lib/ldflags ldflags

 

2. Then, stop the web tier services (adopmnctl.sh stop) and relink the forms executable(s):

$ cd $ORACLE_HOME/forms/lib32/

$ make -f ins_forms.mk install

 

版权声明:本文为博主原创文章,未经博主允许不得转载。

时间: 2024-10-10 08:46:11

AIX 系统 EBS form 打开报错FRM-92101: FORM server在启动过程中失败的相关文章

wpf 报错: 在 AddNew 或 EditItem 事务过程中不允许“DeferRefresh”。

今天修改Bug的时候遇到一个问题: datagrid 设置了双击事件,双击弹出一个窗口,在多次点击后报错:在 AddNew 或 EditItem 事务过程中不允许“DeferRefresh” 网上查了一些资料:http://www.cnblogs.com/huangyuanfengxue/archive/2011/12/02/huangyuanfengxue.html http://blog.csdn.net/stableboy/article/details/17450893 原因是DataG

WIN7 64位EBS R12打开报错FRM-92095:Oracle JInitiator版本太旧,请安装版本1.1.8.2或更高版本

打开EBS的form,系统报错,中文提示信息是:FRM-92095:oracle jinitiator版本太旧,请安装版本1.1.8.2或更高版本:如果是英文环境,则会报错:FRM-92095: Oracle JInitiator version too low. Please install version 1.1.8.2 or higher. 这个问题的图示如上图1.图2所示 (1)解决方法1 因为这个可能是升级了jre到jre7版本,而实际上目前EBS还不能跑在JRE7上,解决方法就是卸载

Lync 2013打开报错Lync即将成为Skype for Business处理方法

Lync 2013无法打开报错如下: Lync即将成为Skype for Business.若要运行此应用,你需要安装Skype for Business的其它更新.有关详细信息,请参阅KB3115883或与管理员联系. 这个报错,是微软在2015年底推出的试探性补丁,让用户体验全新的Skype for Business客户端,紧接着就推出了这个补丁造成服务端是Lync Server 2013的用户无法正常打开并使用. 官方的解释如下: https://support.microsoft.com

Exchange Server 2010 EMC打开报错故障处理

[问题现象] [分析] 此问题,多为由于服务器自身iis服务运行异常导致,后期如遇到此类问题,一般重启iis即可,另外远程连接exchange控制台靠powershell远程方式,此方式会在iis中创建相关目录,如下: [解决方法] 1.打开EXCHANG后端服务器的iis管理控制台,如下图所示: 2.如下图所示,单击"停止"按钮: 3.如下图所示,单击"启动"按钮: 注意:不要直接采用重新启动,有时iis使用重新启动会提示重启失败. Exchange Server

Android开发之自定义Dialog二次打开报错问题解决

之前自定义了一个AlertDialog对话框,第一次点击时正常,但第二次调用时会出现错误:java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first. 关于这个错误纠结了我好久,在网上百度了也不少,但感觉解决效果都达不到自己想要的效果.网上的解释说是一个子视图指定了多个父视图.由此可以推断出,在第二

数据库打开报错: 值不能为空

报错信息如下: 数据库客户端打不开 解决方案: 找到下面的目录C:\Users\<username>\AppData\Local\Temp 创建一个空文件夹 名称是: 2 重新打开数据库 数据库打开报错: 值不能为空

【EBS】adpatch报错:libgcc_s.so: undefined reference to `[email&#160;protected]_2.4&#39;

EBS通过adpatch打补丁报错 /usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to `[email protected]_2.4' collect2: ld returned 1 exit status make: *** [/soft/ebs12/ERPDB/apps/apps_st/appl/ad/12.0.0/bin/adwrknew] Error 1 Done with link 

关于Code Blocks无编译器版本及VC6.0插入、打开报错

CodeBlocks运行C成功,编译C++一直报错:fatal error:stdlib.h:no such file or directory.下载重装了几次Code Blocks无编译器版本以及MINGW.看了很多教程,并不能解决问题.据说是版本对不上,于是重置电脑,安装带有编译器的版本成功运行.至于具体原因有待探究. 另VC6.0插入.打开报错,微软官方之前给出了相应插件,不过现已失效.使用百度引擎找到免费.便捷的链接并不容易.为了方便大众,现将链接附上. https://pan.baid

linux下查看线程数的方法及超过系统线程最大值的报错

通过/proc伪文件系统说明:Linux系统上的/proc目录是一种文件系统,即proc文件系统.与其它常见的文件系统不同的是,/proc是一种伪文件系统(也即虚拟文件系统),存储的是当前内核运行状态的一系列特殊文件,用户可以通过这些文件查看有关系统硬件及当前正在运行进程的信息,甚至可以通过更改其中某些文件来改变内核的运行状态.基于/proc文件系统如上所述的特殊性,其内的文件也常被称作虚拟文件,并具有一些独特的特点.例如,其中有些文件虽然使用查看命令查看时会返回大量信息,但文件本身的大小却会显