6 Replies Latest reply on Mar 22, 2017 1:57 AM by Beauty_and_dBest

    OPP often get dead?

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.1.3

      11gR1

      OL5

       

      We often encountered issue of our OPP manager   actaul != target 

      How do you "tune" this OPP issue? This causes > Concurrent Requests takes too long to finished.

      Per checking, this morning, the actual and target values for output post processor were not equal.

      a.gif

      running the ps -ef | grep OPP, there are 3 processes

      a2.gif

      checking from back-end and running this query there are only 2 records (1 Active and 1 Inactive)

      a3.gif

      We have  killed the runaway processes that was not in the result of the query which is PID 28385.

      After that, the actual and target processes became equal.

      And running the query again, there are now 3 records queried but one of them is still INACTIVE.

      a4.gif

      And still, Concurrent Requests takes too long to finished. Is it because one OPP is still INACTIVE?

       

       

      Please help....

       

      Kind regards,

      jc

        • 1. Re: OPP often get dead?
          mdtaylor

          Hi jc,

           

          Open the Output Post Processor (OPP) manager logs and review the errors present which are killing the concurrent managers.

           

          R12: Troubleshooting Known XML Publisher and E-Business Suite (EBS) Integration Issues (Doc ID 1410160.1)

          BI Publisher - Troubleshooting Oracle Business Intelligence (XML) Publisher For The Oracle E-Business Suite (Doc ID 364547.1)

          R12: AP: One Or More Post-processing Actions Failed. Consult The OPP Service Log For Details. (Doc ID 2147972.1)

           

          You may need to setup OPP temporary file directory or increase RAM for OPP.

           

          Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError" (Doc ID 1266368.1)

          How to Configure the Planning Detail Report in Release 12 for Large Reports (Doc ID 1082672.1)

           

          Regards,

          Michael

          • 2. Re: OPP often get dead?
            Beauty_and_dBest

            Thanks Micheal,

             

            Of the 5 notes above, which is the best one to apply first

            or the nearest solution to our issue?

             

             

            Kind regards,

            • 3. Re: OPP often get dead?
              mdtaylor

              Hi jc,

               

              I am only guessing without seeing the actual errors from the OPP logs causing the failure, but expect from experience that the following will be useful:

               

              R12: AP: One Or More Post-processing Actions Failed. Consult The OPP Service Log For Details. (Doc ID 2147972.1)

              Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError" (Doc ID 1266368.1)

               

              Regards,

              Michael

              • 4. Re: OPP often get dead?
                Beauty_and_dBest

                Thanks Micheal,

                 

                We often encounter this java out of memory error. Last time our users (some only) can not login to the web login page and it seems related to java memory again

                Do they have the same context parameter to change? This OPP and Login?

                 

                <oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-server -verbose:gc -Xmx512M -Xms128M -XX:MaxPermSize=160M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC  -XX:ParallelGCThreads=2  -Dcom.sun.management.jmxremote -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doracle.security.jazn.config=/lv02/oracle/dev1213/inst/apps/dev1213_host/ora/10.1.3/j2ee/oacore/config/jazn.xml</oacore_jvm_start_options>

                 

                 

                Kind regards,

                • 5. Re: OPP often get dead?
                  mdtaylor

                  Hi jc,

                   

                  Increasing oa_core memory will fix login issues:

                   

                  <oacore_jvm_start_options
                  oa_var="s_oacore_jvm_start_options">-server -verbose:gc -Xmx2048M
                  -Xms2048M -XX:MaxPermSize=160M -XX:NewRatio=2 -XX:+PrintGCTimeStamps
                  -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=2
                  -Dcom.sun.management.jmxremote
                  -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy
                  -Djava.awt.headless=true -Dhttp.webdir.enable=false
                  -Doracle.security.jazn.config=/lv02/oracle/dev1213/inst/apps/dev1213_host/ora/10.1.3/j2ee/oacore/config/jazn.xml</oacore_jvm_start_options>

                   

                  You will still need to increase OPP memory:

                   

                  Increase OPP heap size:

                   

                  1. Determine what the heap size per OPP process is currently:

                   

                  select DEVELOPER_PARAMETERS from FND_CP_SERVICES

                  where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

                  where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

                   

                  2. The default should be:

                  J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

                   

                  3. Increase the Heap Space per Process to 2048:

                   

                  update FND_CP_SERVICES

                  set DEVELOPER_PARAMETERS =

                  'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m'

                  where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

                  where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

                   

                  Also ensure the following settings are in place:

                   

                  Large BI Publisher reports fails with ... manager has timed out waiting for the Output Post-processor to finish this request (Doc ID 1600688.1)

                   

                  And increase OPP timeouts:

                   

                  Optimal OPP Process / Response Timeout Profile Setting (Doc ID 2074181.1)

                   

                  Regards,

                  Michael

                  • 6. Re: OPP often get dead?
                    Beauty_and_dBest

                    Thanks Michael,

                     

                     

                    You are really an angel

                    I mean all the people here.