Posts Tagged ‘Oracle Application’

Steps To Run Gather Statistics For A Schema In R12.1.3

January 15th, 2025, posted in Oracle EBS Application
Share
1. Log on to Oracle Applications with
    Responsibility = System Administrator
2. Submit Request Window
    Navigate to: Concurrent > Requests
3. Query for the Gather Schema Statistics
4. Enter the appropriate parameters. This can be run for specific schemas by specifying the schema name or entering  ‘ALL’  to gather statistics for every schema in the database
5. Submit the Gather Schema Statistics program
Share

Oracle R12 E-Business Suite Output Post Processor (OPP) Fails To Pick Up Concurrent Requests With Error ‘Unable to find an Output Post Processor service to post-process request ’

November 17th, 2024, posted in Oracle EBS Application, Oracle Queries
Share
SELECT fcp.concurrent_process_id
FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp
WHERE concurrent_queue_name = ‘FNDCPOPP’
AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND fcq.application_id = fcp.queue_application_id
AND fcp.process_status_code = ‘A’;

Output example:

CONCURRENT_PROCESS_ID
———————
93557
93558
select name from APPLSYS.AQ$FND_CP_GSM_OPP_AQTBL_S ;

Output example:
NAME
——————————
OPP35562
OPP35563
OPP35564
OPP35565
exec fnd_cp_opp_ipc.unsubscribe(”);
Example:
exec fnd_cp_opp_ipc.unsubscribe(‘88933’);
exec fnd_cp_opp_ipc.unsubscribe(‘92625’);
Share

Output Post Processor (OPP) – An Overview By Author – A.Kishore/Sach

October 12th, 2024, posted in Oracle EBS Application, Oracle Queries
Share
SELECT service_id, service_handle, developer_parameters
FROM fnd_cp_services
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');
SERVICE_ID SERVICE_HANDLE DEVELOPER_PARAMETERS

Profile Option : Concurrent:OPP Process Timeout
Internal Name : CONC_PP_PROCESS_TIMEOUT
Description : Specifies the amount of time the manager waits for the OPP to actually
process the request.
Share

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

Query To Get The Front End URL From Backend

February 6th, 2022, posted in Oracle EBS Application, Oracle Queries
Share

Query to get the front end URL,oracle ebs front end URL,oracle ebs url

Query to get the front end URL from back-end

 

SELECT home_url FROM   icx_parameters; 
http://hostname.domainname.com:8000/OA_HTML/AppsLogin

 

 

Share