Home Discussions Questions & Answers Finding Poorly Coded Concurrent Wait Calls in Packages

Finding Poorly Coded Concurrent Wait Calls in Packages

Avatar photoCustomer July 23, 2019 at 2:16 am

We discovered a common performance issue where developers incorrectly call `fnd_concurrent.wait_for_request` with a zero interval time in our custom packages. How can I perform a full text search through all database source code objects to find instances of this anti-pattern?

Viewing 4 reply threads
  • Author
    Replies
    • Support July 23, 2019 at 12:32 pm  

      Use the DBA Text Search report. This report performs a full text search through source code objects like packages, procedures, functions, and triggers.

    • Avatar photoCustomer July 23, 2019 at 4:20 pm  

      Since this is a specific function call with parameters, can the report handle a complex search pattern?

    • Support July 25, 2019 at 3:03 am  

      Yes, the search supports using regular expressions. For your specific example of calling `wait_for_request` with an interval of zero, you can input a multi-line regex search value like: `fnd_concurrent.wait_for_requests*(s*request_ids*=>s*w+s*,s*intervals*=>s*0s*,`.

    • Avatar photoCustomer July 26, 2019 at 4:56 am  

      If I need to search the definitions of all my current Blitz Reports, Parameters, or LOVs for a specific SQL text string, is there a tool for that too?

    • Support July 26, 2019 at 4:43 pm  

      Absolutely. Use the Blitz Report Text Search report. This report helps understand which reports, parameters, or LOVs contain a specific SQL text string, or which reports use a specific LOV.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: