The following sections identify Oracle DIVArchive options, licensing, and tape repack limitations.
The following table describes DIVArchive options and licensing metrics.
| Part Number | Description | Licensing Metric |
|---|---|---|
| L101163 | Oracle DIVArchive Nearline Capacity | Per TB |
| L101164 | Oracle DIVArchive Archive Capacity | Per Slot |
| L101165 | Oracle DIVArchive Actor | Per Server |
| L101166 | Oracle DIVArchive Manager | Per Server |
| L101167 | Oracle DIVArchive Partial File Restore | Per Wrapper |
| L101168 | Oracle DIVArchive Avid Connectivity | Per Server |
| L101169 | Oracle DIVArchive Application Filtering | Per Server |
| L101170 | Oracle DIVArchive Storage Plan Manager (2 storage plans are included with a DIVArchive Manager License) | Per Server |
| L101171 | Oracle DIVAnet | Per Server |
| L101172 | Oracle DIVAdirector | Per User |
| L101918 | Oracle DIVArchive Export / Import | Per Server |
| L101919 | Oracle DIVArchive Additional Archive Robotic System | Per Tape Library |
| L101920 | Oracle DIVArchive Automatic Data Migration | Per Server |
The repack request will fail if the tape contains any corrupted objects and (or) the object fails checksum verification. You must manually resolve the conflict before performing the repack.
A checksum will not be generated for any spanned objects during Repack or Verify Tape requests. The Actor will identify any spanned files and the Manager will not attempt to verify them. A warning event will be displayed stating that a checksum was not generated or verified for the spanned content. In this case, the repack operation will not be aborted. However, the object instance will be marked as Not Verified.