PL/SQL Program Refresh Behavior

When you debug a PL/SQL program, Oracle Developer Tools makes sure that the most updated version of the PL/SQL program is refreshed from the database.

If you have modified the PL/SQL program being debugged, but not saved it to the database (known as a dirty PL/SQL program), a Yes/No dialog box shows up to prompt you to save the PL/SQL program to the database before debugging. If you select Yes, the PL/SQL program is saved to the database and debugging starts. If you select No, debugging is not allowed.

In a scenario where a saved PL/SQL program is being debugged, and it calls a dirty PL/SQL program, the execution stops at the dirty PL/SQL program. An OK dialog box appears indicating that the called PL/SQL program has been modified and debugging might not work properly. When you click OK, the execution stops at the called (dirty) program.

Be aware that the source code might not be synchronized during debugging because the PL/SQL program has been modified.