Posts Tagged ‘oracle erp’

Oracle : FRM-92102 ERRORS

January 14th, 2023, posted in Oracle
Share

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:

FORMS60_TIMEOUT = 120

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 (zone.properties 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
max.

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) .

Share

ORA-01450: maximum key length (6398) exceeded

May 13th, 2018, posted in Oracle Queries
Share

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,

Cause 

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.

Solution 

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:

SQL> show parameter NLS_LENGTH_SEMANTICS

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

SQL> alter system set nls_length_semantics=BYTE;

System altered.

SQL> show parameter NLS_LENGTH_SEMANTICS

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

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

Share

TNS-01155: Incorrectly specified SID_LIST_LISTENER parameter in LISTENER.ORA

April 10th, 2018, posted in Linux OS, Oracle, Windows
Share

TNS-01155: Incorrectly specified SID_LIST_LISTENER parameter in LISTENER.ORA,TNS-01155,Incorrectly specified SID_LIST_LISTENER parameter,LISTENER.ORA,LISTENER ORA,errors,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Oracle Apps,Apps DBA,ERP Application



Issue : While starting the listener we got the below error.


linux01(oracle:orcl1)/home/oracle: lsnrctl start

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 15-SEP-2015 03:43:02

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Starting /opt/oracle/product/11.2.0.4.RAC/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.4.0 - Production
System parameter file is /opt/oracle/product/11.2.0.4.RAC/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/linux01/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
TNS-01155: Incorrectly specified SID_LIST_LISTENER parameter in LISTENER.ORA
 NL-00303: syntax error in NV string

Listener failed to start. See the error message(s) above...



Solution: 

In the listener.ora file there were blank lines under the section SID_LIST_LISTENER. We removed the blank line entries and brought up the listener. (please note that this may be one of the scenarios)

Erroneous listener.ora file excerpts below:

SID_LIST_LISTENER =
 (SID_LIST =
 (SID_DESC =
 (GLOBAL_DBNAME = ORCL1)
 (ORACLE_HOME = /opt/oracle/product/11.2.0.4.RAC)
 (SID_NAME = ORCL1)
 )
 <<<<< blank line
 (SID_DESC =
 (GLOBAL_DBNAME = ORCL2)
 (ORACLE_HOME = /opt/oracle/product/11.2.0.4.RAC)
 (SID_NAME = ORCL2)
 )
 <<<<< blank line
)
Share

Validate Application Accounting Definitions

April 3rd, 2018, posted in Oracle
Share

After setting up of Accounts Receivable (AR) Module. Create Accounting some times completes with warning message “The application accounting definition Multi-Fund Account Receivables Accrual – Balancing Method owned by Oracle is not validated. Please validate the application accounting definition or update the application accounting definitions contained in the subledger accounting method Encumbrance Accrual.”

This warning message we can find in Log file of the concurrent program

Validate Application Accounting Definitions,How To Validate Application Accounting Definitions,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Application Accounting Definitions,Validate ERP Application Accounting Definitions,Oracle Apps,Apps DBA

Validate Application Accounting Definitions,How To Validate Application Accounting Definitions,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Application Accounting Definitions,Validate ERP Application Accounting Definitions,Oracle Apps,Apps DBA

Solution


To overcome this issue go to AR Resposibility and Run Concurrent Program “Validate Application Accounting Definitions“.

Validate Application Accounting Definitions,How To Validate Application Accounting Definitions,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Application Accounting Definitions,Validate ERP Application Accounting Definitions,Oracle Apps,Apps DBA

You can identify that all the Application Accounting Definition Validated by checking the Out put file of the concurrent program.

Validate Application Accounting Definitions,How To Validate Application Accounting Definitions,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Application Accounting Definitions,Validate ERP Application Accounting Definitions,Oracle Apps,Apps DBA

Go to AR Invoice and try to do create accounting. Now Create Accounting concurrent program gets Completes Normal.

Validate Application Accounting Definitions,How To Validate Application Accounting Definitions,Oracle ERP,Oracle ,ERP,Oracle ERP Application,Oracle Application,Oracle DBA,Oracle Forms,Application Accounting Definitions,Validate ERP Application Accounting Definitions,Oracle Apps,Apps DBA

Share