This section describes approaches to debugging your application including viewing Debug Mode, enabling SQL tracing, viewing page reports, and how to manually remove a control or a component to isolate a problem.
This section contains the following topics:
For applications having a large number of concurrent users, maintaining optimal performance is critical. To optimize your application's performance, remember to utilize the following Oracle HTML DB features:
Use bind variables within your application whenever possible. You can reference session state values using bind variable syntax in SQL queries and application logic such as PL/SQL executed from processes and validations. Accessing session state using bind variables is the most efficient way to reference session state.
Include a #TIMING# substitution string in the region footer so that you can view the timing of each region.
Many applications are based on data contained within application controls. For example, buttons may display conditionally based on a value stored in session state. You can view current session state for your application by clicking the Session link on the Developer Toolbar.
Viewing a page in Debug Mode enables you to track what the HTML DB engine is doing as it renders a page. You access Debug mode by clicking the Debug link in the Developer Toolbar.
Debug Mode displays time codes that correspond to specific HTML DB engine actions. This can be useful if you want to determine when the engine is setting session state. The Debug view also shows additional details about item names and computation and processing points. To exit Debug mode, click No Debug in the Developer Toolbar.
You can also use f?p syntax run an application in Debug mode. Simply call the page and set the Debug argument to YES. For example:
f?p=100:1:&SESSION::YES
Tracing your session can be a very effective way to debug an application. From a database perspective, each page request is a single database session. If you enable SQL tracing, then Oracle HTML DB creates a temporary file you can then analyze using the TKPROF utility.
You enable SQL tracing in Oracle HTML DB by using f?p syntax to set the argument p_trace=YES. For example, to trace the display of page 1 in application 100 you would use the syntax:
http:/.../f?p=100:1&p_trace=YES
To use the TKPROF utility:
Navigate to the directory in which the trace file is created.
Type the following to view instructions about using TKPROF utility:
tkprof help=yes
|
See Also: Oracle Database Performance Tuning Guide for information about using the TKPROF program or contact your database administrator |
Oracle HTML DB facilitates the monitoring of resources used by applications and pages by calling the package DBMS_APPLICATION_INFO. Whenever the HTML DB engine renders or processes a page, the module is set to HTML DB and includes the application ID and page ID. Once set, you can query the V$SESSION and V$SQLAREA views to monitor transactions.
When isolating an issue within a page, it is important to clearly understand the functions it is performing. To accomplish this goal, Oracle HTML DB includes a number of page and application reports.
To view page reports:
Navigate to the appropriate Page Definition:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
Click one of the following buttons at the top of the Page Definition:
Event View links to a report that details currently defined page controls and processes.
Object References displays a list of database objects referenced by the current page.
History displays a history of recently changed pages.
To view application reports:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
From the Tasks list, select View Application Reports.
Select the type of reports to view:
Shared Components reports offer information on common elements that can display or be applied on every page within an application. Report examples include Application Comments, Breadcrumb Entries, Database Object Dependencies, Lists of Values, Static Entries, and Messages.
Page Components reports offer detailed information on controls and logic that execute when the page is rendered (for example, branches, buttons, computations, items, and regions).
Activity reports offer details about developer activity within the current application. Available reports include Changes by Developer, Changes by Developer by Day, Chart of Changes by Developer, and Recent Changes.
If your query does not seem to be running correctly, try running it in SQL Plus or in SQL Workshop. Either approach will test your query outside of the context of your application, making it easier to determine what the problem is.
If you have problems running a page, try removing controls and components one at time. Using this approach, you can quickly determine which control or component may be the source of your problem. You can disable a control or component by selecting the Condition attribute Never.
To remove a control or component using conditional attributes:
Navigate to the appropriate Page Definition:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
Select the name of the control or component you want to disable.
The appropriate attributes page appears.
Scroll down to Condition Type and select Never from the Condition Type list.
Click Apply Changes and return to the Page Definition.
Try running the page again.
Continue to remove controls or components until the page runs correctly.