1 2 Previous Next 20 Replies Latest reply on Jan 9, 2019 1:58 PM by J Reinhart

    Concurrent Request Time

    Ramaraju

      Hi All,

      Concurrent Program took 60 mins to complete. Can we track time for all the parts of that concurrent job?

      EBS: R12.2.7

      DB: 12.1.0.2

       

      Thanks,

      Ramaraju

        • 1. Re: Concurrent Request Time
          Kanda-Oracle

          Hi Ramaraju

           

          Please mention whether  requests stay in Pending/standby ; Pending/Normal (or) Running/normal for longer time ? Depends on that we need to progress.

           

          Thanks

          N Kandasamy

          • 2. Re: Concurrent Request Time
            Ramaraju

            The program completed successfully, but it took 1 hour. The developer want to know that which part of that program took more time.

             

            Thanks,

            Ramaraju

            • 3. Re: Concurrent Request Time
              Kanda-Oracle

              When the request took one hour, requests stay in either Pending/standby ; Pending/Normal (or) Running/normal for longer time

               

               

              • 4. Re: Concurrent Request Time
                Kanda-Oracle

                1.Pending/Normal  is a normal situation. As soon as a concurrent manager is available, this request will be picked up for processing.If it stays in the same status for longer time, then indicates that there is insufficient number of process. If you increase number of process you can reduce the time of pending/normal. Ensure you have sufficient RAM/CPU before increasing number of process as it will have additional load on your system.

                 

                2. Pending/Standby

                 

                It is waiting at conflict resolution manager (CRM ).

                 

                I) Either it could be due to CRM. Reduce the sleep time of CRM.

                II) Check any incompatible program is running longer time.

                • 5. Re: Concurrent Request Time
                  Kanda-Oracle

                  Hi,

                   

                  Please enable Database Trace ; If its running/normal for longer then it could Database level issue.

                   

                  Refer (Doc ID 1121043.1) ===> Steps to enable trace for Concurrent Requests: Request Level

                   

                  Thanks!

                  • 6. Re: Concurrent Request Time
                    Kanda-Oracle

                    Hi Ramaraju,

                     

                      You can manipulate the below columns in the fnd_concurrent_requests table to understand what was the status of the request. its helpful for your analysis.

                     

                    1. The difference between REQUESTED_START_DATE and actual_start_date is the time that the request was in Pending/Normal state.
                      • actual_start_date - requested_start_date - = Pending/Normal  (OR) Pending/Standby
                    2. actual_completion_date - actual_start_date  =  Running/Normal .

                     

                    Hope this helps!

                     

                    Thanks


                    N Kandasamy

                    • 7. Re: Concurrent Request Time
                      Ramaraju

                      Hi,

                      I have enabled trace and generated tkprof file.

                      Sort options: fchela 

                             1  session in tracefile.

                           119  user  SQL statements in trace file.

                            46  internal SQL statements in trace file.

                           165  SQL statements in trace file.

                           142  unique SQL statements in trace file.

                         19085  lines in trace file.

                            78  elapsed seconds in trace file.

                       

                      Total elapsed seconds are 78, but concurrent program took 1 hour.

                       

                      https://ufile.io/4mwke

                       

                      Thanks,

                      Ramaraju

                      • 8. Re: Concurrent Request Time
                        Kanda-Oracle

                        As mentioned,  You can manipulate the columns in the fnd_concurrent_requests table to understand how long it stayed in particular status

                         

                        Pending/Normal  (OR) Pending/Standby

                          Running/Normal .

                        • 9. Re: Concurrent Request Time
                          Ramaraju

                          Hi,

                          The difference between REQUESTED_START_DATE and actual_start_date is the time that the request was in Pending/Normal state.

                          actual_start_date - requested_start_date - = Pending/Normal  (OR) Pending/Standby

                          1/7/2019 2:06:43 - 1/7/2019 2:06:11 = 32 sec

                           

                           

                          actual_completion_date - actual_start_date  =  Running/Normal

                          1/7/2019 3:13:48 - 1/7/2019 2:06:43 = 67mins 5sec

                           

                           

                          Thanks,

                          Ramaraju

                          • 10. Re: Concurrent Request Time
                            Kanda-Oracle

                            Hi Ramaraju,

                             

                            It has been in Running/Normal for longer time. So the trace should reflect the delay. But it does not...

                             

                            It could be due to OPP processing. Can you check the concurrent request log to see any OPP processing took longer time.

                             

                            Hope this helps  !

                             

                            Thanks


                            N Kandasamy

                            • 11. Re: Concurrent Request Time
                              Ramaraju

                              How to check that?

                              • 12. Re: Concurrent Request Time
                                Kanda-Oracle

                                Please check the concurrent request log file . That would have all the details to progress further.

                                • 13. Re: Concurrent Request Time
                                  Ramaraju

                                  Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.

                                   

                                   

                                  XXNP_EDI_832_846_EXPRO: NTRS EDI 832 and 846

                                  +---------------------------------------------------------------------------+

                                   

                                   

                                  Current system time is 07-JAN-2019 02:07:33

                                   

                                   

                                  +---------------------------------------------------------------------------+

                                   

                                   

                                  **Starts**07-JAN-2019 02:07:33

                                  **Ends**07-JAN-2019 03:14:38

                                  +---------------------------------------------------------------------------+

                                  Start of log messages from FND_FILE

                                  +---------------------------------------------------------------------------+

                                  fnd_trace start_trace...identifier: 0107_020643 sid/serial/module/action: 241/41084/e:EC:cp:ec/XXNP_EDI_832_846_EXPRO/EC/EDI_GATEWAY_CAN

                                  SET_IDENT_FOR_SESS: user: VPKTR, requestID: 74081379

                                  FND_TRACE.start_trace: Enabling trace

                                  832/846 GENERATION PROGRAM   V8.2  07-JAN-19

                                              Location ID - 1622526

                                              Cust Site Use ID - 1622526

                                              Transaction Type - 846

                                              File Gen Type    - F

                                              Cust Name - BOUTIK INFORMA / MARCO MICHAUD INFORMATIQUE INC

                                              Default Warehouse - 125

                                      Opening Temp Filename - /DEV/Outbound/AXX846F-1622526-74081379-20190107030859.txt

                                  SYSBSCAGM4846FBSCAGM43438                   P  ORG124

                                  07-JAN-2019 03:13:43  Output Completed - Line Count : 78119

                                  07-JAN-2019 03:13:43  Write FTR record

                                  07-JAN-2019 03:13:43  Close Filename - /DEV/Outbound/AXX846F-1622526-74081379-20190107030859.txt

                                  07-JAN-2019 03:13:48  Renaming Filename - /DEV/Outbound/AXX846F-1622526-74081379-20190107030859.txt  to  /DEV/Outbound/EDI846F-1622526-74081379-20190107030859.txt

                                  07-JAN-2019 03:13:48  File Rename Completed

                                  +---------------------------------------------------------------------------+

                                  End of log messages from FND_FILE

                                  +---------------------------------------------------------------------------+

                                   

                                   

                                   

                                   

                                  +---------------------------------------------------------------------------+

                                  No completion options were requested.

                                   

                                   

                                  Output file size:

                                  0

                                   

                                   

                                   

                                   

                                  Output is not being printed because:

                                  The print option has been disabled for this report.

                                  Deleting empty output file.

                                   

                                   

                                  +---------------------------------------------------------------------------+

                                  Concurrent request completed successfully

                                  Current system time is 07-JAN-2019 03:14:38

                                   

                                   

                                  +---------------------------------------------------------------------------+

                                  1 2 Previous Next