Oracle Debugging Tips using Oracle SQL Developer

This tutorial has been written using Oracle installed on an Ubuntu/Linux operating system (Ubuntu 10.04 Lucid Lynx). The version covered in this tutorial is Oracle Database 10g Express Edition Release 10.2.0.1.0.

Debugging Flow

To have a better understanding of the role debugging plays in the Oracle database implementation process, we must start with the design. For starters, database team members are provided with a project from their company to create a database. The first thing they will do is complete the database specifications. These includes what tables need to be created, as well as what fields and their corresponding data types.

Once the specification has been completed, it will then be forwarded to a group of programmers that will write down the database scripts or PL/SQL procedures needed to accomplish the project objectives and specifications.

Before handing it over to the database administrator for implementation, the scripts are tested and compiled for debugging with the test database server. The purpose of this is to identify any errors.  The Oracle debugging process is then started and once the script is clean and final it will be submitted to the database administrator.

The database administrator will then review the code for any additional suggestions or corrections and finally upload it to the company database server. Once uploaded, the database administrator will then run the script. And since it is now clean it will run without any errors.