The following sections provide some guidelines for fixing problems that may arise when you run an Objectivity/DB application.
Federated Database Does Not Open
- Verify that the
OO_FD_BOOTenvironment variable is set to the path of the boot file, or that the full pathname for the boot file is correct.
- Check the network node specified for the lock server in the boot file to make sure that
ooLockServerNameis set to the correct value.
- Verify that the federated database number specified by the
ooFDNumbervalue in the boot file is unique.
- Verify that the federated database has a license that is valid for the application you are running.
Lock Server Not Running
oolockmonto check whether a lock server is running. If necessary, run
oolockserverto start a lock server on your machine.
Object Does Not Open
- Verify that a lock server is running on the node specified by the
ooLockServerNamevalue in the boot file.
- Check whether a network failure is preventing access to the node where the lock server is running.
- If a
dbxsession was terminated while debugging an application, check if any locks remain.
- If your application is run in single-user mode (which turns off locking), make sure that other applications are not accessing the same data.
Lock Server Timed Out
- Consider moving the lock server to a less congested host.
- Consider increasing the network timeout period by setting the
OO_RPC_TIMEOUTenvironment variable to the desired number of seconds (greater than the default of 25 seconds).
- If you are accessing files on a UNIX host running NFS, consider decreasing the NFS data packet size by setting the
OO_NFS_MAX_DATAenvironment variable to the desired number of bytes (less than the default of 8192 bytes).
Monday, August 20, 2012