Gitora Editor includes a PL/SQL debugger. For the PL/SQL debugger to work, the database session being debugged must be able to access the debugger. This requires you or your DBA to open a port or a range of ports in your Oracle database. To achieve this, follow the steps below:
- Execute the script at
gitora/GITORA_DEBUGGER_ACL_SCRIPT.sqlin the zip file, for every database user that you’d like to use with the debugger. The script is a very small PL/SQL code block:
begin
DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(
host => '192.168.1.42',
lower_port => 4000,
upper_port => 4999,
ace => xs$ace_type(privilege_list => xs$name_list('jdwp'),
principal_name => [ORACLE_USER_NAME],
principal_type => xs_acl.ptype_db));end;
Replace the [ORACLE_USER_NAME] in the text above with the actual name of the Oracle user that you want to be able to use with the debugger and execute the script. Run this script once for every Oracle user that needs to be able to connect to the debugger.
Change the start and end port numbers (both inclusive) as you see fit.
- Update the following parameters in the
Settings.propertiesfile.
debug.port.range.start: Set this value to the same value you used for the lower_port input parameter.
debug.port.range.end : Set this value to the same value you used for the upper_port input parameter.
debug.server.ip: This is the IP address of the Apache Tomcat server that is running the Gitora Editor web application. This is NOT your desktop’s IP address (although it could be if you are running Gitora locally.) This IP address will be used by the Oracle database session to be able to find and connect to the Gitora debugger.
Below is an example of how the three parameters are set:
debug.port.range.start = 4000debug.port.range.end = 4999debug.server.ip = 192.168.1.42