RPC-related errors are output in cases such as the following:
If an RPC-related error is output, check the detail codes in Table 4-2, as well as the contents of frequently occurring causes in Table 4-1. Also, if an error message caused by a communication error is output, in some cases RPC-related detail error codes do not appear in the message. In this case, too, contents of frequently occurring causes in Table 4-1 should be checked.
Note that even when a detail code for RPC-related errors is output, the problem can sometimes be resolved through an internal retry. The problem should be investigated and corrective action should be taken in the following cases:
The following table shows frequently occurring causes and the required corrective action to take for RPC-related errors.
Table 4-1 Frequently occurring causes and required action for RPC-related errors
No. | Error description | Meaning | Action |
---|---|---|---|
1 | Host name or port number error |
| Review the following definitions, and revise as necessary:
|
2 | System resources shortage |
| Take one of the following actions:
|
3 | Unresolvable host name or IP address | In the gethostbyname or gethostbyaddr system call, a conversion failure occurred from host name to IP address or from IP address to host name. | Check the following items and revise as necessary:
|
4 | Invalid /dev/HiRDB/pth | The /dev/HiRDB/pth directory is invalid.
| Check to see if HiRDB is correctly installed. If HiRDB is correctly installed, terminate all copies of HiRDB running on the indicated unit, and take the following actions:
|
5 | Unit or server errors | The communication destination unit or server is not running. There has been a spike in the CPU usage rate of the machine where the HiRDB client or server is allocated. | Take the following corrective action: Start the communication destination unit or the server. If the unit or the server has abnormally terminated, check the preceding message, resolve the cause of the error, and then restart the unit or server. If the online status can be maintained in this condition (such as during reduced operation), the problem can be ignored. Determine the reason for the spike in the CPU usage rate of the machine where the HiRDB client or HiRDB server is allocated, and then take corrective action. |
6 | Network error | A network error occurred.
| Take one of the following actions:
|
7 | Firewall settings | The firewall is preventing communication.
| In this case, take the following actions:
|
The following table lists the detail codes for RPC-related errors.
Table 4-2 Detail codes for RPC-related errors
Detail Code | Name | Explanation | Action |
---|---|---|---|
-301 | PDRPCER_INVALID_ARGS | Argument is invalid | See Table 4-1 Frequently occurring causes and required action for RPC-related errors to determine if there are applicable errors. If there are no applicable errors, refer to the event logs (in UNIX, syslogfile) of all server units and the OS log files (such as the hard disk logs) to determine whether any error messages were output immediately before the error. If there is an error message, take corrective action according to the message. If no error messages were output and no corrective action can be taken, save the event logs (in UNIX, syslogfile) for all server units and the files under %PDDIR%\spool, and contact the customer support center. |
-302 | PDRPCER_PROTO | Protocol error occurred (function sequence is invalid). | Take corrective action for detail code -301. |
-303 | PDRPCER_FATAL | The following are possible causes: (1) Not enough memory. (2) Invalid system definition. (3) Error in a system file. (4) Not enough communication resources.
(6) The number of activated processes exceeded the value specified in the pd_max_server_process operand. (7) Error in the host name or port number. (8) Unable to resolve the host name. For other than the above, a fatal or unexpected error occurred. | If the cause is (1), (4), (5), (7) (8), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. If the cause is (2), execute the pdconfchk command to revise the operand in error. If the cause is (6), either reduce the number of startup processes (pd_max_users, pd_process_count, etc.) or increase the maximum number of startup processes (pd_max_server_process). In other cases, see the corrective action for detail code -301. |
-304 | PDRPCER_NO_BUFS | The following are possible causes: (1) Not enough memory. (2) The number of files that can be opened in the system exceeds the limit (3) The number of files that can be opened in the process exceeds the limit. (4) The server is terminating. (5) The service is not registered. (6) The number of ports is insufficient (in Windows only) | If the cause is (1), (2), (3), or (6), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. If the cause is (4), restart the server and rerun the command. If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified). In other cases, see the corrective action for detail code -301. |
-306 | PDRPCER_NET_DOWN | An error occurred during communication processing or communication resource allocation processing. The following are possible causes: (1) Not enough memory (2) Not enough communication resources.
(4) Invalid host name or port number. (5) Unable to resolve the host name. (6) A network error occurred. (7) The communication destination unit or the server is not running. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-307 | PDRPCER_TIMED_OUT | Timeout occurred. If an error occurs in the UAP, command or utility, or an error occurs in the system server, preventing further online operations, the following possible causes should be suspected: (1) A network error occurred. (2) The communication destination unit or the server terminated abnormally. (3) The specification value for the pd_watch_time operand of the system definitions was exceeded. | This message can be ignored. However, if an error occurred in the UAP, command, or utility, or in the system server, preventing further execution of online operations, see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. If the cause is (3), see the manual HiRDB Version 9 System Definition, and revise the specification value for the pd_watch_time operand. |
-308 | PDRPCER_MESSAGE_TOO_BIG | Input parameter length exceeds the limit. | See the corrective action for detail code -301. |
-309 | PDRPCER_REPLY_TOO_BIG | Reply length exceeds the length of the area provided by the calling source. | |
-310 | PDRPCER_NO_SUCH_SERVICE_GROUP | The communication destination unit or the server is not running. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-311 | PDRPCER_NO_SUCH_SERVICE | Service has not been registered. | It is possible that a server name other than a single server or a front-end server is specified in the client environment definition PDSERVICEGRP. In other cases, see the corrective action for detail code -301. |
-312 | PDRPCER_SERVICE_CLOSED | The communication destination unit or the server is not running. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-313 | PDRPCER_SERVICE_TERMINATING | Service is engaged in termination processing. | See the corrective action for detail code -301. |
-314 | PDRPCER_SERVICE_NOT_UP | An error occurred during communication processing or communication resource allocation processing. The following are possible causes: (1) Not enough memory. (2) Not enough communication resources.
(4) Invalid host name or port number. (5) Unable to resolve the host name. (6) A network error occurred. (7) The communication destination unit or the server is not running. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-315 | PDRPCER_OLTF_NOT_UP | The communication destination unit or the server is not running. | |
-316 | PDRPCER_SYSERR_AT_SERVER | A system error occurred. | See the corrective action for detail code -301. |
-317 | PDRPCER_NO_BUFS_AT_SERVER | The following are possible causes: (1) Not enough memory. (2) The number of files that can be opened by the system exceeded the limit. (3) The number of files that can be opened by the process exceeded the limit. (4) The server is terminating. (5) The service is not registered. | If the cause is (1), (2), or (3), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. If the cause is (4), restart the server and rerun the command. If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified). In other cases, see the corrective action for detail code -301. |
-318 | PDRPCER_SYSERR | System error occurred. | See the corrective action for detail code -301. |
-319 | PDRPCER_INVALID_REPLY | Length of reply is invalid after execution of service function. | |
-320 | PDRPCER_OLTF_INITIALIZING | The communication destination unit or the server is not running. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-321 | PDRPCER_ALL_RECEIVIED | All text has been received. | See the corrective action for detail code -301. |
-323 | PDRPCER_NO_BUFS_RB | The following are possible causes: (1) Not enough memory. (2) The number of files that can be opened in the system exceeds the limit. (3) The number of files that can be opened in the process exceeds the limit. (4) The server is terminating. (5) The service is not registered. | If the cause is (1), (2), or (3), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. If the cause is (4), restart the server and rerun the command. If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified). In other cases, see the corrective action for detail code -301. |
-324 | PDRPCER_SYSERR_RB | A system error occurred. | See the corrective action for detail code -301. |
-325 | PDRPCER_SYSERR_AT_SERVER_RB | ||
-326 | PDRPCER_REPLY_TOO_BIG_RB | The reply length exceeds the length of the area provided by the calling source. | |
-330 | PDRPCER_NO_POOL_AT_SERVER | There are not enough shared memory buffers to store the required telegraphic messages during process allocation. The following are possible causes: (1) The pdchprc command was used to request service from the server for which the maximum number of startup processes had been set to 0. (2) Service was requested from refreshing servers by using the pdpfresh command. (3) Too many UAPs were executed concurrently. (4) Too many utilities were executed concurrently. | If the cause is (1), use the pdchprc command to increase the maximum number of startup processes. If the cause is (2), re-execute after the pdpfresh command terminates. If the cause is (3), revise the number of UAPs executed concurrently. If the cause is (4), revise the number of utilities executed concurrently. To find out the maximum number of utilities that can be executed concurrently, see manual HiRDB Version 9 Command Reference. |
-335 | PDRPCER_ROLLBACK_INTR | An internal rollback request was received. This message is generated when the pdstop command is executed while a utility is running or when a process related to the transaction or utility goes down. | If a message indicating an internal rollback as the cause was output before this message, take corrective action according to that message. If there is no message, contact the customer support center. |
-344 | PDRPCER_NO_DEVPTH | Directory /dev/HiRDB/pth is invalid. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-350 | PDRPCER_UNLOAD_FRAGMENT | Fragment was damaged. | See the corrective action for detail code -301. |
-351 | PDRPCER_NO_SUCH_TYPES | Representation format specified for type conversion is not supported. | |
-352 | PDRPCER_NO_SUCH_ADDR | The specified IP address is not defined, or the IP address cannot be converted. | See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-353 | PDRPCER_NO_SUCH_NODENAME | The specified host name is not defined, or the host name cannot be converted. | |
-354 | PDRPCER_TOO_MANY_HANDLERS | The number of handlers exceeded the permitted value per process. | See the corrective action for detail code -301. |
-355 | PDRPCER_NOT_FOUND | Specified thread was not found or is a control thread. | |
-356 | PDRPCER_SERVER_BUSY | The following are possible causes: (1) There is too much load on the server, making it unable to perform service. (2) A memory shortage occurred. | If the cause is (1), rerun the command after a period of time. If this does not resolve the problem, see the corrective action for detail code -301. If the cause is (2), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-357 | PDRPCER_SERVICE_INITIALIZING | RPC environment has not been started. | See the corrective action for detail code -301. |
-359 | PDRPCER_ALREADY_REPLIED | A reply has already been issued. | If the UAP, command, or utility is not in error, ignore this message. If there is an error in the UAP, command, or utility, see the corrective action for detail code -301. |
-360 | PDRPCER_NOT_UPP_STARTED | The pdi_upp_start operand is not issued. | See the corrective action for detail code -301. |
-361 | PDRPCER_NO_SERVICE_CLAUSE | A service clause is not defined in the user service definition. | |
-362 | PDRPCER_WRONG_NUMBER | Data other than nam was specified when registering, deleting, or retrieving service information in nam. | |
-363 | PDRPCER_UPP_FAILED | Acquisition of the system definition failed. The following are possible causes: (1) The system definition contains an error. (2) A memory shortage occurred during the acquisition of the system definition. | If the cause is (1), revise the system definition. If the cause is (2), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action. |
-364 | PDRPCER_ERROR_REPLIED | Error occurred at the server. | See the corrective action for detail code -301. |
-365 | PDRPCER_TRACE_FILE_EMPTY | Trace file contains no data. | |
-371 | PDRPCER_PROFILE | The value of the pd_registered_port operand is invalid. | Take corrective action according to the preceding KFPS00346-E and KFPS00348-E messages. |
-372 | PDRPCER_RETRY_CONNECT | It is one of the following situations:
(1) The client library being used is older than Version 07-01. (2) Either the pdchgcnf or pdprgrenew command failed, preventing HiRDB from starting. (3) Transaction queuing was not released after it was started by the pdtrnqing command. | If the UAP has not generated a connection error, disregard this message.
|
-373 | PDRPCER_RETRY_TRANSACTION | ||
-374 | PDRPCER_RETRY_STOPPING | ||
-375 | PDRPCER_RETRY_STARTING | ||
-376 | PDRPCER_TRNPAUSE | The new transaction scheduling suppressed status is on. | Use the pdls -d svr command to identify the server in a new transaction scheduling suppressed status and resolve the cause of the error. If there is no server in a new transaction scheduling suppressed status, rerun the UAP or the utility. |
Other | -- | -- | See the corrective action for detail code -301. |