There are two ways to compare one database to another in the AWR Warehouse. I covered the ADDM Comparison Report here and now we’ll go through the second one, which is much more involved and has us empowering the AWR Warehouse taking two AWR Warehouse reports and comparing two databases to each other. The AWR Warehouse, once setup and databases that are targets already monitored by your EM12c or EM13c environment, can then be added and upload all AWR snapshots to this central repository. Comparison Period Report The AWR Warehouse second comparison reporting option is accessible from the drop down…
-
-
A lot of my ideas for blog posts come from questions emailed to me or asked via Twitter. Today’s blog is no different, as I was asked by someone in the community what the best method of comparing databases using features within AWR when migrating from one host and OS to another. There is a lot of planning that must go into a project to migrate a database to another host or consolidate to another server, but when we introduce added changes, such as a different OS, new applications, workload or other demands, these need to be taken into consideration.…
-
This issue can be seen in either EM12c or EM13c AWR Warehouse environments. It occurs when there is a outage on the AWR Warehouse and/or the source database that is to upload to it. The first indication of the problem, is when databases appear to not have uploaded once the environments are back up and running. The best way to see an upload, from beginning to end is to highlight the database you want to load manually, (click in the center of the row, if you click on the database name, you’ll be taken from the AWR Warehouse to the…
-
As I’m playing with the AWR Warehouse in EM13c, I noticed a few changes that may send up a red flag and wanted to assist in removing those. As many know, the AWR Warehouse is very dependent upon EM Jobs…even more so now that we’ve moved to EM13c. The EM Job System has gone through quite an overhaul, so let’s go through how this may impact what you’re common to seeing when adding a database to the AWR Warehouse. Discovery After adding a database to the AWR Warehouse in EM13c, you’ll note within just a few minutes, the database will…
-
There may be a reason that one needs to re-add a database to the AWR Warehouse. This is a new opportunity for me to learn and offer assistance, but I’m working off the grid to figure out a solution. Luckily, it’s just a matter of creating a new process from pre-existing code and processes. The process requires both the AWR Warehouse UI and a SQLPlus connection. 1. Disable the snapshots 2. Extract the AWR for the Database 3. Drop the database from the AWR Warehouse 4. Add the database back into the AWR Warehouse with the retention time or any…
-
When sizing the AWR Warehouse, one of my requirements is to have certain reports for a sampling of databases that will source the AWR Warehouse. This report provides me the right information to create the correct sizing requirements vs. any assumptions done with other choices. The report is the General AWR Information report and can be found in the $ORACLE_HOME/rdbms/admin directory. It provides the following information: Time of Report AWR Retention and interval settings, including if non-default setting. Schema percentage of space used in the SYSAUX tablespace. Objects and space consumption in the SYSAUX tablespace, including breakdown of the AWR space…
-
A common issue I’ve noted are dump files generated from the AWR Warehouse, but upon failure to transfer, the dumpfiles simply exist, never upload and the data is stuck in a “limbo” state between the source database, (target) and the AWR Warehouse. This can be a very difficult issue to troubleshoot, as no errors are seen in the actual AWR Warehouse “View Errors” and no data from the source is present in the AWR Warehouse. Empowered by EM Jobs If you go to Enterprise –> Jobs –> Activity and inspect the Log Report after a search for %CAW% jobs that perform…
-
Mauro decided to give me another challenge- run SQLd360 against the AWR Warehouse and let him know how it does straight “out of the box”. It’s a simpler installation process than SQLTXPLAIN, you simply unzip and run, (no installation of any packages…) I chose a SQL_ID from one of the source databases loaded and ran it for a 31 day history: SQL> @sqld360.sql 8ymbm9h6ndphq T 31 I saw a few errors scroll by on the screen as the process to collect the data and zip it up ran. There isn’t the same log file to see on successful runs to…
-
I finally have a moment to look into my “hacked” SQLT XPRECT/XTRACT runs and see if the changes I made were enough to run properly with the AWR Warehouse. The answer is yes and no… and maybe “it depends”… 🙂 The Results The data from the AWR Warehouse to pull the corresponding data for the appropriate SQL_ID from the correct source database in the AWR repository worked, but the environment information still populates incorrectly, as I didn’t update anything outside of the get_database_id function in the SQLT$A package and the executables that call it, as documented in my earlier blog…
-
Yeah, so I did it- I installed SQLTXPLAIN, (SQLT) on the AWR Warehouse! From previous experience with this fantastic tool, I was pretty sure I’d have some great new adventures with the AWR Warehouse data and I wanted to try and test out the AWR pieces of this tool with the Warehouse. This is a work in progress, so I’m going to do this blog in multiple parts to ensure we don’t miss anything. Installation I didn’t expect SQLT AWR features to work out of the box. I still needed to install it, run a few reports and see what would…