1 2 Previous Next 21 Replies Latest reply on Jan 11, 2019 10:54 AM by Beauty_and_dBest

    EBS 12.1.3  OPP actual=0  target=5

    Beauty_and_dBest

      EBS 12.1.3

      11gR1

      OL6

       

       

      Hi ALL,

       

      Just today our end users complaining about their reports completed warning.

      I found out that OPP is not running   with status actual=0 target=0

       

      I already tried cmclean, and autoconfig,  but to no avail

       

       

      Please help....

       

       

      Kind regards,

      jc

        • 1. Re: EBS 12.1.3  OPP actual=0  target=5
          Kanda-Oracle

          Hi JC

           

          Can you share, Was it working fine ? Is it a production instance (or) newly created clone (or) TEST instance ?

           

          1. Please place the mouse on the OPP (Administer screen)

           

          1.1 Please click "Fixed" button and restart the concurrent manger. Let us know the status.

           

          2. Monitor AQ$ tables If the table is grown big.

           

            SQL> select count(*) from AQ$_FND_CP_GSM_OPP_AQTBL_H;

           

          3. Importantly check the Internal concurrent manager log file for any errors While starting OPP manager.

           

          4. Last but not the least...You need to check out FNDOPP log file for any

           

          When the OPP service would experience a serious exception (Out of memory for example) it would enter a state where it would no longer process requests, but

          would not shut down either. This patch would helps in such situations.

           

            Patch 16000609 - OPP IS UNSTABLE / UNRELIABLE

           

           

          Hope this helps!

           

          N Kandasamy

          • 2. Re: EBS 12.1.3  OPP actual=0  target=5
            Kanda-Oracle

             

            For more details..

            • 3. Re: EBS 12.1.3  OPP actual=0  target=5
              Beauty_and_dBest

              Thanks Kanda,

               

              I already bounced the apps and database many times.

              I remember, we encountered something like this before, and the solution was to purge a table. But I lost the documents

              Can you give me the steps to purge the table?

               

              [appmoli@molina2 ~]$ sqlplus apps/apps

               

              SQL*Plus: Release 10.1.0.5.0 - Production on Fri Jan 11 13:30:41 2019

               

              Copyright (c) 1982, 2005, Oracle.  All rights reserved.

               

               

              Connected to:

              Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production

              With the Partitioning, OLAP, Data Mining and Real Application Testing options

               

              SQL> select count(*) from applsys.FND_CP_GSM_OPP_AQTBL ;

               

                COUNT(*)

              ----------

                    8701

               

              SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_H;

               

                COUNT(*)

              ----------

                 1188859

               

              SQL>

               

               

               


              I saw in the FNDOPP logs

               

              [Full GC 42193K->14323K(57064K), 0.0693210 secs]

              [GC 29171K->22275K(53352K), 0.0254580 secs]

              [GC 37123K->29322K(53352K), 0.0296700 secs]

              [GC 44170K->30853K(53352K), 0.0185680 secs]

              [GC 45701K->30872K(53352K), 0.0036410 secs]

              [GC 45720K->30880K(53352K), 0.0008020 secs]

              [GC 45728K->31005K(53352K), 0.0016260 secs]

              [GC 45853K->31012K(53352K), 0.0017040 secs]

              [GC 45860K->31002K(53352K), 0.0013730 secs]

              [GC 45850K->31006K(53352K), 0.0010200 secs]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor84]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor98]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor94]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor86]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor100]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor97]

              [Unloading class sun.reflect.GeneratedMethodAccessor31]

              [Unloading class sun.reflect.GeneratedMethodAccessor45]

              [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor83]

               

               

               

              Kind regards,

              • 4. Re: EBS 12.1.3  OPP actual=0  target=5
                Kanda-Oracle

                Thanks! But you would need to try in APPLSYS user to get the query output

                • 5. Re: EBS 12.1.3  OPP actual=0  target=5
                  Kanda-Oracle

                  Thanks! But you would need to try in APPLSYS user to get the query output

                   

                   

                  Are you looking for the note 1156523.1 by any chance.

                   

                   

                  1 Refer (Doc ID 1156523.1) to purge

                  2 My suggestion: Do not use afopp002.sql to recreate the queue.

                  • 6. Re: EBS 12.1.3  OPP actual=0  target=5
                    Beauty_and_dBest

                    Ok I updated the result above.

                     

                    Why are the two tables differs in count?

                     

                     

                    Kind regards,

                    • 7. Re: EBS 12.1.3  OPP actual=0  target=5
                      Kanda-Oracle

                      around a million record in AQ$_FND_CP_GSM_OPP_AQTBL_H; you may refer my previous update.

                      • 8. Re: EBS 12.1.3  OPP actual=0  target=5
                        Kanda-Oracle

                        AQ$_FND_CP_GSM_OPP_AQTBL_H is a history table.You just ensure to purge at regular interval.

                         

                        Its documented in the note.

                        • 9. Re: EBS 12.1.3  OPP actual=0  target=5
                          Beauty_and_dBest

                          SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_S;

                           

                            COUNT(*)

                          ----------

                                 597

                           

                          SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_T;

                           

                            COUNT(*)

                          ----------

                               14159

                           

                          SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_H;

                           

                            COUNT(*)

                          ----------

                             1188859

                           

                          SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_I;

                           

                            COUNT(*)

                          ----------

                             1161937

                           

                          SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_G;

                           

                            COUNT(*)

                          ----------

                                   0

                          • 10. Re: EBS 12.1.3  OPP actual=0  target=5
                            Beauty_and_dBest

                            Hi Kanda,

                             

                            The notes said:

                             

                            Note: The following applsys.AQ$_FND_CP_GSM_OPP_AQTBL_x objects are also cleaned as part of the above purge.

                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_S
                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_T
                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_H
                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_I
                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_G
                            applsys.AQ$_FND_CP_GSM_OPP_AQTBL_L

                             

                             

                            Do I need to purge all the above one by one?

                             

                            Is it okay that the users are login or using the apps while purging?

                             

                             

                            Kind regards,

                            • 11. Re: EBS 12.1.3  OPP actual=0  target=5
                              Kanda-Oracle

                              Hi

                               

                              Its good if you need to keep the apps down. at least concurrent managers down. purge only those thats grown.. Just test in the test instance.

                               

                              Thanks!

                              • 12. Re: EBS 12.1.3  OPP actual=0  target=5
                                Beauty_and_dBest

                                Hi Kanda,

                                 

                                I already run the purge, but still the issue persist

                                SQL> select count(*) from applsys.FND_CP_GSM_OPP_AQTBL;

                                 

                                  COUNT(*)

                                ----------

                                         0

                                 

                                SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_S;

                                 

                                  COUNT(*)

                                ----------

                                       597

                                 

                                SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_T;

                                 

                                  COUNT(*)

                                ----------

                                         0

                                 

                                SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_H;

                                 

                                  COUNT(*)

                                ----------

                                         0

                                 

                                SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_I;

                                 

                                  COUNT(*)

                                ----------

                                         0

                                 

                                SQL> select count(*) from applsys.AQ$_FND_CP_GSM_OPP_AQTBL_G;

                                 

                                  COUNT(*)

                                ----------

                                         0

                                 

                                System Hold, Fix Manager before resetting counters

                                 

                                 

                                Please help....

                                • 13. Re: EBS 12.1.3  OPP actual=0  target=5
                                  Kanda-Oracle

                                  As i had mentioned, You would need to check the Internal concurrent manager log file for any errors While starting OPP manager... Based on the error you need to progress.

                                   

                                  if required stop and start concurrent manager with diag=y enabled.

                                   

                                   

                                  adcmctl.sh start apps/<passwd> diag=y

                                  • 14. Re: EBS 12.1.3  OPP actual=0  target=5
                                    Beauty_and_dBest

                                    Thanks Kanda,

                                     

                                    I did that and found the OPP logs as:

                                    I saw in the FNDOPP logs

                                     

                                    [Full GC 42193K->14323K(57064K), 0.0693210 secs]

                                    [GC 29171K->22275K(53352K), 0.0254580 secs]

                                    [GC 37123K->29322K(53352K), 0.0296700 secs]

                                    [GC 44170K->30853K(53352K), 0.0185680 secs]

                                    [GC 45701K->30872K(53352K), 0.0036410 secs]

                                    [GC 45720K->30880K(53352K), 0.0008020 secs]

                                    [GC 45728K->31005K(53352K), 0.0016260 secs]

                                    [GC 45853K->31012K(53352K), 0.0017040 secs]

                                    [GC 45860K->31002K(53352K), 0.0013730 secs]

                                    [GC 45850K->31006K(53352K), 0.0010200 secs]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor84]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor98]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor94]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor86]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor100]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor97]

                                    [Unloading class sun.reflect.GeneratedMethodAccessor31]

                                    [Unloading class sun.reflect.GeneratedMethodAccessor45]

                                    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor83]

                                     

                                     

                                     

                                    Can you guide me please where to find the error logs? or diagnostic logs?

                                     

                                    $ adcmctl.sh start apps/apps diag=y

                                     

                                    You are running adcmctl.sh version 120.17.12010000.5

                                     

                                    Starting concurrent manager for PROD ...

                                    Starting PROD_0111@PROD Internal Concurrent Manager

                                    Default printer is noprint

                                     

                                    adcmctl.sh: exiting with status 0

                                     

                                    adcmctl.sh: check the logfile /u02/appmoli/PROD/inst/apps/PROD_molina2/logs/appl/admin/log/adcmctl.txt for more information ...

                                     

                                     

                                     

                                    Kind regards,

                                    1 2 Previous Next