Posts Tagged ‘Oracle Forms’

Oracle : FRM-92102 ERRORS

January 14th, 2023, posted in Oracle

Error reported was

Users are experiencing FRM-92102:A network error has occurred . The forms client attempted to reestablish its connection to the server 5 time(s) witho
ut success. Please check the network connection and try again.

Reference SR is 6782240.992 ( Leviton Mfg Co )

Please read through Note: 365529.1 Ext/Pub Troubleshooting FRM-92XXX Errors in Oracle Applications:
Please provide feedback on the questions listed in sections:
A. General List of Questions
D. Intermittent or Random Disconnects

These sections gave very good understanding on the problem at hand.

The most important point was timeout settings.
What the following timeout settings are set to:
Timeout Parameters:


Heartbeat = 2 in $OA_HTML/bin/appsweb.cfg

Self Service Timeout Profile Options:
ICX: Session Timeout = 30
ICX:Limit Time = 4
ICX:Limit connect = 1000

session.timeout=1800000 ( in Apache)

So analyst recommended following adjustments

The ‘FORMS60_TIMEOUT = 120’ should not be set so high. For users that walk away and stay con
nected, this will consume unnecessary resources.
It is recommended that the ‘FORMS60_TIMEOUT be set to something like 30 minutes with 60 minutes being about the

Concerning the:
ICX:Limit Time = 4
ICX:Limit connect = 1000

The ICX:Limit Time, controls the total time a session can be logged in. If set to 4 hours,
then after 4 hours the user will get disconnected, regardless of what activity
is being done. Bump this setting up to something like 8 to 10 hours.

The ICX:Limit connect, needs to be bumped up to 2000 +, because each time Session Time is
checked it adds another ICX connection. This IS NOT DETERMEND BY THE NUMBER OF U
SER CONNECTIONS. The more ICX checks its self the more ICX connections you are g
oing to see. Session expiration can also occur when the total number of times th
e session is validated exceeds ‘ICX: Limit Connect’.

The above two ICX settings are most likely the source of the errors you are seeing.

So we had to reset above settings and bounce apps.

We had a question about licensing issue as well and analyst said

The ‘ICX:Limit Connect’ has nothing to do with the number of concurrent users connecting to the a
pplications. Increasing ICX:Limit Connect to 2000+ will NOT voilate your licens
ing with Oracle ( Leviton had only 1000 concurrent user license) .


Hide Username And Password in URL for Oracle FORMS

February 1st, 2021, posted in Oracle EBS Application

Username & password which is presented in addressbar like this :

For example the address is like this :

This shows that security is very low !!!

However, if all your users use the same username/password, you could specify this information in the FORMSWEB.CFG file; for example:

Go to you servers form configuration :


And go and do this :

# Forms runtime argument: database connection details
userlogin: userid=username/password@instance%*

For now the address will be like this :

You can also set the value in this file instead of setting it in URL.

Here is what URL look like

and here is some setting you can set in the config file

Code: [Select all] [Show/ hide]Hide Username & Password in URL for Oracle FORMS,Oracle FORMS,Hide Username and Password,form,formsweb.cfg

Enable Export Feature in Custom Forms

April 26th, 2020, posted in Oracle Queries

Occurred In Oracle Reports,Oracle Reports,Oracle,Reports,Enable Export Feature in Custom Forms,Enable Export Feature, in Custom Forms,Oracle Custom Forms,Oracle Forms,In Order to Enable Export option, available in Oracle Application forms to export the data into Excel file.
In the custom form at form level trigger write the below code in When-New-Form-Instance trigger.


ORA-01450: maximum key length (6398) exceeded

May 13th, 2018, posted in Oracle Queries

ORA-01450: maximum key length (6398) exceeded,ORA 01450,Ora error,ORA 01450 errors,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,racle Apps,Apps DBA,ERP Application,Repository Creation Utility - Warning | ORA-01450: maximum key length (6398) exceed,Repository Creation Utility Warning,ORA-01450: maximum key length (6398) exceed,Warning ORA-01450: maximum key length (6398) exceed,


the errors seen above are encountered because the NLS_LENGTH_SEMANTICS initialisation parameter has been set to CHAR. This is not a supported setting for this parameter in an Oracle Fusion Middle ware installation. This is documented in the Release Notes for each platform.


To remove the ORA-01450 errors when creating the MDS and SOAINFRA components ensure that the requirement for NLS_LENGTH_SEMANTICS=BYTE is met.

To check the current setting of NLS_LENGTH_SEMANTICS, login to the target database as SYSDBA and issue the following command:


NAME                     TYPE        VALUE
———————— ———– ——-
nls_length_semantics     string      CHAR

SQL> alter system set nls_length_semantics=BYTE;

System altered.


NAME                     TYPE        VALUE
———————— ———– ——-
nls_length_semantics     string      BYTE

After resetting the parameter you should restart your database for the change to take effect.