Debug mode enables you to track down unexpected application behavior. This section describes how to enable and disable debug mode, access debug mode using f?p syntax, and view debug reports.
Topics:
See Also:
"APEX_DEBUG" in Oracle Application Express API Reference
The Debug mode is a built in mechanism used to track down unexpected application behavior. You enable and disable debug mode for the current page and session by clicking the Debug and No Debug links in the Runtime Developer Toolbar. To view Debug reports, click the View Debug link in the Runtime Developer Toolbar.
If an application runs in debug mode, Oracle Application Express writes information about how it processes each page request to a log table. You can control the logging level of detail, add debug calls in your own code, and analyze the written log information.
When debug is enabled, Oracle Application Express also uses its non-minified JavaScript files to better isolate where possible issues may be coming from with client-side-code.
See Also:
"APEX_DEBUG" in Oracle Application Express API Reference
You can configure whether end users can run the application in debug mode by using the Debugging attribute on the Edit Application Definition page. A developer who is logged into workspace where the application resides can always run the application in debug mode.
To enable or disable debug mode:
See Also:
You run and disable debug mode at runtime by clicking Debug and No Debug on the Runtime Developer Toolbar. By default, Debugging mode is disabled, unless you are logged into the application's workspace as a developer.
To enable or disable Debug mode at runtime:
You can also use f?p
syntax to run an application in Debugging mode. Simply call the page and set the Debug argument to YES
or LEVEL
n
, where n is between 1 (least detailed) and 9 (most detailed). For example:
f?p=100:1:&APP_SESSION.::YES
See Also:
To view debug report from a running application: