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

Finding Poorly Coded Concurrent Wait Calls in Packages

Avatar photoCustomer Questions & Answers 5 replies

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?

5 replies

  • Support Enginatics

    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

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

  • Support Enginatics

    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

    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 Enginatics

    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.

  • You must be logged in to reply to this post.