Carlos Sierra's Tools and Tips

eDB360 has always worked under the premise “no installation required”, and still is the case today – it is part of its fundamental essence: give me a 360-degree view of my Oracle database with no installation whatsoever. With that in mind, this free tool helps sites that have gone to the cloud, as well as those with “on-premises” databases; and in both cases not installing anything certainly expedites diagnostics collections. With eDB360, you simply connect to SQL*Plus with an account that can select from the catalog, execute then a set of scripts behind eDB360 and bingo!, you get to understand what is going on with your database just by navigating the html output. With such functionality, we can remotely diagnose a database, and even elaborate on the full health-check of it. After all, that is how we successfully use it every day!, saving us hundreds of hours of metadata gathering and cross-reference analysis.

Starting with release v1706, eDB360 also supports an optional staging repository of the 26 AWR views listed below. Why? the answer is simple: improved performance! This can be quite significant on large databases with hundreds of active sessions, with frequent snapshots, or with a long history on AWR. We have seen cases where years of data are “stuck” on AWR, specially in older releases of the database. Of course cleaning up the outdated AWR history (and corresponding statistics) is highly recommended, but in the meantime trying to execute edb360 on such databases may lead to long execution hours and frustration, taking sometimes days for what should take only a few hours.

1. dba_hist_active_sess_history
2. dba_hist_database_instance
3. dba_hist_event_histogram
4. dba_hist_ic_client_stats
5. dba_hist_ic_device_stats
6. dba_hist_interconnect_pings
7. dba_hist_memory_resize_ops
8. dba_hist_memory_target_advice
9. dba_hist_osstat
10. dba_hist_parameter
11. dba_hist_pgastat
12. dba_hist_resource_limit
13. dba_hist_service_name
14. dba_hist_sga
15. dba_hist_sgastat
16. dba_hist_sql_plan
17. dba_hist_sqlstat
18. dba_hist_sqltext
19. dba_hist_sys_time_model
20. dba_hist_sysmetric_history
21. dba_hist_sysmetric_summary
22. dba_hist_sysstat
23. dba_hist_system_event
24. dba_hist_tbspc_space_usage
25. dba_hist_wr_control
26. dba_hist_snapshot

Thus, if you are contemplating executing eDB360 on a large database, and provided pre-check script edb360-master/sql/awr_ash_pre_check.sql shows that eDB360 might take over 24 hours, then while you clean up your AWR repository you can use the eDB360 staging repository as a workaround to speedup eDB360 execution. The use of this optional staging repository is very simple, just look inside the edb360-master/repo directory for instructions. And as always, shoot me an email or comment here if there were any questions.