When we
are facing performance issues with frmweb sessions, below CONTEXT_FILE
variables must be considered –
FORMS_CATCHTERM –
This
variable decides enabling/disabling of forms abnormal termination
handler(FATH).
FATH
basically writes diagnostic information into dumpfile or form server log.
Default value is '1'.
FORMS_RECORD_GROUP_MAX –
This is a
customized environment variable when using in servlet mode while we can
directly set this in socket.env with socket mode.
FORMS_MMAP –
This is
mainly monitored in socket mode. When set to 0 will not put .fmx files in
shared memory mapped files resulting in more memory consumption. Recommended
value for this variable is 1.
Scenario -
Common
frmweb process issues are with high CPU and memory consumption. This results in
slowing down application server where forms services are running. Whenever an
end user is working LOVs fetching huge number of records, these records are
loaded in memory and result in paging. CPU consumption then increases paging
process in and out of memory.
Core
dumpfiles or form server logs are located under -
$FORMS_TRACE_DIR
Note that
these settings are same in r12.1 and r12.2 as forms version did not change.
We will
not be discussing about setting these values as it is already mentioned in 745711.1.
We will understand implications post setting these values –
Case – 1 (Default)
FORMS_CATCHTERM=1
This
implies Forms abnormal Termination handler is enabled and as part of post
implementation, we as APPS DBAs must consider setting it to 0 as recommended in
745711.1.
Case – 2 (Socket Mode)
Reference
- 1382442.1
socket.env
under INST_TOP is updated in socket mode and below are 3 variables that should
be modified.
FORMS_CATCHTERM
FORMS_MMAP
FORMS_RECORD_GROUP_MAX
Case – 3 (Servlet Mode)
Reference
- 745711.1
"s_forms_catchterm"
is name for FORMS_CATCHTERM in CONTEXT_FILE.
While FORMS_RECORD_GROUP_MAX
does not have any autoconfig predefined name. We require additional customization
for the same.
FORMS_CATCHTERM
FORMS_RECORD_GROUP_MAX
Implications of Setting FORMS_RECORD_GROUP_MAX
This
variable can impact forms of different module to limit number of records to be
fetched. Below is summarized list of doc ids and recommendations given by Oracle.
It is advisable to set this variable optimally according to your environment.
You can
set it to 10000, 20000 or 30000 as per Oracle. There are some rare occasions
when even 30000 will not suffice. In such rare occasions you can always raise a
ticket with Oracle Support.
Oracle
Support internally should request development team to modify standard form and release
it as a patch for your environment.
Unable To Add Item In ASCP Planning Workbench When
Item List > FORMS_RECORD_GROUP_MAX Environment Variable (Doc ID 2294933.1)
-
Download, review and apply patch 26407840
In Sales Order form Query by Held By Field, LOV does
not show all options (Doc ID 2478176.1)
-
Download, review and apply patch 28521267
EBS: Searching LOV has shown error Choices in list,
limited by maximum rows: 30000 (Doc ID 2190037.1)
-
FORMS_RECORD_GROUP_MAX=50000
'Menus' LOV from 'Responsibilities' form
(FNDSCRSP.fmb) using a filter shows no result or shows part of the existing
menus (Doc ID 2390886.1)
-
Download, review and apply patch 27362828
When Query Manufacturers Part Numbers Via Form
INVIDMPN Error Message "Choices in the list, limited by maximum rows:
30000" (Doc ID 1272217.1)
-
Download, review and apply patch 12983688
CSXSRISR.FMB NEEDS FILTER BEFORE DISPLAY = YES ON
LOV'S (Doc ID 2322101.1)
-
Download, review and apply patch 26522836
Lov Constraint On Project Field In 'Release Sales
Order For Picking' Form (Doc ID 1094523.1)
-
Download, review and apply patch 9434838
Cannot Add Functions To Menus : Some Functions Are Not
Available In The List Of Values (Doc ID 1961346.1)
-
Increase value of variable FORMS_RECORD_GROUP_MAX to 30000
Task Assignee LOV Is Restricted To Show Limited Number
of Records (Doc ID 1142284.1)
-
Increase value of variable FORMS_RECORD_GROUP_MAX to 30000
Comments
Post a Comment