X

An Oracle blog about ZFS Storage

Group hug and a strong handshake


Are you a DBA? Your job is hard.

Are you a Storage Admin? Your job is hard too.

How much easier would a group hug and a strong handshake make your life? What if that handshake was between the technologies you manage rather than with your colleagues?

That is concept behind deep co-engineering between Oracle 12c Database and Oracle ZFS Storage Appliance...and it will definitely make your life—DBA or Storage Admin—so much easier. Oracle Intelligent Storage Protocol (OISP) lets the Oracle 12c database to tag each and every I/O and allows the Oracle ZFS Storage Appliance to dynamically tune to those hints.

With each version OISP has just gotten better and better. OISP 1.0 was introduced to help out DBA’s and Storage Admins reduce time and effort to manually configure and tune storage shares for database deployments.

OISP 1.1 took it a step further and the hints carried information on the DBid /PDBid and additional drill down information. This was especially important for troubleshooting issues in Multi-tenant environments.

Newly introduced OISP 2.0 now has features designed to optimize critical resource usage (CPU, DRAM) on the appliance. Fair Share Scheduling (FSS) eliminates first-in/first-out (FIFO) method of allocating storage resources on the appliance. This eliminates scenarios where large bandwidth I/O workloads that arrived first would take up resources and force critical I/O operations like cluster heartbeat and synchronous database operations like LGWR to wait causing performance degradations at the application layer. OISP 2.0 introduces separate thread pools for READ, WRITE and Synchronous operations and isolates heavy write I/O operations to its own pool and the does the same with critical synchronous operations. The result is a far more consistent database performance.

Not only that: OISP 2.0 introduces negative cache hints through which large block asynchronous I/O are evicted from DRAM freeing up that resource for critical data blocks. Operations like RMAN backups or archive log I/O do not take up blocks in DRAM anymore. This allows operations like backups during the middle of batch schedule without affecting database I/O performance at the appliance.

Finally, OISP 2.0 extended analytics lets Storage Admins have deep visibility into database operations right from the storage management interface. This additional information correlates well with AWR reports that DBAs are well versed at. OISP operations can be broken down by database name, database operation , database filetype to help tie out the I/O operations with the DB function and DB that issued it.All very valuable information to do a deep dive on the analytics to troubleshoot performance issues related to I/O performance.

Now finally DBAs finally have a storage device that understands them and speaks their language ; )

To see all this co-engineering in action take a a look at this demo.

Go give your colleagues a group hug...with OISP, everything is about to get much better!

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.