OPP unsubscribe

 

 

Part 1:  - Please find the troubleshooting/solution for resolving the issues specific to OPP. Please find the symptoms, troubleshooting and solution for resolving the OPP issues.

 

 

1.     Gather the concurrent target processes ID’s

SELECT fcp.concurrent_process_id

FROM apps.fnd_concurrent_queues fcq, apps.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'

 

 

2.     Validate the concurrent target processes ID’s from the queue

select name

from applsys.AQ$FND_CP_GSM_OPP_AQTBL_S

order by name

 

Solution:

If there is any discrepancy between the rows, we need to unsubscribe the processes from the OPP queue. The right and active processes are from query#1.

 

exec fnd_cp_opp_ipc.unsubscribe(‘Concurrent target processes ID’);

 

exec fnd_cp_opp_ipc.unsubscribe(‘824721’);

 

exec fnd_cp_opp_ipc.unsubscribe(‘824722’);

How To Restart Output Post Processor (OPP)

 1.  Restarting OPP can be done using adcmctl.sh script  (to start/stop all managers) as there is no specific script for restarting just the OPP manager.

 

2.  The service can also be started from E-Business Application via System Administrator responsibility -> Concurrent -> Manager -> Administer.

     Then select "Output Post Processor" and click on the "Restart" button.

3.  In addition the service an be started and stopped via Oracle Applications Manager.

     Navigate to System Administration -> Oracle Applications Manager -> Concurrent Managers.

    Then select Output Post Processor -> Next to View Processes select Start or Stop.

 

4.  To stop the OPP service you can kill the OPP process from command line by identifying the OPP process in Linux.
a.  Login to APPTIER server and identify the OPP processes.
b.  ps -ef |grep FNDOPP | grep -v grep
c.  Kill OPP processes:
e.  kill -9 PID

 

5.  The OPP system process can be identified as follows from Forms:
a. System Administator > Concurrent -> Manager -> Administer
b. Query "Output Post Processor" -> Processes button
    Get the system id of "Output Post Processor"
c.  Then run the following command at the OS level:
    ps -ef|grep [system id]
d. kill -9 [system id] in Unix
e. System Administrator -> Concurrent -> Manager -> Administer
f. Query "Output Post Processor" -> Restart button

----

[oracle@lufRAMfebssl311 <RUN> ]$ ps -ef |grep FNDOPP | grep -v grep

oracle   3029362 3029225  0 Feb22 ?        00:03:22 /u01/install/APPS/fs1/EBSapps/comn/util/jdk64/bin/java -Doracle.xml.parser.XMLParser.ExpandEntityRef=false -Doracle.xdkjava.security.resolveEntityDefault=false -DCLIENT_PROCESSID=3029362 -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -Dxdo.xliff.source=EBS -Dhttps.proxyHost=lufnonprodsquid.RAM.gov -Dhttps.proxyPort=3128 -Dhttp.proxyHost=lufnonprodsquid.RAM.gov -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=*.nonprodpvtmt.RAMfwest.oraclevcn.com|eccprojit.RAM.gov|localhost|localhost. -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx3072m -Ddbcfile=/u01/install/APPS/fs1/inst/apps/SRAM1I_lufRAMfebssl311/appl/fnd/12.0.0/secure/SRAM1I.dbc -Dcpid=1086028 -Dconc_queue_id=1425 -Dqueue_appl_id=0 -Dlogfile=/u01/install/APPS/fs_ne/inst/SRAM1I_lufRAMfebssl311/logs/appl/conc/log/FNDOPP1086028.txt -DLONG_RUNNING_JVM=true -DEBS_HOSTNAME=lufRAMfebssl311 -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController

oracle   3029363 3029225  0 Feb22 ?        00:02:59 /u01/install/APPS/fs1/EBSapps/comn/util/jdk64/bin/java -Doracle.xml.parser.XMLParser.ExpandEntityRef=false -Doracle.xdkjava.security.resolveEntityDefault=false -DCLIENT_PROCESSID=3029363 -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -Dxdo.xliff.source=EBS -Dhttps.proxyHost=lufnonprodsquid.RAM.gov -Dhttps.proxyPort=3128 -Dhttp.proxyHost=lufnonprodsquid.RAM.gov -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=*.nonprodpvtmt.RAMfwest.oraclevcn.com|eccprojit.RAM.gov|localhost|localhost. -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx3072m -Ddbcfile=/u01/install/APPS/fs1/inst/apps/SRAM1I_lufRAMfebssl311/appl/fnd/12.0.0/secure/SRAM1I.dbc -Dcpid=1086029 -Dconc_queue_id=1425 -Dqueue_appl_id=0 -Dlogfile=/u01/install/APPS/fs_ne/inst/SRAM1I_lufRAMfebssl311/logs/appl/conc/log/FNDOPP1086029.txt -DLONG_RUNNING_JVM=true -DEBS_HOSTNAME=lufRAMfebssl311 -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController

[oracle@lufRAMfebssl311 <RUN> ]$ kill -9 3029362 3029363

[oracle@lufRAMfebssl311 <RUN> ]$ ps -ef |grep FNDOPP | grep -v grep

[oracle@lufRAMfebssl311 <RUN> ]$ ps -ef |grep FNDOPP | grep -v grep

[oracle@lufRAMfebssl311 <RUN> ]$ ps -ef |grep FNDOPP | grep -v grep

oracle   2672797 3029225 10 15:41 ?        00:00:03 /u01/install/APPS/fs1/EBSapps/comn/util/jdk64/bin/java -Doracle.xml.parser.XMLParser.ExpandEntityRef=false -Doracle.xdkjava.security.resolveEntityDefault=false -DCLIENT_PROCESSID=2672797 -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -Dxdo.xliff.source=EBS -Dhttps.proxyHost=lufnonprodsquid.RAM.gov -Dhttps.proxyPort=3128 -Dhttp.proxyHost=lufnonprodsquid.RAM.gov -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=*.nonprodpvtmt.RAMfwest.oraclevcn.com|eccprojit.RAM.gov|localhost|localhost. -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx3072m -Ddbcfile=/u01/install/APPS/fs1/inst/apps/SRAM1I_lufRAMfebssl311/appl/fnd/12.0.0/secure/SRAM1I.dbc -Dcpid=1086744 -Dconc_queue_id=1425 -Dqueue_appl_id=0 -Dlogfile=/u01/install/APPS/fs_ne/inst/SRAM1I_lufRAMfebssl311/logs/appl/conc/log/FNDOPP1086744.txt -DLONG_RUNNING_JVM=true -DEBS_HOSTNAME=lufRAMfebssl311 -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController

oracle   2672824 3029225  9 15:41 ?        00:00:02 /u01/install/APPS/fs1/EBSapps/comn/util/jdk64/bin/java -Doracle.xml.parser.XMLParser.ExpandEntityRef=false -Doracle.xdkjava.security.resolveEntityDefault=false -DCLIENT_PROCESSID=2672824 -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -Dxdo.xliff.source=EBS -Dhttps.proxyHost=lufnonprodsquid.RAM.gov -Dhttps.proxyPort=3128 -Dhttp.proxyHost=lufnonprodsquid.RAM.gov -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=*.nonprodpvtmt.RAMfwest.oraclevcn.com|eccprojit.RAM.gov|localhost|localhost. -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx3072m -Ddbcfile=/u01/install/APPS/fs1/inst/apps/SRAM1I_lufRAMfebssl311/appl/fnd/12.0.0/secure/SRAM1I.dbc -Dcpid=1086745 -Dconc_queue_id=1425 -Dqueue_appl_id=0 -Dlogfile=/u01/install/APPS/fs_ne/inst/SRAM1I_lufRAMfebssl311/logs/appl/conc/log/FNDOPP1086745.txt -DLONG_RUNNING_JVM=true -DEBS_HOSTNAME=lufRAMfebssl311 -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController

[oracle@lufRAMfebssl311 <RUN> ]$

GSS Troubleshooting

 $TFA_HOME/bin/tfactl diagcollect -srdc dbperf -from "02/15/2025 22:00:00" -to "02/16/2025 10:00:00"

Enter the Database Name [Required for this SRDC] : EBSDE3

Is the issue related to a specific Plugable Database? [Y|N]  [Required for this                                                                                              SRDC]: Y

Enter the PDB Name  [Required for this SRDC] : DRAM5I

Start time when the performance was bad:  2025-02-15 22:00:00

Stop time when the performance was bad:   2025-02-16 10:00:00

For comparison, it is useful to gather data from another period with similar load where problems are not seen. Typically this is likely to be the same time period on a previous day. To compare to the same time period on a previous day enter the number 02 days ago you wish to use. [<RETURN> to provide other time range] :

Start time when the performance was good 2025-02-13 22:00:00

Stop time when the performance was good 2025-02-14 10:00:00

Has any SQL been identified to contribute to the performance issue?[Y|N]  [Required for this SRDC]: N

Do you wish to take an AWR Dump as part of this collection?

 NOTE: AWR Dump Can add signification size to the collection and increase the time necessary for the collection to complete. [Y|N] [Required for this SRDC]: Y

Ending AWR snapshot not needed, existing AWR snapshot exists within time window.

Found 14 snapshot(s) in Bad Performance time range for database EBSDE3

Found 14 snapshot(s) in Baseline Performance time range for EBSDE3

"Automatic Workload Repository (AWR) is a licensed feature. Refer to My Oracle Support Document ID 1490798.1 for more information"

Components included in this collection: DATABASE CHMOS CHA OS INSIGHTS SOSREPORT

Preparing to execute support diagnostic scripts.

 Executing DB Script srdc_db_lfsdiag.sql on EBSDE3 with timeout of 120 seconds...

ETCC CheckMTpatch Issue

 Backup TXK_TCC_RESULTS

Truncate TXK_TCC_RESULTS

Run ETCC on all db nodes

Run ETCC on Applications Server