The forum will be down for maintenance at some point between Friday, September 25, 2020 at 5pm PDT and Sunday, September 27, 2020 at 11:59 PDT. Downtime is unknown but will be minimized.

Hi,

For the first time ever we're installing the Core edition license for SQL Anywhere 17 (4 cores), but at the start setup I only had an option to enter the number of licensed seats, without specifying that it's a Core license. So I entered 100 seats just to install the package.

But now I'm trying to change it using dblic utility:

dblic -l core dbsrv17.lic "Administrator" "Company"

but the utility does not run, I just get the usage text:

*SQL Anywhere Server Licensing Utility Version 17.0.10.6175
Usage: dblic [options] license_file ["user name" "company name"]
        @<data> expands <data> from environment variable <data> or file <data>   
Options (use specified case, as shown):
        -l <type>      license type: perseat or core
        -k <key>       registration key
        -o <file>      append output messages to file
        -q             quiet: do not display messages
        -u <n>         number of users or processors for license*

Curiously, all of these work just fine:

dblic -l perseat -u 10 dbsrv17.lic "Administrator" "Company"

dblic -l perseat -u 200 dbsrv17.lic "Administrator" "Company"

dblic -l perseat -u 500 dbsrv17.lic "Administrator" "Company"

if I want to change the number of licensed seats, but switch "-l core" as indicated in SQL Anywhere 17 documentation does not work, I just get text with how to use dblic command?

Never done this before, so am I missing something about the DBLIC utility?

Thanks

asked 08 Sep, 10:11

PcrMember's gravatar image

PcrMember
1363413
accept rate: 0%

edited 08 Sep, 10:19

Breck%20Carter's gravatar image

Breck Carter
30.8k496680992

2

Maybe it wants a -u option...

-u <n> number of users or processors for license

(08 Sep, 10:18) Breck Carter

Hi Breck,

As ever you're the quickest to reply and absolutely right. God, I feel a bit stupid now, that should have been quite obvious!

Thanks a lot!

(08 Sep, 10:22) PcrMember

You should provide your license key for your Core license to the dblic command i.e.,

dblic -k <core_license_reg_key> dbsrv17.lic

(08 Sep, 10:23) Chris Keating
Replies hidden

Hi Chris, I' wanted to try that earlier, but I think I found in documentation that I shouldn't combine -u with -k switch.

I've just tried it now and the difference I get than using Breck's suggestion is that the dblic output reads

Licensed nodes: 1

instead of

Licensed cores: 4

What's the actual difference between a node and a core in this case? Our license was for 4 cores.

(08 Sep, 10:29) PcrMember

When I tested with -k, it modified a 25 user license to a 4 core with a 4 core advanced license. Breck is correct that you can provide the -u

i.e., dblic -u 4 -l core dbsrv17.lic

(08 Sep, 10:47) Chris Keating
Replies hidden

Hm, I hadn't thought about the advanced Edition parameter. Our license should have been 4-cores advanced license. I quote from our supplier:

"SQL Anywhere Advanced Edition [v16.0 SP6, v17.0 and later OEM - Commercial - Perpetual Licence (4+) Per Core - Electronic]"

But reading out DBLIC DBSRV17 now, it doesn't say "Advanced Edition" anywhere?

(08 Sep, 10:52) PcrMember
1

Please note that the license is an OEM edition so it will be reported as OEM Authenticated Edition.

(08 Sep, 14:46) Chris Keating
showing 5 of 7 show all flat view
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×5

question asked: 08 Sep, 10:11

question was seen: 83 times

last updated: 08 Sep, 14:46