Detail codes for system-related errors

Table 4-3 lists the detail codes for system-related errors.

Table 4-3 Detail codes for system-related errors

Detail Code	Description	Explanation
-104	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-152	The number of shared memory segments is over the limit.	Increase the value specified in the SHMMAX and SHMMAX operands of the OS parameters.
-164 -201	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-203 -206	The value specified for the operand is invalid	Refer to the messages output immediately before the error, identify the invalid operand, and specify a valid value.
-204	An error occurred in the HiRDB system definition	Consider the following causes: A required HiRDB system definition was not created Refer to the section on HiRDB system definition types in the manual HiRDB Version 8 System Definition, and create any uncreated HiRDB system definitions. Eliminate any errors due to required HiRDB system definitions that cannot be referenced by entering HiRDB system definitions that can be referenced. Files under %PDDIR%\lib\sysconf cannot be referenced Make sure the files under %PDDIR%\lib\sysconf can be referenced.
-205	An error occurred in the definition analysis files of the HiRDB system definition	The files under %PDDIR%\lib\sysconf cannot be referenced. Make sure the files under %PDDIR%\lib\sysconf can be referenced.
-202 -208 -209 -210	HiRDB system internal error	Contact the customer engineer.
-301 to -399	HiRDB internal communication error (See 4.1 Detail codes for RPC-related errors.)	Contact the customer engineer.
-600	Internal error in the HiRDB system	If there is an error message, take corrective action according to the message. If there is no error message, contact a customer engineer.
-601	Communication destination server not found
-604	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-605	Version mismatch in service request test detected	Review the environment to determine whether the HiRDB client and the HiRDB server are in versions that can be interconnected and whether there are any invalid libraries on a mixed basis.
-632	Communication destination server not found	If there is an error message, take corrective action according to the message. If there is no error message, contact a customer engineer.
-640 -641	Communication error
-642	Name service facility not started.	Check to see if HiRDB has started. If it has started normally, contact a customer engineer.
-700	Process-to-process communication error	Check to see if either HiRDB or the process server has started.
-702	Invalid status	HiRDB is undergoing the following processing; if necessary, restart it, and then rerun the command: System termination processing Abnormal termination processing Forced termination processing
-706	Server startup already reported	Contact the customer engineer.
-714	Maximum number of processes exceeded	The maximum number of active server processes per unit was exceeded. Re-execute the process after another command has terminated. Or, increase the value of the pd_max_server_process operand after terminating HiRDB.
-718	Undefined local domain name	Register the host name comprising the HiRDB system in the hosts file.
-723	Mismatch between command and server versions	Check to see, for example, if HiRDB files %PDDIR%\bin of different versions are used through linking, and check the version of the entered command to ensure version consistency.
-724	Lock error	Contact the customer engineer.
-725	Server engaged in termination processing	HiRDB is undergoing termination processing. Start HiRDB, if necessary, and execute the command.
-726	Process not found	HiRDB is not active. Restart HiRDB, and then execute the command.
-727	Communication environment not started	Contact the customer engineer.
-734	Shared memory not allocated	Contact the customer engineer.
-816	Server startup failure	If the problem is on the server side, appropriate corrective action should be taken. If a problem has not occurred, contact a customer engineer.
-821	Server shut down
-830	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-832	Not enough memory	If there is a KFPS00854-W message from the server, take corrective action according to the message. If there is no error message, contact a customer engineer.
-839	HiRDB system server process terminating	After terminating HiRDB, start HiRDB.
-840	The service group specified in the client environment definition PDSERVICEGRP is in one of the following conditions: Not started Starting Stopped Error in the name of service group specified in the client environment definition PDSERVICEGRP	Review the status of the service group or the specification value in the PDSRVICEGRP operand, and take corrective action.
-856	Message queue manipulation (msgget) failure	If there is a KFPS00850-W message from the server, take corrective action according to the message.
-879	Error in server type specified in the client environment definition PDSRVTYPE	Start the HiRDB/Single Server, and then rerun the command. For a HiRDB/Parallel Server, start the front-end server at the connection destination, and then rerun the command.
-880	Message queue manipulation (msgget) failure	If there is a KFPS00850-W message from the server, take corrective action according to the message.
-888	HiRDB server not started (startup process not completed)	Restart HiRDB after the server startup processing is complete.
-889	The single-server or the front-end server to connect to is not started	Start the HiRDB/Single Server, and then rerun the command. For a HiRDB/Parallel Server, start the front-end server at the connection destination, and then rerun the command.
-892	Limit on the number of concurrent connections exceeded	Either review the value of the pd_max_users operand or reduce the number of concurrent connections to the HiRDB server.
-893	HiRDB server undergoing termination processing	After terminating HiRDB, start HiRDB.
-894	Lock processing failed during connection	If the problem persists after the command is executed repeatedly, contact a customer engineer.
-895	Mismatch in service request text versions	Review the HiRDB client and HiRDB server environments.
-897	HiRDB system server process either staring or terminating	If HiRDB is being activated, wait until the activation process is complete, and then rerun the command. If HiRDB is undergoing termination processing, activate HiRDB after it has stopped. In addition, this message can be generated if HiRDB abnormally terminates or is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.
-902 -903 -904 -905 -906 -907 -908 -909 -910 -912 -915	HiRDB system internal error	If an error message was output before this message, take action appropriate to that message. If no error message was output, contact the customer engineer.
-916	Library version incompatible with daemon version	Check the media versions comprising the HiRDB system. Use matching versions and re-execute.
-917 -918 -919	HiRDB system internal error	If an error message was output before this message, take appropriate action according to that message. If no error message was output, contact the customer engineer.
-921	Transaction not settled	After the transaction undergoing recovery processing has been settled, rerun the error-flagged transaction or the command.
-943	Due to a recovery unnecessary front-end server, utility transactions cannot be generated.	Rerun the utility on a front-end server other than the recovery unnecessary front-end server.
-944	Connection is established to a recovery unnecessary front-end server from a UAP that uses the X/Open XA interface.	Reconnect to a front-end server other than the recovery unnecessary front-end server, and rerun the command.
-945 -946 -947	Either the pdchgconf command or the pdprgrenew command is currently executing.	If the error occurred in a utility or operation command, terminate the pdchgconf or pdprgrenew command, and re-execute the utility or operation command. If the error occurred in a UAP, check the following: If the client library is version 07-00 or later: The pdchgconf or pdprgrenew command may have failed. Ask the system administrator to check HiRDB status, and re-execute the UAP once HiRDB is online. If the client library version is earlier than 07-00: Terminate the pdchgconf or pdprgrenew command, and re-execute the UAP.
-948	Scheduling of new transactions is being suppressed.	Scheduling of new transactions is being suppressed. Using the pdls -d svr command, locate the server on which scheduling of new transactions is being suppressed, and eliminate the error. If no server is suppressing the scheduling of new transactions, re-execute the utility or UAP.
-949	HiRDB system engaged in termination processing	Rerun the command when HiRDB is active.
-1006	Error in status file input/output processing	Take corrective action in reference to the preceding KFPS01040-E message.
-1012	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-1018	Status file size not large enough	Review the size of the status file and check to see if the required size is met.
-1021	Input of required information from a server status file failed	This code is sometimes generated if all server status files are initialized before HiRDB is restarted. In this case, HiRDB cannot be restarted. If this problem occurs, cancel the restart process, and recover the database from a backup file.
-1024	Status file access failure	This code can be ignored if it is generated during the abnormal termination or aborting of HiRDB or a unit, or when HiRDB or a unit is stopped. If the message is generated in other cases, contact a customer engineer.
-1033	Communication error	See Table 4-1 Frequently occurring causes and required action for RPC-related errors and take appropriate corrective action. If corrective action cannot be taken, contact a customer engineer.
-1039	No swap-destination status file found (no backup file)	Either resolve the error in the status file that generated KFPS01040-E and KFPS01042-E messages, or create a backup file.
-1110	Invalid log point information detected	For pdi_jnl_show_recovery_fg(): The following problems are suspected. Determine the cause of the error based on information output to the event log (in UNIX, syslogfile), and take corrective action. Cause 1: The record length for the system log file is different from the value specified in the pd_log_rec_leng operand. The record length for the system log file can be determined by executing the pdlogls -e command. If this is the problem, make the record length for the system log file equal to the value specified in the pd_log_rec_leng operand. Cause 2: The system log file indicated in the log point information file has been overwritten. In this case, the database cannot be recovered using the system log file. If this is the problem, restore the database to the condition that existed when a backup was made and re-execute the transactions that have occurred since the backup was made. Cause 3: The system log file indicated in the log point information file is missing. Or, the user's access privilege to the system log file is invalid. In this case, check to see whether the system log file name specified in the pdlogadpf operand is the correct one. If the system log file created during the backup creation process has been removed from the pdlogadpf operand, add the file to the pdlogadpf operand and re-execute. Whether the user's access privilege is valid can be determined by executing the pdfls command. Check to see whether the access privilege to HiRDB files has been improperly modified. Cause 4: The log point information itself contains an error. If this is the case, contact the customer engineer. For other functions: Contact a customer engineer.
-1113	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-1117 -1118	Log input starting failure	For pdi_jnl_org_get_start(): Take corrective action by seeing the preceding KFPS01170-E and KFPS01171-E messages. For other functions: Contact a customer engineer.
-1143	Log positioning failure	For pdi_jnl_org_point_set(): If there is a preceding KFPS01040-E message, take corrective action according to the message. If there is no message, contact a customer engineer. For pdi_jnl_org_get_block(): If there are preceding KFPS01170-E or KFPS01171-E messages, take corrective action according to those messages. If there is no message output, updatable online reorganization cannot be continued. If the cause of the problem needs to be investigated, contact a customer engineer. For other functions: Contact a customer engineer.
-1144	Log input failure	For pdi_jnl_org_get_block(): If there are preceding KFPS01170-E or KFPS01171-E messages, take corrective action according to those messages. If there is no message output, updatable online reorganization cannot be continued. If the cause of the problem needs to be investigated, contact a customer engineer. For other functions: Contact a customer engineer.
-1801	Internal error in the HiRDB system	Contact a customer engineer.
-1802	Definition analysis error	If there is a definition error message output before this message, revise the system definition according to the error message. If there is no error message, contact a customer engineer.
-1807 -1817	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-1811	Internal error in the HiRDB system	Contact a customer engineer.
-1850	File I/O error	Check the file privilege and confirm that the disk can be accessed. If an error message was output immediately before the error, take the indicated corrective action. If no message was output, contact a customer engineer.
-1851	Inter-process communication error	If there is an error message output, take corrective action according to the message. It is also possible that the process server has stopped. Verify whether the process server is active. In other cases, contact a customer engineer.
-1852	Internal error in the HiRDB system	Contact a customer engineer.
-1854	Internal error in the HiRDB system	This message is sometimes generated when HiRDB terminates abnormally or it is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.
-1859	System call error	If an error message was output immediately before the error, take the indicated corrective action. If no message was output, contact a customer engineer.
-1900	HiRDB system internal error	Check to see if the unit containing the system manager has started normally. The problem is sometimes caused by an error in the unit containing the system manager. In other cases, contact a customer engineer.
-1901	HiRDB internal communication error
-1902	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-1903 -1904 -1905 -1906 -1907 -1908	Internal error in the HiRDB system	Check to see if the unit with the system manager has started normally. The problem can be caused by an error in the unit with the system manager. In other cases, contact a customer engineer.
-1909	File %PDDIR%\lib\msgtxt not found	UNIX version: Recover the HiRDB execution environment according to the following procedures: Terminate HiRDB. Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message. Use the pdsetup command to re-set up HiRDB. Windows version: Re-install HiRDB.
-1910	File %PDDIR%\lib\msgtxt corrupt	UNIX version: Recover the HiRDB execution environment according to the following procedures: Terminate HiRDB. Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message. Use the pdsetup command to re-set up HiRDB. Windows version: Re-install HiRDB.
-1911	File %PDDIR%\lib\msgtxt not accessible	UNIX version: Check the access privilege for the file $PDDIR/lib/msgtxt and grant the necessary access privilege to the HiRDB administrator. If the problem persists when the valid access privilege is in place, recover the HiRDB execution environment according to the following procedures: Terminate HiRDB. Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message. Use the pdsetup command to re-set up HiRDB. Windows version: Re-install HiRDB.
-1912	Internal error in the HiRDB system	Check to see if the unit with the system manager has started normally. The problem can be caused by an error in the unit with the system manager. In other cases, contact a customer engineer.
-5100	HiRDB system internal error	Contact the customer engineer.
-5101	Communication error between servers within HiRDB	If HiRDB was aborted or has terminated abnormally, the command or utility may terminate due to this error. In this case, restart HiRDB, and then rerun the command or utility. In other cases, contact a customer engineer.
-5103	HiRDB system internal error	Contact the customer engineer.
-5105	Shared memory or temporary file access error	Contact the customer engineer.
-5108	HiRDB system engaged in termination processing	Execute the command when HiRDB is running.
-5110	Too many concurrently executing users	Wait until other users terminate. Or, increase the value of the pd_max_users operand. If the pdchprc command was used to change the maximum number of server processes for a single-server or front-end server, use the pdchprc command to increase the maximum value.
-5112	Lock timing error	Re-execute.
-5116	HiRDB is in start processing, or HiRDB is running as a log application site.	Re-execute after HiRDB start processing completes. If HiRDB is running as a log application site, convert the connection target HiRDB to a transaction execution site, and then re-execute.
-5125	Other utilities or operation commands cannot be executed because the pdvrup command is executing or was requested.	Rerun the command after HiRDB startup processing is complete.
-5137	Invalid HiRDB status	This message is sometimes generated when HiRDB terminates abnormally or it is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.
-5142 -5143 -5144	Either the pdchgconf command or the pdprgrenew command is currently executing.	If the error occurred in a utility or operation command, terminate the pdchgconf or pdprgrenew command, and re-execute the utility or operation command. If the error occurred in a UAP, check the following: If the client library is version 07-00 or later: The pdchgconf or pdprgrenew command may have failed. Ask the system administrator to check HiRDB status, and re-execute the UAP once HiRDB is online. If the client library version is earlier than 07-00: Terminate the pdchgconf or pdprgrenew command, and re-execute the UAP.
-5301	HiRDB system internal error	Contact the customer engineer.
-5302	HiRDB not active (activation process being initialized)	Wait until completion of activation of HiRDB (completion of initialization), and then rerun the command.
-5303	HiRDB system internal error	Check the cause based on the error message that was output before this message and take appropriate action. If necessary, re-execute the command.
-5304	Definition file open error	Check if the PDDIR or PDCONFPATH environment variable has been set. Check if the read privilege has been defined for %PDDIR%\conf\pdsys. If the error cannot be corrected by actions 1 and 2 above, contact a customer engineer.
-5305	Communication error	If HiRDB is operating normally, contact the customer engineer. If HiRDB has not started, wait until its activation is complete (completion of the activation-time process initialization), and then rerun the command.
-5324	Error acquiring the value of the PDDIR environment variable	The PDDIR environment variable is not set, or the directory cannot be referenced. Revise the setting of the PDDIR environment variable.
-5400	Internal error in the HiRDB system	Contact a customer engineer.
-5401	Communication error between HiRDB servers	If HiRDB is aborted or has terminated abnormally, this error can cause the command or utility to terminate. In this case, check the reasons for the communication error based on the preceding message, and take corrective action. If necessary, restart HiRDB, and then rerun the command or utility. If the condition in which HiRDB is unable to terminate persists due to the pdstop command causing this error, use the kill-6 command of the OS (in Windows, the pdkill command) to delete the pdrdmd process of HiRDB, forcibly terminate the unit. Save the data under the path %PDDIR%\spool, and then contact a customer engineer.
-5800	There is no HiRDB file system for audit trail files or there is no audit trail file.	Check if the audit trail file name specified in the control statement file used when the pdload command was executed is correct. If the problem occurs in command other than the pdload command, it is an indication of an internal HiRDB system error. If that is the case, contact a customer engineer.
-5801	HiRDB system internal error.	Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact a customer engineer.
-5805
-5810
-5825
-5802	HiRDB system internal communication error.
-5803	There is no audit trail file that can be swapped.	Take the following corrective action to secure a file that can be swapped. Contact the auditor so that the file whose data is waiting to be loaded can be loaded into an audit trail table. For details about how to handle errors that occur in audit trail files, see the HiRDB Version 8 System Operation Guide.
-5806 -5807	An error occurred when an audit trail file was opened.	Data loading cannot be performed because the audit trail file specified in the control statement file used when the pdload command was executed is in one of the following states: Shutdown status Current Data loading completed Not created To resolve the error, correct the control statement file and re-execute the pdload command. If this method does not resolve the problem, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact a customer engineer.
-5809	Not enough process-private memory	In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.
-5817	Audit facility stopped; unable to acquire audit trail	If the audit facility was running, check the reason for its stoppage based on the preceding message. If necessary, use the pdaudbegin command to run the audit facility.
-20****: Any numeric character	System call error (The value obtained when the detail code is subtracted from -20000 is the system call errno.)	See Table 4-4 to check the cause of the system call error, and take corrective action.
-20999	Other system call error	Contact the customer engineer.
Other		Contact the customer engineer.

[Figure] : Not applicable

4.2 Detail codes for system-related errors