Note: Pervasive recommends that you use client requesters that are the same version as the database engine. If you choose, you may use a client requester that is an older version than the database engine with which it interacts. In some situations, depending on the type of SDK access method used by your application, an older version requester will not work with the database engine. Your application will be unable to communicate with the database engine. For those situations, you must use client requesters that are the same version as the database engine.
Client requesters that are a
newer version than the database engine may or may not function correctly. Pervasive does not guarantee that newer versions of client requesters will function correctly with older versions of the engine. Therefore, Pervasive recommends that you
avoid the use of newer version client requesters with an older engine.
On Windows, open Services under
Administrative Tools. Verify that
Pervasive PSQL Transactional Engine and
Pervasive PSQL Relational Engine have been started. If not, start these services.
If everything checks out so far, but you still cannot get to the data you want to access, make sure a server DSN has been set up for your target data. Using PCC, expand the Databases node for that server and inspect the databases that are present. Make sure one of the databases represents the data you want to access. If so, then a server DSN has been created for your data.
Ensure that your client is using the same protocol. Using PCC, right-click on Local Client then click
Properties. Click
Communication Protocols and ensure that the correct protocol is selected in the
Supported Protocols list.
The parameter -vmargs is required if you specify the other parameters.
The parameter -Xms specifies the
minimum amount of memory to allocate to PCC. The parameter
-Xmx specifies the
maximum amount of memory to allocate to PCC. If you specify the
-Xms parameter, you must also specify the
-Xmx parameter.