When FairCom DB or system monitoring tools detect unexpected system or server resource usage, follow these steps to identify the cause of the unexpected resource usage so the problem can be understood and resolved:
Identify the nature of the unexpected resource usage as specifically as possible. For example:
Is the resource a system resource or a FairCom DB resource? If a system resource, use system tools to identify the process that is directly responsible for the unexpected resource usage. If the responsible process is the c tree Server, use application and FairCom DB monitoring tools to identify whether activity by particular clients accounts for the change in resource usage. System tools can be used to monitor system calls, dump a core image of the server, or stack traces for server threads. The ctadmn utility can be used to terminate clients suspected of contributing to the unexpected resource usage.
Does the unexpected resource usage occur consistently, or does it occur only occasionally? Any pattern that can be identified might help determine the cause of the behavior.
Consider whether any recent changes to the system could account for the unexpected resource usage. For example:
Has the system load changed (for example are more than the usual number of clients using the server or are the clients performing different different operations than usual)? Application monitoring tools and the c tree Server’s snapshot ability can help identify whether the load on the system has changed recently.
Have there been any hardware or software changes (including FairCom DB configuration option changes)?