Oracle LMS Collection Tool – Under what terms can I make use of it?
Oracle went through some changes recently, one of them being the audit clause, the other its audit team. We covered both these changes in previous articles. Moreover, we also addressed the fact that Oracle LMS developed their own tools to identify where products are being deployed and used – specifically the Oracle LMS Collection Tool. Since now you know what it is and what it does, let’s have a look into how you can use it. Are there any specific terms you need to comply with? Can you analyze the output of this tool yourself to understand your license requirements and resulting license compliance position? Read on to find the answers.
The moment you start making use of the LMS Collection Tool you are required to accept the license agreement that is part of this tool. If you don’t accept it, the tool won’t work. But what does this agreement actually say? Let’s have a closer look by analyzing the most important and relevant sections of this agreement.
By making use of the LMS Collection Tool, you are required to accept the included license agreement, which is legally binding between yourself and Oracle America Inc.
The agreement is governed by the substantive and procedural laws of the State of California, USA. In case of any disputes, you need to submit your complaints to the courts of San Francisco or Santa Clara counties in California.
You receive the right to make use of the LMS Collection Tool for the limited purpose of measuring, monitoring and/or managing your usage of the programs. You may allow your agents and contractors (including outsourcers) to use the LMS Collection Tool for this purpose. You may not use the LMS Collection Tool for your own internal data processing or for any commercial or production purposes or use the software for any other purpose.
Oracle does not guarantee that the LMS Collection Tool will perform error-free or uninterrupted. To the extent not prohibited by law, the LMS Collection Tool is provided “as-is” without warranty of any kind.
Oracle’s technical support organization will not provide you with technical support during the installation, configuration and/or use of the LMS Collection Tool.
Limitation of Liabilities
In no event shall Oracle be liable for any indirect, incidental, special punitive or consequential damages or any loss of profits, revenue, data or data use, incurred by you or any third party. Oracle’s entire liability for damages arising out of or related to this agreement, whether in contract or tort or otherwise, shall in no event exceed the greater of one thousand US dollars (US $ 1,000) or the license fees that you have paid to Oracle for programs pursuant to an Oracle license agreement.
Security & Privacy
Can you understand the output of the LMS Collection Tool?
The answer on this question is simple. No, you can’t. The LMS Collection Tool collects a large amount of raw data in different output logfiles that cannot be understood or read if you don’t have in-depth knowledge of what the information means, how it should be analyzed and what logic should be applied to understand your license requirements. To give some examples:
- the SQL queries that are run on your database instances will produce – per database instance – a total amount of 11 distinct *.csv files with hundreds of lines of output specifying the database version, database edition, database options and database management packs installed and/or used.
- the CPU queries that are run on your operating system will produce – per server – a single *.txt file with hundreds of lines of output providing details of your hardware infrastructure and its configuration.
- the FMW queries that are run on your operating systems will produce – per server – a *.zip file with a registry.xml, config.xml, comps.xml, opmn.xml, server.xml, domain.xml, pthome.xml and many more raw data files.
- the E-business Suite queries that are run on your database instances being used for your Oracle E-business suite application will collect data from your FND tables (FND Security Groups, FND Application, FND Application TL, FND Responsibility, FND Product Installations, FND User, FND User Groups, etc.), containing hundreds or thousands of rows of raw data.
Due to Oracle’s change in its standard audit clause, you will be required to run Oracle’s LMS Collection Tool on your servers and share the resulting output logfiles. The terms and conditions of the accompanied license agreement are non-negotiable. Oracle does not guarantee that the LMS Collection Tool will perform error-free or uninterrupted and Oracle Support does not provide any technical support during the installation configuration and/or usage of the tool and in case of any damages as a result of making use of this tool (e.g. performance issues, systems outage). Then, if applicable, Oracle will pay you a maximum of 1.000 USD as compensation.
You are not allowed to make use of the LMS Collection Tool for your own internal data processing. In other words: you are not allowed to make use of the tool for any other purpose than measuring, monitoring and/or managing your usage of the programs. This means that you can continue to use the LMS Collection Tool for your own internal regular audits as well.
There are high chances that you’ll not completely understand the resulting output logfiles of the LMS Collection Tool to know what your license requirements are. You need in depth knowledge and analysis skills, that we can help you with. Sharing the raw data collected by the Oracle LMS Collection Tool without understanding the implications (from a licensing and from a commercial perspective) is never a good idea. Especially since it is common knowledge that almost any end user that is going through an Oracle audit is found to be non-compliant.
The best way to properly manage your Oracle compliance position is by performing regular internal software license audits. In addition to detecting any compliance issues at an early stage, this will also allow you to optimize your available licenses, monitor your software spend, reduce your financial risk and ultimately save costs. How do you do this? By engaging license experts, who use measurement tools and methodologies similar to the ones Oracle uses. B-lay’s Oracle Managed Services are developed to address this specific need, with or without making use of the LMS Collection Tool. For more information, contact us.
Richard is one of the managing partners at B-lay. He started to work in the license management industry in 2004 and worked for almost 10 years at Oracle as regional director of compliance. He uses his knowledge of enterprise software vendors (such as Oracle, SAP, IBM and Microsoft) to educate, equip and enable software end users in their challenges regarding proper software license management. Richard holds a master’s degree in IT, from University of Amsterdam in the Netherlands.