An Oracle blog about ZFS Storage

  • February 5, 2015

Oracle Storage Takes a Cue from Oracle Database

Guest Author

Oracle Intelligent Storage Protocol (OISP) version 1.1 was
recently announced along with Oracle ZFS Storage Appliance’s new OS 8.3.  So,
what’s the scoop on this, and what’s the strategy it represents?

At the most basic level, OISP is a mechanism by which Oracle
Database 12c can pass cues to Oracle ZFS Storage Appliance.  We use the Direct
NFS client within the Database to do this.  What sort of cues do we transmit,
you ask?  In principal, pretty much whatever we want!  Well, within reason, of
course.  But the point is that Oracle owns both products – Oracle Database 12c
and Oracle ZFS Storage Appliance.  We can figure out what cues are helpful and
how to use them, and then program them into the code for both products.  Now –
that’s pretty cool from an engineering perspective.

But… Passing cues?  Sound a little vague?  Let me make it
more concrete…

There’s two ways we use these cues, at present.  The
original version automatically and dynamically tunes storage share settings for
specific I/O from Oracle Database.  Without OISP, the best practice is to
create multiple shares on the storage appliance for each of the major database
file types (data files, control files, online redo log files, etc).  The reason
for this is so each share can be optimally tuned with different record size and
logbias settings for the workload profile of each file type.  Performance can
be greatly enhanced by tuning, but it is a manual effort.  With OISP, however, the
shares can be consolidated and the storage adjusts share parameters
appropriately, on-the-fly, for each of the different file types.  In this way,
optimal tuning can be achieved without wasted time and guesswork.

OISP version 1.1 adds per-database analytics functionality
to the picture.  Many are already familiar with our advanced D Trace analytics
package that is included with the Oracle ZFS Storage Appliance, which provides
the industry’s best end-to-end visibility into the storage workload, including
drill-down capabilities.  Now, as an enhancement to our analytics, OISP version
1.1 uses cues to provide drill-downs on a per-database basis.  This even
works at the pluggable database (PDB) level in Oracle Multitenant
environments.  This is significant because, even with PDBs, which share Online
Redo Logs and Control Files at the container database level, you can
immediately see the effect of a particular database on overall storage resource
utilization.  So, for example, if one database falls victim to a rogue query in
a multitenant environment, the administrator can immediately see which database
that is and quickly act to solve the issue causing the problem.   

So, OISP significantly speeds and simplifies database
storage provisioning.  It also provides deep visibility, so admins can
immediately know, rather than just guess, the linkages between storage workloads
and individual databases.  And this is only the beginning.  Imagine the opportunities
ahead of us to bring further game-changing customer value to Oracle Database

See my related video at href="https://www.youtube.com/watch?v=onz5T2Q3i6k">https://www.youtube.com/watch?v=onz5T2Q3i6k

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.