4.1 Detail codes for RPC-related errors

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 descriptionMeaningAction
1Host name or port number error
  • The host name or port number specified in the client environment definition contains an error.
  • The host name or port number specified in the system definition contains an error.
Review the following definitions, and revise as necessary:
  • Client environment definitions:
    PDHOST
    PDFESHOST
    PDCLTRCVADDR
    PDNAMEPORT
    PDSERVICEPORT
    PDCLTRCVADDR
    PDCLTRCVPORT
    PDFESGRP
  • System definitions:
    pd_name_port
    pd_service_port
    pd_scd_port
    pd_trn_port
    pd_mlg_port
    pd_alv_port
    The -x, -c, -p, -s, -t, -m, and -a options of the pdunit operand
    pd_hostname
    pd_registered_port
    The -x, -m, and -n options of the pdstart operand
    pd_security_host_group
2System resources shortage
  • Not enough ports
  • Not enough memory
  • Not enough files that can be opened by the system
  • Not enough files that can be opened by processes
  • Message queue operation error
Take one of the following actions:
  • Not enough ports:
    Take corrective action according to the contents of the preceding KFPS00349-E message.
  • Not enough memory:
    There is not enough process-private area. Review the memory requirements. Terminate any unneeded processes.
  • Not enough files that can be opened by the system (the limit on files that can be opened has been exceeded):
    In UNIX:
    Increase the value specified for the maximum number of files that can be opened by the system, using the operating system parameter (kernel parameter) (nfile for HP-UX, maxuproc[Figure] nofiles[Figure] number of fixed licenses for AIX, or NR_FILE or fs.file-max for Linux). Also, terminate any unneeded processes and windows.
    In Windows:
    On the installation drive, allocate at least as much free space as is required for the shared memory size.
  • Not enough files that can be opened by a process (the limit on the number of files that can be opened has been exceeded):
    In UNIX:
    Increase the maximum number (maxfiles_lim for HP-UX, rlim_fd_max for Solaris, nofiles_hard for AIX, or NR_OPEN for Linux) of files that can be opened by a process, using the OS parameter (kernel parameter). If the specification value for pd_max_open_fds is too small, it should be increased.
    In Windows:
    On the installation drive, allocate at least as much free space as is required for the shared memory size.
  • Message queue manipulation error:
    In UNIX:
    Review message queue-related parameters in terms of OS parameters (kernel parameters).
    In Windows:
    On the installation drive, allocate at least as much free space as is required for the shared memory size. Or, assign the required number of resources to the system environment variable PDUXPLMSGMNI (number of message queue identifiers) or to the system environment variable PDUXPLMSGTQL (number of message queue tables). For making estimates, see the HiRDB Version 9 Installation and Design Guide.
3Unresolvable host name or IP addressIn 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:
  • hosts file settings error
  • Invalid privilege for the hosts file
  • Settings errors on various DNS and NIS settings files (nsswitch.conf, resolv.conf, etc.)
  • Invalid privilege for various DNS and NIS settings files (nsswitch.conf, resolv.conf, etc.)
Note that if DNS or NIS is used, errors can occur during communications with the DNS or NIS server. Also, an error can occur in a multiple-unit configuration if the host name used by HiRDB is given the loopback address (127.0.0.1).
4Invalid /dev/HiRDB/pthThe /dev/HiRDB/pth directory is invalid.
  • inode shortage
  • Directory not found
  • Invalid privilege
  • Other
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:
  • inode shortage:
    Delete the files under the path /dev/HiRDB/pth.
  • Directory not found, invalid privilege, etc.:
    Execute the pdsetup -d command, followed by the pdsetup command.
    After running the pdsetup -d command, run the pdsetup command again. If you do not have valid permissions, delete the /dev/HiRDB and /dev/HiRDB/pth directories prior to running the pdsetup command.
For Linux ES 4 and AS 4, check for the following problems:
  • If you do not have permissions to the /etc/udev/devices/HiRDB or /etc/udev/devices/HiRDB/pth directories:
    Delete the directories for which you do not have valid permissions, and then run the pdsetup command again.
  • If both the /etc/udev/devices and /lib/udev/devices directories exist:
    If the /etc/udev/devices/HiRDB and /etc/udev/devices/HiRDB/pth directories do not exist, create them as a superuser and restart the OS. However, set the permissions for the /etc/udev/devices/HiRDB and /etc/udev/devices/HiRDB/pth directories as 755 and 777, respectively.
In Linux 5 and later, also check the following:
  • If you do not have permissions to the /lib/udev/devices/HiRDB or /lib/udev/devices/HiRDB/pth directories:
    Delete the directories for which you do not have valid permissions, and then run the pdsetup command again.
5Unit or server errorsThe 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.
6Network errorA network error occurred.
  1. Hardware error
  2. Software error in a layer below the OS level
  3. Insufficient Listen queue
  4. There may be a set period of time for communication.
This is true even for temporary network errors related to network load.
Take one of the following actions:
  1. Use the ping command of the OS to determine if the network for the host being used is operating normally.
  2. Refer to the OS manual to determine if there is a network error.
  3. It is possible that the Listen queue is full due to the occurrence of too many requests for connection to the HiRDB server. If that is the case, wait for a period of time and then re-execute. In UNIX, increase the value specified for the Listen queue.
  4. Determine the cause of the heavy network load, and take corrective action.
You might not be able to confirm the cause of a temporary network error. If the network still doesn't work even after some time has passed, and an RPC-related error details code is output, forcibly terminate the HiRDB system# and then restart it.
7Firewall settingsThe firewall is preventing communication.
  1. Between the HiRDB client and server
  2. Between the HiRDB servers
In this case, take the following actions:
  1. Revise the firewall settings between the HiRDB client and HiRDB server, and do likewise for the HiRDB settings.
    For information on operation when you have set the HiRDB settings and firewall settings between the HiRDB client and HiRDB server, see Settings when a firewall and NAT are installed in the HiRDB Version 9 Installation and Design Guide.
  2. If firewall settings between the HiRDB servers were set, remove the firewall settings.
#
If you forcibly terminate a HiRDB system consisting of two or more units, perform the following procedure:
  1. Run the pdstop -z command in all units where the MGR is not allocated, and forcibly terminate those units.
  2. Run the pdstop -z or pdstop -f command in units where the MGR is allocated, and forcibly terminate those units.

The following table lists the detail codes for RPC-related errors.

Table 4-2 Detail codes for RPC-related errors

Detail CodeNameExplanationAction
-301PDRPCER_INVALID_ARGSArgument is invalidSee 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.
-302PDRPCER_PROTOProtocol error occurred (function sequence is invalid).Take corrective action for detail code -301.
-303PDRPCER_FATALThe following are possible causes:
(1) Not enough memory.
(2) Invalid system definition.
(3) Error in a system file.
(4) Not enough communication resources.
  • A shortage of ports
  • The number of files that can be opened in the system or process exceeds the limit.
(5) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(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.
-304PDRPCER_NO_BUFSThe 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.
-306PDRPCER_NET_DOWNAn error occurred during communication processing or communication resource allocation processing. The following are possible causes:
(1) Not enough memory
(2) Not enough communication resources.
  • Not enough ports.
  • The number of files that can be opened in the system or process exceeds the limit.
(3) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(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.
-307PDRPCER_TIMED_OUTTimeout 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.
-308PDRPCER_MESSAGE_TOO_BIGInput parameter length exceeds the limit.See the corrective action for detail code -301.
-309PDRPCER_REPLY_TOO_BIGReply length exceeds the length of the area provided by the calling source.
-310PDRPCER_NO_SUCH_SERVICE_GROUPThe 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.
-311PDRPCER_NO_SUCH_SERVICEService 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.
-312PDRPCER_SERVICE_CLOSEDThe 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.
-313PDRPCER_SERVICE_TERMINATINGService is engaged in termination processing.See the corrective action for detail code -301.
-314PDRPCER_SERVICE_NOT_UPAn error occurred during communication processing or communication resource allocation processing. The following are possible causes:
(1) Not enough memory.
(2) Not enough communication resources.
  • Not enough ports.
  • The number of files that can be opened in the system or process exceeds the limit.
(3) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(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.
-315PDRPCER_OLTF_NOT_UPThe communication destination unit or the server is not running.
-316PDRPCER_SYSERR_AT_SERVERA system error occurred.See the corrective action for detail code -301.
-317PDRPCER_NO_BUFS_AT_SERVERThe 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.
-318PDRPCER_SYSERRSystem error occurred.See the corrective action for detail code -301.
-319PDRPCER_INVALID_REPLYLength of reply is invalid after execution of service function.
-320PDRPCER_OLTF_INITIALIZINGThe 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.
-321PDRPCER_ALL_RECEIVIEDAll text has been received.See the corrective action for detail code -301.
-323PDRPCER_NO_BUFS_RBThe 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.
-324PDRPCER_SYSERR_RBA system error occurred.See the corrective action for detail code -301.
-325PDRPCER_SYSERR_AT_SERVER_RB
-326PDRPCER_REPLY_TOO_BIG_RBThe reply length exceeds the length of the area provided by the calling source.
-330PDRPCER_NO_POOL_AT_SERVERThere 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.
-335PDRPCER_ROLLBACK_INTRAn 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.
-344PDRPCER_NO_DEVPTHDirectory /dev/HiRDB/pth is invalid.See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
-350PDRPCER_UNLOAD_FRAGMENTFragment was damaged.See the corrective action for detail code -301.
-351PDRPCER_NO_SUCH_TYPESRepresentation format specified for type conversion is not supported.
-352PDRPCER_NO_SUCH_ADDRThe 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.
-353PDRPCER_NO_SUCH_NODENAMEThe specified host name is not defined, or the host name cannot be converted.
-354PDRPCER_TOO_MANY_HANDLERSThe number of handlers exceeded the permitted value per process.See the corrective action for detail code -301.
-355PDRPCER_NOT_FOUNDSpecified thread was not found or is a control thread.
-356PDRPCER_SERVER_BUSYThe 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.
-357PDRPCER_SERVICE_INITIALIZINGRPC environment has not been started.See the corrective action for detail code -301.
-359PDRPCER_ALREADY_REPLIEDA 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.
-360PDRPCER_NOT_UPP_STARTEDThe pdi_upp_start operand is not issued.See the corrective action for detail code -301.
-361PDRPCER_NO_SERVICE_CLAUSEA service clause is not defined in the user service definition.
-362PDRPCER_WRONG_NUMBERData other than nam was specified when registering, deleting, or retrieving service information in nam.
-363PDRPCER_UPP_FAILEDAcquisition 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.
-364PDRPCER_ERROR_REPLIEDError occurred at the server.See the corrective action for detail code -301.
-365PDRPCER_TRACE_FILE_EMPTYTrace file contains no data.
-371PDRPCER_PROFILEThe value of the pd_registered_port operand is invalid.Take corrective action according to the preceding KFPS00346-E and KFPS00348-E messages.
-372PDRPCER_RETRY_CONNECTIt is one of the following situations:
  • The pdchgconf command is running
  • The pdprgrenew command is running
  • A transaction is queuing due to the pdtrnqing command
If the UAP generated a connection error, the following possible causes should be suspected:
(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.
  • If the cause is (1):
    Wait until the pdchgcnf and pdprgrenew commands terminate, and then re-execute the commands.
    During transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the command.
  • If the cause is (2):
    Resolve the cause of the error, restart HiRDB, and then re-execute the command.
  • If the cause is (3):
    Release transaction queuing, and then re-execute the command.
-373PDRPCER_RETRY_TRANSACTION
-374PDRPCER_RETRY_STOPPING
-375PDRPCER_RETRY_STARTING
-376PDRPCER_TRNPAUSEThe 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.