Error while clicking on verify buttun under alert manager

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Error while clicking on verify buttun under alert manager

satish
Hi Erman,

In our prod server,We are defing a custom alert and while clicking on verify button,we are facing the below error.It is giving same error for all alerts

      FRM-92101: There was a failure in the Forms Server during startup. This could happened due to invalid configuration.
 
We got a note id describing the same behaviour.(The Verify Button Fails Under Alert Manager / Define Form With FRM-92101 (Doc ID 1537468.1)).

But the thing is,the same alerts are working in test server when clicking on verify button.Both prod and test are at same patch level and the file version is same

[test@server1~]$ strings -a $ALR_TOP/bin/ALECDC | grep Header | grep aluapp
$Header: aluapp.lc 120.1.12010000.3 2008/11/14 21:38:47 jwsmith ship $

PROD:
/home/applprod >  strings -a $ALR_TOP/bin/ALECDC | grep Header | grep aluapp
$Header: aluapp.lc 120.1.12010000.3 2008/11/14 21:38:47 jwsmith ship $
/home/applprod >

1)Is this normal behaviour like working on test server and not working in prod?
2)Is there any work around apart from applying this patch?

Thank You
Reply | Threaded
Open this post in threaded view
|

Re: Error while clicking on verify buttun under alert manager

ErmanArslansOracleBlog
Administrator
This is adressed with the patch.
Sometimes, some bugs can only be triggered with some circumstances..
It seems the frmweb process crashes when you hit the bug.
That process is running on top OS, so it may depend on the OS and even the hardware as well.
When I look at the bug defitinion, I see the following;

adb $ORACLE_HOME/bin/....core file = core -- program
  ``/appl/R12/apps/tech_st/10.1.2/bin/frmweb'' on platform
    SUNW,Sun-Fire-V440
    SIGSEGV: Segmentation Fault

As you see, they even specified the platform there.

So probably, the bug is present in TEST too, but there is something in your TEST environment which prevents the bug to be triggered and that's why you don't get the same error there.
So I suggest you the apply the patch in any case.  (first apply it on TEST, then on PROD)