The symptoms of a FairCom DB in a non-responsive state are the following:
Requests from connected clients hang indefinitely.
Client connection attempts hang or fail with an error such as FairCom DB error 133.
A non-responsive server can be detected by monitoring connected clients and looking for client requests that have not completed within a reasonable timeframe. Note that some c tree API function calls can be expected to take a significant amount of time (for example, when rebuilding a large file or physically closing a file that has many unwritten updated cache buffers). Even reading a record can take awhile if the call must wait to acquire a lock on the record. The specific symptoms that indicate a fully non-responsive FairCom DB are that all client requests hang and new connection attempts may fail.
When FairCom DB is in a non-responsive state follow these steps to identify the cause and to correct the problem:
The ctadmn utility can be used to monitor the status of client connections, but in the event of a non-responsive server, ctadmn may be unable to connect to the server or its requests may also hang. If ctadmn can connect and can list connected clients, it may be possible to use it to terminate FairCom DB clients or to shut down FairCom DB.
If ctadmn cannot connect to the server, use system monitoring utilities to determine the state of the FairCom DB process. Verify that the process is in a running state and if possible use system utilities to save a core image of FairCom DB process and stack traces for all the server threads. See Monitoring FairCom DB in the FairCom DB Server Administrator's Guide for details about system utilities that can be used to collect information about the state of the FairCom DB process. Any information that can be collected about the state of a non-responsive server can be useful in determining the cause and finding a way to prevent future occurrences of such a problem.
To shut down a non-responsive FairCom DB, follow the steps described in the section Stopping FairCom DB in the FairCom DB Server Administrator's Guide. Shutting down a non-responsive server might require a hard kill.
