This time we thought it might be useful to put together an A-Z of Oracle licensing terms, rules, metrics and general information. Even though lots of companies are moving to the Cloud there are still plenty of on-premise installations out there and many of the traditional computing methods are still in use. We hope you find it helpful, but if you need more information please don’t hesitate to contact us by email to email@example.com or check out our online training courses at https://madora.teachable.com/
This first part will cover A, B and C and we’ll gradually build up over the next few weeks and months to Z. There are lots of options for each letter, so if you have any suggestions for what we could include, please let us know.
An Application Specific Full Use (ASFU) licence is a restricted type of licence sold by a Solution Provider in conjunction with its Application Package. Application Specific Full Use licences may only be used by the end user to execute the Solution Provider’s application program and may not be used with more than one Application Package.
These licences can work out cheaper if you know you will only use them to underpin the one application from your solution provider, but it is important to make sure that you will not be using any other applications on the server. If you do, you will need to purchase normal full use licences.
Batch processing is the execution of a set of jobs run on a computer without human interaction, the input parameters are predefined through scripts, command-line arguments, control files, or job control language. The input data is collected into batches or sets of records and each batch is processed as a unit. An example would be automatic running of a cheque printout overnight.
Automatic batch processing is included with Processor and Named User Plus licences, but if you have manual batch processes created by a user, then the user needs to be counted when you are reviewing the number of users you have.
There are lots of items we could have put in for C, such as Cloud, CPU and Core Factors, but we feel it is important to keep an eye on your usage so have included counting instead. How do you work out how many licences you need? How often do you check you have the right number? How do you count the usage? How do you count the number of CPUs, Processors Cores or Users? All these things are important in making sure you have the correct number of licences, even if you are using Cloud now, especially with BYOL or Bring Your Own Licences where Oracle will expect you to have the right quantity. Don’t forget some products have different metrics based on employees or revenue, so you also need to make sure you can count these accurately if you need to report them to Oracle on a regular basis.
Don’t forget Oracle licensing isn’t always as straightforward as counting the number of licences against the number of users, so ask us if you need help.
Look out for the next Blog where we will cover D-F.
Check out @oralicencepro's A-Z of #Oracle #Licensing Part 1