on 06-01-2015 2:19 PM
Having this scenario: A SQLAnywhere 16 with Workgroup edition and 10 seats (running e.g. on Linux). Another 20 seats package is brought and needs to be added to the server. For the 20 seats there can be a new key generated. When adding the new key with
dblic -k "newkey" /opt/sybase/bin64/dbsrv16
the number of seats can be updated with e.g.
dblic -l perseat -u 30 /opt/sybase/bin64/dbsrv16.lic
But running dblic /opt/sybase/bin64/dbsrv16.lic after is only showing the last licence key, not the previous one -- so in my understanding -- it should only be valid for 20 seats.
So my question is: What is the correct way on adding an additional 20 seats to an SQLAnywhere (16) installation.
Hi Frank,
dblic only displays/applies the data from the last license key applied. The license keys do not 'stack' when you apply them using dblic.
Once you have purchased the correct paper licenses, you can simply update the number of seats as you have done in your second example. You do not have to use the new key.
--Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
9 | |
9 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.