SySAM checks feature licensing at various times. Some features are only checked on startup; others after the feature has been added to the database (e.g., passed the threshold for IQ store size, created multiplex writer, etc.); others are triggered by a particular event.
IQ_SECURITY licenses are ALWAYS checked out during startup. This is necessary because IQ_SECURITY features (column encryption, Kerberos authentication, etc.) need to be turned on at startup. If you do not have an IQ_SECURITY license, IQ_SECURITY checkout failures may simply mean that security features will not be initialized during startup.
Table B-1 describes the events that determine when SySAM checks out different licenses.
License |
Initial checkout occurs on |
Coordinator |
Writer |
Reader |
Node checking out |
Separate license per node |
|---|---|---|---|---|---|---|
IQ_SECURITY |
Database startup |
Yes |
Yes |
Yes |
All nodes |
Yes |
IQ_MPXNODE |
Database startup |
Never |
Yes |
Yes |
Secondary nodes only |
Yes |
IQ_VLDBMGMT |
User creates 3rd dbspace |
Yes |
Never |
Never |
Coordinator only |
No |
IQ_LOB |
User creates/accesses LOB/CLOB table |
Yes |
Yes |
Yes |
All nodes |
Yes |
IQ_CORE |
Database startup |
Yes |
Yes |
Yes |
All nodes |
Yes |
IQ_UDF |
User accesses UDF |
Yes |
Yes |
Yes |
All nodes |
Yes |
IQ_SYSTEM_MAIN
and one more user dbspace is provided with the server; a third dbspace
requires a IQ_VLDGMGMT license.
Table B-2 identifies when SySAM verifies different licenses.
License |
Consistent checks on startup |
Checks on startup after feature enabled |
Checks on feature access |
|---|---|---|---|
IQ_SECURITY |
• |
• |
|
IQ_MPXNODE |
• |
• |
|
IQ_VLDBMGMT |
• |
• |
|
IQ_LOB |
• |
||
IQ_CORE |
• |
||
IQ_UDF |
• |
Changes to licensed features may not appear until the
server is restarted. Checked out licences remain in use until you
restart the server.
