From the Execution Console you can select an entry point (for packages), enter the parameter input values, and choose various run options, such as profiling and directing the results to DBMS_OUTPUT.

The Execution Console helps you set various parameters for wrapping an anonymous block around a stored program so that you can execute it. If you generate an anonymous block, the Console assigns a file name to your block in the form: <Schema name>.<procedure name>.STB. If the anonymous block is for a packaged procedure, then the assigned name has an additional component—the entry point.

Note: If an error occurs when trying to run a generated code block (for example, due to a syntax error), the text is opened in the Output Window.

Run Time Parameters

Option	Description
Parameter	Name and type of each input parameter.
Input	Define input values for each parameter. Field Description Def Select to use the default input value. Null Select to use a Null input value. Exp Select to use a PL/SQL Expression. Value/Expression When Exp is selected, enter a value or expression in the Value/Expression column.
Load/Save	Click to load the input parameter values from an external file.
Save	Click to save the input parameter values to an external file.
Reset	Click to Reset changes to the parameter values.

 

Run Options

Command	Description
Auto-create test case after code execution	When selected a test case is automatically created (when you click Execute) based on the parameter values (both input and output) currently displayed in the grid. For more information, see Code Test.
Use Profiler	Select to use the PL/SQL Profiler. Analyze the execution time and efficiency of your stored programs. Click (...) to open the Profiler Options dialog. Option Description Collect Session Statistics when Creating the Profiling Run Select to store session statistics in a table. Before Creating the Profiling Run … Select when measuring performance and tuning. Re-initialize the execution environment after a previous run, giving you a better basis for comparison between one run and another. For more information, see PL/SQL Profiler.
Direct results to Output	Select Generate a DBMS_OUTPUT PUT statement for each OUT parameter. Clear Generate a Bind variable for each OUT parameter. This is useful when you want to view complex data returned by the procedure, such as REF cursors and LOBs. For more information, see DBMS_OUTPUT.
Include exception block	Select to populate the Exception block when the Stub tab is generated. TIP: Click Preview to generate the Stub tab.
Commit changes after code execution	Once the procedure has finished executing, do you want to COMMIT / ROLLBACK changes made by the procedure?
Preview	Show the code to be executed. Note: This generates the Stub tab. For more information, see PL/SQL Stub. Toggle between the Code / Run / Stub tabs at the bottom of the screen.
Execute	Execute the PL/SQL code. If Use Profiler is selected, opens PL/SQL Profiler.

 

Code Test

The Code Test panel automates the process of testing PL/SQL programs. See also the module: Code Test.

Command	Description
Test Case	Select the test case to work on.
In/Out	Display the in/out parameters and associated values for the selected test case.
New	Create a test case. Open Test Case Properties
Edit	Edit the selected test case. Open Test Case Properties
Delete	Delete the selected test case.
Test > Param	Upload the selected test case into the parameters.
Param > Test	Update the selected test case with the current parameters.
Manage	Clone and edit existing test cases, create new test cases and run multiple test cases at once. Open Code Test
Run Test	Run the selected test case. The result of the test is displayed in the Test case status pane.
Run All Tests	Run all code tests available for the current object.