The Database Probe in Toad for Oracle does not show any statistics (4230185)

The Database Probe in Toad for Oracle does not show any statistics. I want to analyze related files and data in Toad for Oracle, but information is blank even after refreshing the data.

See Screen Shot: DB Probe Blank.doc

RESOLUTION 1:

This Toad feature is only available in the commercial version of Toad that has the DBA module installed.

To see if you have the DBA module go to Help | About and verify that DBA is listed under your options.

RESOLUTION 2:

Please note there are certain V$ tables you need permission to run this tool.

The following public synonyms must be present as well:

V$ARCHIVE_PROCESSES
V$BH
v$buffer_pool
V$buffer_pool_statistics
v$database
v$dispatcher
V$INSTANCE
v$librarycache
v$library_cache_memory
V$LOG
V$LOG_history
V$PARAMETER
v$pq_slave
v$process
V$ROWCACHE
v$session
V$SESSTAT
v$sga
v$sgastat
V$STATNAME
v$sysstat
v$version

RESOLUTION 3:

Minimum Oracle Database Requirements
Note: This extended Toad feature is only available in Toad for Oracle editions that include debugging functionality.

For all databases, you must have the Oracle Probe API v2.0 or later installed in order to debug PL/SQL using Toad.

To check the Oracle Probe API version:

1. Make sure a packaged called DBMS_DEBUG exists in the SYS schema.
To find out what version of the Probe API you have, run the following anonymous PL/SQL block in the SQL editor with a DBMS Output window tab selected:

declare
probe_major_ver varchar2(10);
probe_minor_ver varchar2(10);
begin
dbms_debug.probe_version(probe_major_ver, probe_minor_ver);
dbms_output.put_line('MAJOR='||probe_major_ver);
dbms_output.put_line('MINOR='||probe_minor_ver);
end;

2. If the DBMS Output window appears:

MAJOR=2
MINOR=2

Then the version of Oracle Probe API is 2.2.

NOTE: Issues with Database versions. The Debugger works on the following database versions with the following caveats:

Database Version Notes
Oracle Version Notes
 
Oracle 7.3.4
1. For the Call Stack to display, you must set the BLANK_TRIMMING value to TRUE in the init.ora Oracle Initialization parameters file and restart your database. Otherwise, you will receive a load error invoking the Call Stack window.

*******************************

Oracle 8
1. BLANK_TRIM requirement also refers to databases 8.0.4 and 8.0.5.The PL/SQL Debugger works without issues on Oracle8 databases.
 
Oracle 8i
1. No notes or issues. The PL/SQL Debugger works without issues on Oracle8i databases.

*******************************

Oracle 10g
1. You must have the DEBUG CONNECT SESSION privilege, or Oracle will not let you use DBMS_DEBUG.

2. On 10g and above the dba needs to run stats on data dictionary and static tables. The commands are as follows:

exec dbms_stats.gather_dictionary_stats;
exec dbms_stats.gather_fixed_objects_stats;
 

ADDITIONAL NOTES:
You cannot use the Evaluate/Modify window to change argument values.

On Oracle 7 databases, if you receive "Debugger is not responding" message, comment out all DBMS_OUTPUT statements and then recompile, and use watches to display the values. Also uncheck Enable DBMS Output before every debugging session. Watches on package variables are only allowed for Probe v2.2 or higher.