BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation








Automating Oracle

Oracle Tips by Mike Ault

Automated Statistics Gathering

The actual code for the full DBMS_REVEALNET.RUNNING_STATS procedure runs to 12 or more pages and reports on up to nearly a hundred statistics (some are based on latch statistics or contention statistics so the exact number monitored changes). The private procedure write_out contained in the master procedure RUNNING_STATS uses one of two tables, Remote DBA_RUNNING_STATS or Remote DBA_TEMP to hold all of the retrieved values. If the “is_interactive” flag is set to TRUE the Remote DBA_TEMP table is used. If the “is_interactive” flag is set to the default, FALSE, then the Remote DBA_RUNNING_STATS table is used. The Remote DBA_TEMP table only holds one set of values and is deleted before use. The Remote DBA_RUNNING_STATS table keeps an ongoing set of statistics taken at whatever interval is desired (usually 15 minutes). This allows the procedure to double duty, either as an instant monitor script (when combined with a SELECT against the Remote DBA_TEMP table) or as a background statistics collection script.

Using the DBMS_JOB.SUBMIT procedure, the command to submit the RUNNING_STATS procedure to the job queue would be:



Notice how the BEGIN-END; block structure is used. This block structure is used to prevent some problems that have been reported when a straight procedure call is made to the job queue. Notice that the interval is specified as a character string: ’SYSDATE+(15/14440)’ that evaluates to a future date. The interval will tend to creep unless the string is specified using concatenated date values. Also notice how the value for “is_interactive” is specified, even though it will default to FALSE, this is to reduce confusion when the job is viewed using the Remote DBA_JOBS view.


For more information on this topic, I recommend Don Burleson's latest book "Oracle Tuning: The Definitive Reference". 

You can buy it direct from the publisher for 50%-off and get instant access to the code depot of Oracle tuning scripts:


Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.



Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software







BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.

Hit Counter