Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

20.2 When a UAP does not execute correctly

Executor: HiRDB administrator

This section explains the actions to be taken when a UAP does not execute correctly.

Organization of this section
(1) Actions to be taken when a UAP will not execute
(2) Actions to be taken when a UAP does not terminate itself
(3) Actions to be taken when a UAP terminates abnormally

(1) Actions to be taken when a UAP will not execute

The following table lists the possible causes of UAP execution errors.

Table 20-7 Causes of UAP execution errors and actions to be taken

Possible cause Action to be taken
A HiRDB system definition is invalid A message is displayed indicating the HiRDB system definition that is invalid. Correct the definition on the basis of this message.
Memory is insufficient A message is issued indicating the memory where the shortage occurred. For shared memory, reevaluate the HiRDB system definitions. For process private memory, terminate any unneeded processes.
Too many users are executing concurrently
  • Increase the value of the pd_max_users operand.
  • If the maximum number of server processes for front-end server or single server has been changed with the pdchprc command, increase the maximum value.
An environment variable is invalid in the client environment definition See the HiRDB Version 9 UAP Development Guide and correct the environment variable.
HiRDB has not been started Start HiRDB.
For a HiRDB parallel server configuration, a specific unit or server might be shut down; in such a case, start the unit or server.

(2) Actions to be taken when a UAP does not terminate itself

Check the UAP's execution status (for the procedure, see 8.2 When a UAP or utility execution takes too long). If necessary, use the pdcancel command to terminate the UAP forcibly.

We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.

(3) Actions to be taken when a UAP terminates abnormally

If a UAP terminates abnormally, use the pdls -d prc command to check for any remaining UAP server processes. If there are any remaining UAP server processes, terminate them with the pdcancel command.

We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.