Correcting consumption for Oracle Compression Advisor option

[#1]

Summary

A rare abnormal exit by the Oracle option leaves temporary DB tables that previously triggered false positives for license consumption. Queries are now updated to exclude those tables.

Symptoms

Usage-based license consumption for the Oracle Compression Advisor option may be excessive after the Compression Advisor fails to complete successfully.

Cause

When you run Oracle Compression Advisor to test the benefits of database compression, it creates temporary tables named CMP3$nnnnnn or CMP4$nnnnnn (where nnnnnn is a number). If Compression Advisor completes successfully, it removes these tables. However, if its operation is interrupted, the tables remain. For details, see Oracle Support Document 1606356.1 at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1606356.1

FlexNet Manager Suite uses the presence of any compressed database tables as evidence that the Compression Advisor option is in use and licensable. If you have decided against using compression, but the temporary tables from Compression Advisor are still present, this creates a false positive for license consumption.

Resolution

The Oracle database queries used for database inventory are now modified to filter out compressed tables with names matching the above patterns.

Ensure distribution of InventorySettings.xml version 30 to all installed FlexNet inventory agents locally installed on your Oracle Database servers:

• If you have taken responsibility for distributing copies of the InventorySettings.xml file within your enterprise, you must distribute version 30 or later to give the installed FlexNet inventory agent the ability to gather this inventory correctly.
• For installations of the FlexNet inventory agent managed by policy (that is, those that automatically upload to an inventory beacon), the updated InventorySettings.xml file is delivered automatically in the next device policy update after delivery of the XML file as part of the ARL update 2297, May 31, 2018. In this case, no action is necessary.

Once the inventory has been corrected by distributing the updated queries, and the results uploaded, the consumption calculations are corrected at their next run (typically overnight, in conjunction with a full inventory import).

Workaround

Not applicable.

Related Documents

Known issue FNMC-129 "Inaccurate license consumption for Oracle Compression Advisor option after option fails"

Additional Information

None.

Related KB Articles

None.