Configuration of UnivDBAcGrLkTest

For each lock mode, this test reveals the number of active group locks in that mode. The detailed diagnostics provided by this test provide deep insights into these locks, and in the process, enables administrators to figure out:

• Which processes are holding what type of lock?

• Which process is holding a lock on which group of which file?

With the help of these details, administrators can identify processes that are unnecessarily holding a lock, and can unlock the files and groups so locked, so as to ease processing.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the host for which the test is to be configured in the HOST text box.

• Specify the port at which the specified HOST listens to in the PORT text box. By default, this is 31438.

• This test uses UniVerse shell commands to pull the desired metrics from the server. To enable the test to run these commands, provide the path to the bin folder of the UniVerse install directory. For example, for a Windows installation of UniVerse, the UNIVERSE SHELL PATH can be: C:\U2\UV. For a Unix installation, your specification can be: \usr\uv

• U2 DBTools include Eclipse-based tools for programming and administration. Eclipse is an integrated development environment (IDE). It contains a base workspace and an extensible plug-in system for customizing the environment. Eclipse is written mostly in Java and its primary use is for developing Java applications. Where Eclipse IDE is installed, the eG agent should be configured to use the Eclipse environment for executing the UV shell commands. In this case therefore, type the full path to the Eclipse home directory. By default however, the ECLIPSE PATH is set to none, indicating that by default, the eG agent runs the commands from the UniVerse shell only and not Eclipse.

• This test reports detailed diagnostics for the interactiveSessions and backgroundSessions measures. By default, the details of these sessions - eg., the user who launched the sessions, the commands last executed in the sessions, and the terminal that the user logged in from, will be reported as part of detailed diagnosis. The login time of the user will however, not be reported as part of the detailed measures by default. This is why, the INCLUDE LOGGED IN TIME flag is set to No by default. To make sure that the detailed diagnosis includes the login time of the user as well, set this flag to Yes.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.