"The number one rule for setting up an Oracle database on ZFS is to set ZFS recordsize equal to
the database block size for the file systems that contain the Oracle data files."
"Starting with Oracle Solaris 11.1, blocks that are referenced from either the snapshot or from the
database image actually share ZFS cache buffers for a reduced memory footprint."
"Taking a snapshot of a database can involve placing the database in hot-backup mode just for the
instant necessary to capture the ZFS snapshot. The database can then be returned to normal operation."
"A clone is a full read/write accessible fork of the original database. Therefore, by using either the primary
or a replicated storage system, you can cheaply create hundreds of copies of your up-to-date database to
run test and development workloads under real data conditions."
They also allow compression of the archived (intent) logs.
https://www.oracle.com/technetwork/server-storage/solaris10/...
"The number one rule for setting up an Oracle database on ZFS is to set ZFS recordsize equal to the database block size for the file systems that contain the Oracle data files."
"Starting with Oracle Solaris 11.1, blocks that are referenced from either the snapshot or from the database image actually share ZFS cache buffers for a reduced memory footprint."
"Taking a snapshot of a database can involve placing the database in hot-backup mode just for the instant necessary to capture the ZFS snapshot. The database can then be returned to normal operation."
"A clone is a full read/write accessible fork of the original database. Therefore, by using either the primary or a replicated storage system, you can cheaply create hundreds of copies of your up-to-date database to run test and development workloads under real data conditions."
They also allow compression of the archived (intent) logs.