TROUBLESHOOTING STEPS for FRM-92050 FRM-92100 FRM-92101 FRM-92102

SCOPE & APPLICATION 

9i 
Oracle 9iAS Rel 2 Forms Services (Forms 9i (9.0.2)) 
Oracle 9iDS Rel 2 (Forms 9i (9.0.2)) 
Not supported anymore. 

10G R1 
Oracle Application Server 10g (9.0.4 
Oracle Developer Suite 10g (9.0.4) (Forms 10g (9.0.4)) 
Not supported anymore. 

10G R2 
Oracle Application Server 10g (10.1.2) 
Oracle Developer Suite 10g (10.1.2) (Forms 10g (10.1.2.))

WHERE TO BEGIN? 
FRM-92050 
FRM-92100 
FRM-92101 
FRM-92102 

While running your Forms application, you may encounter various FRM errors. These errors can be raised by several different conditions. When you receive these errors, you will need to obtain more information to resolve it. In this section we will see some of the common errors that one may encounter and how to resolve them.  
Broadly speaking, the FRM errors occur due to the following. 

Configuration Problems: 
Some FRM errors are raised by configuration problems. For example, the Forms Service is not started, or is listening on a different port to that specified in the HTML file. Typically these errors will reproduce consistently. 

Forms server process has crashed: 
The majority of FRM errors that occur after a successful connection has been established and the form started, are due to the server crashing. Once the server process has died, then the client cannot continue running - the applet has no life of its own, and it cannot continue to run without being able to communicate with the server process. 
These errors are often difficult to diagnose: the problem may not reproduce consistently, or the user may be unaware of the sequence of events that led to the crash. 

Network Problems: 
The communication between the applet and the Forms Server process has experienced network problems, and the communication has been broken. 

Please verify following Matrix Table A-1 it lists the FRM -92xxx errors caused by these reasons. It also briefly explains what they mean.

If the matrix "Table A-1" does not help to resolve the issue, please try to verify following information 
It will help Oracle Support services to identify and to resolve the issue. 
If possible copy and paste the list below into the new SR in addition to add your information to it.

1. Is the problem reproducible at will? 

2. What is the approximate frequency of the problem? Is it consistent with some well-defined steps? 
    If it does not consistently reproduce, which of the following statements describe its frequency better: 

a. A single occurrence so far. 
b. Once per month 
c. A few times per month 
d. Once per week 
e. A few times per week 
f. Once per day 
g. A few times per day 
h. Once per hour 
i. A few times per hour 
h. Many times per hour 

4. Does the problem occur in production, test or development instance(s)? 
    Does it occur in one more than one instance? 
    Is it a cloned System? 

5. On which platform is Oracle iAS / iDS Forms installed? 

6. What is the exact version(s) of instance(s) where the problem occur? 

7. What patchsets and/or one-off patches are installed on these installations? 
To obtain the list of one-off patches installed, please execute the following statement :

opatch -lsinventory

8. What type of install(s) does the problem reproduce : 
a. IDS 
b. OAS 

9.Does the error reproduce with the latest supported versions of Oracle Jinitiator /Sun plug-in? 
a) Does your problem reproduce on Supported environment?

Please be aware Oracle Support Services cannot open a Bug request on an unsupported environment.

10. Does the error reproduce if running a simple form like the test.fmx supplied as part of the 
Default Oracle AS, Oracle DS install e.g. 

http://machinename.domain:portno/forms90/f90servlet?form=test.fmx 
http://machinename.domain:portno/forms/frmservletet?form=test.fmx 


11. Did the problem start to occur after some change in the system? 

a. After upgrading from one version to another. 
b. After installing some patches, for Oracle products and/or Operating System. 
c. Some configuration changes. 
d. Installation of some new Reports / Applications on the application server. 

The JInitiator Java Console 

If you are using JInitiator and a Java error is encountered then the error will be written to the browser status line. However, this does not show the full Java error stack. You need to look for it in the JInitiator Java console. 

If you have turned the Java Console on, by checking its option in JInitiator Control Panel Applet on a Windows computer, the JInitiator Console window will pop up when your Form runs in a browser. The JInitiator Control Panel Applet can be found on the Start | Settings | Control Panel option in Windows. If JInitiator's Java console does not appear, you can always invoke it manually from the taskbar tray icon by double clicking it. 

How to Enable Forms trace 

Note:271095.1 - How to Interpret Forms Listener Servlet Debug / Log Information? 
Note 219471.1 - Forms Servlet Logging Explained 
http://www.oracle.com/technetwork/developer-tools/forms/documentation/trace9i-133379.pdf

Known Issues 

Problems: If you try to open a new Browser session.

FRM-92100 occurs when invoking a new forms session from existing form session, or another URL is invoked from the parent browser window of the forms applet? 

Note:251915.1 - FRM-92050 When Invoking a Second Forms Session in a New IE Browser Window 

Bug:2715718 (Fixed In Ver: 9.0.2) 
FRM-92050 CONNECTION FROM NEW BROWSER WINDOW NOT SUPPORTED 

Bug:2688385 (Fixed In Ver: 9.0.2) 
NOT ABLE TO RUN 2 FORMS SERVLET SESSIONS AT THE SAME TIME FROM PORTAL 

Bug:2481184 (Fixed In Ver: 9.0.4) 
FRM-92050:FORMS 9I:WHEN RUNNING FORMS SERVLET IN MULTIPLE IE SESSION. 

Bug:2689990 (Fixed In Ver: 9.0.4) 
SESSION-TRACKING COOKIES="DISABLED" IN ORION-WEB.XML STILL SENDS COOKIE IN HDR 

NLS_LANG settings. 

Bug:2667950 - GETTING FRM-92100 OR FORM HANGS WHEN NLS_LANG SET TO JAPANESE_JAPAN.UTF8

FRM-92100 and error: java.io.UTFDataFormatException java.io.DAtaInputStream.readUTF(Unknown Source) occurs when NLS_LANG is not set or has an incorrect value. 
Set NLS_LANG in the default.env ( or customized envFile) to a correct value.

Usage of RUN_PRODUCT 

The RUN_PRODUCT built-in no longer works in Forms 10G / 9i. 

Usage of SSO with Forms 

FRM-92050 Integrating Forms 9i / 10g with SSO 
Verify that Forms 9i / 10g Single Sign-on integration has been configured correctly. 

Note 980793.1 Troubleshooting Oracle Forms 10gR2 Single Sign-On (SSO) Integration Issues  

Issues which can be causd by Clients. 

It can help to resolve or to identify the cause of an issue. 

a) If using Oracle Jinitiator, try clearing the Jinitiator JAR or jcache 
b) If using MS Internet Explorer check that permissions / security options are set correctly. 
c) Launch Microsoft Internet Explorer.

Select the Tools -> Internet Options from the top level menu. 
Click the SECURITY Tab: 
Choose Local Intranet Zone from the list. 
Click Custom Level. 
Select Java Permissions - Custom from the list. 
Click Java Custom Settings. 
Select the Edit Permissions tab. 
Choose Enable for Run Unsigned Content. 
Choose Enable for Run Signed Content. 
Select the ADVANCED tab. 
Scroll down to Java VM. 
Check the Java console enabled option. 
Select the CONNECTIONS tab. 
Click the LAN Settings button. 
If IE is using a proxy server : Check the Bypass proxy server for local addresses check box. Click the Advanced button, and enter the local domain in the Exceptions box. 
Use the form *.domain.com, where domain.com maps to your local domain. 
Click OK to exit the dialog. 
Click OK to save the changes and exit IE.

Yahoo's Anti-spy. 
Remove the Hijacker software using Yahoo's Anti-spy

Frm-92050:Failed to connect to the Server:
/prod/oracle.forms.servlet.ListenerServlet/session:
java.io.IOException: 
Negative contentlength occurs when Hijacker software installed on the computer. 
The hijacker software called Comet. font 

Issues with Proxy Settings or HTTPS mode 

Using Oracle Jinitiator 1.3.1.8 / 1.3.1.9 in conjunction with reverse proxy in HTTPS mode? 
Bug:2673273 - JINITIATOR DOESN'T WORK WITH REVERSE PROXY IN HTTPS MODE 

Time-out issue 

Try changing the FORMSXX_TIMEOUT and heartbeat settings, especially if the disconnects coincide with users leaving forms sessions idle for periods of time.

Note:549735.1 - Ext/Pub Description List For Parameters Affect Timeout In Webforms
Note:271611.1 - Long Running Query / Procedure Causes Web Deployed Forms 6i - 9i to Disconnect? 
Bug:2121212 - WEBFORMS:FORMS LISTENER SERVLET GET READ TIMEOUT WHEN LONG DB PROGRAM RUNS. 
Bug:3032966 - LONG RUNNING PROCEDURE CAUSES DISCONNECT 

Note:271611.1 - Long Running Query/ Procedure Causes Web Deployed Forms 6i - 9i to Disconnect? 
This issue is fixed with the introduction of the maxBlockTime servlet parameter in: 
Oracle Forms 9i patchset 3 (9.0.2.3) or higher, 
and Oracle Forms 10g (9.0.4) 

Forms OC4J instance setting. 

10G R2(10.1.2.x)

Note:294749.1 - Troubleshooting WebForms Tuning / Performance /Time out Problems: 
Note:271095.1 -  How to Interpret Forms Listener Servlet Debug / Log Information? 

Issues with 3rd party Load Balancer 
 

Using O/S or 3rd Party Software Machine Load Balancing? 

Note: The principles outlined in this white paper can be applied to Forms 9i / 10g Services  e. Using O/S or 3rd Party Software Machine Load Balancing? 
Poblems can arise when using a O/S or 3rd Party software solution (e.g Windows Load Balancing ) to load balance machines hosting Forms Listener Servlet configurations. This will be, particularly, the case if the load balancing solution does not maintain session information or has no concept of session persistence.   

For example: 
  
There are two machines hosting Oracle AS Forms Services machineA and machineB.
A client machine invokes the URL to call the forms application.   
The O/S or 3rd Party machine load balancing mechanism directs the client request to one of the machines.   
The forms applet is initialised and the client is connected to a Forms Runtime process on the given machine e.g machineA.   
At some point thereafter an unexpected disconnect / interrupt occurs on the network check.   
The connection is then restored.   
If the O/S or 3rd Party load balancing software has not maintained information about the previous session, it may direct the client back to the 'wrong' machine i.e machineB.   
As there is no corresponding Forms Runtime process running on this machine, the Forms session on the client remains broken.   

How to check for this scenario?   

· Rename or remove the existing access_log, error_log and jserv.log files on machine A and B.   
· Stop and restart the Oracle AS middle tier so that new versions of these logs are created
· On the client machine, enable the Oracle Jinitiator java console.   
· Run the forms application until the disconnect/ failure occurs   
· In the Oracle Jinitiator java console there should be a unique JServSessionIdroot string   
· e.g it make look something like 'axct5t4fa1.pR9GpBiTmA4Up6XxmkLCpRbOcx4Sc3m)   
· Take this string and make a search for it in the access_log files on both machines A and B
. The string should only appear in one of the access_log files.
  If it appears in more than one access_log, the O/S or 3rd Party load balancing  
  solution has directed the client back to the 'wrong' machine. The timestamps  
  in the access_logs will also give an indication of when the disconnect occurred. 

 

 

FRM-92101 Not enough space error

After a server crash and try to restore Oracle AS middle tier appears the   
following error in the application.log too many times:  

….formsweb: Not enough space ... 
Reviewing the RDA output I see in the Operating system setup ----> System Error Log the following output: 
Sep  8 14:31:28 <address>AFSR 0x00000000.00100000<CE> AFAR 0x00000000.97caf310 
Sep  8 14:31:28 <address> AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x1178e7c 
Sep  8 14:31:28 <address> UDBH Syndrome 0x31 Memory Module U1302 
Sep  8 14:31:28 <address> unix: [ID 566906 kern.warning] WARNING: [AFT0] Most recent 3 soft errors from Memory Module U1302 exceed threshold (N=2, T=24h:00m) triggering page retire Sep  8 14:31:28 <address> unix: [ID 618185 kern.notice] NOTICE: Scheduling removal of page 0x00000000.97cae000 Sep  8 14:31:28 <address> SUNW,UltraSPARC-II: [ID 855227 kern.info] [AFT0] errID 0x0002b711.55a0ccff Corrected Memory Error on U1302 is Persistent Sep  8 14:31:28 <address> SUNW,UltraSPARC-II: [ID 755585 kern.info] [AFT0] errID 0x0002b711.55a0ccff ECC Data Bit  0 was in error and corrected Sep  8 14:31:28 <address> unix: [ID 693633 kern.notice] NOTICE: Page 0x00000000.97cae000 removed from service

Cause 
The behavior and errors recorded in the application.log are generated for the issue at memory 
level in that UNIX server in accordance with the error reported in the System Error log file. 
No swap devices configured. The command swap -l output shows "No swap devices configured" 

Solution 
Set on correctly swap memory.