Release Notes
Release 7.5
E79745-02
April 2017
This document provides product release information for the Oracle DIVArchive Suite 7.5, and Oracle DIVArchive Suite 7.5.1 releases. Read this documentation before installing and using Oracle DIVArchive.
Contact Oracle Support for assistance installing, updating, or configuring DIVArchive. The Oracle Support Contacts Global Directory can be found at:
http://www.oracle.com/us/support/contact/index.html
Refer to the Oracle DIVArchive Operations Guide in the Oracle DIVArchive 7.5 Core documentation library for user-configurable parameters.
The following table identifies 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 |
Oracle recommends keeping the operating system up to date with the latest security patches. However, Oracle cannot guarantee that all patches will operate correctly with DIVArchive because the operating system security patches are independent of the DIVArchive application.
You should determine the acceptable operating system security patch level for your environment. Contact Oracle Support for assistance in determining operating system patch level compatibility if necessary.
The DIVArchive 7.5.1 release is essentially a bug fix release, but also includes the new Oracle DIVA Enterprise Connect 1.0.
Note:
DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.The following issues are resolved when running DIVArchive in a Windows environment:
25261525: Actor fails on Linux while running Cloud Stress Test.
25546242: Issue with GetObjectDetailList in DIVArchive 7.3 through Inmedia.
25585487: Transaction ID is missing from the logs of the DIVArchive OAC connector.
25608149: Plain text password when Verify Disk is turned on.
25668048: Canceling a restore while Actor is reading from real tape may cause the Actor to fail.
25682315: Actor should report success when ejecting a tape that is already ejected.
25689335: DBupgrade DIVA_07-01-01_to_07-01-02 error.
25838534: Errors in DBupgrade when upgrading from 6.5.3 to 7.3.1.
The following issues are resolved when running DIVArchive in a Linux environment:
25261525: Actor fails on Linux while running Cloud Stress Test.
25585487: Transaction ID is missing from the logs of the DIVArchive OAC connector
25668048: Canceling a restore while Actor is reading from real tape may cause the Actor to fail.
25682315: Actor should report success when ejecting a tape that is already ejected.
Oracle DIVA Enterprise Connect provides web services that allow client applications to submit requests to an Oracle DIVArchive or Oracle DIVAnet system. Oracle DIVA Enterprise Connect is built on top of the Oracle Weblogic Platform, supporting both REST and SOAP bindings. DIVA Enterprise Connect 1.0 is compatible with DIVArchive 7.4 and later (DIVArchive 7.5 is recommended), and DIVAnet 2.1 and later (DIVAnet 2.2 is recommended). DIVA Enterprise Connect 1.0 supports the 2.2 version of the DIVArchive Web Services API; earlier API versions are not supported on release 1.0. This is true for both SOAP and REST.
The DIVArchive Web Services 2.2 API contains the same basic information elements as the 2.1 version, but applications written against version 2.1 may not be compatible with version 2.2 platform. Some minor changes from 2.1 can be expected, including changes in return code behavior and in service authentication.
See the Oracle DIVA Enterprise Connect 1.0 documentation set in the Oracle DIVA Enterprise Connect 1.0 documentation library for more information.
DIVArchive 7.5 includes the new features and enhancements described in the following sections.
Note:
DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.DIVArchive 7.5 only supports the following database packages:
Windows only supports DIVAOracle Database Oracle 12c package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_Windows_64-bit.zip and later. No previous database package will work with DIVArchive 7.5 and later.
The OracleDivaDB_3-0-0_12_1_0_2_0_SE2_Windows_64-bit.zip and later releases no longer include the 32-bit Oracle database client.
Linux only supports DIVAOracle Database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_x86_64.sh and later.
See the Oracle DIVArchive Installation and Configuration Guide, and the Oracle DIVArchive Database User's Guide in the Oracle DIVArchive 7.5 Core documentation library for more information about the database.
DIVArchive 7.5 supports the following storage enhancements:
Oracle Storage Cloud integration is now available in DIVArchive 7.5. Two classes of cloud arrays are available; Archive Storage Class and Standard Storage Class. The Archive Storage Class is less expensive than the Standard Storage Class. Content stored in the Archive Storage Class requires a minimum of four hours for retrieval, while content in a Standard Storage Class array is immediately available for download from the cloud. You can use both storage classes with DIVArchive 7.5.
You configure an Actor to archive and restore to cloud disks through the Actor Settings in the Configuration Utility. You must designate whether the Actor is enabled for archiving or restoring content. Only Actors with these designations will be used to transfer content to and from the cloud.
See the Oracle DIVArchive Installation and Configuration Guide in the DIVArchive 7.5 Core documentation library for configuration information.
For information on Oracle Storage Cloud visit the following links.
http://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csgsg/
http://docs.oracle.com/cloud/latest/storagecs_common/index.html
DIVArchive 7.5 supports new Sony ODA drives. The details of these drives are as follows:
Sony released a new generation of ODA drives: ODS-280F and ODS-280U. DIVArchive has only been tested with the Fibre Channel type. These drives are twice as fast as the Gen1 drives. The ODS-280U has not been qualified for use with DIVArchive 7.5.
A new type cartridge is available for this drive: ODC3300R. This is a WORM drive with a 3.3 TB capacity.
Gen2 drives can read content written on Gen1 media with Gen1 drives. DIVArchive does not support the READ-ONLY media-drive compatibility. Oracle recommends isolating Gen1 media from Gen2 media in the configuration (no cross-generation compatibility) and there must be at least one Gen1 drive in a library containing Gen1 cartridges.
The Actor now reports true remaining size on tapes and the last written position on the tape to the Manager during transfers of content to tape for Oracle T10000 and IBM LTO drives. The remaining size is presented in the number of bytes of uncompressed data.
The Manager uses the remaining size and last written position to obtain the true total and remaining size on the tape, and then uses the true total and remaining size on tapes in all tape-based operations instead of relying on the size of the tape.
The following enhancements are included in the 7.5 release:
Support for the Telestream Vantage transcoder in Linux environments.
Oracle DIVArchive Partial File Restore for MXF is supported on Windows Actors (only).
DIVArchive 7.5 enables archive and restore of symbolic links.
Only supported for AXF objects.
Only supported with an SFTP Source/Destination on Windows.
Only symbolic links created in Linux are supported and identified as a symbolic link because shortcuts created in Windows are treated as files.
Because Linux-based Actors cannot use CIFS, a new path is required to enable Linux-based Actors to transfer content to and from SMB network shares (transcoder cache). The new path is required when using Linux-based Actors with Vantage Transcoders.
Caution:
The order of theactor, actorPath, and transcoder settings discussed in the following paragraphs is important. The order of the parameters must be actor, followed by actorPath, followed by transcoder. The actorPath represents the path the Linux Actor will use to transfer content to and from the SMB network share (transcoder cache) on a Linux system.The CIFS path is specified as the value of the actorPath parameter in a delimited list as follows:
[actor:actor_name,actorPath:actor_path,transcoder:trancoder_ip_address],cifs://username:password@\\transcoder_cache_ip_address\transcoder_cache
You do not need to change an existing CIFS path if you are switching from a Windows Actor to a Linux Actor for use with a pre-existing Vantage transcoder configuration. The path will only be used by Vantage to access the cache. The only thing that changes is adding the actorPath to the working directory of the transcoder. For example:
[actor:actor1,actorPath:/tmp/vantagecache,transcoder:100.100.100.100],cifs://Administrator:password@\\100.100.100.100\VantageStore
See the Oracle DIVArchive Operations Guide in the DIVArchive 7.5 Core documentation library for more information.
The following new and enhanced features and functionality have been added in DIVArchive 7.5 Control GUI:
DIVArchive 7.5 identifies symbolic links in the Control GUI in the Components List under types on the Properties tab. Directories are designated with a D, files with an F, and symbolic links with an S.
Symbolic links are also displayed in the Elements list on the Instances tab, and as files in the Components tab of the Object Properties screen.
A new column is available in the Disks View of the Control GUI. The column titled Consumed Size represents the space in kilobytes consumed by content on the disk. This new column is particularly useful for cloud accounts with unlimited disk space because this provides visibility into the amount of content stored in the cloud.The cloud storage class associated with the array is also displayed. Non-cloud disks have a storage class of NONE. Cloud disks have a storage class of Standard (content immediately available for download from the cloud) or Archive (content requires at least four hours to download from the cloud).
The Object Properties View contains a new column called Cloud Storage Class enabling you to view the storage class associated with a particular cloud instance.
Migration service jobs now have events associated with them. All job events are displayed under the Job Events tab in Job Properties dialog box. By default, events are loaded in descending order by time and event id. The Events table in the Job Events tab highlights events with different colors based on severity. Red indicates an Error, yellow indicates a Warning, and white indicates Information. The new Refresh button refreshes the entire Job Properties dialog box.
You must use a migration job to change a tape format from Legacy to AXF, repacking a tape will not change the tape format. Repacking of existing Legacy format objects retains the format of the tape even if the tape group format was updated in the configuration from Legacy to AXF.
Oracle DIVArchive Storage Plan Manager has been ported to use 64-bit operating systems. The OracleDivaDB_3-0-0_12_1_0_2_0_SE2_Windows_64-bit.zip and later releases no longer include the 32-bit Oracle database client.
You can now change the status of SPM Failed Actions to Completed by right clicking the action and selecting Mark Action Completed from the context menu.
Normally SPM will retry a completed Copy action if the Once Only option is set to NO, and a user manually (or accidentally) deletes the instance that SPM copied before the Storage Slot expires. Also, SPM will normally retry a completed Delete action if a user manually (or accidentally) copies an instance to the Storage Slot medium after SPM deleted it. Actions marked as complete by a user will never be retried by SPM. However, you can reschedule a user-completed action by right clicking it and selecting Reschedule Action from the context menu. The Mark Action Completed (by a user) option is only available using the administrator profile.
DIVArchive 7.5 Local Delete allows delayed delete mode to perform site deletes that are not based on remaining disk space on a DIVArchive array. When watermarking is not used to purge from a disk array, the Local Delete application will delete all object instances from the selected site. The configuration file for delayed mode is the new standard for Local Delete, and the legacy configuration file format is deprecated. The following other features are introduced:
Time-based criteria enables purging only after an object is N hours old.
Exclude List Functionality enables you to create a list of media that will not be purged when a site delete occurs.
See the Oracle DIVArchive 7.5 Local Delete User's Guide in the Oracle DIVArchive 7.5 Additional Features documentation library for detailed information.
DIVAprotect Archive, Copy, Copy As, Restore, and Partial File Restore request events will populate the Transfer Size and Duration fields.
See the Oracle DIVArchive 7.5 DIVAprotect User's Guide in the Oracle DIVArchive 7.5 Additional Features documentation library for detailed information.
DIVAprotect Archive, Copy, Copy As, Restore, and Partial File Restore request events will populate the Transfer Size and Duration fields.
The ANALYZE_END and ANALYZE_ERR predefined events are removed from DIVAprotect.
To standardize the Metric ID across all DIVArchive installations, all predefined metrics have a hard-coded Metric ID instead of using a database sequence. All user-defined metrics start with Metric ID 1001. The database upgrade scripts handle this migration for you during upgrades from DIVArchive 7.4 to release 7.5. If you already had any user-defined metrics, they are automatically assigned a new Metric ID starting with 1001.
Removed predefined metrics are in the following list. However, there is no impact for earlier releases and customers currently using them, those metrics will continue to exist, update, and are not removed during the upgrade process to the 7.5 release. This only affects new installations of DIVArchive 7.5 and later.
ANALYZE_NUMBER_DAY
ANALYZE_NUMBER
ANALYZE_ABORTED_NUMBER_DAY
ANALYZE_ABORTED_NUMBER
ANALYZE_DATA_DAY
ANALYZE_DATA
ANALYZE_AVG_THROUGHPUT_DAY
ANALYZE_AVG_THROUGHPUT
ANALYZE_MIN_THROUGHPUT_DAY
ANALYZE_MIN_THROUGHPUT
ANALYZE_MAX_THROUGHPUT_DAY
ANALYZE_MAX_THROUGHPUT
ANALYZE_TIME_DAY
ANALYZE_TIME
MEDIA_OBJECT_INSTANCE_CREATE_DELETE_DAY
MEDIA_OBJECT_INSTANCE_CREATE_DELETE
New predefined metrics are as follows:
ACTOR_READ_WRITE_MONTH
ACTOR_READ_WRITE_NUMBER_MONTH
ACTOR_TIME_ALL_OPERATION_MONTH
ACTOR_TIME_READ_MONTH
ACTOR_TIME_WRITE_MONTH
DISK_AVG_TRANSFER_RATE_READ_MONTH
DISK_AVG_TRANSFER_RATE_WRITE_MONTH
DISK_CHECKSUM_FAILURE_COUNT_MONTH
DISK_NUMBER_READ_ABORTED_MONTH
DISK_NUMBER_READ_MONTH
DISK_NUMBER_WRITE_ABORTED_MONTH
DISK_NUMBER_WRITE_MONTH
DISK_READ_MONTH
DISK_TIME_ALL_OPERATION_MONTH
DISK_TIME_READ_MONTH
DISK_TIME_WRITE_MONTH
DISK_WRITE_MONTH
DIVARCHIVE_SYSTEM_ACTIVE_ARCHIVE_NUMBER_MONTH
DIVARCHIVE_SYSTEM_ACTIVE_COPY_AS_NUMBER_MONTH
DIVARCHIVE_SYSTEM_ACTIVE_COPY_NUMBER_MONTH
DIVARCHIVE_SYSTEM_ACTIVE_RESTORE_NUMBER_MONTH
DIVARCHIVE_SYSTEM_AVG_READ_WRITE_NUMBER_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_ARCHIVE_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_CREATED_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_DELETED_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_COPY_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_CREATED_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_DELETED_MONTH
DIVARCHIVE_SYSTEM_NUMBER_OBJECT_RESTORE_MONTH
DIVARCHIVE_SYSTEM_OBJECT_EXPORT_NUMBER_MONTH
DIVARCHIVE_SYSTEM_OBJECT_IMPORT_NUMBER_MONTH
DIVARCHIVE_SYSTEM_OBJECT_INSTANCE_EXPORT_NUMBER_MONTH
DIVARCHIVE_SYSTEM_OBJECT_INSTANCE_IMPORT_NUMBER_MONTH
DIVARCHIVE_SYSTEM_READ_WRITE_ABORTED_NUMBER_MONTH
DIVARCHIVE_SYSTEM_READ_WRITE_MONTH
DIVARCHIVE_SYSTEM_READ_WRITE_NUMBER_MONTH
MEDIA_ARCHIVED_OBJECT_DATASIZE_MONTH
MEDIA_DATA_SIZE_DAY
MEDIA_DATA_SIZE_MONTH
MEDIA_OBJECT_INSTANCE_EXTERN_MONTH
MEDIA_OBJECT_INSTANCE_ONLINE_MONTH
MEDIA_READ_WRITE_MONTH
MEDIA_READ_WRITE_NUMBER_MONTH
MEDIA_RESTORE_OBJECT_DATASIZE_MONTH
MEDIA_TAPE_EXPORT_NUMBER_MONTH
MEDIA_TAPE_IMPORT_NUMBER_MONTH
SD_ARCHIVE_OBJECT_DATASIZE_MONTH
SD_READ_MONTH
SD_READ_NUMBER_MONTH
SD_RESTORE_OBJECT_DATASIZE_MONTH
SD_TIME_MONTH
SD_WRITE_MONTH
SD_WRITE_NUMBER_MONTH
TAPE_DRIVE_DATA_RATE_MONTH
TAPE_DRIVE_ERROR_RATE_MONTH
TAPE_DRIVE_NUMBER_READ_WRITE_ABORTED_MONTH
TAPE_DRIVE_OPERATION_TOTAL_TIME_MONTH
TAPE_DRIVE_READ_WRITE_MONTH
TAPE_DRIVE_READ_WRITER_NUMBER_MONTH
TAPE_DRIVE_TIME_ALL_OPERATION_MONTH
TAPE_DRIVE_TIME_READ_MONTH
TAPE_DRIVE_TIME_WRITE_MONTH
TAPE_LIBRARY_NUMBER_DISMOUNT_ABORTED_MONTH
TAPE_LIBRARY_NUMBER_MOUNT_ABORTED_MONTH
TAPE_LIBRARY_NUMBER_MOUNT_MONTH
TAPE_LIBRARY_NUMBER_READ_MONTH
TAPE_LIBRARY_NUMBER_WRITE_MONTH
TAPE_LIBRARY_READ_MONTH
TAPE_LIBRARY_WRITE_MONTH
TRANSCODE_DATA_MONTH
TRANSCODE_NUMBER_MONTH
TRANSCODE_TIME_MONTH
MEDIA_OBJECT_INSTANCE_CREATE_DAY
MEDIA_OBJECT_INSTANCE_DELETE_DAY
MEDIA_OBJECT_INSTANCE_CREATE
MEDIA_OBJECT_INSTANCE_DELETE
MEDIA_OBJECT_INSTANCE_CREATE_MONTH
MEDIA_OBJECT_INSTANCE_DELETE_MONTH
MEDIA_OBJECT_INSTANCE_EXTERN_DATASIZE_DAY
MEDIA_OBJECT_INSTANCE_EXTERN_DATASIZE_MONTH
MEDIA_OBJECT_INSTANCE_ONLINE_DATASIZE_DAY
The Oracle Java and Oracle DIVArchive C++ APIs support the following enhancements. See the appropriate API reference documentation in the Oracle DIVArchive 7.5 Additional Features documentation library for details.
The file list returned from a getFilesAndFolders call now contains symbolic links.
The getArrayList call returns the storage class of each array.
The lists returned by the getObjectInfo and getObjectDetailsList calls now include the storage class of each disk instance.
The -delete_on_source option is now supported in archiveOptions for DIVA_ArchiveObject calls. See the Oracle DIVArchive C++ API Reference Manual in the Oracle DIVArchive 7.5 Additional Features documentation library for detailed information.
Additional Services and QOS values are now supported for restoreOptions for DIVA_RestoreObject and DIVA_PartialRestoreObject calls. See the Oracle DIVArchive C++ API Reference Manual in the Oracle DIVArchive 7.5 Additional Features documentation library for detailed information.
DIVArchive 7.5 Export and Import functions enable the following enhancements. See the Oracle DIVArchive Export/Import User's Guide in the Oracle DIVArchive 7.5 Core documentation library for detailed information.
The type attribute now includes S to represent a symbolic link.
The Export and Import process now includes the total tape size.
DIVArchive 7.5 enables specifying a QOS value as a Request Option. The following request options map to their logical quality of service:
-qos_direct_only
-qos_cache_only
-qos_direct_and_cache
-qos_cache_and_direct
-qos_nearline_only
-qos_nearline_and_direct
Request Options take precedence over the normal quality of service specification. Also, the normal quality of service specification takes precedence over the Source/Destination Connect options.
NEARLINE-ONLY and NEARLINE_AND_DIRECT QOS values are now supported in the Source/Destination Connect Options. These options are only valid for a Restore request. If a source or destination server with either setting is used in any other type of request, the setting is ignored and the usual default is applied.
The QOS value is no longer case-sensitive and no longer must be specified at the beginning of the options. For example, -login test -pass test qos=nearline_only is a valid option.
You can now specify Additional Service Delete on Source in Archive requests, and the Additional Services Do not overwrite, Do not check existence, and Delete and Write services in Restore requests as Request Options.
DIVArchive 7.5 enables use of the following request options:
Archive Requests
-delete_on_source
Restore Requests
-do_not_overwrite -do_not_check_existence -delete_and_write
Request Options take precedence over the normal Additional Service specification. Also, the normal Additional Service specification takes precedence over the Source/Destination Connect Options.
You can also specify the Additional Services available for a Restore request in the Source/Destination Connect Options. If specified, the Source/Destination will use the Additional Service setting as a default. This can be overridden by specifying the Additional Service at a request level in the normal way, or as a new Request Option. Because these connect options are specific to a Restore request, the options are ignored for any other type of requests using the Source/Destination.
The Oracle database included with the DIVArchive system is limited to use only for the operation of the DIVArchive software.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle DIVArchive Suite Release Notes, Release 7.5
E79745-02
Copyright © 2016, 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.