Oracle Database transparency now default opt in

With the previous (2019 R1.5) cloud release, we announced a new feature to help you better understand the evidence showing that an Oracle feature or option was (or was not) used on a particular database instance.

At that time, early adopters could opt in to try the functionality, which relies on processing and storage within Amazon Web Services (AWS). (For this reason, the functionality is available only on cloud implementations of IT Asset Management.)

Now that the decision period has expired, customers who have not communicated their need to avoid any data storage in AWS are now assumed to have opted into those services, and therefore to have opted into the Oracle Database transparency feature that relies on those services. From this release, this feature is enabled for all those customers.

One point to notice is that from this 2019 1.6 update, when the feature is enabled, the results dialog first shows Data is not available for all Oracle features/options – until you have uploaded the next Oracle inventory (.ndi) file, gathered by the FlexNet Inventory Agent locally installed on the Oracle Database server. It is while this .ndi file is resolved into the inventory database that the relevant data is saved to AWS for processing and storage. The hyperlinks on Yes or No are enabled by default to optimize performance, but actual results are available only after the next Oracle inventory is uploaded.

Learn more about the feature in our previous announcement: Transparency into the licensing of Oracle Database features.

IT Asset Management (Cloud)

Current