1. Companies are not aware that the ULA exit process includes a license audit

Oracle will perform a “stealth” audit at the end of your ULA.

Oracle will demand that you to run their data measurement / audit tools. These tools will not only see what is in use today, but also what has been used in the past. What I see all the time is for example someone in our clients IT Operations, such as a DBA have used a features that requires a license that is not part of their ULA. Oracle audit tools will also capture data on products that are not part of your ULA.

I have helped over 40 companies exiting or renewing their Oracle ULA and not single one has been compliant with their ULA contract. License gaps has varied from 1 MUSD – 500 MUSD.

Recommendation:

Perform your own licensing review to provide yourself maximum flexibility and multitide options to choose from. You want to be in control for how to resolve your ULA licensing risks. Relying on a SAM tool would be a big mistake, it is essential that you use Oracle LMS style scripts for reaching your licensing position. These scripts you can request from Oracle or work with a licensing expert who usually have made their own scripts.

A combination of SAM/Inventory tools and Oracle audit scripts will always produce the most best result.

2. Companies have mistakenly deployed ULA software in a third-party cloud such as AWS/Azure/Google.

While in an Oracle ULA, you can freely deploy the ULA software in any third-party cloud provider,if the cloud zone is placed in within your territory deployment rights. (check territory clause in your ULA contract).

The “got-cha” moment appears when you exit your Oracle ULA and submit deployment data to Oracle LMS for verification. At which point Oracle will inform you that you are non-compliant for all your third-party cloud deployments such as AWS and Azure. As Oracle standard contract terms prohibit you from counting any deployments in third party cloud towards your exit numbers.

Oracle will then propose a new ULA to resolve these issues and you might have to pay millions to Oracle when you have no need for a new ULA.

  1. While in an Oracle ULA, you can freely deploy the ULA software in any third-party cloud provider,if the cloud zone is placed in within your territory deployment rights. (check territory clause in your ULA contract).
  2. The “got-cha” moment appears when you exit your Oracle ULA and submit deployment data to Oracle LMS for verification. At which point Oracle will inform you that you are non-compliant for all your third-party cloud deployments such as AWS and Azure. As Oracle standard contract terms prohibit you from counting any deployments in third party cloud towards your exit numbers.
  • While in an Oracle ULA, you can freely deploy the ULA software in any third-party cloud provider,if the cloud zone is placed in within your territory deployment rights. (check territory clause in your ULA contract).
  • The “got-cha” moment appears when you exit your Oracle ULA and submit deployment data to Oracle LMS for verification. At which point Oracle will inform you that you are non-compliant for all your third-party cloud deployments such as AWS and Azure. As Oracle standard contract terms prohibit you from counting any deployments in third party cloud towards your exit numbers.

Perform your own licensing review to provide yourself maximum flexibility and multitide options to choose from. You want to be in control for how to resolve your ULA licensing risks. Relying on a SAM tool would be a big mistake, it is essential that you use Oracle LMS style scripts for reaching your licensing position. These scripts you can request from Oracle or work with a licensing expert who usually have made their own scripts.

A combination of SAM/Inventory tools and Oracle audit scripts will always produce the most best result.

  • While in an Oracle ULA, you can freely deploy the ULA software in any third-party cloud provider,if the cloud zone is placed in within your territory deployment rights. (check territory clause in your ULA contract).
  • The “got-cha” moment appears when you exit your Oracle ULA and submit deployment data to Oracle LMS for verification. At which point Oracle will inform you that you are non-compliant for all your third-party cloud deployments such as AWS and Azure. As Oracle standard contract terms prohibit you from counting any deployments in third party cloud towards your exit numbers.

Social