
1-105
1 to 199
For more information about purchasing and installing additional
user counts, refer to Getting Started With Pervasive PSQL. You can
use Monitor to determine which users currently have connections to
Pervasive PSQL. For information about Monitor, refer to Advanced
Operations Guide.
You may also receive this status code if your machine configuration
changed since you authorized Pervasive PSQL. To avoid this error,
delete the key, make any necessary machine configuration changes,
and then apply the key again.
162: The client table is full
This status code is obsolete in Pervasive.SQL 2000i and later
versions. The related configuration setting is managed dynamically
by the engine.
You may receive this status code due to one of the following:
You have run out of memory.
Your number of Active Clients has exceeded 64K.
163: The NULL indicator cannot be the last segment
The NULL indicator segment (NIS) cannot be the last segment of the
key descriptor.
169: Protocol mismatch between client cache and remote
engine
This status code indicates that your client software is not up-to-date
with your remote database engine. You should only receive this
status code if you are running V8 pre-release client software against
a V8 general-release remote engine.
The solution for this issue is to uninstall your client software and
install the latest V8 client.
170: Database login required
Authentication to the database failed due to a wrong or missing
username.
Comentários a estes Manuais