How to generate a PL/SQL Profiler from iStore?
(Doc ID 1429765.1)
Last updated on MARCH 31, 2020
Applies to:Oracle iStore - Version 18.104.22.168 to 12.2.8 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
While troubleshooting performance issues in iStore, such as Submitting Order, tkprof might show iStore PL/SQL wrapper API (IBE_QUOTE_W1_PVT.SubmitQuoteWrapper) as the most expensive statement.
Trace tkprof could show something like this:
IBE_Quote_W1_pvt.SubmitQuoteWrapper(x_return_status => :1, x_msg_count
=> :2, x_msg_data => :3, p_quote_headerid => :4, p_last_update_date
=> :5, p_minisite_id => :6, p_sc_book_flag => :7, x_last_update_date => :8,
x_order_number => :9, x_order_header_id => :10, x_order_request_id =>
:11, x_contract_id => :12, x_status => :13, x_hold_flag
=> :14 ); IBE_UTIL.reset_debug(); END;
This API calls so many other APIs, such as OM, QP and TAX APIs and potentially custom APIs. PL/SQL Profiler could help narrowing down to a specific API or a line of pl/sql code that is taking the most time. This document provides steps to enable and gather Profiler output. This document does not provide steps to install Profiler utility itself but has a reference to the document to do so.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document