What is new with EDB360?

Many things, but most important is that it got bigger and better. This EDB360 free tool provided is maturing over time. Its core function has not changed although, which is to present a 360-degree view of a database (10g or higher).

EDB360 is a nice complement to other tools like Exacheck, Raccheck or Oracheck. It has some additional benefits, like taking a snapshot of a system to then be analyzed offline or simply to preserve this snapshot as a baseline.

Keep in mind that EDB360 does not install anything on the database, nor it changes any data on it. In some cases, where direct access to the database server is not an option, having the capability of executing EDB360 through a SQL*Plus client connection is a big plus.

I use EDB360 as a starting place to perform a whole database health-check.

Since pictures tell more than words, please find below 4. The first two are about the new entries on EDB360 main menu (menu is a tad bigger than what you see in these two pictures, and its content is dynamic). The last two pictures are just a sample of the charts that are now part of EDB360.

EDB360 execution parameters changed from 4 to 6:

Oracle Pack License: If your site has the Tuning Pack, then enter ‘T’, else if your site has the Diagnostics Pack enter ‘D’, else enter ‘N’.
Days of History to consider. If you entered ‘T’ or ‘D’ on first parameter, then specify on 2nd parameter up to how many days of history you want EDB360 to use. By default it uses 31, assuming your AWR history is at least that big.
Do you want HTML Reports? By default it is ‘Y’.
Do you want Text Reports? Defaults to ‘Y’.
Do you want CSV Files? Defaults to ‘Y’.
Do you want Charts? Defaults to ‘Y’.

Once you login into SQL*Plus while on top of the edb360 directory, simply execute script edb360.sql and pass all 6 parameters one by one or all of them inline. For example: @edb360 T 31 Y Y Y Y

EDB360 Dynamic Menu (part 1)

EDB360 Dynamic Menu (part 2)

CPU Load per Instance (sample chart)

ASH Top Modules and Actions for Cluster (sample chart)

If you have downloaded EDB360 before, then I encourage you to download and test the new version. If you have never used it, I hope you find this tool useful.

Written by Carlos Sierra

April 2, 2014 at 10:04 am

Posted in Active Session History, ASH, AWR, edb360, Health-Checks, Scripts, Tools

9 Responses

Subscribe to comments with RSS.

This just keeps getting better!

spbutterworth

April 2, 2014 at 4:08 pm

Reply
Question about the packs .. what if you have both Tuning and Diagnostics.. is one better than the other in terms of this tool? Should I use T or D?

darylerwin

April 3, 2014 at 4:25 pm

Reply
- If you have both Tuning and Diagnostics pass T
  
  Carlos Sierra
  
  April 3, 2014 at 5:39 pm
  
  Reply
Reblogged this on L1dge’s Weblog and commented:
Worth a look….

l1dge

April 5, 2014 at 4:39 pm

Reply
Carlos,

With the latest version I was getting the following error:
SP2-0310: unable to open file “sql/Yedb360_one_pie_chart.sql”

I assume a Y got into the code somehow and just linked the one without it to that name and all is well. Just thought you should know.

Thanks for this outstanding tool!

Bryan

Bryan

April 16, 2014 at 8:49 am

Reply
- Bryan,
  
  That error is intentional. That is the way to skip a script. On next version I am hiding those messages.
  
  Carlos Sierra
  
  April 16, 2014 at 8:56 am
  
  Reply
[…] What is new with EDB360? […]

Some eDB360 Frequently Asked Questions | Carlos Sierra's Tools and Tips

January 7, 2015 at 2:56 pm

Reply
any reason why edb360 would be getting stuck here?:

SELECT TO_CHAR(ROWNUM) row_num, v0.* FROM /* 2d.189 */ (
SELECT /*+ NO_MERGE */ /* 2d.189 */
*
FROM v$backup_set_details
ORDER BY
1, 2, 3, 4, 5
) v0 WHERE ROWNUM <= 10000
1 SELECT TO_CHAR(ROWNUM) row_num, v0.* FROM /* 2d.189 */ (
2 SELECT /*+ NO_MERGE */ /* 2d.189 */
3 *
4 FROM v$backup_set_details
5 ORDER BY
6 1, 2, 3, 4, 5
7* ) v0 WHERE ROWNUM <= 10000
RMAN Backup Set Details

ONE_SPOOL_FILENAME
————————————————–
00211_edb360_939093_2d_189_rman_backup_set_details
HH_MM_SS
——–
19:19:34
19:19:34 2d “00211_edb360_939093_2d_189_rman_backup_set_details.html”

Michael Fontana

July 18, 2016 at 9:18 pm

Reply
- I’d be looking at control file record keep time – and the number of individual RMAN backup sets that have taken place – that combined with the complexity of each set might contribute to an elongated run time – but not its failure – looks like a user-generated interrupt.
  
  Stephen Butterworth
  
  July 18, 2016 at 9:39 pm
  
  Reply