Is Oracle’s “Processor” license definition technically flawed? If yes, then what are the implications for license calculations, and the infamous “installed and/or running” language? How would this impact licensing on systems where Oracle software is not actually running? I will do a deep dive into this topic in an upcoming post, so stay tuned. 

In this post, I wanted to go over the final two articles I wrote for the NoCOUG Journal and bring this series to an end.

I should clarify that the first article is not really about cloud licensing, even if the title says so. In this article I went over Oracle’s legacy licensing metrics, including Universal Power Unit (UPU), Concurrent Devices (CD), and various Named User metrics. I also discussed considerations for mixing metric types and considerations around migrating legacy license metrics to current ones.

“Oracle Licensing in the Cloud-Part V”, May 2018 (Pages 23-25)

The second article titled “The Hitchhiker’s Guide to Oracle Software Asset Management—Part I” departs from the cloud licensing theme and into the world of effective software asset management (SAM) for Oracle. We discuss SAM in general, then dive into key Oracle related concepts like agreements and important documents, dealing with different license metrics, and SAM considerations for the primary Oracle product categories like Database, Middleware, and Applications. On an unrelated note, while the article was has “Part I” in the title, I have not had the time for a follow up part, but hopefully readers will find this useful.

“The Hitchhiker’s Guide to Oracle Software Asset Management—Part I”, August 2018 (Pages 9-12)

As always, if you any questions about Oracle license compliance and optimization, feel free to contact us for a complimentary consultation. Contact Us.