How do I change user and company name for my license file?

[VolkerBarth]

That's a follow-up to this question: Can I upgrade a SQL Anywhere 12 developer edition to a paid version?

After I have successfully set my license key with DBLIC -k and thereby turned my install into a Workgroup Edition, how do I change the user and company name from "Developer Edition / Restriced Use" to the correct ones?

The following display the current status:

"%SQLANY12%\\bin32\\dblic" "%SQLANY12%\\bin32\\dbsrv12.lic"

whereas the following attempt to add user and company name by just adding those to the command line gives the usage screen:

"%SQLANY12%\\bin32\\dblic" "%SQLANY12%\\bin32\\dbsrv12.lic" MyName MyCompany

It doesn't matter if I include both names in double quotes or not.

So what am I doing wrong?

[MarkCulp · Accepted solution]

It would appear that in order to change your license file name and company name using dblic, you need to supply your license key (-k option) as well as specify the license type (-l) and number of units (-u), and then supply the name of the executable (not the name of the .lic file) followed by your name and company name.

dblic -k <your-lic-key> -l <perseat-or-percpu> -u <n> "Name" "Company Name"

I am not sure why it is this way, but it appears to work.

[VolkerBarth · Accepted solution]

In my case, it works with supplying the license file (as documented) and the options you have stated. Therefore I had to run the command both for the personal and the network engine. (Before raising the question, I had tested with including -k but not the other options).

[VolkerBarth · Accepted solution]

Mark, if this is a (somewhat surprising) feature - in contrast to unwanted behaviour -, I would suggest to add this to the docs.

[MarkCulp · Accepted solution]

@Volker: I asked the author of the dblic tool if this behaviour is intended. It seems to me that changing the name(s) without changing the other values would be a reasonable thing to do. I see if there is a technical reason why it was done this way... and then let you know.

[VolkerBarth · Accepted solution]

@Mark: Just to add: It seems to be sufficient to add only the -u <n> option, i.e. dblic -u <> dbeng12.lic "Name" "Company Name" works, too.

[MarkCulp · Accepted solution]

The current behaviour is not intended but is simply "the way it works today". An enhancement request has been made to allow changing of the name(s) without requiring (re)specification of the other information.