2
|
Authorize Pervasive PSQL using License Administrator. See To Authorize a Key for the GUI and To Authorize a Key for the CLI.
|
2
|
•
|
Active – key is authorized and available for use.
|
•
|
Inactive – key is no longer in use. This state is reserved for situations where the key is incompatible with the current engine. Examples would include previous versions of Pervasive PSQL, such as v10 and prior on v11, or a Workgroup key on a Server engine, or 32 bit key on a 64-bit engine.
|
•
|
Expired – key is no longer available for use. Temporary keys move to the Expired state once their evaluation period has passed.
|
•
|
Disabled – key is no longer available for use. If a key is disabled because of a failed validation, it can be restored to active by fixing the problem and then performing a validation on the key.
|
•
|
Failed Validation – key is usable but only for a set number of days. See Failed Validation and Failed-Validation Period.
|
1The Windows 32-bit version of Pervasive PSQL Server or Pervasive PSQL Vx Server can be installed on a Windows 64-bit machine but must run under the Windows-on-Window (WOW) execution layer.
|
1The Linux 32-bit version of Pervasive PSQL Server or Pervasive PSQL Vx Server can be installed and run on a Linux 64-bit machine.
|