KFPD00001-E S
System initialization error occurred aa....aa
- An error occurred during system initialization.
- aa....aa: The following character string is displayed:
- illegal MASTERDIR: Contents of the master directory are invalid.
- S: Terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPD00003-E S
File I/O error on aa....aa func=bb....bb errno=cc....cc
- An error occurred during file I/O processing.
- aa....aa: Server name
- bb....bb: Name of function resulting in the error
- cc....cc: Value of errno
- S: Terminates abnormally.
- O: Check the cause of the error on the basis of the displayed function name and errno value and take appropriate action.
KFPD00004-E S
System call error occurred on aa....aa func=bb....bb errno=cc....cc
- A system call error occurred.
- aa....aa: Name of processing resulting in the error
- bb....bb: Name of function resulting in the error
- cc....cc: Value of errno
- S: Resumes processing when code convert is displayed as the name of the processing resulting in the error; otherwise, terminates abnormally.
- O: Check the cause of the error on the basis of the displayed function name and errno value and take appropriate action.
- Action
- Name of process where the error occurred is pdi_olk_thdlock and the value of errno is -20023
- An attempt was made to open a file when the number of files that the system can open simultaneously has been exceeded. Increase the maximum number of files that the system can open simultaneously. In UNIX, see Estimating operating system parameters in the manual HiRDB Version 9 Installation and Design Guide. In Windows, increase the memory.
- Name of process where the error occurred is pdi_olk_thdlock and the value of errno is -20024
- An attempt was made to open a file when the number of files that a process can open simultaneously has been exceeded. Increase the maximum number of files that a process can open simultaneously. In UNIX, see Estimating operating system parameters in the manual HiRDB Version 9 Installation and Design Guide. In Windows, increase the memory.
KFPD00005-E S
Server initialization error occurred on aa....aa func=bb....bb return code=cc....cc
- An error occurred during server startup.
- aa....aa: Name of server resulting in the error
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Terminates abnormally.
- Action
- Name of process resulting in the error is pdi_omm_mget and the error code is -142:
- Reduce the values specified as the buffer length for table definition information (pd_table_def_cache_size), buffer length for user privilege information (pd_auth_cache_size), and buffer length for view analysis information (pd_view_def_cache_size).
- Name of process where the error occurred is pdi_omm_mget and the error code is -143
- Revise the value specified for the shared memory size (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) of the server definition of the server where the error occurred. Revise the specification, and restart the server.
- Name of process resulting in the error is pdi_adm_pddicinf or pdi_adm_pdbesinf and the error code is -1807:
- Because the process private memory size is insufficient, wait until another process terminates and re-execute. Or, increase the swap area.
- Other:
- Contact the customer support center.
KFPD00008-E S
Internal inconsistency occurred on aa....aa(bb....bb,cc....cc,dd....dd)
- Internal conflict occurred.
- aa....aa: Name of server resulting in the error
- bb....bb: Maintenance information 1
- cc....cc: Maintenance information 2
- dd....dd: Maintenance information 3
- S: Terminates abnormally.
- Action
- Contact the customer support center. Ignore this message in the following case:
- This message was output during normal termination or planned termination, bb....bb in the message is dicsfenv.c, and cc....cc is -949.
KFPD0011-E L
Process initialization error occurred on aa....aa, func=bb....bb return code=cc....cc
- An error occurred during processing startup.
- aa....aa: Name of server at which the error occurred
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Terminates abnormally.
- Action
- If bb....bb is p_f_dic_hds_start, take action appropriate to the KFPD00026-E message that is output before the current message. In all other cases, contact the customer support center.
KFPD00012-E L
Transaction initialization error occurred on aa....aa func=bb....bb return code=cc....cc
- An error occurred during transaction startup processing.
- aa....aa: Name of server resulting in the error
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- Name of process where the error occurred is pdi_omm_mget and the error code is -143
- Revise the specification of the shared memory size (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) of the server that issued the error. Revise the specification, and restart the server.
- Name of process where the error occurred is pdi_adm_pddicinf or pdi_adm_pdbesinf, and the error code is -1807
- The process native memory is insufficient. Wait for the other processes to terminate and then re-execute, or increase the swap area.
- Other than the above
- Contact the customer support center.
KFPD00013-E L
Transaction termination error occurred on aa....aa func=bb....bb return code=cc....cc
- An error occurred during transaction termination processing.
- aa....aa: Name of server resulting in the error
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- Name of process where the error occurred is p_f_dic_hds_release_userinfo
- See the KFPD00026-E message that was output prior to this message for the action to take.
- Name of process where the error occurred is pdi_com_combuf_disconnect or pdi_com_combuf_process_end, and the error code is -300 through -399
- See 4.1 Detail codes for RPC-related errors.
- Other than the above
- Contact the customer support center.
KFPD00014-E L
Process termination error occurred on aa....aa, func=bb....bb return code=cc....cc
- An error occurred during processing termination.
- aa....aa: Name of server at which the error occurred
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Terminates abnormally.
- Action
- If bb....bb is p_f_dic_hds_end, take action appropriate to the KFPD00026-E message that is output before the current message. In all other cases, contact the customer support center.
KFPD00015-E S
Server termination error occurred on aa....aa func=bb....bb return code=cc....cc
- An error occurred during server termination processing.
- aa....aa: Name of server resulting in the error
- bb....bb: Maintenance information 1
- cc....cc: Maintenance information 2
- S: Resumes processing.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPD00016-E S
Transaction termination error occurred on aa....aa func=bb....bb return code=cc....cc
- An error occurred during transaction termination processing.
- aa....aa: Name of server resulting in the error
- bb....bb: Maintenance information 1
- cc....cc: Maintenance information 2
- S: Terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPD00017-E S
Message output error occurred func=aa....aa return code=bb....bb message no=cc....cc
- An error occurred during message output.
- aa....aa: Maintenance information 1
- bb....bb: Maintenance information 2
- cc....cc: Message number
- S: Resumes processing.
- O: Contact the HiRDB administrator.
- Action
- Maintenance-information-2 is -1902
- The process native memory of the process where the error occurred became insufficient. Revise the swap area size.
- Maintenance-information-2 is -1909
- %PDDIR%\lib\msgtxt was not found. In UNIX, use the pdsetup command to set up HiRDB after HiRDB has terminated. In Windows, re-install HiRDB.
- Maintenance-information-2 is -1910
- A %PDDIR%\lib\msgtxt I/O error occurred. In UNIX, use the pdsetup command to set up HiRDB after HiRDB has terminated. In Windows, re-install HiRDB.
- Maintenance-information-2 is -1911
- %PDDIR%\lib\msgtxt cannot be accessed. Revise the access privilege to %PDDIR%\lib\msgtxt.
- Other than the above
- Contact the customer support center.
KFPD00020-E L
bbb initialization error occurred errorinf=aa....aa
- A bbb initialization error occurred due to the reason indicated in aa....aa.
- aa....aa: Error message indicating the cause of the initialization error
- bbb: Type of server on which the initialization error occurred
- FES: Front-end server
- SDS: Single server
- S: The system takes the following actions:
- Front-end server error:
The front-end server is placed in the SUSPEND status. If the error is due to Insufficient pd_max_rdarea_no, the system terminates abnormally.
- Single server error:
The system terminates abnormally.
- Action
- Take the following action:
- Front-end server error:
Resolve the cause of the error and then reset the SUSPEND status of the front-end server.
For a description of how to reset the SUSPEND status, see HiRDB Version 9 System Operation Guide.
If the error is due to Insufficient pd_max_rdarea_no, increase the value specified in the pd_max_rdarea_no operand in the system common definition, and then restart the unit on which the front-end server is located.
- Single server error:
Resolve the cause of the error, and then restart HiRDB system.
KFPD00021-E L
Insufficient aa....aa memory,server=bb....bb, size=cc....cc
- Shared memory or process private memory is insufficient.
- aa....aa: Type of area resulting in the memory shortage error:
- SHARED: Shared memory
- PROCESS: Process private memory
- bb....bb: Name of the server resulting in the error
- cc....cc: Insufficient memory size (in bytes)
- S: If the server has started, stop server startup. During transaction input, abnormally terminate the process that attempted to process the applicable transaction.
- Action
- Take one of the following actions:
- When the type of the area where a memory shortage occurred is SHARED:
If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, increase the specification value of the shared memory size in the server definition (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) for the server where the memory shortage occurred. Then, restart the server where the error occurred.
- When the type of the area where a memory shortage occurred is PROCESS
Either wait for another process to end and re-execute, or increase the size of the swap area.
KFPD00022-E E
Not specified definition aa....aa
- aa....aa is not defined.
- aa....aa: Name of definition operand:
{ pd_max_list_users |pd_max_list_count }
- S: Terminates processing.
- P: Specify a nonzero value for aa....aa.
KFPD00028-E L
Version incompatible with HiRDB, func=aa....aa
- HiRDB and an added PPaa....aa versions do not match.
- aa....aa: Added PP name
- S: Abnormally terminates HiRDB.
- Action
- Install an added PP version that is compatible with HiRDB version.
KFPD00029-W L
No RDAREA for db management
- An RDAREA that uses a data dictionary for which datadictionary of dbmanagement has been specified is not defined. For this reason, the facility for predicting reorganization time cannot be used.
- S: Continues processing.
- Action
- If the facility for predicting reorganization time is used, create an RDAREA that uses a data dictionary by using pdmod and specifying datadictionary of dbmanagement. If the facility for predicting reorganization time is not used, change the specification of the system definition pd_rorg_predict operand.
KFPD00030-W L
Unable to make an entry SQL_DB_MANAGEMENT, RDID=aa....aa, OBJID=bb....bb, code=cc....cc
- Because registering of the database management table failed, the facility for predicting reorganization time is invalid.
- aa....aa: RDAREA ID
- bb....bb: Table or index ID
- cc....cc: SQL code that caused the error
- S: Terminates processing.
- O: Refer to the SQL code cc....cc that caused the error, and eliminate the cause of the error.
KFPD00031-E L
Insufficient Audit definition buffer memory, size=aa....aa code=bb....bb
- HiRDB could not be started because there was a shared memory shortage for the security audit information buffer.
- aa....aa: Memory size to be allocated (in bytes)
- bb....bb: Error code
- 01: When HiRDB was started, the shared memory for the security audit information buffer specified in the pd_audit_def_buffer_size operand could not be allocated.
- S: Cancels server startup.
- O: Take the following action:
- Error code 01:
- If a KFPD00035-W message is output, follow the instructions given in the message. If the error persists, increase the OS memory by aa....aa, create a free OS memory area, or reduce the size of the pd_audit_def_buffer_size operand, and then restart HiRDB.
KFPD00032-W L
Insufficient Audit definition buffer memory, size=aa....aa code=bb....bb completed size=cc....cc
- There was a shared memory shortage for the security audit information buffer.
- aa....aa: Memory size to be allocated (in bytes)
- bb....bb: Error code
- cc....cc: Size that was allocated (in bytes)
- S: Continues processing.
- O: Take action appropriate to the error code:
Error code | Description | Operator action |
---|
01 | When HiRDB was started, the shared memory for the security audit information buffer was allocated based on the value specified in the pd_audit_def_buffer_size operand; however, not all audit event definitions could be registered in the security audit information buffer. | Re-estimate the value of the pd_audit_def_buffer_size operand, and then restart HiRDB. |
02 | When HiRDB was started, the size required for the shared memory for the security audit information buffer could not be allocated; therefore, the security audit information buffer could not be created. | If a KFPD00035-W message is output, follow the instructions given in the message. If the error persists, either increase the OS memory by aa....aa or create a free OS memory area. |
03 | Audit event definitions increased when HiRDB was running; therefore, not all audit event definitions were registered in the security audit information buffer specified in the pd_audit_def_buffer_size operand. | Re-estimate the value of the pd_audit_def_buffer_size operand, and then restart HiRDB. |
04 | Audit event definitions increased when HiRDB was running; therefore, not all audit event definitions could be registered in the security audit information buffer. | Restart HiRDB. |
KFPD00033-I L
Refresh Audit definition buffer completed, size=aa....aa code=bb....bb completed size=cc....cc
- All audit event definitions were registered in the security audit information buffer.
- S: Continues processing.
KFPD00034-W L
Unable to get Audit definition buffer space requirement, code=aa....aa
- Unable to calculate a required security audit information buffer size due to a dictionary access error or communication error.
- aa....aa: Error code
- S: See operator actions.
- O: Take action appropriate to the error code:
Error code | Security audit information buffer size specification | System action | Operator action |
---|
01 | User-specified | Continues processing after acquiring shared memory for the security audit information buffer equal to a specified size. However, in some cases, not all audit event definitions can be registered in the shared memory for the security audit information buffer. | If a KFPD00032-W message is output when HiRDB is running, take corrective action according to that message. |
02 | Calculated automatically | Continues processing with a 0-byte shared memory size for the security audit information buffer. | To ensure performance, resolve the error, and then restart HiRDB. |
03 | Terminates abnormally in the case of HiRDB/Single Server. In the case of HiRDB/Parallel Server, generates a message, and attempts to start the server a fixed number of times. If the dictionary access error is not resolved, places the front-end server in a SUSPEND state. | In the case of HiRDB/Single Server, resolve the error, and then restart HiRDB. In the case of HiRDB/Parallel Server, resolve the error, and use the pdstart -a command to reset the front-end server from the SUSPEND state. |
KFPD00035-W L
Failed to shmget Audit definition buffer,errno=aa
- Unable to acquire shared memory segments for the security audit information buffer.
- aa: Error code
- S: Continues processing.
- O: Take action appropriate to the error code:
Error code | Description | Operator action |
---|
04 | An internal resource shortage in HiRDB occurred. | The maximum number of shared memory segments controlled by HiRDB (16) was exceeded. Increase the specification value in the SHMMAX operand in the system common definition or unit control information definition. If the specification value in the SHMMAX operand is increased, the same OS command must be used to make the value of shmmax greater than or equal to that value. When modifying shmmax, you must restart the OS. |
08 | A memory shortage occurred. | Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action. |
12 | The maximum size of shared memory segments was exceeded. | Take the following action: In Unix: The shared memory size for the security audit information buffer exceeded either the value specified in the OS parameter shmmax or the value specified in the SHMMAX operand of the system common definition or unit control information definition. Change the value specified in the OS parameter shmmax or the value specified in the SHMMAX operand to a value greater than or equal to the estimated shared memory size for the security audit information buffer. Use the sam command to change the OS parameter shmmax. When you make any modification to shmmax, you must restart the OS. In Windows: The shared memory size for the security audit information buffer exceeded the value specified in the SHMMAX operand of the system common definition or unit control information definition. Change the value specified in the SHMMAX operand to a value greater than or equal to the estimated shared memory size for the security audit information buffer. If the SHMMAX value was not exceeded, it is possible that a work file in the HiRDB installation directory was deleted when HiRDB was running; if that is the case, restart HiRDB service. |
16 | The maximum number of shared memory identifiers was exceeded. | Refer to system call=shmget, errno=28, mnemonic=ENOSPC in 4.3 System call return codes to investigate and resolve the error, and take corrective action. |
KFPD00036-W L
Failed to attach Audit definition buffer,errno=aa
- Unable to attach the shared memory for the security audit information buffer.
- aa: Error code
- S: Continues processing.
- O: Take action appropriate to the error code:
Error code | Description | Operator action |
---|
04 | The upper limit on the number of shared memory segments that can be attached was exceeded. | Use the sam command in the OS to increase the value of shmseg. Any change to shmseg requires restarting the OS. |
08 | A memory shortage occurred. | Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action. |
KFPD01001-E E
SQL error occurred, SQLCODE=aa....aa
- An error that prevents the continuation of processing occurred in the SQL statement in the command.
- aa....aa: SQLCODE
- S: Terminates processing.
- Action
- Check the cause of the error, based on the previously output message; resolve the cause of the error and then re-execute.
KFPD01002-E E
REGISTRY CONTEXT already catalogued
- A context with the same name is already in the registry.
- S: Terminates processing.
- Action
- Confirm that the context name is the correct one; if it is incorrect, revise it and re-execute.
KFPD01003-E E
Invalid REGISTRY ACCESS PASSWORD
- The access password for the registry context is invalid.
- S: Terminates processing.
- Action
- Specify the correct access password and re-execute.
KFPD01004-E E
REGISTRY CONTEXT not found
- The specified context is not in the registry.
- S: Terminates processing.
- Action
- Specify the correct context name and re-execute.
KFPD01005-E E
REGISTRY KEY not found
- The specified key is not in the registry.
- S: Terminates processing.
- Action
- Specify the correct key name and re-execute.
KFPD01006-E E
REGISTRY KEY already catalogued
- The specified key is already in the registry.
- S: Terminates processing.
- Action
- Confirm that the specified key name is the correct one. If it is incorrect, correct it and re-execute. If the specified key name is the correct one, either delete the previously registered key and register the new one, or register the new one under a different name.
KFPD01007-E E
Invalid value in lock_wait option
- The lock_wait option is incorrectly specified (an internal system error).
- S: Terminates processing.
- Action
- Only Y, N, or y, n can be specified in the lock_wait option. Specify the correct value and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01008-E E
Invalid value in lock_mode option
- The lock_mode option is incorrectly specified (an internal system error).
- S: Terminates processing.
- Action
- Only 'R', 'W', or 'r', 'w' can be specified in the lock_mode option. Specify the correct value and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01009-E E
REGISTRY KEY catalogued by long format
- The key value is registered in the registry in the long format (long key value) (an internal system error).
- S: Terminates processing.
- Action
- Notify the customer support center.
KFPD01010-E E
REGISTRY KEY catalogued by short format
- The key value is registered in the registry in the short format (short key value) (an internal system error).
- S: Terminates processing.
- Action
- Notify the customer support center.
KFPD01011-E E
Over 2147483647 in REGISTRY CONTEXT
- The maximum number of registry context items that can be registered was exceeded.
- S: Terminates processing.
- Action
- Use the pdregrmcont command to delete previously registered contexts that are no longer needed and re-execute.
KFPD01012-E E
REGISTRY CONTEXT NAME length is 0 bytes
- The name of the specified registry context is 0 bytes.
- S: Terminates processing.
- Action
- Specify the name of the context within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01013-E E
REGISTRY ACCESS PASSWORD length is 0 bytes
- The name of the specified registry access password is 0 bytes.
- S: Terminates processing.
- Action
- Specify the access password within the effective length range (1 to 100 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01014-E E
REGISTRY KEY NAME length is 0 bytes
- The name of the specified registry key name is 0 bytes.
- S: Terminates processing.
- Action
- Specify the name of the key within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01015-I E
Usage: aa....aa
- The command format is invalid.
- aa....aa: Command format
- S: Terminates processing.
- Action
- Revise the command format and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01016-E E
Insufficient memory, size=aa....aa
- A memory shortage occurred.
- aa....aa: The size to be allocated (in bytes)
- S: Terminates processing.
- Action
- Either re-execute the UAP after other processes have ended or increase the size of the swap area.
KFPD01017-E E
REGISTRY CONTEXT NAME length exceeds 240 bytes
- The name of the specified registry context is greater than the maximum value.
- S: Terminates processing.
- Action
- Specify the name of the context within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01018-E E
REGISTRY ACCESS PASSWORD length exceeds 100 bytes
- The specified registry access password is greater than the maximum value.
- S: Terminates processing.
- Action
- Specify the access password within the effective length range (1 to 100 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01019-E E
REGISTRY KEY NAME length exceeds 240 bytes
- The name of the specified registry key is greater than the maximum value.
- S: Terminates processing.
- Action
- Specify the name of the key within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.
KFPD01020-E E
Read error occurred on file, file name=aa....aa
- The read operation from the specified file failed. Or, the specified file does not exist.
- aa....aa: Specified file name
- S: Terminates processing.
- Action
- Resolve the cause of the error and re-execute.
KFPD01021-E E
System error occurred, return code=aaa
- An internal system error occurred.
- aaa: Return code
- -10: An SQL error
- -30: An invalid interface
- S: Terminates processing.
- Action
- Notify the customer support center.
KFPD01023-I E
Usage: pdlistls [-d {1 |2}][-u list user name]
[-t base table owner.base table name]
- Shows the format of the pdlistls command.
- S: Terminates processing.
- Action
- Specify the command correctly and re-execute it.
KFPD01024-E
Usage: pddef [-e] [-s] [-R]
- Shows the format of the database definition utility command.
- S: Terminates processing.
- Action
- Specify the utility command correctly and re-execute it.
KFPD01025-E E
Invalid option for pddef
- Specification of the database definition utility command is invalid.
- S: Terminates processing.
- Action
- Specify the utility command correctly and re-execute it.
KFPD01026-E E
Argument of aa option is invalid
- Either the option argument is invalid or the specified value is incorrect.
- aa: Option name
- S: Terminates processing.
- Action
- Specify the option correctly and re-execute the utility.
KFPD01100-I E
Usage: aa....aa
- This message indicates how to specify commands.
- aa....aa: Specification method
- pdacunlck {auth_id[,auth_id]...|ALL}
- S: Terminates processing.
- Action
- Check the command format and re-execute.
KFPD01103-E E
Invalid option for aa....aa
- An error was found in the command option specification format.
- aa....aa: Command name
- S: Terminates processing.
- Action
- Check the command format, and then re-execute the process.
KFPD01104-E E+L
Insufficient memory on PROCESS, size=aa....aa
- There is insufficient process private area, so sufficient work area required to execute the command was not secured.
- aa....aa: Area size that was to be allocated (in bytes)
- S: Terminates processing.
- Action
- Use one of the following methods to increase the size of the process private area so that sufficient memory is available, then re-execute the command:
- Reduce the number of concurrently executing processes
- Increase the swap area
- Add more real memory
KFPD01105-E E+L
Internal function error, func=aa....aa, return code=bb....bb
- An error occurred in the internal processing of the command.
- aa....aa: Name of the function in which the error occurred
- bb....bb: Detailed code of the system-related error
- S: Terminates processing.
- Action
- Correct the error by referring to 4.2 Detail codes for system-related errors and re-execute the command. If the error code is -310, the server at the communication destination may not have been activated. If an error that cannot be handled by HiRDB administrator has occurred, contact the customer support center.
KFPD01106-E E+L
Invalid execution node
- The command cannot be executed from this server machine.
- S: Terminates processing.
- Action
- Check the settings of environment variables (PDHOST, PDNAMEPORT, PDDIR, PDCONFPATH, etc.). If a setting a incorrect, correct it and re-execute the command. If all settings are correct, re-execute the command from the server machine where the system manager (MGR) is located.
KFPD01108-E E+L
Hostname=aa....aa, unable to execute cc....cc command, unit bbbb state not ONLINE
- The command cannot be executed because unit bbbb with host name aa....aa is not active.
- aa....aa: Name of host where command could not be executed
- bbbb: Unit identifier
- cc....cc: Command name
- S: Terminates processing.
- Action
- Start HiRDB or the unit, and then re-execute the command.
KFPD01109-E E+L
Server aa....aa not running
- The command cannot be executed because the server is not running.
- aa....aa: HiRDB server name
- S: Terminates processing.
- Action
- Start the server, and then re-execute the command.
KFPD01110-E E+L
Server down detected
- Abnormal termination of the server was detected.
- S: Terminates processing.
- Action
- Check the message or abort code to find what caused the server to abnormally terminate. Eliminate the cause, and then re-execute the command.
KFPD01112-E E+L
Unable to execute "pdacunlck" command, code=aa(bb....bb)
- The pdacunlck command cannot be executed.
- aa: Reason code
- bb....bb: Additional error information
- cc....cc: Authorization identifier
- S: Ignores this SQL statement.
- Action
- From the output reason code and additional error information, remove the error cause, and re-execute the command.
Reason code | Additional error information | Explanation |
---|
02 | Not found authorization identifier cc....cc | The authorization identifier specified in the pdacunlck command does not exist. |
03 | Duplicate authorization identifier cc....cc | The authorization identifier specified in the pdacunlck command is duplicated. |
04 | Number of authorization identifier exceeds 128 | The number of authorization identifier specifications exceeds 128. |
KFPD01113-I L+S
"pdacunlck" command ended, return code=a
- The pdacunlck command terminated with return code a.
- a: Return code
- 0: Normal termination
- 8: Abnormal termination
- S: Ignores this SQL statement.
- Action
- If the return code is 8, refer to the output message and eliminate the cause of the error, and then execute the pdacunlck command.
KFPD01114-E E+L
File access error, func=aa....aa, errno=bb....bb, file=cc....cc
- A file access error occurred during XDS start processing or termination processing.
- aa....aa: Processing code during which the error occurred
- open: Open file processing
- close: Close file processing
- read: Reading
- write: Write processing
- bb....bb: errno value returned by the system call
- cc....cc: File name
- If the file name exceeds 128 bytes, two periods (..) are added in the front, the beginning of the file name is truncated, and the last 126-byte portion is output.
- S: Terminates processing.
- O: Refer to 4.3 System call return codes to eliminate the cause of the error, and perform corrective action by referring to Corrective action to take when an error occurs during XDS start processing or Corrective action to take when an error occurs during XDS end processing in the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPD01115-E E+L
Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb
- An error occurred during execution of the SQL statement for XDS start processing or termination processing.
- aa....aa: SQL communication area (SQLCA) SQLCODE
- bb....bb: SQL communication area (SQLCA) SQLERRMC
- If the information length of the SQLERRMC is 128 bytes or more, the first 128 bytes is output and bytes 129 and following are discarded.
- S: Terminates processing.
- O: Refer to SQL CODE and follow the corresponding message to eliminate the cause of the error. Also, perform corrective action by referring to Corrective action to take when an error occurs during XDS start processing or Corrective action to take when an error occurs during XDS end processing in the HiRDB Version 9 Memory Database Installation and Operation Guide. If corrective action cannot be performed, contact the customer support center.
KFPD01115-W E+L
Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb
- An error occurred during execution of the SQL statement for XDS start processing or termination processing.
- aa....aa: SQL communication area (SQLCA) SQLCODE
- bb....bb: SQL communication area (SQLCA) SQLERRMC
- If the information length of the SQLERRMC is 128 bytes or more, the first 128 bytes is output and bytes 129 and following are discarded.
- S: Because an error occurred, processing is retried.
KFPD01116-I L+S
Retried processing executed successfully
- The re-tried process was able to be executed normally.
- S: Continues processing.
KFPD01117-W E+L
Update of table status for memory DB possibly failed
- The status of the memory database allocation table might not have been updated.
- S: Continues processing.
- Action
- No action is necessary for the status of the memory database allocation table to update correctly the next time the XDS starts up. However, if you stop using the memory database, update the memory database allocation table status using the following procedure.
- Check the status of the memory database allocation table. For details about how to check this, see Memory database allocation table conditions in the HiRDB Version 9 Memory Database Installation and Operation Guide.
- Execute DEALLOCATE MEMORY TABLE on the SQL_TABLES table that has a value of D in the MEMORY_TABLE column.
KFPD01200-I S
"pddivinfgt" command ended,return code=a
- The pddivinfgt command terminated with return code a.
- a: Return code
- 0: Normal termination
- 8: Abnormal termination
- S: Terminates processing.
- P: If the return code is 8, see the message output prior to this message, eliminate the cause of the error, and then re-execute the command.
KFPD01201-E E
Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb
- During execution of the command (pddivinfgt command) for acquiring partitioning conditions, an error occurred in the SQL statement that executes internally.
- aa....aa: SQL communication area (SQLCA) SQLCODE
- bb....bb: SQL communication area (SQLCA) SQLERRMC
- If the information length of the SQLERRMC is 128 bytes or more, output the first 128 bytes and discard bytes 129 and following.
- S: Terminates processing.
- P: Follow the message corresponding to SQLCODE aa....aa, and eliminate the cause of the error.
KFPD01202-E E
Unable to get partitioning information due to aa....aa,code=bb
- Because of aa....aa, the partition conditions of the specified table cannot be acquired.
- aa....aa: Additional information
- bb: Reason code
- S: Terminates processing.
- P: If the specified table name is invalid, revise the table name and re-execute. If the table name is not invalid, follow the additional instructions for the error codes and errors shown below, and take corrective action accordingly.
Reason code | Additional information | Explanation | Action |
---|
01 | not found table | The specified table does not exist. | Check whether the specified table name is correct. |
02 | not base table | It is not a base table. | None (nothing other than a base table can be specified in the command) |
03 | HASH partitioning | Hash partitioning table | None (a hash-partitioned table cannot be specified in the command). |
04 | matrix-partitioned table | Matrix partitioned table | None (a matrix-partitioned table cannot be specified in the command). |
05 | not "=" only partitioning condition | This is not the specified partitioning of stored conditions that were only specified in the comparison operator. | None (you cannot specify anything other than = in the comparison operator of the conditions stored in the command). |
06 | not table owner | This table does not belong to you. | Specify the table that belongs to you, and then re-execute. Or the user with DBA privileges should re-execute it. |
KFPD01203-E E
File access error,access=aa....aa,func=bb....bb,errno=cc....cc, file=dd....dd
- A file operation error occurred.
- aa....aa: Processing code during which the error occurred
- open: Open file processing
- close: Close file processing
- write: Write processing
- bb....bb: System call resulting in the error
- cc....cc: errno value returned by the system call
- dd....dd: File name
- If the file name is 128 bytes or less, the entire file name is displayed. If the file name exceeds 128 bytes, two periods (..) are added in the front, and the last 126-bytes of the file name are displayed.
- S: Terminates processing.
- P: Refer to 4.3 System call return codes, eliminate the cause of the error, and then re-execute.