Upgrade? What's New In Stori 2j

Posted on 29-Oct-2013 by Craig Shallahamer, craig@orapub.com

Upgrade? What's new in Stori 2j

We are pleased to announce the new Stori release, 2j! In summary, Stori has undergone a capability and stability update paving the way for a future Windows port and referencing AWR data. Yes, we are excited too!

1. Download the Stori 2j here:

http://stori.orapub.com/Stori_Downloads.html

Look for the 2j release near the top. If you don't see it, refresh your screen. You can get a StoriFree license here

2. Quick and Flexible Scope Change

Customers wanted a way to automatically and periodically run an analysis each day during peak times. Key to this is easily setting the analysis scope and using the Playback facility. So we enhanced the set scope command.

Like a Statspack report, Stori references Statspack data within a selected snapshot range. Stori now has the capability to set the scope a number of different ways beside the traditional interactive step-by-step approach. The new options are 100% automated, which means they can be scripted into a Playback file. Here are some set scope examples:

set scope yesterday   1430 60
set scope today       1430 60
set scope 12-Jul-2012 1430 60
set scope snap_ids 105 115
set scope latest

The first three examples are setting the start time to 1430 with a duration of 60 minutes, but at various days. Example four is a nice when you know the snap_ids. Example five is perfect when you are scripting a Statspack snap followed by an analysis. This is detailed below.

Here is how you can use this. Suppose peak time is between 10am to noon and when you arrive back from lunch you want a short performance summary in your inbox. Place the below commands into a Playback file, then either run the Playback File manually or via cron.

set scope today 1000 120
analyze summary

That's it! This is a good example of how Stori can perform a periodic, automated and advanced analysis.

3. Do a Statspack Snap Within Stori

Customers wanted a way for Developers to analyze their recent work in a QA environment. For example, suppose a key module was changed and placed into QA and later (we all hope) production. Here is one way to on-the-fly analyze the situation.

start statspack snap
pause 300
start statspack snap
set scope latest
analyze summary

In fact, you can place the above commands into a Stori Playback file (e.g., snap_anal.pbf) and execute it like this:

storiLin64 -pbf snap_anal.pbf

or from within Stori ask, start pbf snap_anal.pbf

That's all you need to do! This is a good example of Stori proactive performance management.

3. Stability and Performance Improvements

Would you contract a consultant to analyze performance on an unloaded system? Sometimes new Stori users and prospects install Stori on an unloaded test machine and ask for an analysis. In rare cases Stori would crash because of a zero load situation...not real impressive! So the development team went through all the code to ensure a zero load situation would not cause a problem. Obviously we are encouraging DBAs to test Stori in real world situations so Stori can shine! We also improved performance in the more intensive analysis functions. Finally, the 2j development and QA environments are now running Oracle 12c!

We hope you have a chance to experience the new Stori release. If you have any questions or would like more information, contact us.

All the best in your Oracle database performance tuning work!

Craig.

If you have any questions or comments, feel free to email me directly at craig at orapub.com.

How To See Unseen Activity Using ASH And SQL*Net Message From Client Watching An Oracle Buffer Over Time Altering Oracle Database DML Batch Sizes (Log File Sync) - Part 2