KFPS00010-I R+S
HiRDB setup start, func = aa....aa, HIRDB directory=bb....bb
- HiRDB setup processing has started.
- aa....aa: Function name:
- add: HiRDB registration in OS
- delete: HiRDB deletion from OS
- bb....bb: Name of HiRDB directory
- S: Resumes processing.
KFPS00011-I R+S
HiRDB setup ended, return code=aa
- HiRDB setup processing has terminated.
- aa: Termination code:
- 0: Terminated normally
- 8: Error occurred during processing
- S: Terminates processing.
- Action
- If the termination code is not 0, take action appropriate to the message output before this message. If the text busy status has just occurred, HiRDB's zombie process may still remain. In such a case, terminate the zombie process with UNIX's kill command and re-execute.
KFPS00012-I S
Library setup for character code set aa....aa
- Library for using aa....aa character codes has been set up.
- aa....aa: HiRDB character codes:
- CHINESE: EUC Chinese kanji codes
- CHINESE-GB18030: Chinese GB18030 codes
- LANG-C: One-byte character codes
- SJIS: Shift JIS kanji codes
- UJIS: EUC Japanese kanji code
- UTF-8: Unicode(UTF-8)
- S: Terminates processing.
KFPS00014-I S
Load module setup completed for aa....aa
- The load module for aa....aa has been set up.
- aa....aa: Load type:
- POSIX: POSIX library version of HiRDB
- S: Continues processing.
KFPS00015-E S
Unable to setup aa....aa, reason code=bb....bb
- The load module for aa....aa could not be set up.
- aa....aa: Load type:
- POSIX: POSIX library version of HiRDB
- NO-POSIX: Non-POSIX library version of HiRDB
- bb....bb: Reason code:
- REMOVED: This module has been deleted
- S: Terminates processing.
- O: Reinstall HiRDB.
KFPS00016-E S+L
Error occurred while setup HiRDB
- An error occurred during HiRDB setup processing.
- S: Terminates processing.
- Action
- Check whether, before or after this message was issued, a memory shortage occurred in the /etc or /tmp directory. If a memory shortage occurred, allocate free disk space. Also, determine whether a disk failure occurred. If a disk failure occurred, recover from the disk failure. Then, re-execute the command.
KFPS00020-E S
Pdsetup already used by another user
- The pdsetup command cannot be input because it is being used by another user.
- S: Terminates processing.
- Action
- Wait until the pdsetup command being executed by the other user terminates, then re-execute.
KFPS00021-E S
Invalid user name, user=aa....aa
- The authorization identifier of the HiRDB administrator is invalid.
- aa....aa: Authorization identifier
- However, if a check of the authorization identifier cannot be performed due to a memory shortage, ******** is output.
- S: Terminates processing.
- Action
- Take one of the following actions:
- If ******** is output for the authorization identifier:
Stop unneeded programs and re-execute.
- Other than above (in UNIX)
Take one of the following actions:
Change the user name to the name that corresponds to the user ID of the HiRDB administrator defined in /etc/passwd.
Change the HiRDB administrator and the owner of the HiRDB operation directory.
- Other than above (in Windows)
Change the HiRDB administrator and the owner of the HiRDB operation directory.
KFPS00022-E S
Language "aa....aa" not installed
- Language aa....aa has not been installed.
- aa....aa: Language name
- S: Terminates processing.
- Action
- Install language aa....aa.
KFPS00030-E S
Permission denied
- Specified processing is not permitted.
- S: Terminates processing.
- Action
- Ask the super user to execute the pdsetup and pdopsetup command.
KFPS00031-E S
Specified HiRDB system already catalogued
- Specified HiRDB system has already been registered.
- S: Terminates processing.
- Action
- Check the specified HiRDB directory, enter pdsetup -d, then re-execute, if necessary.
KFPS00032-E S
Specified HiRDB system not catalogued
- Specified HiRDB system has not been registered.
- S: Terminates processing.
- Action
- Check the specified HiRDB directory, enter pdsetup, and re-execute, if necessary.
KFPS00033-E S
Specified HiRDB home directory not exist
- Specified HiRDB directory was not found.
- S: Terminates processing.
- Action
- Check the specified HiRDB directory and re-execute.
KFPS00034-E E+L+S
Insufficient disk capacity
- There is not enough disk space.
- S: Terminates processing.
- Action
- Allocate sufficient space to the specified HiRDB directory and re-execute. If the text busy status has just occurred, HiRDB's zombie process may still remain.
- Terminate the process with the kill command (in UNIX) or with the pdkill command (in Windows), and re-execute.
KFPS00035-I S
Creates files necessary for execution
- File required for execution is created.
- S: Resumes processing.
KFPS00036-Q S
Specify whether to delete files necessary for execution from specified HiRDB home directory ? [y:YES , n:NO]
- Asks whether or not the files under the specified HiRDB directory that are required for execution are to be deleted.
y: Delete; n: Do not delete. - S: Resumes processing.
- O: Enter y (yes) or n (no).
KFPS00038-E S
Specified HiRDB home directory not full pathname
- Asks the absolute pathname for the HiRDB directory.
- S: Terminates processing.
- Action
- Specify the absolute pathname of the HiRDB directory and re-execute.
KFPS00040-I R+S
Delete files necessary for execution
- The files required for execution have been deleted.
- S: Resumes processing.
KFPS00050-E S
Root directory specified
- No root directory was specified for the HiRDB directory.
- S: Terminates processing.
- Action
- Because the root directory cannot be changed to the HiRDB directory, create a separate HiRDB directory and re-execute.
KFPS00054-E S
Unable to specify HiRDB home directory pathname more than aaa bytes
- The specified HiRDB directory path exceeds the maximum length.
- aaa: Maximum HiRDB directory path length
- Linux: 118
- Other than Linux: 128
- S: Terminates processing.
- Action
- Specify a HiRDB directory path whose length does not exceed 128 bytes (118 bytes in Linux). When using a symbolic link, be sure that the length of the actual path to be linked to does not exceed 128 bytes (118 bytes in Linux).
KFPS00055-E S
"program ID" invalid
- The length of the character string of the specified program ID exceeds 256 bytes.
- S: Terminates processing.
- Action
- Specify the program ID with a maximum length of 256 bytes.
KFPS00056-I S+L
OS shutdown action setup mode=aa....aa
- During OS shutdown, the function that terminated HiRDB was set to aa....aa.
- aa....aa:
- on: Explicitly terminate HiRDB.
- off: Do not terminate HiRDB (depending on the OS, terminates the HiRDB process).
- S: Terminates processing.
KFPS00060-E S
Usage: aa....aa
- Command format aa....aa is invalid.
- aa....aa:
- HP-UX (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }] [-p program][-l load][-k {on|off}]} HiRDB_home_directory
- HP-UX (64-bit mode):
- pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory
- Solaris (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-l load] [-k {on|off}]} HiRDB_home_directory
- Solaris (64-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory
- AIX (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-l load]} HiRDB_home_directory
- AIX (64-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }]} HiRDB_home_directory
- Linux:
pdsetup { -d [-f] | [-c { ujis|chinese|lang-c|utf-8|sjis|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory
- S: Terminates processing.
- Action
- Check the operands and re-execute the command.
KFPS00320-I R
RPC Info. RC=aa....aa, Func:bb....bb, Msg:cc....cc, Local(Pid=dd....dd, Port=ee....ee)
- Displays RPC information.
- aa....aa: Return code
- bb....bb: Maintenance information 1 (function name, module name, etc.)
- cc....cc: Maintenance information 2
- dd....dd: ID of local process
- ee....ee: Local port number
- S: Resumes processing.
KFPS00326-E E+R
Insufficient memory for RPC. Local pid=aa....aa, Local port number=bb....bb
- A system call issued to execute RPC, such as socket() or send(), terminated abnormally due to a memory shortage.
- aa....aa: ID of local process
- bb....bb: Local port number
- S: Terminates the displayed server abnormally.
- Action
- Take appropriate action as indicated in 4.1 Detail codes for RPC-related errors.
KFPS00327-E R
Too few sockets. RPC is unavailable. Local pid=aa....aa, Local port number=bb....bb, error number=cc....cc
- RPC cannot be executed because there is no available socket.
- aa....aa: ID of local process
- bb....bb: Port number of local process
- cc....cc: Error number
- S: If the error number is 20490, terminates abnormally; otherwise, resumes processing.
- Action
- If the error number is 20490, contact the customer support center.
- For any other error number, take appropriate action as indicated in 4.1 Detail codes for RPC-related errors.
KFPS00328-E E
No data in RPC trace file aa....aa
- Specified file aa....aa contains no data.
- aa....aa: Specified file name
- S: Cancels the applicable command's processing.
- Action
- Check the file name and reenter the command.
KFPS00330-E E
RPC trace file aa....aa not found
- Specified file aa....aa was not found.
- aa....aa: Specified file name
- S: Cancels the applicable command's processing.
- Action
- Check the file name and reenter the command.
KFPS00332-E E
RPC trace file access error. Return information=aa....aa, Function name=bb....bb
- One of the following possible errors is displayed:
- Memory shortage occurred
- RPC trace file I/O error occurred
- aa....aa: Return information
- bb....bb: Function name
- S: Cancels the applicable command's processing.
- Action
- Contact the customer support center.
KFPS00335-E R
Time out occurred in chained RPC. Service group=aa....aa, local pid=bb....bb
- The call target already aborted a chained RPC (a server in the same service function group was called more than once within the same transaction using a reply RPC). Or, the transaction was not terminated within the specified time since the last chained RPC call.
- aa....aa: Name of service group
- bb....bb: Local process number
- S: Terminates the displayed server abnormally.
- P: Contact the HiRDB administrator.
- Action
- Take appropriate action as indicated in the message output to the message log.
KFPS00336-E E+R
RPC of message received from client or server with different HiRDB version. Local pid=aa....aa, Remote node address=bb....bb, Remote port number=cc....cc
- The version of the text at the send side does not match the version at the receive side.
- aa....aa: Received process ID
- bb....bb: Node address of send side
- cc....cc: Port number of send side (up to 5 numeric digits)
- S: Resumes processing after discarding the message resulting in output of this message (does not send a message to that effect to the send side).
- Action
- Check the HiRDB version of the server that output this message and the HiRDB version of the HiRDB client or server that sent the message. If they do not match, use matching versions.
KFPS00337-E E+R
Unable to open RPC trace file aa....aa
- An open error or a definition analysis error occurred in an RPC trace file.
- aa....aa: Name of RPC trace file
- If the path name of the RPC trace file exceeds 187 characters, the last 187 characters of the RPC trace file path name are output.
- S: Resumes processing (RPC trace will not be collected).
- Action
- Check the following operands for an error:
- pd_rpc_trace_name
- pd_rpc_trace_size
- If this message is reissued after correcting these operands, contact the customer support center. If there is a shortage of system resources (disk space shortage, file count shortage, etc.), change the operating system kernel parameters.
KFPS00345-W L
Insufficient HiRDB registered ports, reason code=aaa. Use OS assigned ports
- Port numbers assigned automatically by the OS are being used because the number of ports being used for communication by HiRDB exceeded the number of ports specified in the pd_registered_port operand, or because all port numbers specified in the pd_registered_port operand are in use by other programs.
- aaa: Reason code:
- -10: The number of ports specified in the pd_registered_port operand was exceeded
- -20: All port numbers specified in the pd_registered_port operand are in use by other programs
- S: Continues processing.
- Action
- Take one of the following actions:
Reason code | Action |
---|
-10 | Check the value specified in the pd_registered_port operand; there may be too few port numbers. |
-20 | Check the value specified in the pd_registered_port operand; all port numbers in the specified range may be in use by other programs. If this is the case, re-evaluate the specification; if all port numbers are not being used by other programs, there may be too few ports specified in the pd_registered_port operand. |
- When this message is output, it is recommended that the statistics analysis utility (statistical information related to system operations) be executed. Check the following items:
- Number of HiRDB reserved ports being used (#OF REGISTERED PORTS)
- Number of ports assigned automatically (by the OS) that were being used when the number of HiRDB reserved ports was exceeded (#OF ASSIGNED PORTS)
KFPS00346-E E+L
Port number in registered ports definition invalid
- The specification of the pd_registered_port operand is invalid.
- S: Terminates the pdconfchk command or HiRDB startup processing.
- Action
- Modify the contents of the pd_registered_port operand in the system common definition or unit control information definition, and then re-execute the pdconfchk command or HiRDB startup processing.
KFPS00347-E L
Insufficient shared memory. Required memory size=aa....aa bytes
- A shortage of shared memory space occurred.
- aa....aa: Size of shared memory that needs to be allocated
- S: Terminates HiRDB startup processing.
- Action
- Reconsider the shared memory estimate. Also, if an error message was output before this message, take the action indicated in that message. If this message is output even after these measures, save the contents of the message and contact the customer support center.
KFPS00348-E E+L
Duplicate registered ports, type=aa....aa, port number=bb....bb
- There is a duplication of a port number that must not be duplicated in the range of port numbers specified in the pd_registered_port operand.
- aa....aa: Type of duplicate port number:
- NAME
- Port number specified in pd_name_port operand or in -p option of pdunit operand.
- SERVICE
- Port number specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand is a duplicate.
- SERVICES
- Port numbers in the following services file are duplicated:
- In UNIX: /etc/services
- In Windows: %windir%\system32\drivers\etc\services
- However, in an NIS or DNS environment, the files defined in the NIS or DNS configuration are used.
- TRN:
- Port number specified in the -t option of the pd_trn_port operand or pdunit operand is a duplicate.
- MLG:
- Port number specified in the -m option of the pd_mlg_port operand or pdunit operand is a duplicate.
- ALV:
- Port number specified in the -a option of the pd_alv_port operand or pdunit operand is a duplicate.
- bb....bb: Duplicated port number
- S: Terminates the pdconfchk command or HiRDB startup processing.
- Action
- Review the value specified in the pd_registered_port operand of the system common definition or unit control information definition, and the value of the duplicated port number, and, if necessary, set the correct values. Then, re-execute the pdconfchk command or HiRDB startup processing.
- Because this message shows only the first duplicated port number, it is wise to check for any other duplicated port numbers.
KFPS00349-E L
Insufficient network port
- An attempt to allocate a communication port number failed.
If this message is output, the system attempts to reacquire the communication port number. If successful, the HiRDB process will run without problem. If this message is output frequently or a communication error causes a HiRDB process error after this message is output, one of the following is the most likely cause: - There is a shortage of automatically allocated port numbers for the operating system
- The network of the IP address described in the KFPS00352-I message output immediately after this message terminated abnormally
- There is an error in the IP address of the host name used by the HiRDB specified in the hosts file (in UNIX, /etc/hosts, and in Windows, OS-installation-directory\system32\drivers\etc\hosts)
- There is a memory shortage
- The port number output in the KFPS00352-I message is already in use
(when it is the same as the value of the port number set by HiRDB, such as the value specified in the pd_name_port operand)
- S: Continues processing. Attempts to reacquire communication port number.
- Action
- Take the following actions:
- If there is a shortage of port numbers, check if a program other than HiRDB is using many communication ports. If another program is using many communication ports, reduce the number of ports it uses.
Alternatively, do one of the following to secure the communication ports required for HiRDB.
Modify OS parameters and configure the settings to prevent a shortage of TCP ports. For details about the settings to prevent a shortage of TCP ports, see Ways to avoid a shortage of ports in the HiRDB Version 9 Installation and Design Guide.
Use the HiRDB reserved port facility to secure the communication ports required for HiRDB. For details about the HiRDB reserved port facility, see the HiRDB Version 9 Installation and Design Guide.
Also, if this message is output by a server machine specifying a system manager on HiRDB/Parallel Server, or for HiRDB/Single Server, specifying 1 in the PDTCPCONOPT operand in the client environment definition is often effective. For details about the PDTCPCONOPT operand, see the HiRDB Version 9 UAP Development Guide.
- If the network terminates abnormally, start the network.
- Re-evaluate the content of the hosts file, and check if an incorrect IP address is specified in the host name entries defined by HiRDB. Correct any incorrect IP addresses found, and then start HiRDB.
- If there is a memory shortage, re-estimate the memory. Alternatively, terminate any unneeded processes.
- If the port number is already in use, revise the value of the port number set by HiRDB (such as the value specified in the pd_name_port operand) to a value that is not in use
KFPS00350-W L
Process memory over pd_svr_castoff_size value. Server=aa....aa, memory size=bb....bb, value= size=cc....cc
- Server processing has been terminated because the amount of memory space used exceeded the value specified in the pd_svr_castoff_size operand.
- aa....aa: Server name (server name specified in the pdstart operand of the system common definition)
- bb....bb: Memory size used (in MB)
- cc....cc: Size specified in pd_svr_castoff_size operand (in MB)
- S: Terminates processing.
- Action
- If this message is output often, the effectiveness of resident processes will decline. In addition, frequent processing terminations and startups, as well as large amounts of output to the system and message logs, will result in overall performance degradation. Therefore, specify the pd_svr_castoff_size operand value for each server so that the following condition is satisfied:
- a - b < c
- a: Server process virtual memory size after SQL process termination
- b: Server process virtual memory size immediately following HiRDB startup
- c: Value set in pd_svr_castoff_size operand
- Use an operating system command (e.g., the top command in HP-UX) to check the virtual memory size.
KFPS00351-E L
Hostname (aa....aa) not found
- Host name aa....aa could not be obtained.
aa....aa: Host name
S: Terminates processing. - Action
- The following are possible causes of this problem; eliminate the cause and re-execute the processing:
- In UNIX:
- The host name or IP address was not found in the hosts file.
- Referencing privilege for the hosts file has not been granted.
- The hosts file was modified while HiRDB was running. When the hosts file is modified, terminate normally, and then start HiRDB.
- If DNS or NIS is being used, the host name or IP address was not found in the database to be retrieved.
- If DNS or NIS is being used, then either the referencing privilege for the database to be retrieved or for the environment setup file of DNS has not been granted, or one or both of these settings is invalid.
- If DNS or NIS is being used, the setting of the /etc/nsswitch.conf file is invalid.
- In Windows:
- The host name or IP address was not found in the hosts file.
- Reference privilege for the hosts file has not been granted.
- The hosts file was modified while HiRDB was running. After the hosts file is modified, terminate normally, and then start HiRDB.
- If DNS or WINS is being used, the host name or IP address was not found in the database to be retrieved.
- If DNS or WINS is being used, either there is no reference privilege for the database to be retrieved or one of the settings is invalid.
KFPS00352-I L
Port number maintenance information,(aa....aa)
- This is the port number maintenance information of the KFPS00349-E message.
- aa....aa: Maintenance information
- S: Continues processing.
- Action
- This is the maintenance information of the KFPS00349-E message output immediately before this message. Take action according to the KFPS00349-E message.
KFPS00353-E L
System call error occurred while communication, func=aa....aa, errno=bb....bb, info=cc....cc
- An error occurred in the processing of inbound communication, and no requests could be accepted for a period of 3 minutes.
HiRDB relies on server-client and inter-process communications. If an error occurs while it is processing inbound communications and no execution requests can be accepted, other errors might result, such as online processing delays. To mitigate the effects of such errors, if the system enters a state in which no execution requests can be accepted for a period of 3 minutes, this message is output, and the process that detected the error is terminated. Monitoring whether this message is output allows you to detect errors such as online processing delays at an early stage. - aa....aa: Name of the system call
- bb....bb: System call return code
- cc....cc: Internal information
- S: Outputs an abort code (Psrc780), and terminates the process that detected the error. If the process is the system server, the unit is shut down.
- Action
- Check whether a port scanner or similar program is making a large number of connection requests to a HiRDB process, and, if so, terminate that program.
- In cases other than the above, refer to the OS's documentation to determine the cause of the error based on the name of the system call and the return code that are displayed in this message. For typical system call return codes, see 4.3 System call return codes. Once you identify the cause of the error, eliminate it, and take corrective action to prevent errors from occurring in the processing of inbound communication.
- After eliminating the cause of the error, restart HiRDB if it terminated abnormally.
- If the cause of the error cannot be determined, contact the customer support center.
KFPS00354-W E+L
Duplicate registered ports, port number=aaaaa
- The port number specified as the HiRDB reserved port duplicates the port number registered in the following services file:
- In UNIX: /etc/services
- In Windows: %windir%\system32\drivers\etc\services
- However, in an NIS or DNS environment, the files defined in the NIS or DNS configuration are used.
- aaaaa: Duplicate port number
- S: Does not use the duplicate port number as the HiRDB reserved port.
- Action
- Review the value set in the system common definition or in the unit control information definition pd_registered_port operand and in the services file, and, if necessary, set the correct value.
KFPS00355-E E+L
Loopback address not specified
- The loopback address was not specified in the -x option of the pdunit operand in the system common definition. If Y or S is specified in the pd_rpc_bind_loopback_address of the system common definition, you must specify the loopback address in the -x option of the pdunit operand in the system common definition.
- S: Terminates the pdconfchk command or HiRDB start processing.
- Action
- Perform one of the following actions, and then re-execute the pdconfchk command or HiRDB start processing:
- If one of the following applies, specify the loopback address in the -x option of the pdunit operand in the system common definition.
- In a system configuration in which a HiRDB client and HiRDB server exist on the same server machine, in order to record an entry on the Windows Firewall exceptions list for HiRDB server processes, specify Y in the pd_rpc_bind_loopback_address of the system common definition.
- In a system configuration in which a HiRDB client and HiRDB server exist on different server machines, in order to record only those processes receiving connection requests from the HiRDB client on the Windows Firewall exceptions list for HiRDB server processes, specify S in the pd_rpc_bind_loopback_address of the system common definition.
- If neither of the configurations described in 1 apply, specify N in the pd_rpc_bind_loopback_address operand in the system common definition.
KFPS00356-E E+L
Port number of scheduler process not specified.
- The scheduler process port number was not specified.
If S is specified in the pd_rpc_bind_loopback_address operand in the system common definition, you must specify the scheduler process port number. - S: Terminates the pdconfchk command or HiRDB start processing.
- Action
- Perform one of the following actions, and then re-execute the pdconfchk command or HiRDB start processing:
- As mentioned previously, in a system configuration in which a HiRDB client and HiRDB server exist on different server machines, in order to record only those processes receiving connection requests from the HiRDB client on the Windows Firewall exceptions list for HiRDB server processes, you must specify S in the pd_rpc_bind_loopback_address of the system common definition. When specifying S as just described, also specify one of the following operands to set the scheduler process port number.
pd_service_port operand
pd_scd_port operand
-s option of the pdunit operand
- In a system configuration in which a HiRDB client and HiRDB server exist on the same server machine, in order to record an entry on the Windows Firewall exceptions list for HiRDB server processes, specify Y in the pd_rpc_bind_loopback_address of the system common definition.
- If neither 1 nor 2 apply, specify N in the pd_rpc_bind_loopback_address operand in the system common definition.
KFPS00403-E E+L
Unable to start lock service. reason code=aa....aa
- An error occurred during lock service function startup or restart processing.
- aa....aa: Reason code indicating the nature of the error
- S: Terminates the HiRDB system abnormally.
- Action
- Take action appropriate to the reason code, as listed below, and restart:
Reason code | Explanation | Action |
---|
10 | Error occurred during definition analysis startup processing. | If an error message was issued before this message, take action appropriate to that message |
20 | Communication error occurred. |
30 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources. |
40 | Shared memory shortage occurred | Re-evaluate the value of the pd_lck_pool_size operand and pd_lck_pool_partition operand specified in the corresponding server definition#. |
60 | There is no directory for output of deadlock information. | Create a %PDDIR%\spool\pdlckinf directory. |
- #
- For the front-end server, re-evaluate the value of the pd_fes_lck_pool_size operand and pd_fes_lck_pool_partition operand.
KFPS00412-E L
Error occurred while terminating lock service; continues processing. reason code=aa....aa
- An error occurred during lock service function termination.
- aa....aa: Reason code indicating the nature of the error
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
10 | Communication error occurred. | If an error message was issued before this message, take action appropriate to that message. |
KFPS00421-W E+L
Too big aa....aa. bb....bb assumed, server=cc....cc
- A value larger than that specified for the bb....bb operand was specified for the aa....aa operand. The value specified for bb....bb is assumed.
- aa....aa: Operand name
- bb....bb: Operand name
- cc....cc: HiRDB server name
- S: Continues processing.
- Action
- Revise the value specified for the aa....aa operand.
KFPS00430-E L
Unable to execute aa....aa command. reason code=bb....bb
- The indicated command cannot be executed due to an invalid parameter or execution error.
- aa....aa: Command name
- bb....bb: Reason code indicating the nature of the error
- S: Cancels command execution and terminates.
- Action
- Take action appropriate to the reason code, as listed below, and reenter the command:
Reason code | Explanation | Action |
---|
10 | Communication error occurred. | If an error message was issued before this message, take action appropriate to that message |
30 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources. |
40 | Versions do not match | Check the version of each library in HiRDB. |
50 | Name server daemon is inactive. | Check if the name server daemon is active |
KFPS00433-E E
Unable to execute aa....aa command command execution mode not set up for lock service.
- The lock service function is inactive. Or, the command cannot be executed because the system is being terminated.
- aa....aa: Command name
- S: Cancels command processing.
- O: Check that the system has started, then re-enter the command.
KFPS00434-E E
Unable to execute the command versions of the aa....aa command and lock service library different.
- Unable to execute the aa....aa command because the command version and the lock HiRDB library version do not match.
- aa....aa: Command name
- S: Cancels command processing.
- Action
- Check the command as to whether or not it supports the HiRDB being used, take appropriate action, then re-execute the command.
KFPS00440-W L
Deadlock occurred. server=aa....aa
- Deadlock occurred.
- aa....aa: Name of the server resulting in deadlock
- S: Resumes processing.
KFPS00441-I L
Deadlock information output to aa....aa file.
- Deadlock information was output.
- aa....aa: Name of the file containing the deadlock information
- S: Resumes processing.
- Action
- Check the output deadlock information and eliminate the cause of the deadlock, if necessary. Delete deadlock information that is no longer needed.
- For the output contents of deadlock information, see the HiRDB Version 9 System Operation Guide; for details on how to handle deadlock, see the HiRDB Version 9 UAP Development Guide.
KFPS00442-E E+L
Unable to output deadlock information. reason code=aa....aa
- Deadlock information cannot be output.
- aa....aa: Reason code indicating the nature of the error
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
10 | Acquisition of the value of PDDIR environment variable failed. | Check if the value of PDDIR has been set. |
20 | File open processing failed. | Check if there is a %PDDIR%\spool\pdlckinf directory. Check if there are too many files. If there are too many files, delete any unneeded ones. |
30 | Error occurred while writing data into a file. | Check if there are too many files. If there are too many files, delete any unneeded ones. |
40 | Acquisition of time failed. | -- |
50 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources. |
- --: Not applicable
KFPS00443-I L
Insufficient memory in lock table. server=aa....aa, code=bb, using=cc....cc, total=dd....dd, PROGRAM=ee....ee
- Server aa....aa does not have enough space in the lock pool (or lock pool partition if the lock pool is divided into partitions) to be used during lock processing.
- aa....aa: Server name
- bb: Error code
- cc....cc: Number of the table currently being used for managing locked resources in which the error occurred
- dd....dd: Total number tables for managing locked resources available to all users
- ee....ee: UAP identification information
- Identification information about the UAP specified in the client environment definition PDCLTAPNAME is displayed. For a utility, the command name is displayed. Some utilities cannot be displayed, in which case the symbol ******** is displayed.
- S: Resumes processing.
- Action
- Take the following action according to the error code:
Error code | Explanation | Action |
---|
10 30 | A shortage of space for storing tables used to manage locked resources or shared-resource lock waits | Check the cause of this problem by referring to the information about tables for managing locked resources indicated in a KFPS00447-I message, which is output following this message (if multiple messages are output, see the message with a matching process ID in the information attached to the message). For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide. If a UAP is making too many lock requests, revise the UAP to reduce its lock requests. The number of lock requests made per UAP varies with SQL. For details on how to estimate the number of locked resources, see the HiRDB Version 9 System Definition. A maximum number of lock requests per UAP can be set in the PDLOCKLIMIT client environment definition. If the estimated number of tables for managing locked resources is too small, either execute the UAP at a different time of day when there is less need to use tables for managing locked resources or change the definitions shown below. When changing a definition, shut down and re-start the entire HiRDB system or the unit in which the problem occurred.
- Front-end server:
- Increase the value specified in the operand pd_fes_lck_pool_size in the server definition in which the error occurred.
- Other servers:
- Increase the value specified in the operand pd_lck_pool_size in the server definition in which the error occurred.
|
20 40 50 | A shortage of tables used for storing the lock resource tables to manage transactions or lock-release waits | Reduce the number of UAPs or utilities that are concurrently executed. |
60 | A shortage of space used for managing locked resources specified in UNTIL DISCONNECT | Increase the value specified in the operand pd_lck_until_disconnect_cnt in the server definition in which the error occurred. |
KFPS00444-I L
Number of lock requests exceeds the limit, server=aa....aa, number=bb....bb
- Lock requests reached the maximum value at server aa....aa.
- aa....aa: Server name
- bb....bb: Number of lock requests
- S: Resumes processing.
- Action
- Increase the PDLOCKLIMIT operand value in the client environment definition.
KFPS00446-W L
Lock queue length reached aaa, server=bb....bb, resource type=cccc, resource id=dd....dd
- During lock processing of the resource indicated by ID dd....dd, the number of users waiting for locking has reached aaa.
- aaa: Number of users waiting for resource lock release
- bb....bb: Server name
- cccc: Resource type
- dd....dd: Resource information
- S: Resumes processing.
- P: Check whether or not locking of this resource is valid.
- O: Check the value specified in the pd_lck_queue_limit operand. If the value is correct, check whether or not locking of this resource is valid. For details on resources, see 6. Lock Control Errors.
KFPS00447-I L
Insufficient exclusive control table information output to aa....aa file
- Information about tables for managing locked resources was output.
aa....aa: Name of the file to which information about tables for managing locked resources was output. - S: Continues processing.
- P: Check the information about tables for managing locked resources that was output. Determine whether the number of locked resources used by users is appropriate. If necessary, take an action according to the preceding KFPS00443-I message (if multiple messages are output, see the message with a matching process ID in the information attached to the message).
- For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide.
- Action
- Check the information on tables for managing locked resources that was output. If necessary, take action according to the preceding KFPS00443-I message (if multiple messages are output, see the message with a matching process ID in the information attached to the message).
- For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide.
- In addition, because the data file for the locked resources management table increases in size, after detection has been completed, or for files that do not need to be detected, delete files where appropriate using one of the following methods:
- pdcspool command
- The OS's rm command (in UNIX)
- Explorer (in Windows)
KFPS00448-E E+L
Unable to output insufficient exclusive control table information. Reason code=aa....aa
- Information about tables for managing locked resources cannot be output.
- aa....aa: Reason code describing the nature of the error
- S: Resumes processing.
- Action
- Take the following action according to the reason code.
Reason code | Explanation | Action |
---|
10 | Environment variable PDDIR get failure | Make sure that a value is assigned to PDDIR. |
20 | File opening failure | Check whether the %PDDIR%\spool\pdlckinf directory exists and make sure that there are not too many files in it. If there are too many files, delete unneeded files using one of the following methods:
- pdcspool command
- the OS's rm command (in UNIX)
Explorer (in Windows) |
30 | File write error |
40 | Time get error | -- |
50 | Shortage of swap area | Make sure that there are no unneeded processes or processes with an excessive amount of memory. If a problem is found, stop the affected process. |
- --: Not applicable
KFPS00450-W L
Waiting time for exclusive control release out. server=aa....aa, wait_time=bb....bb
- Lock release wait timeout occurred.
- aa....aa: Name of the server resulting in timeout
- bb....bb: Lock-release wait time (seconds)
- S: Resumes processing.
KFPS00451-I L
Timeout information output to aa....aa file.
- Timeout information was output.
- aa....aa: Name of the file to which timeout information was output
- S: Resumes processing.
- Action
- Check the output timeout information and eliminate the cause of the timeout, if necessary. Delete any timeout information that is no longer needed.
- For the output contents of timeout information, see the HiRDB Version 9 System Operation Guide.
- If timeout resulted from a deadlock, take action appropriate to the deadlock.
- For details on how to handle deadlock, see the HiRDB Version 9 UAP Development Guide.
KFPS00452-E E+L
Unable to output timeout information. reason code=aa....aa
- Timeout information cannot be output.
- aa....aa: Reason code indicating the nature of the error
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
10 | Acquisition of the value of PDDIR environment variable failed. | Check if the value of PDDIR has been set. |
20 | File open processing failed. | Check if there is a %PDDIR%\spool\pdlckinf directory. Check if there are too many files. If there are too many files, delete any unneeded ones. |
30 | Error occurred while writing data into a file. | Check if there are too many files. If there are too many files, delete any unneeded ones. |
40 | Acquisition of time failed. | -- |
50 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources. |
- --: Not applicable
KFPS00460-E E+L
Insufficient memory. size=aa....aa bytes, area type=bb....bb
- A memory shortage occurred.
- aa....aa: Size of memory that was to be allocated
- bb....bb: Type of area resulting in memory shortage:
- DYNAMIC_SHMPOOL: Dynamic shared memory area
- PROCESS: Process area
- STATIC_SHMPOOL: Static shared memory area
- S: Resumes processing.
- Action
- If the memory shortage occurred in the process area, re-evaluate the number of processes, etc., and take appropriate action. If the same error recurs, contact the customer support center.
KFPS00601-I E+L
Shared memory aa....aa found insufficient while executing name service; another bb....bb bytes required.
- A shortage occurred in the shared memory while executing the name service function.
- aa....aa: HiRDB's internal information
- bb....bb: Size insufficiency (in bytes)
- S: Cancels the processing requested to the name service function. If the HiRDB system is engaged in startup processing, the startup processing is suspended.
- Action
- Re-examine the shared memory estimation. Also, if an error message was output before this message, take the action indicated in that message. If this message is output even after these measures, save the contents of the message and contact the customer support center.
KFPS00602-W E
Error occurred during name service for HiRDB/client. reason code=aa....aa, maintenance information=bb....bb
- The name service function is no longer available to the HiRDB client functions.
- aa....aa: Cause code
- bb....bb: Maintenance information
- S: Resumes the regular name service function. However, the name service function is no longer available to the client functions.
- Action
- If the reason code is nclt001 or nclt007, there is a shortage in the process native memory. In this case, take action such as reducing the number of processes.
- If the reason code is other than the above, save the contents of this message and contact the customer support center.
- Furthermore, if the HiRDB client environment variable specifies a UAP that specified PDHOST, this does not influence the name service facility.
KFPS00606-E E
Definition variable aa....aa specifies undefined host name bb....bb. definition file=cc....cc
- Node name bb....bb specified in definition variable aa....aa has not been defined.
- aa....aa: HiRDB's internal information
- bb....bb: Node name
- cc....cc: Erroneous definition file:{SERVER}
- SERVER: %PDCONFPATH%\pdsys
- S: Resumes analysis of the configuration definition, but does not execute the name service.
- Action
- Correct the definition file or hosts file and re-execute HiRDB.
KFPS00608-W E+L+R
Interprocess communication error occurred in name service.maintenance information=aa....aa
- An interprocess communication error occurred during name service execution.
- aa....aa: Maintenance information
- S: Resumes processing.
- O: Check the following items and take appropriate action:
- If any host constituting the HiRDB system has not been started, start it. Similarly, if the LAN has not been started, start it. If this message is output even though all other hosts and the LAN have been started, ignore the message (for example, when starting HiRDB in a parallel configuration).
- If communication errors occur frequently, contact the HiRDB administrator and have the administrator check the cause.
- Contact the HiRDB administrator and have the administrator check for errors in the HiRDB definition information.
- Action
- Check the items shown below and take appropriate action:
- If the cause of frequent communication error occurrences is known, stop HiRDB, take appropriate action, and then restart HiRDB.
- Check that the following definition information is correct; if the information is incorrect, stop the HiRDB system, correct the definition information, then restart the system:
Name of host for which the -x and -c options were specified in the pdunit operand of the system common definition
- If neither of the above applies, contact the customer support center.
KFPS00609-E E+L
Unable to analyze definition file due to insufficient memory
- A shortage of process memory was detected. The system common definition file cannot be analyzed.
- S: Terminates processing.
- Action
- Use the following methods to increase the amount of available memory and restart the HiRDB system:
- Reduce the number of other processes running in the same machine.
- Increase the swap area.
- Add more real memory.
KFPS00610-I L
Transaction queuing started, queuing unit=aa....aa, down unit=bb....bb
- If rapid system switchover or standby-less system switchover (1:1):
- Transaction queuing started at the aa....aa unit because the bb....bb unit is terminating abnormally.
- If standby-less system switchover (effects distributed):
- Because server bb....bb is abnormally terminating, transaction queuing has started on unit aa....aa.
- This message is output when the unit queuing the transaction receives a transaction queuing communication.
- aa....aa: Name of the unit queuing the transaction
- bb....bb:
- If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is abnormally terminating
- If standby-less system switchover (effects distributed): Name of the server that is abnormally terminating
- cc....cc:
- If rapid system switchover or standby-less system switchover (1:1): unit
- If standby-less system switchover (effects distributed): server
- S: Starts transaction queuing. There are also cases when a transaction start error occurs and the retry process queues a transaction before this message is output.
KFPS00611-I L
Transaction queuing ended, queuing unit=aa....aa, down unit=bb....bb
- If rapid system switchover or standby-less system switchover (1:1):
- The aa....aa unit terminates transaction queuing because the bb....bb unit is ready to receive a transaction.
- If standby-less system switchover (effects distributed):
- The aa....aa server terminates transaction queuing because the bb....bb unit is ready to receive a transaction.
- This message is output if the unit that is queuing a transaction receives a communication from the receiving unit that it is ready to receive a transaction.
- aa....aa: Name of the unit that is queuing a transaction
- bb....bb:
- If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is ready to receive a transaction
- If standby-less system switchover (effects distributed): Name of the server that is ready to receive a transaction
- cc....cc:
- If rapid system switchover or standby-less system switchover (1:1): unit
- If standby-less system switchover (effects distributed): server
- S: Terminates transaction queuing.
KFPS00612-E L
Timeout for transaction queuing occurred, reason=aa....aa, queuing unit=bb....bb, down unit=cc....cc
- The transaction queuing process for the bb....bb unit timed out for one of the following reasons:
- Even though the value of the pd_ha_trn_queuing_wait_time operand was exceeded, the abnormally terminating unit or server did not communicate that it was ready to receive a transaction.
- Even though the value of the pd_ha_trn_restart_retry_time operand was exceeded, the abnormally terminating unit or server did not start.
- aa....aa: Timeout reason
- pd_ha_trn_queuing_wait_time: Exceeded the value of the pd_ha_trn_queuing_wait_time operand
- pd_ha_trn_restart_retry_time: Exceeded the value of the pd_ha_trn_restart_retry_time operand
- bb....bb: Name of the unit queuing a transaction
- cc....cc:
- If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is abnormally terminating
- If standby-less system switchover (effects distributed): Name of the server that is abnormally terminating
- dd....dd:
- If standby-less system switchover (1:1): unit
- If standby-less system switchover (effects distributed): server
- S: Terminates transaction queuing. All transactions issued after this transaction generate an error, and none is queued.
- Possible causes:
- The value of the pd_ha_trn_queuing_wait_time operand or the value of the pd_ha_trn_restart_retry_time operand is too small
- The rapid system switchover facility process failed
- System switchover processing failed
- When the abnormally terminating unit or server becomes ready to receive a transaction, the transaction is processed normally without any error occurring.
- Action
- Take the following actions:
- When aa....aa is pd_ha_trn_queuing_wait_time:
Possible causes:
- The HiRDB startup process could not be completed within the pd_ha_trn_queuing_wait_time operand value (time). In this case, increase the pd_ha_trn_queuing_wait_time operand value.
- An error occurred during the restart process of the abnormally terminating unit or server, and restart failed. See the message output before this message to determine the cause of the error.
- When aa....aa is pd_ha_trn_restart_retry_time:
Possible causes:
- The unit or server that abnormally terminated did not restart within the pd_ha_trn_restart_retry_time operand value (time). During system switchover, the disk disconnection process could be taking a long time. In this case, increase the pd_ha_trn_restart_retry_time operand value.
- If the system switchover process failed, see the message output before this message to determine the cause of the error. Alternatively, also see the operating system messages or cluster software messages.
KFPS00613-E E+L
Duplicate port number=aa....aa, type=bbbb,cccc
- Port numbers bbbb and cccc are duplicates of each other.
- aa....aa: Duplicate port number
- bbbb and cccc: Duplicate port number types
- NAME: HiRDB port number
- (Specified in the -p option of the pd_name_port operand or pdunit operand)
- SCD: Scheduler port number
- (Specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand)
- TRN: Transaction server port number
- (Specified in the -t option of the pd_trn_port operand or pdunit operand)
- MLG: message log server port number
- (Specified in the -m option of the pd_mlg_port operand or pdunit operand)
- ALV: Monitoring server port number between units
- (Specified in the -a option of the pd_alv_port operand or pdunit operand)
- S: Terminates processing.
- Action
- Re-examine the contents of the operands corresponding to the port number types (bbbb and cccc), and change the setting values to the correct values. Then, re-execute processing.
KFPS00614-E E+L
Port number not fixed, type=aaaa, unit=bbbb
- The aaaa port number was not specified.
- aa....aa: Port number
- NAME: HiRDB port number
- (Specified in the -p option of the pd_name_port operand or pdunit operand)
- SCD: Scheduler port number
- (Specified in the -s option of the pd_scd_port operand or pdunit operand)
- TRN: Transaction server port number
- (Specified in the -t option of the pd_trn_port operand or pdunit operand)
- MLG: message log server port number
- (Specified in the -m option of the pd_mlg_port operand or pdunit operand)
- ALV: Monitoring server port number between units
- (Specified in the -a option of the pd_alv_port operand or pdunit operand)
- bbbb: Unit name
- S: Terminates processing.
- Action
- If you specify Y in the pd_name_fixed_port_lookup operand, you must specify the operand that corresponds to aaaa to specify the port number of the system server that is performing communication between units. If you do not set a port number, when you resolve the address of the system sever that uses port number aaaa, communication processing to all units is generated. If you set a port number, do one of the following:
- If an error occurs in the pdconfchk command, specify the operand that corresponds to aaaa, and then re-execute.
- If an error occurs in HiRDB start processing, specify the operand that corresponds to aaaa. Then, restart HiRDB.
- For details about how to specify each operand, see the manual HiRDB Version 9 System Definition.
KFPS00615-W L
Multi-connection address definition invalid, reason code=aa, hostname=bb....bb
- There is an invalid specification related to the multi-connection address facility specified in the system common definition.
- aa: Reason code
- bb....bb:
- Reason code 01: ****
- Reason code 02 or 03: Invalid host name specification
- S: Continues HiRDB startup processing.
- Reason code 01:
- Host names for which the -n option of the pdstart operand was set will not be enabled in the multi-connection address facility.
- Reason code 02 or 03:
- Host names indicated in bb....bb will not be enabled in the multi-connection address facility.
- Action
- Terminate HiRDB normally, change the system common definition according to the reason code, and then start up HiRDB.
Reason Code | Meaning | Action |
---|
01 | The -n option was specified in the pdstart operand, but the -m option corresponds to one of the following:
- The -m option has not been specified.
- None of the host names specified in the -m option can be resolved.
| If the -m option is not specified in the pdstart operand, specify it there. In all other cases, revise the host name specified in the -m option of the pdstart operand. Take action based on the KFPS00615-W (reason code 02) message. |
02 | Either the host name specified in the -m option of the pdstart operand in the system common definition is invalid, or the name cannot be resolved. | If the host name is invalid, specify the correct host name. For other cases, the host name has not been resolved. Record the host name in the hosts file or in the DNS. |
03 | Either the host name specified in the -n option of the pdstart operand in the system common definition is invalid, or the name cannot be resolved. |
KFPS00700-E E+L
Error occurred in system call aa....aa. errno=bbb, function name=cc....cc
- A system call aa....aa resulted in an error.
- aa....aa: Name of system call
- bbb: Return code of the system call
- cc....cc: Name of the function resulting in the error
- S: Resumes processing, or terminates the HiRDB system abnormally.
- Action
- Check errno.h or the OS manual for the details of errno (external integer variable indicating the error status), eliminate the cause of the error, then re-execute.
- For representative errno, see 4.3 System call return codes.
KFPS00701-E L
Unable to continue processing due to file system error.
- A system call for manipulating a file terminated abnormally.
- S: Terminates the system.
- Action
- If another message was output immediately before this message, refer to that message. If there is no problem with the access privilege to the file to be operated on, contact the customer support center.
KFPS00703-E L
Insufficient memory. required memory size=aa....aa bytes, area type=bb....bb
- A memory shortage occurred.
- aa....aa: Size of the area that was to be allocated
- bb....bb: Type of area resulting in memory shortage:
- PROCESS: Process private area
- STATIC_SHMPOOL: Static shared memory
- S: Terminates the system.
- Action
- If the memory shortage occurred in the process private area, check the number of processes and re-execute.
- If the same error recurs, check the cause of the error and contact the customer support center.
KFPS00705-E L
Error found while analyzing definition file.
- An error was detected while analyzing a HiRDB system definition file.
- S: Waits for the start command.
- O: Correct the HiRDB system definition file and enter the pdstart command.
- Action
- If another message was output immediately before this message, refer to that message. If there is no error in the HiRDB system definition file, contact the customer support center.
KFPS00707-E L
Max number of processes in process service definition invalid
- The specified maximum number of processes is invalid in the system common definition or unit control information definition.
- S: Waits for the start command.
- O: Correct the definition file and reenter the pdstart command. If the definition file is correct, contact the customer support center.
KFPS00709-E L
Process monitoring time in process service definition invalid
- The specified process monitoring interval is invalid in the system common definition or unit control information definition.
- S: Waits for the start command.
- O: Correct the definition file and reenter the pdstart command. If the definition file is correct, contact the customer support center.
KFPS00710-E E+L
Shared memory unavailable; unable to continue processing.
- Shared memory is not available to a process server process. Another possibility is that shared memory is not available to a command.
- S: Terminates the system. In the case of a command, terminates it abnormally.
- O:
- In the case of a process server process:
- Contact the customer support center.
- In the case of a command:
- Reenter the command. If HiRDB is not started or if it is in the process of starting, wait for HiRDB start processing to complete and then execute the command. If the same message is output even after executing this command a number of times, contact the customer support center.
KFPS00712-E E+L
Unable to continue processing due to program error or hardware failure.
- Processing cannot continue due to a program error or a hardware failure.
- S: Terminates the system.
- Action
- Check the cause of the error and contact the customer support center.
KFPS00713-E L
Load module bb....bb for server aa....aa not found.
- Load module bb....bb for server aa....aa was not found.
aa....aa: Server name
bb....bb: Load module name
S: Terminates the system abnormally. - Action
- Determine the cause of the error and contact the customer support center.
KFPS00714-E L
Load module bb....bb for server aa....aa not executable file.
- Load module bb....bb for server aa....aa is not an executable file.
- aa....aa: Server name
- bb....bb: Load module name
- S: Terminates the system abnormally.
- Action
- Determine the cause of the error and contact the customer support center.
KFPS00715-E E+L
Unable to continue processing serious error occurred (reason code=aaa). enter pdrpause
- HiRDB processing cannot continue due to an error.
- aaa: Reason code
- 1: One of the following errors was found:
- An error was found in the setting of environment variable PDDIR.
- The content of /etc/inittab is invalid (in UNIX).
- The installation directory name contains a space (in UNIX).
- The HiRDB installation target is invalid (in Windows).
- The HiRDB installation did not terminate normally (in Windows).
- 2: There is a memory shortage.
- 3, 4, 13, 44, 101: Failed to open the status file.
- 5, 104: Failed to read the status file.
- 6: Failed to acquire the time.
- 7: HiRDB terminated abnormally three consecutive times during the restart process. However, if the pd_term_watch_count operand is specified, HiRDB terminated abnormally the number of consecutive times this operand was specified.
- 8: The content of the status file is invalid.
- 9, 105: Failed to move the file pointer in the status file.
- 10, 14, 42, 102: Failed to write to the status file.
- 11, 15, 103: Failed to close the status file.
- 16: Common memory is corrupted.
- 20: This is a definition error.
- 21: Failed to move the directory.
- 22: Failed to copy the common library (the file system is full or text busy).
- 30: No related program product is installed.
- 43: Failed to change privileges of the status file.
- S: Terminates processing.
- Action
- Take the following action:
- Ignore this message if 1 is specified in the pd_start_level operand in the system definition and it is okay to continue the start process, except for the unit in the additional information of this message.
- Execute the pdstop -f command if this message is output, and then the pdstart command did not terminate.
- If an error message or a warning message in the event log (in UNIX, syslogfile) of the system manager unit was output before or after this message, take the action for that message.
- If an error message or a warning message in the event log (in UNIX, syslogfile) of a unit in the additional information of this message before or after this message was output, take the action for that message.
- Eliminate the cause of the error according to the reason code for a unit in the additional information of this message.
- In UNIX, execute the pdrpause command for a unit in the additional information of this message.
- In Windows: Restart the service. If the service did not stop, stop the service, and then restart it.
- Execute the pdstart command.
- If a problem occurs that the HiRDB administrator cannot resolve, contact the customer support center.
KFPS00717-E L
System went down aaa consecutive times.
- The system shut down aaa times in a row.
- aaa: Abnormal terminations count
- S: Cancels HiRDB restart processing.
- Action
- Refer to the message that was output before this message to eliminate the cause of the error, then restart. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.
KFPS00719-E E+L
Message output error. message ID= aaa
- An error occurred during message output.
- aaa: ID of the message that was to be output
- S: Resumes processing.
- O: Take an operator's action appropriate to the displayed message ID.
- Action
- Take a HiRDB administrator's action appropriate to the displayed message ID.
KFPS00720-E L
Load module name not defined in definition file of server aa....aa
- A load module name (set module =) is not defined in the server definition file.
- aa....aa: Server name (same as the definition file name)
- S: Resumes processing.
- O: Specify the load module name in the definition file and restart the server.
- Action
- Contact the customer support center.
KFPS00721-E E
Versions of process service library and process service daemon different.
- The process server process does not match the version of the library that issued a service request to the process server process. Therefore, the process server process cannot execute the service.
- S: Cancels processing.
- Action
- Re-create the user server or command using a library that is supported by the HiRDB system that is being used, and restart. If the same error recurs, contact the customer support center.
KFPS00722-E E+L
Unable to excute recover process, code=aa....aa
- Process activation failed while recovering an abnormally terminated process.
- aa....aa: Error code:
- -729: Attempt was made to activate more processes than the value specified in the pd_max_server_process operand
- Other: Internal error occurred
- S: Terminates abnormally.
- Action
- Take action appropriate to the error code:
- -729: Increase the value of the pd_max_server_process operand in the system common definition or unit control information definition
- Other: Take appropriate action to the message output before this message
KFPS00727-E L
HA monitor has been stopped
- The HA monitor or the Hitachi HA Toolkit Extension is currently stopping.
- S: Terminates abnormally.
- O: Start the HA monitor or the Hitachi HA Toolkit Extension and restart HiRDB.
KFPS00728-E L
System error detected during communication with HA monitor. error code=aaaa, detail code=bbbb
- A system error was detected during communication processing with the HA monitor or Hitachi HA Toolkit Extension.
- aaaa: The HA monitor or Hitachi HA Toolkit Extension's return code
- bbbb: The HA monitor or Hitachi HA Toolkit Extension's detail return code
- S: Terminates abnormally.
- Action
- Check whether the HA monitor or Hitachi HA Toolkit Extension is running. If it is running, contact the customer support center.
KFPS00729-E L
Unable to continue HiRDB unit processing because server process went down aa....aa times; stops HiRDB unit bbbb
- Unit bbbb terminated abnormally because a HiRDB server process terminated abnormally aa....aa times within the monitoring interval of the process abnormal termination count monitoring facility (the pd_down_watch_proc operand).
- aa....aa: Number of times the server process terminated abnormally
- bbbb: Unit identifier
- S: Abnormally terminates.
- Action
- See the message output after this message and start HiRDB if necessary. To avoid abnormal termination of HiRDB due to abnormal termination of a server process, either omit the pd_down_watch_proc operand or specify 0. For details about the abnormal termination monitoring facility, see the HiRDB Version 9 System Operation Guide.
KFPS00730-I S
pdpfresh ended, return code = aa....aa
- The pdpfresh command ended with return code aa....aa.
- aa....aa: Return code (see Action below)
- S: Continues processing if the -c option is not specified when the pdpfresh command is executed and the return code is 0 or 4. Otherwise, terminates processing.
- Action
- Take action according to the following return codes:
Return code | Processing results of the pdpfresh command | Action |
---|
0 | No -c | Started refreshing the server process. | None. |
-c | No server process is currently refreshing. |
1 | No -c | Is not set. | Procedure:
- Execute the pdls -d prc -c command. The server process whose STATUS is C might be accessing a HiRDB file system area, including subsystem RDAREAs.
- If it is okay to forcibly refresh this process, execute the pdpfresh -f command again. If you decide not to refresh this process, re-execute the pdpfresh command after the running process terminates (if necessary, take action so the server process will terminate).
|
-c | A server process is currently refreshing. |
4 | The warning ended (an error occurred on at least one server). | Check the status of the server where the error occurred. If it is running, that server's server process might remain in a state in which it is accessing an RDAREA (which prevents resynchronizing of the pair volume). Specify that server in the pdpfresh command, and then retry the operation. |
6 | Terminated because the utility is running. | After the utility terminates, re-execute the pdpfresh command. Alternatively, if it is okay for an error to occur in the currently running utility, re-execute the pdpfresh -p command. |
8 | Abnormally terminated. | Contact the customer support center. |
KFPS00731-E L
Unable to create desktop, because of insufficient desktop heap. Required memory size=aa....aa(bb....bb) bytes
- Desktop heap is insufficient, so desktop creation failed.
- aa....aa: Memory size that the system attempted to allocate
- bb....bb: Insufficient memory size
- S: Terminates the command abnormally.
- Action
- Stop any other processes that are running. In addition, calculate how much desktop heap is used by HiRDB, specify in the pd_max_server_process operand a value at or below the maximum desktop heap value, and then restart HiRDB. For details about how much desktop heap is used by HiRDB, see the manual HiRDB Version 9 System Definitions.
KFPS00750-E E
Unable to execute command due to insufficient memory. required memory size=aa....aa bytes, area type=bb....bb
- A command cannot be executed due to a memory shortage.
- aa....aa: Size of the area that was to be allocated
- bb....bb: Type of area resulting in memory shortage:
- PROCESS: Process private area
- STATIC_SHMPOOL: Static shared memory
- S: Terminates the command abnormally.
- Action
- If the memory shortage occurred in the process private area, check the number of processes and re-execute.
- If the same error recurs, check the cause of the error and contact the customer support center.
KFPS00751-E E
Command syntax incorrect.
- A syntax error was detected in a command.
- O: Check the command syntax.
KFPS00752-E E
Load module name invalid.
- The length of a pdls command argument (load module name) is invalid.
- O: Set the correct argument.
KFPS00753-E E
Server name invalid.
- The length of a pdls command argument (server name) is invalid.
- O: Set the correct argument.
KFPS00754-E E
Process ID invalid.
- The length of a pdls command argument (process ID) is invalid.
- O: Set the correct argument.
KFPS00755-E E+L
Inter-process communication unavailable.
- A command cannot be executed because inter-process communication is not available. Possible reasons are as follows:
- HiRDB is not active.
- An inter-process communication environment has not been set up
- S: Terminates processing.
- O: Enter the command when the HiRDB system is active.
KFPS00756-E E
Command argument invalid.
- A command argument is invalid.
- O: Set the correct argument.
KFPS00759-E E
Service group name invalid.
- The length of a pdls command argument (service group name) is invalid.
- O: Set the correct argument.
KFPS00760-E E
Unable to execute pdrpause command, HiRDB unit is not PAUSE
- The pdrpause command cannot be executed because the pause of HiRDB startup or restart processing has been released.
- S: Terminates processing.
- O: There is no need to execute the pdrpause command.
KFPS00791-I S
Usage: pdls -d prc {[-a |-s server ID |-g service group name |-l load module name |-p process ID]}
- Displays the format of the pdls command. This message is displayed when the command specification is invalid.
- S: Terminates the command abnormally.
- O: Reenter correctly the specified command.
KFPS00793-I S
Usage : pdrpause
- The specification format of the pdrpause command is invalid.
- S: Terminates processing.
- O: Specify the command correctly and re-execute.
KFPS00803-E E+L
Unable to start scheduler. reason code=aa....aa
- An error occurred during scheduler normal startup or restart processing.
- aa....aa: Reason code indicating the nature of the error
- S: Cancels HiRDB system normal startup or restart processing.
- Action
- Take action appropriate to the reason code in the list, and restart HiRDB. The following table shows the reason codes and actions:
Reason code | Explanation | Action |
---|
1 | Impossible to allocate shared memory | If an error message has been output before this message, take action appropriate to that message and restart HiRDB. |
2 | Definition analysis error |
5 | Communication error | The port number specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand might be the same as the port number of another definition or program. If they are the same, change one of the values in the port number settings so that they do not overlap, and then restart. Otherwise, if any error messages were output before this message, take corrective action according to those messages, and then restart. |
6 | Queue information file access error | Check whether there is an access privilege to the spool directory under the HiRDB working directory. If there is an access privilege, contact the customer support center. |
KFPS00830-E E+L
Unable to start server aa....aa, reason code=b
- An error occurred during the server start process.
- aa....aa: Name of the server that cannot start
- b: Reason code indicating the error content
- S: Aborts the server start process.
- O: If it is necessary to start the applicable server, after the HiRDB administrator takes action, start the server using the pdstart -s command.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
1 | Server already active | Specified server or service group has already been started; if the specification is invalid, specify the correct server name and enter the pdstart -s command. |
2 | Timing error | Scheduler has not been started or is engaged in termination processing; enter the pdstart -s command after restarting the system. |
3 | Invalid number of servers | The maximum number of servers that can be run under the scheduler has been exceeded; check the schedule service definition, take appropriate action, then enter the pdstart -s command. |
4 | Communication error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command. |
5 | Incompatible program versions | Check the version of each library in the HiRDB system, take appropriate action, then enter the pdstart -s command. |
6 | Unable to activate a resident process | Check and, if necessary, change the number of processes that the applicable server machine can start (for example, pd_process_count and pd_max_server_process). If this message is output after HiRDB starts, execute the pdstart command and restart HiRDB. If this error occurs when executing the pdstart -s command, re-execute the pdstart -s command. |
7 | Memory shortage | Check the memory size specified in the definition, take appropriate action, then enter the pdstart -s command. |
8 | Definition analysis error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command. |
KFPS00835-E E+L
Unable to terminate server aa....aa. reason code=bb....bb
- An error occurred during server termination processing.
- aa....aa: Name of server that cannot be terminated
- bb....bb: Reason code indicating the nature of the error
- S: Cancels server termination processing.
- O: If the server needs to be terminated, take the appropriate HiRDB administrator's action and terminate the server with the server termination command (pdstop -s).
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
1 | Server inactive | Specified server or service group has not been started; if the specification is invalid, specify the correct server name and enter the pdstop -s command. |
2 | Timing error | Scheduler has not been started or is engaged in termination processing; enter the pdstart -s command after restarting the system. |
3 | Communication error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command. |
4 | Incompatible program versions | Check the version of each library in the HiRDB system, take appropriate action, then enter the pdstop -s command. |
5 | Memory shortage | Check the memory size specified in the definition, take appropriate action, then enter the pdstop -s command. |
6 | Definition analysis error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command. |
KFPS00836-E E+L
Unable to create a server process. server=aa....aa, reason code=bb....bb (cc....cc)
- Server processing generation occurred during server scheduling.
- aa....aa: Name of the server that could not create the process
- bb....bb: Reason code for process creation error
- cc....cc: Internal code
- S: Resumes processing.
- Action
- Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
1 | Maximum number of processes was exceeded | Decrease the number of processes being executed. Alternatively, increase the value specified in the pd_max_server_process operand. |
2 | Memory shortage (fork error) | Correct the memory shortage. |
99 | HiRDB internal error | Check the message or the internal and error detail codes that were output before this message and eliminate the cause of the error. If the standby-less system switchover (effects distributed) facility is being used, internal code -725 may be output during system switchover, but this is not a problem because server startup is suppressed during switchover. |
KFPS00840-E E+L
Error occurred while analyzing definitions. server attribute=aa....aa
- An error occurred while analyzing the system definition information.
- aa....aa:
- Type of server subject to system definition information analysis:
- "SYSTEM": System server
- "USER": Front-end server, back-end server, or dictionary server
- The system processing and action to take differ depending on the server attributes.
- System server:
- S: Terminates HiRDB abnormally.
- Action
- If an error message was output before this message, take the action indicated in that message, and restart HiRDB. If the same error recurs, contact the customer support center.
- HiRDB/Parallel Server:
- S: Cancels the server processing and terminates the process.
- Action
- Check the corresponding server definition, take appropriate action, and then restart the server with the pdstart -s command. If the same error recurs, contact the customer support center.
KFPS00841-E E+L
Service group name not defined in server definition file. server=aa....aa
- A service group name is not defined in the server definition file.
- aa....aa: Name of the server resulting in the definition error
- S: Cancels server startup processing.
- O: If the server needs to be started, take the appropriate HiRDB administrator's action and enter the server startup command (pdstart -s).
- Action
- Specify the server group name in the corresponding server definition file.
KFPS00843-I S+L
Changed process count. server: aa....aa
- The number of resident server processes and the maximum number of startup processes have been changed.
- aa....aa: Name of the server for which the values have been changed
- S: Resumes processing.
KFPS00844-E E+L
Error code in pdchprc command. server:aa....aa, reason code=bb
- An error occurred during pdchprc command execution.
- aa....aa: Name of the server resulting in the error
- Depending on the timing of the error, ******** may be output as the server name.
- bb: Reason code indicating the nature of the error
- S: Terminates processing.
- Action
- Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
11 | Server inactive | If an invalid server name was specified, enter the pdchprc command with the correct server name specified. |
12 | Invalid server name | Enter the pdchprc command with the correct server name specified. |
13 | Server terminating | If an invalid server name was specified, enter the pdchprc command with the correct server name specified. |
14 | Unit did not start up | After startup of the server aa....aa unit is complete, execute the pdchprc command. |
16 | Alternating | The number of normal BES server processes cannot be changed, because processing is alternating with alternate BES units. To change the number of normal BES server processes that are alternating with alternate BES units, change the number of alternate BES server processes. However, the number of alternate BES server processes at this time will be the total number of normal BES server processes that are alternating with alternate BES units. For details, see Server process allocation after system switchover in the HiRDB Version 9 System Operation Guide. |
21 | Definition analysis error | If an error message was output before this message, take action appropriate to that message. |
22 | Communication timeout |
23 | Memory shortage | Take appropriate action to prevent a memory shortage. |
24 | Mismatched program versions | Check the version of each HiRDB library and take appropriate action. |
25 | Maximum number of processes exceeded | Reduce the number of processes being executed. |
26 | Communication error | If an error message was output before this message, take action appropriate to that message. |
Other | Does not apply | If an error message was output before this message, take the action indicated in that message. If no message was output, contact the customer support center. |
KFPS00847-W E+L
Unable to delete message queue automatically in next system startup; queue information failed to be cataloged. server=aa....aa
- The message queue cannot be deleted automatically at the next system startup, because the queue information file write operation failed.
- aa....aa: Name of the server resulting in the queue information write error
- If the unit is applicable to the standby-less system switchover (effects distributed) facility, ****** may be output instead of the server name.
- S: Resumes processing.
- Action
- Take action appropriate to the error message output before this message. When HiRDB is stopped, use the ipcrm command to delete the relevant message queue.
KFPS00849-W E+L
Specified aa....aa is too large for max users, assumed limit bbb, server:cc....cc
- The number of processes specified in the pdchprc command is greater than the maximum number of startup server processes defined for the HiRDB.
The system resumes processing assuming the maximum number of startup server processes specified in the HiRDB definition. - aa....aa: Item whose value is to be modified:
- max_process_count: Maximum number of startup processes
- resident_process_count: Number of resident processes
- bbb: Maximum number of startup server processes specified in the HiRDB definition
- cc....cc: Server name
- S: Resumes processing.
- O: If there are too many processes, enter the pdchprc command to reduce their number.
KFPS00850-E E+L
Unable to perform scheduling for server bb....bb due to an error in system call aa....aa. errno=cc....cc
- The indicated server cannot be scheduled, because system call aa....aa resulted in an error.
- aa....aa: Name of the system call resulting in the error
- bb....bb: Name of the server on which the error occurred
- If the unit is applicable to the standby-less system switchover (effects distributed) facility, ****** may be output instead of the server name.
- cc....cc: System call return code
- S: Terminates the scheduling on the indicated server; continues other scheduling operations. However, if the server name is ******, startup of the unit is terminated.
- Action
- In UNIX:
- Based on the return information, determine and correct the cause of the error. If the cause cannot be determined, contact the customer support center.
- If an error occurs in the MSGGET system call, the value of the operating system parameter (kernel parameter) msgmni (message queue identifier count) in the operating system may be too small. Estimate the amount required for all programs to run on the server machines when msgmni is invoked. Reboot the applicable server machines after changing the specified value.
- If an error occurs in the MSGSND or MSGRCV system calls, the value of the operating system parameters (kernel parameters) msgmni or msgtql in the operating system may be too small. Estimate the amount required for all programs to run on the server machines. Reboot the applicable server machines after changing the specified value. Also, the message queue HiRDB uses may have been improperly deleted by the ipcrm or other command. If the message queue was deleted, forcibly terminate HiRDB if it does not abnormally terminate. Then, reboot the applicable server machines.
- If the HiRDB server's start processing terminates without outputting message KFPS01851-E, even though errno=11 (EAGAIN) occurred in the MSGSND system call, the HiRDB server's start processing has terminated normally and this message KFPS00850-E can be ignored.
- In Windows:
- Estimate the number of message queue identifiers required by HiRDB, and specify a value at least that large in the PDUXPLMSGMNI and PDUXPLMSGTQL system environment variables. Then, terminate HiRDB and restart all services. For details on how to estimate the number of needed message queue identifiers, see the HiRDB Version 9 Installation and Design Guide.
In addition, if message KFPS02179-I is output frequently, consider following the actions described in message KFPS02179-I to reduce the number of skips in synchronization point processing.
- If the HiRDB server's start processing terminates without outputting message KFPS01851-E, even though errno=11 (EAGAIN) occurred in the MSGSND system call, the HiRDB server's start processing has terminated normally and this message KFPS00850-E can be ignored.
KFPS00851-E E
Unable to delete message queue due to an error occurred in MSGCTL system call. errno=aa....aa, queue ID=bb....bb
- In UNIX:
- The message queue cannot be deleted, because the MSGCTL system call resulted in an error.
- In Windows:
- The message queue cannot be deleted, because an error occurred.
- aa....aa: Return code of the system call
- bb....bb: ID of the message queue resulting in the error
- S: Resumes processing.
- O: To delete message queues in UNIX, use the ipcrm command to delete the appropriate message queues.
- In the case of Windows, restart the HiRDB service. If the error recurs even after a restart or if the cause cannot be determined, contact the customer support center.
- Action
- In UNIX, refer to the OS manual to determine the cause on the basis of the return code of the system call, and take action. If the cause of the error cannot be identified or the message is reissued, contact the customer support center.
KFPS00852-E E
Unable to delete message queue due to queue information acquisition failed. reason code=aa....aa
- The message queue cannot be deleted, because acquisition of queue information failed.
- aa....aa: Reason code
- S: Cancels message queue deletion processing.
- Action
- If an error message has been output before this message, take action appropriate to that message. The following table lists the reason codes and the actions to be taken:
Reason code | Explanation | Action |
---|
1 | Memory shortage | Terminate any unneeded processes and restart. |
2 | Queue information file access error | If an error message has been output before this message, take action appropriate to that message and restart. Also, check for any unauthorized access to a file under %PDDIR%\spool. |
3 | Incompatible program versions | Check the versions of HiRDB commands, libraries, etc., take appropriate action, then restart. |
4 | Invalid environment variable | Set the correct environment variable and restart. |
KFPS00854-W E+L
Insufficient memory in message buffer pool. server=aa....aa
- During allocation on the indicated server, a memory shortage occurred in the message storage buffer pool. Because of this the service cannot be executed on the indicated server.
- aa....aa: Name of the server where the buffer shortage occurred
- S: Resumes processing.
- Action
- Take the following actions:
- If the name of the server is _trnrcv
- There is insufficient space in the transaction recovery message queue. Refer to the pd_trn_rcvmsg_store_buflen operand in the manual HiRDB Version 9 System Definition and increase the size of the transaction recovery message queue.
- If the name of the server is not _trnrcv
- If this message is output during execution of a UAP:
- If you are executing UAPs concurrently, reduce the number of UAPs that are executed concurrently.
- If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.
- If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the UAP after the pdpfresh command terminates.
- If this message is output during execution of a utility:
- If you are executing utilities concurrently, review and, if necessary, change the maximum number of utilities that can be executed concurrently. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.
- If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.
- If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the utility after the pdpfresh command terminates.
- If this message is output during execution of a command:
- If you are executing commands concurrently, reduce the number of commands that are executed concurrently.
- If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes
- If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the command after the pdpfresh command terminates.
KFPS00855-W E+L
Insufficient memory. required area size=aa....aa bytes, area type=bb....bb
- A memory shortage occurred.
- aa....aa: Size of the area that was to be allocated
- bb....bb: Type of area resulting in memory shortage:
- DYNAMIC SHMPOOL: Dynamic shared memory area
- PROCESS: Process private area
- STATIC SHMPOOL: Static shared memory area
- S: Resumes processing.
- Action
- If an error message was output before this message, take the action indicated in the message. If the type of the area where a memory shortage occurred is a process private area, take the following action and then re-execute.
- Reduce the number of resident HiRDB server processes.
- Stop unnecessary processes.
- Extend the virtual memory.
- If the same error recurs, contact the customer support center.
KFPS00856-E E+L
Scheduler library and scheduler daemon have different version
- The version of the scheduler library does not match the version of the scheduler process.
- S: Terminates processing.
- Action
- Contact the customer support center.
KFPS00857-E E+L
Mismatched version found during scheduler processing, version type=aa....aa
- A version mismatch was detected during scheduler processing.
- aa....aa: Type of version resulting in mismatch:
- COMMAND: Command version
- HOLD: Shutdown file version
- NAMDATA: Name server registration version
- QUEUE: Queue information file version
- REQUEST: Service request header version
- STATUS: Status file version
- TABLE: Table version
- S: Terminates processing.
- Action
- Check the current HiRDB environment, take appropriate action, and restart HiRDB.
KFPS00860-W E+L
Pd_service_port ignored, reason code=aaaa(bbbbb), cannot use PDSERVICEPORT for HiRDB/client.
- HiRDB ignored the specification of the pd_service_port operand for the reason indicated in aaaa(bbbbb), and continued processing. A HiRDB client cannot use the high-speed connection feature. An attempt to use a high-speed connection to the HiRDB where this message was output fails because the HiRDB server is not active.
- aaaa: Reason code
- bbbbb: Maintenance information for the displayed reason code:
- Reason code 1:
0
- Reason code 2 or 3:
-208: HiRDB-provided load module is invalid
- S: Resumes processing.
- O: Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
1 | The value of the pd_service_port operand is the same as the value of the pd_name_port operand. | The port number specified in the pd_service_port operand in the system common definition or unit control information definition is the same as the port number specified in the pd_name_port operand. Change a definition so that these values are not duplicated, then re-execute HiRDB. |
2 3 | Definition analysis is invalid. | - Maintenance information: -208
HiRDB may not have been installed correctly, or the HiRDB-provided load module may be invalid. Reinstall and set up HiRDB, then re-execute.
- Maintenance information: Other than -208
Contact the administrator.
|
- Action
- If none of the reasons provided under "O" applies, contact the customer support center.
KFPS00880-I S
Usage: pdls -d scd [-s server name]
- The format of an option is invalid in the pdls -d scd command.
- S: Terminates processing.
- Action
- Reenter correctly the specified command.
KFPS00888-W L
Server aa....aa exceeded pd_queue_watch_time value. value=bb....bb
- No message can be acquired from the message queue even if the message queue monitoring time (pd_queue_watch_time operand value) of the message queue monitoring facility is exceeded. The problem occurred on server aa....aa. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
Possible causes of the message queue monitoring time being exceeded: - The CPU load reduced the processing capacity.
- I/O is delayed by an I/O error.
- The number of processes available is less than the number required for fetching messages from the message queue because the number of HiRDB server processes is too small for the number of multiply executing UAPs and utilities.
- The number of HiRDB server processes is restricted by the following operands:
- pd_max_server_process
If there are several servers running within a unit, perform a detailed estimate of the value specified for this operand. Also, if the standby-less system switchover facility is being used, the estimate must include the case of a system switchover.
- pd_max_bes_process
If multiple front-end servers are being used or if the standby-less system switchover (1:1) facility is being used, perform a detailed estimate of the value specified for this operand.
- pd_max_dic_process
If multiple front-end servers are being used, perform a detailed estimate of the value specified for this operand.
- pd_ha_max_server_process
If the standby-less system switchover (effects distributed) facility is being used, perform a detailed estimate of the value specified for this operand.
- pd_max_users
If there are numerous concurrent connections, an appropriate value must be selected.
- aa....aa: Server name
- bb....bb: Value of the pd_queue_watch_time operand
- S: Continues processing.
- Action
- For details on causes of and actions for server processes not responding, and messages remaining in the message queue, see the HiRDB Version 9 System Operation Guide.
- If you are unable to determine the cause of the problem, contact the customer support center.
KFPS00889-E L
Server aa....aa exceeded pd_queue_watch_time value, Unit terminated.
- No message can be acquired from the message queue even if the message queue monitoring time (pd_queue_watch_time operand value) of the message queue monitoring facility is exceeded. The problem occurred on server aa....aa.
The unit is terminated because stop was specified in the pd_queue_watch_timeover_action operand. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
Possible causes of the message queue monitoring time being exceeded: - The CPU load reduced the processing capacity.
- I/O is delayed by an I/O error.
- The number of processes available is less than the number required for fetching messages from the message queue because the number of HiRDB server processes is too small for the number of multiply executing UAPs and utilities.
- The number of HiRDB server processes is restricted by the following operands:
- pd_max_server_process
If there are several servers running within a unit, perform a detailed estimate of the value specified for this operand. Also, if the standby-less system switchover facility is being used, the estimate must include the case of a system switchover.
- pd_max_bes_process
If multiple front-end servers are being used, or if the standby-less system switchover (1:1) facility is being used, perform a detailed estimate of the value specified for this operand.
- pd_max_dic_process
If multiple front-end servers are being used, perform a detailed estimate of the value specified for this operand.
- pd_ha_max_server_process
If the standby-less system switchover (effects distributed) facility is being used, perform a detailed estimate of the value specified for this operand.
- pd_max_users
If there are numerous concurrent connections, an appropriate value must be selected.
- aa....aa: Server name
- S: Abnormally terminates HiRDB.
- Action
- For details on causes of and actions for server processes not responding, and messages remaining in the message queue, see the HiRDB Version 9 System Operation Guide.
- If you are unable to determine the cause of the problem, contact the customer support center.
KFPS00890-E E
Error occurred during scheduler command processing. reason code=aa....aa, command=bb....bb
- An error occurred during scheduler command processing.
- aa....aa: Reason code indicating the nature of the error
- bb....bb: Command name
- S: Cancels command processing.
- O: Take action appropriate to the reason code, as listed below, and reenter the command:
Reason code | Explanation | Action |
---|
31 | Memory shortage | Determine the number of active processes, and reduce the amount of memory used. Also, if an error message was output before this message, take the action indicated in that message. After taking action, re-execute the command. |
33 | Definition analysis error | If an error message has been output before this message, take action appropriate to that message and reenter the command. |
KFPS00891-E E
Invalid use of command aa....aa
- The usage of command aa....aa is invalid.
- aa....aa: Command name
- S: Terminates processing.
- Action
- Reenter the command with the correct usage.
KFPS00892-E E
Scheduler inoperable; unable to execute aa....aa command
- The scheduler is inactive. Or, the indicated command cannot be executed because the system is engaged in termination processing.
- aa....aa: Command name
- S: Cancels command processing.
- O: Reenter the command after system startup is completed.
KFPS00894-E E
Scheduler aa....aa command and scheduler daemon have different version
- The version of scheduler command aa....aa does not match the version of the process program.
- aa....aa: Command name
- S: Cancels processing.
- Action
- Check the commands available to the HiRDB that is being used, take appropriate action, then reenter the command. If the same error recurs, contact the customer support center.
KFPS00900-I L
Communication protocol error occurred. status code=aaaaaa, request code=bbbb, branch number=ccccc, server=dddddd
- A communication protocol error occurred during transaction processing.
- aaaaaa: HiRDB internal code (status code)
- bbbbbb: HiRDB internal code (request code)
- cccccc: HiRDB internal code (branch number)
- dddddd: Server name
- Action
- Take one of the following actions:
- Tune the RPC and socket-related communication parameters by referring to the manual for the OS being used, a TCP/IP network guide, and the HiRDB Version 9 System Definition manual.
- Increase the concurrency level of the corresponding server.
- Check the network workload of the server machine where the corresponding server is located.
KFPS00935-I L
Transaction decision resending aa....aa, TRNGID=bb....bbcc....cc, TRNBID=bb....bbdd....dd, server=ee....ee, completion type=f
- Retransmission processing of a rollback request has either started or stopped. This message is output either at the expiration of the maximum wait time for rollback completion response specified in the pd_trn_rollback_watch_time operand in the system common definition, or when the transaction is completed after retransmission of the rollback request.
- aa....aa: Processing event
- start: Processing started
- stop: Processing stopped
- bb....bb: HiRDB identifier, and unit identifier
- cc....cc: Global transaction number
- dd....dd: Transaction branch number
- ee....ee: Name of server
- f: Global transaction completion type
- r: Rollback
- S: Continues processing.
KFPS00936-E L
Transaction decision resending timeout occurred, TRNGID=aa....aabb....bb, TRNBID=aa....aacc....cc, server=dd....dd, reason=ee....ee
- Retransmission stopped because the rollback instruction retransmission time limit elapsed. This message is output after the start of retransmission processing of the rollback request, at the expiration of the rollback instruction retransmission time limit specified in the pd_trn_rollback_watch_time operand in the system common definition.
- aa....aa: HiRDB identifier, and unit identifier
- bb....bb: Global transaction number
- cc....cc: Transaction branch number
- dd....dd: Name of server
- ee....ee: Reason code
- COMMUNICATION: An inter-process communication error occurred.
- S: Abnormally terminates the relevant HiRDB server process.
- O: Contact the HiRDB administrator.
- Action
- Execute the pdls -d svr command to make sure that the dictionary server and all back-end servers are up and running. Check the status information, and if there is a server that is not running, restart it according to the description of the execution results of the pdls -d svr command in the manual HiRDB Version 9 Command Reference.
KFPS00955-E E+L
Unable to start transaction service. reason code=aaaa
- An error indicated by the reason code occurred while starting or restarting the transaction server process. As a result, the transaction server process cannot be started.
- aaaa: Reason code
- S: Terminates HiRDB abnormally.
- Action
- Take an action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action |
---|
0001 | Memory shortage occurred in the process. | Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center. |
0002 | Read error occurred in the transaction manager management file. | Contact the customer support center. |
0100 | Shared memory shortage occurred | Contact the customer support center. |
0200 | Definition analysis startup processing resulted in an error. | If an error message has been output before this message, take action appropriate to that message. |
0201 | Analysis of the system common definition or unit control information failed. | Check the system common definition or unit control information and restart HiRDB. If the definition is correct, contact the customer support center. |
0300 | Communication error occurred. | The port number specified in the -t option of the pd_trn_port operand or pdunit operand might be the same as the port number of another definition or program. If they are the same, change the values in the port number settings so that they do not overlap, and then restart HiRDB. Otherwise, if an error message has been output before this message, take action appropriate to that message. |
0600 | Registration of service information in the name service function failed. | If an error message has been output before this message, take action appropriate to that message. |
1100 | Error occurred while starting the statistics log service function. |
1800 | Activation of transaction recovery process failed |
1801 | Error occurred while reporting server completion to the system manager. |
KFPS00956-E E+L
Error occurred while terminating transaction service; continues processing. reason code = aaaa
- An error occurred while terminating the transaction server process.
- aaaa: Reason code
- S: Resumes processing.
- Action
- Check the reason code to determine why the transaction server process cannot be terminated normally, then take appropriate action, as listed below:
Reason code | Explanation | Action |
---|
0001 | Memory shortage occurred in the process. | Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center. |
0300 | Communication error occurred. | If an error message has been output before this message, take action appropriate to that message. |
0601 | Deletion of service information by the name service function failed. |
1101 | Error occurred while terminating the statistics log service function. |
1802 | Termination of transaction recovery process failed. |
KFPS00957-E E+L
Unable to change definition at transaction service restart
- During restart or during start of a log application site, the value specified for the pd_max_users, pd_max_bes_process, or pd_max_dic_process operand has changed since the previous normal startup.
- S: Resumes processing.
- Action
- Transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Start the HiRDB system by restoring the system definition that should not be changed. After that, terminate the HiRDB system normally and change the system definition.
- Log application site
Make the operand value the same as that of the application site, perform system log optimizations, and then restart.
KFPS00958-I E+L
Unit terminating; stops receiving new transations
- No new transactions will be accepted because unit termination has been requested. The transaction server process is starting preparations for termination processing.
KFPS00961-E E+L
Unable to start transaction recovery service. reason code = aaaa
- The error indicated by the reason code occurred while starting the transaction recovery process. As a result, the transaction recovery process cannot be started.
- aaaa: Reason code
- S: Terminates HiRDB abnormally.
- Action
- Take action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action |
---|
0200 | Definition analysis startup processing resulted in an error. | If an error message has been output before this message, take action appropriate to that message. |
0300 | Communication error occurred |
0800 | Registration of the schedule service function of the transaction recovery process failed |
1801 | Error occurred while reporting completion of the process activation to the system manager |
KFPS00962-E E+L
Error occured while terminating transaction recovery service; continues processing. reason code=aaaa
- An error occurred while terminating the transaction recovery process.
- aaaa: Reason code
- S: Resumes processing.
- Action
- Check the reason code to determine why the transaction server process cannot be terminated normally, then take appropriate action, as listed below:
Reason code | Explanation | Action |
---|
0300 | Communication error occurred. | If an error message has been output before this message, take action appropriate to that message. |
KFPS00965-E E+L
Insufficient memory. required memory size=aa....aa bytes, area type=bb....bb
- A memory shortage occurred.
- aa....aa: Size of the area that was to be allocated
- bb....bb: Type of area resulting in memory shortage:
- DYNAMIC SHMPOOL: Dynamic shared memory area
- PROCESS: Process private area
- STATIC SHMPOOL: Static shared memory area
- S: Cancels processing.
- Action
- If the memory shortage occurred in the process private area, re-evaluate the number of processes, take appropriate action, then re-execute.
- If the same error recurs, contact the customer support center.
KFPS00969-E L
Error occurred during aa....aa processing, reason code=bbbb, TRNGID=ccccccccdddddddd, TRNBID=cccccccceeeeeeee, server=ff....ff, PID=gg....gg
- An error occurred during transaction completion processing.
TRNGID: Global identifier of the transaction
TRNBID: Branch identifier of the transaction - aa....aa: Transaction completion processing
- prepare: One-phase commit processing
- commit: Two-phase commit processing
- rollback: Rollback processing
- bbbb: Reason code
- cccccccc: HiRDB system identifier and unit identifier
- dddddddd: Global transaction number
- eeeeeeee: Transaction branch number
- ff....ff: Server name
- gg....gg: Process ID of the HiRDB server
- S: Terminates the process.
- Action
- Take action based on the reason code.
Transaction completion processing | Reason code | Explanation | Action |
---|
commit | 0001 | During transaction commit processing, synchronization with the transaction on another server failed. | For whatever reason, a server other than the one where the message was output (excluding recovery-unnecessary front-end servers) could not continue processing the transaction. Check the status of the network, system, and server. |
KFPS00970-E E
Unable to execute aa....aa command of transaction, reason code=bbbb
- A transaction command aa....aa cannot be executed.
- aa....aa: Command name
- bbbb: Reason code
- S: Cancels processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
0001 | Memory shortage occurred on process | Reduce the number of processes and restart HiRDB. If this error recurs, contact the customer support center. |
0003 | The number of characters in a flag argument is outside the permitted range. | Check the flag argument, correct the error, then reenter the command. |
0004 | Character string in a flag argument contains an invalid character. |
0005 | A decimal character string in a flag argument is outside the permitted range. |
0008 | There is no information to be displayed. The transaction cannot be concluded. | (1) The possible causes are given below. If necessary, change the status of the unit or server, and re-execute the command.
- The applicable transaction cannot be found.
- The transaction server process cannot be used.
- The transaction status does not allow the transaction to be concluded.
- There is no server running.
- Because this is a log application site, the transaction cannot be displayed or resolved.
(2) Because the transaction was executed on a recovery-unnecessary front-end server, the transaction cannot be completed. Refer to the section on methods for finishing incomplete transactions in the manual HiRDB Version 9 System Operations Guide, and make sure the transaction finishes automatically. |
0009 | Option flag or flag argument is invalid. | Check the option flag or flag argument, correct the error, then reenter the command. |
0010 | System call error occurred because of a temporary memory shortage. | Wait a while, then reenter the command. |
0200 | Definition analysis startup processing resulted in an error. | If an error message has been output before this message, take action appropriate to that message. |
0300 | Communication error occurred. | Reasons are:
- The communication error was caused by the error that was reported before this message; take action appropriate to the error message.
- The communication error was caused by a temporary memory shortage; reduce the number of processes and reenter the command.
|
0301 | Timeout occurred. |
0602 | Versions do not match. | Check the version of each library in the HiRDB system, take appropriate action, then reenter the command. |
0700 | An error occurred during file access. | If an error message was output before this message, take the action indicated in the message. |
0701 | An error occurred during transaction commit processing. |
0702 | An error occurred during transaction rollback processing. |
0703 | An error occurred during transaction forcible termination processing. |
0704 | An error occurred during transaction status information acquisition. |
0705 | The unit that contains the system manager is not running. | Start the unit with the system manager, then execute the command. |
0706 | The command was entered from a server machine that does not contain the system manager. | Execute the command from the server machine that contains the system manager. |
0707 | An environment information acquisition error occurred. | If an error message was output, follow the action indicated in the message. Eliminate the error, and then restart HiRDB. |
KFPS00971-I L+S
Command accepted; (aa....aa)
- The aa....aa command has been accepted.
- aa....aa: Character string of entered command
- S: Resumes processing.
KFPS00972-I L
Error occurred during commit processing; reason code=aaaa, TRNGID=bb....bb PROGRAM=cc....cc
- An error occurred during commit processing.
- aaaa: Reason code
- bb....bb: Global transaction identifier
- cc....cc: UAP identification information
- S: Resumes processing.
- Action
- Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
0001 | Transaction was concluded by rollback processing because a timeout occurred while the system was waiting to receive communication from a child branch for the commit request. | Check the status of the network, system, and server. Or, check the maximum response wait time that has been set. |
KFPS00973-I L
Transaction branch completed. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, completion type=ff
- Because an error occurred in a transaction branch, a rollback was completed.
- TRNGID: Transaction global identifier
- TRNBID: Transaction branch identifier
- aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Server name
- ee....ee: HiRDB system internal code
- ff: Transaction completion type
- r: Rollback
- hr: Heuristic rollback
- S: Continues processing.
KFPS00974-I E+S
Usage: pdfgt {-A [-x host_name |-u unit_id] [-s server_name] |-t TRNGID [-x host_name |-u unit_id] [-s server_name]
- Displays the format of the pdfgt command (to forcibly terminate transaction). This message is displayed in the following cases:
- The format of a specified option or argument of the command is invalid.
- -h was specified as a command option.
- S: Terminates processing.
- O: If the command specification is invalid, reenter the command specified correctly.
KFPS00975-I E+S
Usage: pdls -d trn {[-t TRNGID] [-{a |c}] |-bc |-B system_node_ID [-{ a |c }] |-rc |-R RM_name [-{ a |c }] [-s server _name]}
- Displays the format of the pdls command that displays transaction status.
This message is displayed in the following cases: - -h was specified as a command option.
- The format of a command option or argument is invalid.
- S: If the command specification is invalid, cancels command processing.
- O: If the command specification is invalid, reenter the command specified correctly.
KFPS00976-I E+S
Usage: pdcmt {-A [-x host_name |-u unit_id] [ -s server_name] |-t TRNGID [-x host_name |-u unit_id] [ -s server _name]}
- Displays the format of the pdcmt command that commits a transaction. This message is displayed in the following cases:
- The format of a command option or argument is invalid.
- -h was specified as a command option.
- S: If the command specification is invalid, cancels command processing.
- O: If the command specification is invalid, reenter the command specified correctly.
KFPS00977-I E+S
Usage: pdrbk {-A [-x host_name |-u unit_id] [ -s server_name] |-t TRNGID [-x host_name |-u unit_id] [ -s server _name]}
- Displays the format of the pdrbk command that rolls back a transaction. This message is displayed in the following cases:
- The format of a command option or argument is invalid.
- -h was specified as a command option.
- S: If the command specification is invalid, cancels command processing.
- O: If the command specification is invalid, reenter the command specified correctly.
KFPS00978-E E
Command aa....aa used invalidly
- The usage of command aa....aa is invalid.
- aa....aa: Command name
- S: Cancels command processing.
- O: Reenter the command with the correct usage.
KFPS00979-E E
Transaction service inoperable; unable to execute aa....aa command
- The transaction server process has not been started, or it is engaged in termination processing. As a result, command aa....aa cannot be executed.
- aa....aa: Command name
- S: Cancels command processing.
- O: Reenter the command after the system has been started.
KFPS00980-W E+L
Unable to monitor elapsed time for transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee
- Transaction branch elapsed time cannot be monitored.
TRNGID: Transaction's global identifier
TRNBID: Transaction's branch identifier - aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Server name
- ee....ee: HiRDB's internal code
- S: Resumes processing.
- Action
- If there is no need to monitor the elapsed time, ignore this message. Otherwise, terminate HiRDB, refer to the timer service function message that was displayed before this message to eliminate the cause of the error, then restart HiRDB.
KFPS00981-I E+S
Usage: pdtrndec -i input_file_name[,input_file_name...] [-r rollback_script_file_name] [-o output_directory_name]
- This shows the method for using the pdtrndec command (the command to forcibly complete uncompleted transactions). This message is output in the following cases:
- If the method of specifying the pdtrndec command options or arguments was incorrect
- If the pdtrndec command was specified with the -h option
- S: If the command specification method was incorrect, terminates the command processing.
- Action
- If the command specification method was incorrect, re-execute the command using a correct specification method.
KFPS00982-E E
System call error, func=aa....aa, errno=bb....bb, path name=cc....cc
- Error aa....aa occurred in file or directory cc....cc.
- aa....aa: Name of the system call where the error occurred
- open: File or directory open
- close: File or directory close
- read: File or directory read
- write: File or directory write
- fseek: File pointer or directory setting
- bb....bb: errno of the system call where the error occurred
- cc....cc: Absolute path name of the file or directory where the error occurred
- If the path name exceeds 163 bytes, the path name is displayed preceded by an ellipsis (...), and the last 161 bytes are displayed.
- S: Terminates processing.
- Action
- See error.h and the OS manual, and eliminate the cause of the error.
KFPS00983-I L
Current transaction cancel occurred, server = aa....aa, transaction count = bb....bb
- The current transaction was forcibly terminated.
- aa....aa: Server name
- bb....bb: The number of forcibly terminated transactions
- S: Continues processing.
- Action
- If an error message is output before this message, see that message to eliminate the error.
KFPS00985-I E+L
Undetermined transaction information stored in aa....aa
- Information about unsettled transactions was collected in aa....aa.
- aa....aa: Absolute pathname of a file
- S: Resumes processing.
KFPS00986-W E+L
Unable to store undetermined transaction information in aa....aa. reason code=bbbb
- Information about unsettled transactions could not be collected in aa....aa.
- aa....aa: Absolute pathname of a file
- bbbb: Reason code
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
0001 | Memory shortage occurred in the process. | Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center. |
0052 | File manipulation failed. | Refer to the reason code in the message that was output before this message to check the cause of the error, and take appropriate action. |
0056 | Environment variable is invalid. | Set the correct value in the environment variable and re-execute. |
KFPS00988-I L
Transaction information. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, PID=dd....dd, C-PID=ee....ee(ff....ff), TIME=gghhii, PROGRAM=jj....jj, TMID=kkkk, XID=llllllllllllllll,mmmmmmmmmmmmmmmm,ENVGRP=nnnn
- This message, which displays additional information about a transaction error, is output in the following cases:
- When a transaction-related error has occurred.
- When a transaction is still being processed while planned termination is underway.
- TRNGID: Transaction's global identifier
- TRNBID: Transaction's branch identifier
- aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Process ID of the server processing the transaction as part of UAP or utility processing
- ee....ee: Process ID of the client (a UAP or a utility) that was connected to a server process. However, 0 is displayed in the following cases:
- A server process that is not connected to the client
- A server process that is connected to a client linked to a client library version prior to 04-00
- A server process that is connected to a Type 4 JDBC Driver
- ff....ff: IP address of the client (a UAP or a utility) that was connected to a server process. However, if no server process is connected to the client, 0.0.0.0 is displayed.
- gghhii: Time (hour, minute, second) the service request was accepted.
- If you are collecting statistics about the UAP from the statistics analysis utility on a per-transaction basis:
The transaction's execution start time is displayed.
- If you are collecting statistics about the UAP from the statistics analysis utility on a per-connection basis, or you are not collecting statistics about the UAP from the statistics analysis utility:
The connection start time is displayed.
- The PDSTJTRNOUT operand in the client environment definition specifies whether statistics about the UAP are collected on a per-transaction or per-connection basis.
- In the case of a server process that is not connected to the client, 999999 is displayed for the time the service request was accepted.
- jj....jj: UAP identification information (UAP name specified in PDCLTAPNAME in the client environment definition):
- PDCLTAPNAME not set:
Unknown is displayed.
- Utility:
The name of the utility is displayed.
- However, if the utility was running on a utility server process or if there was an error, such that the UAP identifier information could be not obtained, spaces may be displayed.
- kkkk: OLTP identifier of the connected OLTP (HiRDB_PDTMID or PDTMID in the client environment definition)
- This information is output if the client (UAP) connected to the HiRDB server process is an XDS client or an application complying with X/Open. If no OLTP identifier has been specified, **** is displayed.
- When an XDS client is used, HRDB is displayed.
- llllllllllllllll,mmmmmmmmmmmmmmmm:
- One of the following is output:
- The transaction identifier assigned by OLTP
This information is output when the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the OLTP is OpenTP1 or TPBroker for C++.
- The transaction identifier assigned by XDS
This information is output when the client (UAP) connected to the HiRDB server process is an XDS client.
- nnnn: Environment variable group identifier assigned by OLTP
- This is output when the client (UAP) connected to the HiRDB server process is an X/Open-compliant application and it uses the multi-connection facility; if the multi-connection facility is not used, **** is displayed.
- S: Resumes processing.
- O: Follow the HiRDB administrator's instructions.
- Action
- Transaction-related error occurred:
- This message is used to investigate the cause of the error indicated by one of the following error messages, which was output before this message:
- KFPS00972-I
- KFPS00973-I
- KFPS00990-I
- KFPS00991-I
- KFPS00992-E
- KFPS00993-I
- KFPS00935-I
- KFPS00936-E
- Transaction still executing while planned termination is underway:
- This message is used to check for transactions that have not been completed.
KFPS00990-I E+L
Transaction branch recovery complete. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, completion type=f,gg
- Recovery of a transaction branch has been completed.
- TRNGID: Transaction's global identifier
- TRNBID: Transaction's branch identifier
- aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Server name
- ee....ee: HiRDB's internal code
- f: Completion type of the corresponding transaction branch:
- c: Commit
- r: Rollback
- gg: Completion type of the corresponding global transaction:
- c: Commit
- hc: Heuristic commit
- hh: Heuristic hazard
- hm: Heuristic mix
- hr: Heuristic rollback
- r: Rollback
- S: Resumes processing.
KFPS00991-I E+L
Unable to recover from transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, determination type=ff
- Transaction branch recovery will be re-executed because recovery could not be completed.
- TRNGID: Transaction's global identifier
- TRNBID: Transaction's branch identifier
- aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Server name
- ee....ee: HiRDB internal code
- ff: Settlement type:
- c: Commit
- hc: Heuristic commit
- hh: Heuristic hazard
- hm: Heuristic mix
- hr: Heuristic rollback
- r: Rollback
- S: Resumes processing.
- Action
- If an error message has been output before this message, correct the error.
KFPS00992-E E+L
Unable to determine commit or rollback for transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee
- A transaction branch cannot be committed or rolled back by the system due to a communication error, etc.
- TRNGID: Transaction's global identifier
- TRNBID: Transaction's branch identifier
- aaaaaaaa: HiRDB system identifier and unit identifier
- bbbbbbbb: Global transaction number
- cccccccc: Transaction branch number
- dd....dd: Server name
- ee....ee: HiRDB internal code
- S: Retains the transaction branch status and resumes processing.
- Action
- Prepare for transaction commit with the pdcmt or pdrbk command if you cannot recover from the error. Another possibility is that the OLTP system might not have started. Check whether the OLTP system has started and, if not, start it.
- If the pdcmt or pdrbk command is used to commit the transaction, use the same commit type as the other transaction branches with the same TRNGID.
- For other transaction branches, use the same commit type as the transaction branch with the same TRNGID displayed in the KFPS00990-I message that is output after recovery processing has been completed. If there is no KFPS00990-I message containing the same TRNGID and no other transaction branch is found by pdls -d trn, use the pdrbk command to conclude the transaction.
KFPS00993-I L
Accepted process abnormal end request. PID=aa....aa, TRNGID=bb....bb, TRNBID=cc....cc, REQUEST=dd....dd
- A request for forced termination of the server process was received for one of the following reasons:
- A related server process stopped.
- A related unit terminated abnormally.
- A cause that must abort the transaction occurred.
- aa....aa: Process ID subject to forced termination
- bb....bb: Transaction identifier (transaction's global identifier)
- cc....cc: Transaction identifier (transaction's branch identifier)
- dd....dd: Request type:
- abnormal_unit_branch:
- Request for forced termination of the abnormal unit-related branch
- clt_attention:
- Request for forced termination accompanied by an interrupt at the client (this applies as well if Ctrl+C is pressed at the keyboard during execution of the client UAP)
- force_end:
- Request for forced termination based on a recovery instruction from OLTP or XDS (In the case of OLTP, this only applies to OpenTP1; for example, if OpenTP1 is abnormally terminated, and then restarted. In the case of XDS, this applies to internal rollback of the transaction and similar situations)
- pdcancel_end:
- Request for forced termination by pdcancel
- PDCWAITTIME_over:
- Request for forced termination due to the end of client's PDCWAITTIME
- subordinate_branch:
- Request for forced termination of a subbranch (for example, this applies if the subbranches related to a transaction are forcibly terminated due to another error)
- superior_branch:
- Request for forced termination of a master branch (for example, this applies if the master branch of a transaction is forcibly terminated due to an abnormality in one of the subbranches)
- abnormal_tran_end:
- Forced termination request from the skip count monitoring facility for enabling a synchronization point dump
- log_remain_check
- Request for forced termination from the facility for monitoring free area for the system log file
- abnormal_svr_branch:
- Request to forcibly terminate a branch related to an abnormal server
- S: Terminates abnormally by terminating the indicated server process.
- P: Contact the HiRDB administrator. After taking action, re-execute the process.
- Action
- Take a corrective action according to the message output by the related server process, the related unit, or the transaction.
- If the request type is abnormal_tran_end:
If, in the KFPS00988-I message that is output following this message, the UAP identification information is hdssqle[aa....aa]bb (aa....aa: reflection-group-name, bb: extraction-source-HiRDB Datareplicator-identifier), see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 9 System Operation Guide.
KFPS01001-I L+S
aa....aa assigned as current logical status file. server kind:bb server:cc....cc
- The status file aa....aa was allocated as the current file.
- aa....aa: Name of the current status file
- bb: Server type:
- 00: Unit
- 01: Server
- cc....cc: Name of the server used to allocate the file (if the server type is 00, the unit name is displayed; if it is 01, the server name is displayed)
- S: Resumes processing.
- Action
- If HiRDB is started when there is a status file in which an error occurred, the information displayed in the message is required for the specification of the following operands:
- The unit control information definition pd_syssts_last_active_file operand (if this message is output by a log application site, the pd_syssts_last_active_subfile operand)
- The server definition pd_sts_last_active_file operand (if this message is output by a log application site, the pd_sts_last_active_subfile operand)
KFPS01005-E E+L
Unable to status service due to aa....aa.
- The status server process cannot be started.
- aa....aa: Reason code indicating the nature of the error
- S: Terminates HiRDB abnormally.
- Action
- Take action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action |
---|
0000000001 | Error in the definition environment of the status server process | Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB. |
0000000003 | Error in the definition of the status server process | Revise the unit control information definition or server definition, and then restart HiRDB. |
0000000004 | All status files specified in the unit control information definition or server definition are in hold status. | Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB. |
0000000005 0000000006 | Memory shortage | Take action as indicated in the message output before this message. Determine the cause of and take measures against memory shortage. Revise the operating system parameters (maximum number of processes, maximum memory allocation per process, etc.), and then restart HiRDB. |
0000000007 0000000008 | Status file error | Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB. |
0000000009 | Swapping error |
0000000010 | An error occurred in the status file. Because stop was specified in the pd_syssts_initial_error operand or the pd_sts_initial_error operand, HiRDB start processing was terminated. | Take action as indicated in the message output before this message. Eliminate the cause of the error and restart HiRDB. If HiRDB terminates with this error code again after restarting, consider that during HiRDB startup there may be a status file in which an error occurred. For the procedure on starting HiRDB with a status file in which an error occurred, see the HiRDB Version 9 System Operation Guide. |
0000000011 0000000012 0000000013 0000000014 | Internal processing error | If an error message was output before this message, take action as indicated in that message. If no error message was output before this message, contact the customer support center. |
0000000015 | The current file name indicated by HiRDB does not match the file name indicated in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand). | See the section on the procedure for starting HiRDB with a status file for which an error occurred in the HiRDB Version 9 System Operation Guide. Determine whether the file name of the previous operation is specified in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand). If the file name of the previous operation is not specified, specify the file name of the previous operation in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand), and start HiRDB. If this reason code is output even though the current file name used during the previous session was specified, an error occurred in the current file name used during the previous session. Follow the procedure when HiRDB (unit) cannot be restarted because an error occurred in the current file on both systems in the HiRDB Version 9 System Operation Guide, and then start HiRDB. |
0000000016 | If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was not specified, the file name of the previous operation could not be indicated, and HiRDB startup processing was interrupted. If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was specified, there is no spare file, and HiRDB startup processing was interrupted. | If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was not specified, see the section on the procedure for starting HiRDB when an error occurred in the status file in the manual HiRDB Version 9 System Operation Guide. Specify the file name of the previous operation in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand), and start HiRDB. If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was specified, prepare a spare file, and then start HiRDB. |
0000000017 | The normal system of the current file indicated by HiRDB does not match the system specified in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand). | See the section on the procedure for starting HiRDB when an error occurred in the status file in the HiRDB Version 9 System Operation Guide. Confirm that the normal system of the file indicated in the previous operation was specified in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand). If the normal system was not specified, specify the normal system in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand), and then start HiRDB. If this reason code was output even though the normal system was specified, an error occurred in the file name specified in the previous operation. Follow the procedure when HiRDB (unit) cannot be restarted because an error occurred in the current file on both systems in the HiRDB Version 9 System Operation Guide, and start HiRDB. |
0000000018 | Because the normal system of the current file of the previous operation cannot be determined, HiRDB start processing was terminated. | See the section on the procedure for starting HiRDB when an error occurred in the status file in the manual HiRDB Version 9 System Operation Guide. Specify the normal system of the current file in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand), and then start HiRDB. |
0000000102 | There is no inheritance information from the application site. | Consider the following causes: (1) During preparation for log application, the secondary status file was not created as per the procedure (2) The current secondary status file was deleted If (1), determine whether there is an error in the preparation for log application procedure, and then re-execute the preparation for log application. If (2), preparation for log application is required to start the log application site HiRDB. Perform preparation for log application, and then restart HiRDB. For details about preparation for log application, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. |
KFPS01006-E E+L
aa....aa statement in status service definition is invalid. reason code=bb....bb
- There is a specification error in the unit control information definition or the server definition aa....aa operand. An error occurred during analysis of the unit control information definition or the server definition.
- aa....aa: Name of the operand specified in the unit control information definition or the server definition
- bb....bb: Reason code indicating the nature of the error (table below lists the reason codes and actions to be taken)
- S: Continues processing.
- O: Correct the unit control information definition or the server definition.
- Action
- Determine the cause from the following reason codes, and correct the unit control information definition or server definition.
Reason code | Explanation | Action |
---|
0000000001 | Duplicated information was specified in the definition. | Revise the unit control information definition or the server definition, and then restart HiRDB. |
0000000002 | A definition statement is missing or is invalid. |
0000000003 | Invalid value was specified in the definition. |
0000000004 | The number of characters specified in the definition is invalid. |
0000000005 | The file name specified in the definition was not found. |
0000000006 | Combination of definition statements is invalid. |
0000000101 | The logical file name of the secondary status file does not match the logical file name of the corresponding primary status file. |
0000000102 | There is no definition for the secondary status file that corresponds to the primary status file. |
0000000103 | There is no definition for the primary status file that corresponds to the secondary status file. |
KFPS01008-I E+L
aa....aa file unable to be used as standby status file due to bb....bb
- Indicated file cannot be used as a reserve status file.
- aa....aa: Path name of the status file or name of the status file
- If the path name of the status file exceeds 152 characters, the last 152 characters of the status file path name are output.
- bb....bb: Reason code indicating the nature of the error
- S: Terminates processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
0000000001 | Record length does not match that of the current file. | Use the same record length as the current file. |
0000000002 | The numbers of records in file versions A and B do not match. | Match the numbers of records in file versions A and B. |
0000000003 | Record lengths of file versions A and B do not match. | Match the record lengths of file versions A and B. |
KFPS01009-E E+L
File consistency error occurred in physical status file aa....aa
- A file inconsistency error occurred in a status file.
- aa....aa: Path name of the status file
- If the path name of the status file exceeds 161 characters, the last 161 characters of the status file path name are output.
- S:
- Reserve status file available:
Swaps the files.
- Reserve status file not available:
Cancels startup processing and places the erroneous file on shutdown status.
- O: Check the previous session for any online shutdown or file system error and the status file for any allocation error. Correct the status file error and either provide a status file or restart HiRDB.
KFPS01010-E E+L
Error occurred in last updated status file aa....aa. reason code=bb....bb
- An error occurred in the status file containing the most recent file.
- aa....aa: Path name of the status file
- If the path name of the status file exceeds 144 characters, the last 144 characters of the status file path name are output.
- bb....bb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S:
- 0000000006 set as the reason code:
Recovers the file error and resumes processing.
- Other than 0000000006 set as the reason code:
If a reserve status file is available, swaps the files; otherwise, cancels startup processing and places the erroneous file on shutdown status.
- Error occurred in both file versions A and B:
Cancels startup processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
0000000001 | The numbers of records or record lengths of file versions A and B do not match. | Use the same number of records or the same record length as the normal file version and initialize the file with the pdstsinit command. |
0000000002 | The numbers of records or record lengths of file versions A and B do not match, and a data error was detected. | Match the numbers of records or record lengths of file versions A and B and initialize them with the pdstsinit command. |
0000000003 | Record update numbers do not match in file versions A and B. | Initialize file version B with the pdstsinit command. |
0000000004 | Record update error was detected in both file versions A and B. | Initialize both file versions A and B with the pdstsinit command. |
0000000005 | Record input error was detected. | Take action appropriate to the KFPS01040-E message that was output before. |
0000000006 | Incomplete file update status was detected. | No action is necessary. However, if both file versions A and B resulted in an error, initialize the erroneous files with the pdstsinit command. |
KFPS01011-I L+S
HiRDB system selected aa....aa as last updated status file
- Of the open files, status file aa....aa holds the most recent information. If continue or excontinue was specified in the pd_syssts_initial_error operand or the pd_sts_initial_error operand, and the current file of the previous session could not be determined, the name of the file from among the open status files that holds the most recent information is shown in aa....aa.
The name of the file output in aa....aa is not restricted to the current file of the previous session. For details on conditions where the current file of the previous session cannot be determined, see the explanation of the pd_syssts_initial_error operand or the pd_sts_initial_error operand in the manual HiRDB Version 9 System Definition. - aa....aa: Name of the status file
- S: Resumes processing.
KFPS01012-I L+S
Error occurred in last updated status file b on aa....aa system
- An error occurred in the one-way system of the status file aa....aa that holds the most recent information.
- aa....aa: Name of the current status file
- b: System where the error occurred {A | B}
- S: Continues processing.
KFPS01040-E E+L
aa....aa error occurred in physical status file bb....bb. reason code=cc....cc
- Error aa....aa occurred in status file bb....bb. HiRDB processing after this message is output differs depending on HiRDB startup or command execution.
- While HiRDB is running
If it is before the current file was allocated (before the KFPS01001-I message was output): Error shutdown is performed on the file where the error occurred.
If it is after the current file was allocated (after the KFPS01001-I message was output): Error shutdown is performed on the file where the error occurred, after which, if the status file where the error occurred is the current file, the file is swapped.
- During command execution
Continues processing.
- aa....aa: Nature of the error:
- close: File Close
- create: File creation
- delete: File deletion
- filecheck: File validity checking
- fstat: File status report
- logical: Inconsistent record
- open: File Open
- read: Record input
- write: Record output
- bb....bb: Path name of the status file
- If the path name of the status file exceeds 144 characters, the last 144 characters of the path name are output.
- cc....cc: Reason code indicating the nature of the error
- S: If a reserve status file is available, swaps files; otherwise, places the erroneous file on shutdown status and resumes processing.
- Action
- Determine the cause from the following reason codes, and take the appropriate action.
Reason code | Explanation | Action |
---|
0000000001 | Invalid status file record occurred. | Initialize the applicable status file with the pdstsinit command. |
0000000002 | Contact the customer support center. |
0000000003 | Status file update incomplete. | Initialize the applicable status file with the pdstsinit command. |
0000000004 | HiRDB file system error occurred. | Contact the customer support center. |
0000000005 | Invalid status file management area occurred. | Initialize the applicable status file with the pdstsinit command. |
0000000006 | The applicable file is not defined as a status file. | Check that the path name of status file bb....bb is correct. Correct the unit control information definition or the server definition. |
0000000007 | Erroneous file has not been initialized. | Delete the applicable status file with the pdstsrm command, and initialize it with the pdstsinit command. |
0000000008 | Invalid status file initialization occurred. | Initialize the applicable status file with the pdstsinit command. |
0000000009 | Invalid status file management area occurred. |
0000000010 |
0000000011 |
0000000020 | No access privilege for a character special file | Revise the access privilege to the HiRDB file system area that stores the status file. |
0000000021 | No access privilege for a file. | Revise the status file access privilege. |
0000000022 | Lock error (in use by another process) occurred. | The pdstsrm, pdstsinit, or pdcat -d sts -e command may have been executed for the open status file. Execute the pdls -d sts command, and check that the specified file is open. If it is open, take the following actions:
- For the pdstsrm or the pdstsinit command, close the status file using the pdstscls command and then re-execute the command.
- For the pdcat -d sts -e command, use the pdstscls command to close the status file. Or, omit the -e option and re-execute the command.
|
0000000023 | System resource (file lock) shortage occurred. | If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.). |
0000000024 | No write privilege for file | Revise the access privilege to the status file. If Real Time SAN Replication is used, it is possible that the pair volume that stores the status file is an S-VOL. See the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and determine whether there is an error in the HiRDB startup procedure. |
0000000025 | System resource (file descriptor) shortage occurred. | If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.). |
0000000026 | Not initialized as a HiRDB file system area. | Check that the path name of status file bb....bb is correct. Use the pdfmkfs command to initialize as a HiRDB file system area. |
0000000027 | I/O error occurred. | Check if a disk error or operating system error occurred, and take appropriate action. Check that the disk where the status file was allocated is enabled. If the disk is not enabled, enable it. If an attempt was made to start individual units in a multiple-unit HiRDB/Parallel Server configuration that uses Real Time SAN Replication with the log-only synchronous method, it is possible that the combination of the use of the pdstart command -l option, the site status, and the disk settings is inappropriate. Use a correct combination of the pdstart command -l option, site status, and disk settings. For details about appropriate combinations, see the section on pdstart command notes in the manual HiRDB Version 9 Command Reference. |
0000000028 | Memory shortage occurred. | Revise the operating system parameters (maximum number of processes, maximum memory allocated per process, etc.). |
0000000029 | File not found | Check that the path name of status file bb....bb is correct. Or, revise the unit control information definition or server definition. |
0000000030 | In UNIX, the number of character special files that can be opened has been exceeded. In Windows, the number of files that can be opened has been exceeded. | If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.). |
0000000031 | Invalid file name. | Consider the following causes:
- An illegal character was used in the path name.
- The path name length exceeded the limit (167 characters).
- The HiRDB file name length exceeded the limit (30 characters).
Check the status file name specified in the command argument, or re-evaluate the unit control information definition or the server definition. |
0000000032 | Internal processing error occurred. | Contact the customer support center. |
0000000033 |
0000000034 |
0000000035 |
0000000036 |
0000000037 | Specified path is not a HiRDB file system area. | If an error message was output immediately before this, take the action indicated in the message. Check that the path name of status file bb....bb is correct. Initialize the applicable status file using the pdfmkfs command. |
0000000038 | There is a shortage of area in the HiRDB file system area. | Increase the area of the HiRDB file system area, and re-initialize using the pdfmkfs command. Allocate the status file to another HiRDB file system area. |
0000000039 | The system version of the HiRDB file does not match. | If an error message was output immediately before this, take the action indicated in the message. The HiRDB file system area that contains bb....bb cannot be used. Either specify another HiRDB file system area or use the pdfmkfs command to re-initialize the HiRDB file system area. |
0000000040 | Internal processing error occurred. | Contact the customer support center. |
0000000041 |
0000000042 |
0000000043 | Attempt was made to create a status file in a HiRDB file system area that is not for system files. | Check the HiRDB file system area name, use the pdfstatfs command to check the purpose of use of the HiRDB file system area, and create a status file in a HiRDB file system area for use with system files. |
0000000051 | The possible causes are:
- Attempt was made to open a status file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.
- Attempt was made to open a status file created in a HiRDB file system area created by the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.
| Take the following actions:
- Specify Y in the pd_large_file_use operand, or omit the specification.
- Delete status file bb....bb with the pdstsrm command, and then initialize the settings with the pdstsinit command.
|
KFPS01041-I E+L
Physical status file with error is closed and status service is placed in shutdown state. remove the closed file with pdstrsrm command and switch over to standby status file with pdstsinit command and pdstsopen command
- The status server process will be placed in shutdown status after closing the erroneous status file. Delete the erroneous file with the pdstsrm command, and provide a reserve status file with the pdstsinit and pdstsopen commands.
- S: Resumes processing.
- O: Delete the erroneous file with the pdstsrm command. Initialize a file with the pdstsinit command and switch to a reserve status file with the pdstsopen command.
KFPS01042-E E+L
Logical status file aa....aa is short of capacity
- An area shortage error occurred in the status file.
- aa....aa: Name of the status file
- S: If a reserve status file is available, swaps files; otherwise, cancels swapping.
- Action
- Check the size of the status file.
KFPS01043-I E+L
Fragmentation occurred in logical status file aa....aa
- Fragmentation occurred in the status file.
- aa....aa: Name of the status file
- S: If a reserve status file is available, swaps files; otherwise, cancels swapping.
KFPS01044-I L+S
Current logical status file aa....aa is placed in the one-system operation state. The normal system is b. Take appropriate action immediately.
- Current status file aa....aa was placed in single operation mode. The normal system is displayed. Take appropriate action immediately.
- aa....aa: Name of current status file
- b: Normal file version { A | B }
- S: Continues processing.
- Action
- Take either of the following actions:
- Prepare a reserve file, and use the pdstsswap command to swap the status file.
- Determine the cause of the error and take action, use the pdstsinit command to initialize the system where the error occurred to the current file, and then open using the pdstsopen command.
- If you are starting HiRDB when using the status file in single-operation mode, the information displayed in this message must be specified in the following operands:
- pd_syssts_last_active_file (if a log application site, pd_syssts_last_active_subfile)
- pd_syssts_last_active_side (if a log application site, pd_syssts_last_active_side_sub)
- pd_sts_last_active_file (if a log application site, pd_sts_last_active_subfile)
- pd_sts_last_active_side (if a log application site, pd_sts_last_active_side_sub)
KFPS01050-E E
Inter-process communication error occurred
- An inter-process communication error occurred.
An inter-process communication error occurred while processing a service request to the status server process. Another possibility is that an RPC error occurred while the status server process was active. - S: Cancels processing.
- O: Check the HiRDB operating environment, eliminate the cause of the error, and then reissue the service request to the status server process.
KFPS01051-I E+L
Physical status file with error is closed and status service is placed in shutdown state
- The status server process will be placed in shutdown status after closing the erroneous physical status file.
- S: Initialize the erroneous file with the pdstsinit command, and switch to a reserve status file with the pdstsopen command.
KFPS01060-I L+S
Status file aa....aa open
- Status file aa....aa has been opened (the system has completed opening of the status file).
- aa....aa: Path name of the status file or name of the status file
- S: Resumes processing.
KFPS01061-I L+S
Status file aa....aa closed
- Status file aa....aa has been closed (the system has completed closing of the status file).
- aa....aa: Path name of the status file or name of the status file
- S: Resumes processing.
KFPS01062-I L+S
Status file swapping started. reason=aaaaaaaa
- Status file swapping has started.
- aaaaaaaa: Reason for swapping:
- COMMAND: Swap command (pdstsswap) was entered
- ONLINE: Access error occurred in the current file in the online mode
- START: Error occurred in the current file while starting or restarting the status server process (access error, logical error between file versions A and B)
- S: Resumes processing.
KFPS01063-I L+S
Status file swapping completed. current logical status file: aa....aa
- Status file swapping has been completed.
- aa....aa: Name of the current status file
- S: Resumes processing.
- Action
- If you are starting HiRDB when an error occurred in the status file, the information displayed in this message must be specified in the following operands:
- pd_syssts_last_active_file (if a log application site, pd_syssts_last_active_subfile)
- pd_sts_last_active_file (if a log application site, pd_sts_last_active_subfile)
KFPS01064-E E+L
Error occurred during status file swapping. reason code=aa....aa
- Status file swapping resulted in an error.
- aa....aa: Reason code (the table below lists the reason codes and actions to be taken)
- S: Cancels swapping.
- O: Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
0000000001 | No available reserve status file | Prepare a reserve status file. |
0000000002 0000000003 | Allocation of the process private area failed. | Take the action indicated in the error message that was output immediately before this. |
0000000004 | No reserve status file exists for the swap target. A status file other than the current file is in hold or reserve status. Or, there is an area shortage. | Prepare a reserve status file. If this reason code is output even when there is a reserve status file, there is an area shortage in the reserve status file. Revise the estimate of the status file area to prepare a larger reserve status file. Once the larger status file has been made the current status file, increase the size of the remaining status files. |
0000000005 | Error occurred in the current status file. | If an error message was output immediately before this message, take the action indicated in the message. If no message was output, contact the customer support center. |
0000000006 | Internal processing error occurred. | Contact the customer support center. |
0000000007 | If an error message was output immediately before this message, take the action indicated in the message. If no message was output, contact the customer support center. |
0000000008 0000000009 | Contact the customer support center. |
KFPS01070-E E+L
Error occurred during aa....aa command processing. reason code=bb....bb
- An error occurred while processing command aa....aa (error occurred while processing a status service function command).
- aa....aa: Command name
- bb....bb: Reason code (the table below lists the reason codes and actions to be taken)
- S: Terminates command processing.
- O: Check the error message output before, correct the error, the reenter the command.
Reason code | Explanation | Action |
---|
0000000001 | Invalid information in status file management record (STR) | If an error message has been output before this message, take action appropriate to that message. Or, check the arguments specified in the command. If the cause of the error cannot be identified, retain the file and contact the HiRDB administrator. |
0000000002 | Invalid information in status file management record (SHR) |
0000000003 | Record length differs from that of the current file, or the sizes of file versions A and B are different | Check the record length or the number of records in the status file with the pdls command specifying the -d sts option. Or, initialize the file with the pdstsinit command. |
0000000004 | File status does not allow command entry | Check the file status with the pdls command specifying the -d sts option. Correct the file status and re-execute the command. |
0000000005 | Basic file system error | If an error message has been output before this message or a message has been output from the status server process, take action appropriate to that message. |
0000000006 | Specified file name is undefined in the unit control information definition or server definition | Check the arguments specified in the command. |
0000000007 | Inter-process communication error | If an error message has been output before this message, take action appropriate to that message. Correct the error and re-execute the command. |
0000000008 | No reserve status file exists. | Provide a reserve status file. |
0000000009 | Swapping error | Provide a status file and restart HiRDB. |
0000000010 | System call error | Correct the error and re-execute the command. |
0000000011 | Status file is being used (OPEN) by another status server process or is being processed by another status service function command. | Check the system definition and server definition for a duplicate physical file name. Alternatively, close the status file that is being used by the other status server process, or wait until the status service function or command has terminated. |
0000000012 | System definition analysis error | Re-evaluate the system definition. |
0000000013 | Inter-process communication initialization error | Correct the error and re-execute the command. |
0000000014 | No commands are being accepted | Re-execute the command while HiRDB is active. |
0000000015 | Invalid data length in RPC text | Contact the customer support center. |
0000000016 | Current file was specified | Check the file status and the arguments specified in the command with the pdls command specifying the -d sts option. Or, swap status files and re-execute the command. |
0000000017 | Status of a specified file has already been changed | Check the file status with the pdls command specifying the -d sts option. |
0000000018 | Error was detected during file checking | Initialize the erroneous file with the pdstsinit command. |
KFPS01081-I E+S
Usage: pdstsinit [-x host_name |-u unit_id] -f full_path_name[-l record_length] [-c record_number] pdstsinit -s server_name -f full_path_name [-l record_length] [-c record_number]
- Displays the format of the pdstsinit command for a HiRDB/Single Server. This message is output when the command format is invalid.
- Usage
- pdstsinit -f file-name[-l record-length] [-c record-count]
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01081-I E+S
Usage: pdstsinit {-x host_name | -u unit_id} -f full_path_name [-l record_length] [-c record_number] [-D]
pdstsinit -s server_name [-x host_name | -u unit_id] -f full_path_name [-l record_length] [-c record_number] [-D]
- Displays the format of the pdstsinit command for a HiRDB/Parallel Server. This message is output when the command format is invalid.
- Usage
- pdstsinit -f file-name [-l record-length] [-c record-count] [-D]
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01082-I E+S
Usage: pdstrsrm [-x host_name |-u unit_id] -f full_path_name
pdstrsrm -s server_name [-x host_name|-u unit_id] -f full_path_name
- Displays the format of the pdstsrm command for a HiRDB/Single Server. This message is output when the command format is invalid.
- Usage
- pdstsrm -f file-name
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01082-I E+S
Usage: pdstsrm {-x host_name | -u unit_id} -f full_path_name [-D]
pdstsrm -s server_name -f full_path_name [-D]
- Displays the format of the pdstsrm command for a HiRDB/Parallel Server. This message is output when the command format is invalid.
- Usage
- pdstsrm -f file-name [-D]
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01083-I E+S
Usage: pdstsopen [-x host_name |-u unit_id] {-f full_path_name |-n logical_file_name}
pdstsopen -s server_name {-f full_path_name |-n logical_file_name}
- Displays the format of the pdstsopen command for a HiRDB/Single Server. This message is output when the command format is invalid.
- Usage
- pdstsopen { -f file-name |-n logical-file-name }
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01083-I E+S
Usage: pdstsopen {-x host_name |-u unit_id} {-f full_path_name |-n logical_file_name}
pdstsopen -s server_name {-f full_path_name| -n logical_file_name}
- Displays the format of the pdstsopen command for a HiRDB/Parallel Server. This message is output when the command format is invalid.
- Usage
- pdstsopen { -f file-name |-n logical-file-name }
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01084-I E+S
Usage: pdstscls [-x host_name |-u unit_id] {-f full_path_name |-n logical_file_name}
pdstscls -s server_name {-f full_path_name |-n logical_file_name}
- Displays the format of the pdstscls command for a HiRDB/Single Server. This message is output when the command format is invalid.
- Usage
- pdstscls { -f file-name |-n logical-file-name }
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01084-I E+S
Usage: pdstscls {-x host_name |-u unit_id} {-f full_path_name |-n logical_file_name}
pdstscls -s server_name {-f full_path_name |-n logical_file_name}
- Displays the format of the pdstscls command for a HiRDB/Parallel Server. This message is output when the command format is invalid.
- Usage
- pdstscls { -f file-name |-n logical-file-name }
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01086-I E
Usage: pdstsswap [-x host_name |-u unit_id]
pdstsswap -s server_name
- Displays the format of the pdstsswap command for a HiRDB/Single Server. This message is output when the command format is invalid.
- Usage
- pdstsswap
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01086-I E
Usage: pdstsswap {-x host_name |-u unit_id}
pdstsswap -s server_name
- Displays the format of the pdstsswap command for a HiRDB/Parallel Server. This message is output when the command format is invalid.
- Usage
- pdstsswap
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS01090-E E+L
Error occurred in system call aa....aa [error code=bb....bb] function with error: cc....cc
- System call aa....aa resulted in an error.
- aa....aa: Name of the system call resulting in the error
- bb....bb: Return value of the system call
- cc....cc: Name of the function that issued the system call
- S: Either resumes processing or terminates HiRDB abnormally, depending on the nature of the error.
- Action
- Contact the customer support center.
KFPS01091-E E+L
Insufficient memory. required memory size=aa....aa bytes, area type: bb....bb
- A memory shortage occurred in the status server process.
- aa....aa: Size (in bytes) of the area to be allocated
- bb....bb: Type of area in which the memory shortage occurred:
- PROCESS: Process private area
- STATIC SHMPOOL: Static shared memory
- S: Either resumes processing or terminates HiRDB abnormally, depending on the error.
- Action
- Take action appropriate to the area type in which the memory shortage occurred:
- Static shared memory:
- If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, contact the customer support center.
- Process private area:
- Check the usage of the process private area, take appropriate action, and then re-execute the function.
- If the error recurs, contact the customer support center.
KFPS01099-E E+L
Error occurred with aa....aa function. error code=bb....bb function: cc....cc
- Function aa....aa (an HiRDB function) resulted in an error.
- aa....aa: Name of the HiRDB function resulting in the error
- bb....bb: Internal return value of the HiRDB function
- cc....cc: Name of the function that issued the HiRDB function
- S: Either resumes processing or terminates HiRDB abnormally, depending on the nature of the error.
- Action
- Check the message output before or after this message to find the cause of the error, eliminate the error, and then re-execute. If no message was output before or after this message, see 4.1 Detail codes for RPC-related errors and 4.2 Detail codes for system-related errors. If the codes are the same as the HiRDB function internal return values, take the action appropriate for the codes. In UNIX, if HiRDB terminates abnormally, collect thecore file.
KFPS01103-E E+L
Unable to start log service. reason code=aaaa
- The log server process cannot be started.
An error occurred while starting or restarting the log server process. - aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Abnormally terminates HiRDB.
- Action
- Check the reason code to determine why the log server process cannot be started or restarted, take appropriate action, and then restart HiRDB.
Reason code | Explanation | Action | Remarks |
---|
101 | Memory shortage occurred. | Re-evaluate the memory usage. | -- |
103 | Network error occurred. | Correct the error and restart the system. |
405 | Error was detected during definition analysis. | Check the definition file, correct the specification, and restart the system. | Error details are provided in a KFPU002XX message. |
501 | The number of HiRDB servers exceeded the maximum. | Correct the defined information and restart the system. | -- |
502 | The information required to recover the system was not found in the status file. | Re-evaluate the operand related to the status file for the server in each server definition. Possible causes:
- The status file name specified in the pd_sts_file_name_1-7 (if a log application site, pd_sts_subfile_name_1-7) operand has been changed
- The status file specified in the pd_sts_file_name_1-7 (if a log application site, pd_sts_subfile_name_1-7) operand has been initialized
- The logical file name specified in the pd_sts_last_active_file and pd_sts_last_active_side (if a log application site, pd_sts_last_active_subfile and pd_sts_last_active_side_sub) operands or the status file that was current in the previous system operation are different
|
503 | Error occurred during status file I/O processing. | Check the cause of the error, correct the error, and restart the system. | -- |
504 | Error occurred while activating the log server process. | Check the cause of the error, correct the error, and restart HiRDB. |
508 | Error occurred while activating the log s process. |
512 | Error occurred while analyzing the log swapper process-related definitions. |
514 | Error occurred while activating the log swapper process. | Check the cause of the error, correct the error, and restart HiRDB. | Details of the cause of the error are displayed before this message. |
515 | Error occurred while analyzing the log swapper process definitions. | Correct the definition according to the message that was output before this message and restart HiRDB. | -- |
516 | Activation of an internal thread failed in the log server process. | Check the cause of the error, correct the error, and restart HiRDB. | Details of the cause of the error are displayed before this message. |
541 | Error occurred while activating the status server process. | Correct the error on the basis of the message that was output before this message and restart the system. | -- |
- --: Not applicable
KFPS01104-W L
Unable to recover previous log service conditions referring to status file; continues restart processing without status file. reason code=aaaa
- The status of the previous log server process could not be restored from the status file. The system resumes restart processing without the status file.
- aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action | Remarks |
---|
502 | Previous online status was not found in the status file | For a log application site, if a failure occurred during startup, perform preparation for system log application, and then restart. If other than the above, no action is required in response to this message. | Possible reason is:
- Error occurred while writing the status during the previous session
- For a log application site, all secondary status files have been initialized
|
503 | Error occurred during status record I/O processing. | If restart fails, take action appropriate to the status server process message (KFPS010xx) that was output before this message. | -- |
- --: Not applicable
KFPS01108-W L
Error occurred while terminating log service; continues processing. reason code=aaaa
- An error occurred while terminating the log server process, but processing continues.
- aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- Action
- Refer to the reason code in order to check the cause of the error and take appropriate action, if necessary.
Reason code | Explanation | Action |
---|
101 | Memory shortage occurred. | Check the memory size before the next startup. |
103 | Network error occurred. | Correct the network error before the next startup. |
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup. |
KFPS01109-W E+L
Minor error occurred while analyzing definitions for log service. file being analyzed aa....aa, record number=bb....bb, reason code=cc....cc
- A minor error occurred while analyzing the log server process-related definitions.
- aa....aa: Name of definition file being analyzed
- bb....bb: Record number resulting in the error
- cc....cc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Ignores the definition statement containing the erroneous pdlogadfg or pdlogadpf operand and starts or restarts the log server process (assumes that the definition statement has not been specified).
- Action
- Re-evaluate the log server process-related definitions.
Reason code | Explanation | Action | Remarks |
---|
408 | The pdlogadfg operand is invalid:
- -g option is not specified.
- Specified file group name is duplicated.
| If necessary, terminate the system, correct the definition, then restart. | -- |
409 | -g option is invalid in the pdlogadpf operand:
- -g option is not specified.
- File group specified in the -g option is undefined in the pdlogadfg operand specified in the previous row
| If necessary, stop the system, check the following items, and correct the pdlogadpf operand. Then, restart the system.
- Is the g option specified?
- Is the file group name specified in the -g option correct?
- Is the file group specified in the -g option defined in the pdlogadfg operand specified in the previous row?
|
411 | -a option is invalid in the pdlogadpf operand:
- -a option is not specified.
- Length of path specified in the -a option exceeds the character maximum.
- Length of the HiRDB file system area name specified in the -a option exceeds the limit (117 characters).
- Length of HiRDB file name specified in the -a option exceeds the maximum (30 characters).
- HiRDB file name specified in the -a option duplicates another HiRDB file name.
| If necessary, terminate the system, correct the definition, then restart. |
412 | -b option is invalid in the pdlogadpf operand:
- -b option is not specified (applicable when dual log is used).
- Length of path specified in the -b option exceeds the character maximum.
- Length of the HiRDB file system area name specified in the -b option exceeds the limit (117 characters).
- Length of HiRDB file name specified in the -b option exceeds the maximum (30 characters).
- HiRDB file name specified in the -b option duplicates another HiRDB file name.
| Applicable when dual log is used. |
413 | The number of pdlogadfg operands exceeds the maximum. | An erroneous pdlogadfg operand is not included in the operands count. |
415 | More than one pdlogadpf operand with the same file group name was specified. | -- |
422 | -d option is invalid in the pdlogadfg operand or is not specified. |
423 | -d option is invalid in the pdlogadpf operand or is not specified. |
- --: Not applicable
KFPS01113-E E+L
Unable to start aaaa(xx....xx) log file service. reason code=bbbb
- The aaaa(xx....xx) log server process cannot be started.
An error occurred while starting or restarting the log server process. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Cancels unit startup processing.
- Action
- Take action appropriate to the reason code, as listed below, then restart HiRDB:
Reason code | Explanation | Action | Remarks |
---|
101 | Memory shortage occurred. | Check the memory size in use. | -- |
103 | Network error occurred. | Correct the error and restart the system. |
114 | Required information was not found in the message queue identifier table in the system. | Reconfigure the kernel, changing the value of message-related msgmni parameter. |
117 | Because the value specified for the operand changed, an attempt was made to allocate more memory than the size of the shared memory that was allocated at system startup. | For the formula for calculating the log server, see the section on formulas for calculating shared memory used by unit controllers in the manual HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the log server shared memory less than 2 GB. For HiRDB/Parallel Server, calculate using 1 as the value for number-of-servers-in-unit+D and number-of-FES-in-unit. | -- |
405 | Error was detected during definition analysis. | Check the definition file, correct the error, then restart the system. | Error details are provided in a KFPU002XX message. |
414 | The number of valid log file group definitions is less than the minimum number of generations required for system startup. | Correct the pdlogadfg operand in the applicable HiRDB server definition and restart the system. | A valid definition means a correct pdlogadfg operand with ONL specified. |
416 | The file group names specified in the -g option of the pdlogadfg operand include file groups not defined in the pdlogadpf operand; or file groups are defined in the pdlogadpf operand before the pdlogadfg operand. | Check the following items, and correct the pdlogadfg operand and pdlogadpf operand of the corresponding HiRDB server definition. Then, restart the system.
- Is the file group name specified in the -g option correct?
- Is the pdlogadpf operand defined after the pdlogadfg operand definition?
| -- |
503 | Error occurred during status file I/O processing. | Check the cause of the error, correct the error, then restart the system. |
504 | Error occurred while activating the log swapper process. |
508 | Error occurred during startup of the log swapper process. | Details of the error have been displayed before this message. |
510 | Error was detected during log file checking. |
- --: Not applicable
KFPS01114-W E+L
Error occurred while terminating aaaa(xx....xx) log file service;continues processing. reason code=bbbb
- An error occurred while terminating the aaaa(xx....xx) log server process, but processing continues.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- Note
- Even though this message was output, the log server process will start normally the next time.
- S: Resumes termination processing.
- Action
- Take action appropriate to the reason code as listed below, if necessary:
Reason code | Explanation | Action | Remarks |
---|
101 | Memory shortage occurred. | Check the memory size before the next startup. | -- |
103 | Network error occurred. | Recover the network environment before the next startup. |
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup. |
511 | Error occurred during log file termination processing. | Check the cause of the error and take appropriate action before the next startup. | Details of the error have been displayed before this message. |
- --: Not applicable
KFPS01115-E E+L
Unable to start I/O service of aaaa(xx....xx) log file. reason code=bbbb
- aaaa(xx....xx) log swapper process cannot be started.
- aaaa: Type of log file
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Terminates HiRDB.
- Action
- Take action appropriate to the reason code, as listed below, then restart HiRDB:
Reason code | Explanation | Action | Remarks |
---|
101 | Memory shortage occurred. | Check the memory size in use. | -- |
103 | Network error occurred. | Correct the error and restart the system. |
405 | Error was detected during definition analysis. | Check the definition file, correct the error, then restart the system. | Error details are provided in a KFPU002XX message. |
503 | Error occurred during status file I/O processing. | Check the cause of the error, correct the error, then restart the system. | -- |
- --: Not applicable
KFPS01116-W L
Error occurred while terminating I/O service of aaaa(xx....xx) log file; continues processing. reason code=bbbb
- An error occurred while terminating the aaaa(xx....xx) log swapper process, but the system resumed processing.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- Note
- Even though this message was output, the log server process will start normally the next time.
- S: Resumes termination processing.
- Action
- Take action appropriate to the reason code, as listed below, if necessary:
Reason code | Explanation | Action |
---|
101 | Memory shortage occurred. | Check the memory size before the next startup. |
103 | Network error occurred. | Recover the network environment before the next startup. |
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup. |
KFPS01121-E L
Insufficient memory. required memory size=aa....aa, area type:bb....bb
- A memory shortage occurred.
- aa....aa: Size of the area that was to be allocated
- bb....bb: Type of the area resulting in the error:
- STATIC_SHMPOOL: Static shared memory
- S: Cancels processing.
- Action
- If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, revise the system definitions, and then retry the operation.
KFPS01125-E L
Unable to use log service server aaaa(xx....xx). reason code=cccc-dd
- Server aaaa(xx....xx) cannot use the log service function.
- aaaa: Server name
- xx....xx: HiRDB internal code
- cccc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- dd: HiRDB internal code
- S: Depends on server message aaaaaaaa that is issued after this message.
- O: Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
101 | Memory shortage occurred. | -- | Take action appropriate to the message output after this message. |
104 | Log server process is not online. | Terminate the system and restart it. | Check the cause of the error to determine why HiRDB has not started normally. |
903 | Server with the same name attempted to use the log service function. | -- | Check the server name or startup mode. |
904 | This server cannot be restarted because the log service function has started normally. | Take action appropriate to the message output after this message. |
905 | Log service cannot be provided to this server due to a status file access error. | Check the cause of the status file access error. |
906 | Log required for server restart is not available due to a log file I/O error or other error. | Check the cause of the log file error as required. |
907 | Attempt was made to start the synchronization point service function, but this service cannot be provided to this server. | Take action appropriate to the message that is output after this message. | Check the HiRDB server definition for an error. |
908 | Synchronization point service definition was defined for a server that does use the synchronization point service function. | -- |
- --: Not applicable
KFPS01128-W L
Unable to specify bb....bb in aa....aa operand, replace bb....bb with cc....cc, server=dd....dd
- bb....bb cannot be specified in the aa....aa operand. bb....bb has been replaced with cc....cc.
- aa....aa: Operand name
- bb....bb: Specified value of the aa....aa operand
- cc....cc: Value replacing the aa....aa operand
- dd....dd: Server name
- S: Continues processing.
- Action
- Referring to the manual HiRDB Version 9 System Definition, re-evaluate the value specified in the aa....aa operand. Pay particular attention to the following points:
- Check if values that cannot be combined are specified.
- Check if values that cannot be changed during startup have been changed.
KFPS01129-E E+L
Definition analysis error. definition name=aa....aa, server name=bb....bb, reason code=cc....cc
- An analysis error occurred on the aa....aa operand in the definition analysis of the server bb....bb.
- aa....aa: Operand name
- bb....bb: HiRDB server name
- cc....cc: Reason code indicating the nature of the error
- 1: The specified value is greater than the operand specification range.
- 2: The specified number of operands is invalid.
- 606: Other than the above
- S: Terminates processing.
- Action
- Referring to the manual HiRDB Version 9 System Definition, re-evaluate the value specified in the aa....aa operand.
KFPS01130-W L
Error occurred while starting aaaa(bb....bb) log service; continues processing. reason code=cccc
- An error occurred while the aaaa(bb....bb) log service facility was being started, but processing continues.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cccc: Reason code indicating the nature of the error:
- 1654: Invalid file for data linkage
- S: If the reason code is 1654, the system continues system startup processing using the same HiRDB Datareplicator extraction-completed or extracting status in the system log file as the last time HiRDB was terminated. Extracting status will not be released even for a log file whose extraction was completed when HiRDB was terminated at the corresponding server.
- O: If the reason code is 1654, check the HiRDB Datareplicator linkage file by entering the pdls -d rpl -j command to determine whether or not the linkage operation can continue. If linkage processing with HiRDB Datareplicator cannot be continued, contact the administrator.
- Action
- If the reason code is 1654 and the HiRDB Datareplicator linkage cannot be performed, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, and redo the data linkage.
KFPS01150-E L
Auto log unload service terminated. server=aa....aa:create dir=bb....bb:reason=cccc
- The automatic log unloading facility was terminated in server aa....aa.
- aa....aa: HiRDB server name
- bb....bb: Unload log file creation directory
- cccc: Reason code indicating the error cause:
- 1660: Unloading of system log files failed in all unload log file creation directories.
- 1661: Creation of log server process failed.
- 1664: The unload log file that was to be created is already being used by another process.
- S: Continues processing.
- Action
- Take corrective action according to the reason code.
- 1660 displayed as the reason code (when an unload log file creation directory is specified in the pd_log_auto_unload_path operand)
The possible causes are listed in the table below. After taking corrective action, resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.
No. | Cause | Action |
---|
1 | A disk space shortage occurred in the unload log file creation directory. | Allocate more free disk space. |
2 | A disk error occurred in the unload log file creation directory. | Correct the disk error. |
- 1660 displayed as the reason code (when a HiRDB file system area is specified in the pd_log_auto_unload_path operand)
The possible causes are listed in the table below. After taking corrective action, resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.
No. | Cause | Action |
---|
1 | A disk space shortage occurred in the HiRDB file system area. | Allocate more free disk space. |
2 | A disk error occurred in the HiRDB file system area. | Correct the disk error. |
3 | One of the following items, which were specified when the HiRDB file system area was created, has reached its maximum value.
- Maximum number of files (value specified in the -l option)
- Maximum number of extensions (value specified in the -e option)
- HiRDB file system area size (value specified in the -n option)
| Increase the value specified for the item that has reached its upper limit#, and then re-create the HiRDB file system area. For appropriate values for each item, see Guidelines for options to be specified in the pdfmkfs command under Using the automatic log unloading facility in the HiRDB Version 9 System Operation Guide. The procedure for re-creating the HiRDB file system area is as follows:
- Use the pdfbkup command to back up the unload log files in the HiRDB file system area.
- Use the pdfmkfs command to re-create the HiRDB file system area. Increase the value specified for the item that has reached its upper limit.
- Use the pdfrstr command to restore the HiRDB file system area. Using the backups from step 1, store the unload log files inside the re-created HiRDB file system area.
|
- #
- Execute the pdfstatfs command to check for items that have reached their upper limit. Check the following items in the execution results of the pdfstatfs command:
- remain file count: Displays the number of HiRDB files that can be created. If 0 is displayed, the maximum number of files (the value specified in the -l option) has been reached.
- available expand count and current expand count: Displays the value specified in the -e option in available expand count, and the total number of extensions in current expand count. When the values in available expand count and current expand count are the same, the maximum number of extensions (the value specified in the -e option) has been reached.
- If neither of the two items above are applicable, the HiRDB file system area size (the value specified in the -n option) has reached its upper limit. Check the amount of unused space in the HiRDB file system area in remain user area capacity in the execution results of the pdfstatfs command.
- 1661 displayed as the reason code
Check the maximum number of processes that can be executed in the server machine and terminate unnecessary processes; also check if sufficient system resources, such as memory space, are available.
- 1664 displayed as the reason code
Check if there is another process that is manipulating a file in the unload log file creation directory. Then resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.
- In all other cases
Obtain the following information and contact the customer support center:
All files under %PDDIR%\spool
HiRDB system definition files
Event log (in UNIX, syslogfile)
Execution results of the pdlogls -d sys command
KFPS01151-I L
aa....aa changed auto log unload directory from bb....bb to cc....cc.reason=dddd
- The unload log file creation directory to be used by server aa....aa was switched from bb....bb to cc....cc.
- aa....aa: HiRDB server name
- bb....bb: Unload log file creation directory before the switch
- If the name of the unload log file creation directory before the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory before the switch is output.
- cc....cc: Unload log file creation directory after the switch
- If the name of the unload log file creation directory after the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory after the switch is output.
- dddd: Reason code:
- 1665: The disk in which the unload log file creation directory is located became full.
- S: Continues processing.
- Action
- Move unload log files in the unload log file creation directory to another area or delete unneeded unload log files.
KFPS01152-W L
No use aa....aa as auto log unload directory. server=bb....bb:reason=cccc
- Directory cannot be switched to the unload log file creation directory (directory name aa....aa) used by server bb....bb. Another directory is being used as the switching destination.
- aa....aa: Name of the unload log file creation directory
- bb....bb: HiRDB server name
- cccc: Detail code (see the list of detail codes in the Action section)
- S: Continues processing.
- Action
- Take the action appropriate to the detail code, as shown below:
Detail code | Meaning | Action |
---|
1661 | A shortage of resources occurred (such as memory space, file descriptors, or lock segments). | Recheck the amount of memory that is required. In UNIX, change the values of the following operating system parameters as necessary:
|
1666 | A permission error occurred. | Grant the write privilege for the unload log file creation directory. |
1667 | An I/O error occurred. | Correct the error on the disk in which the unload log file creation directory is located. If the unload log files necessary for database recovery have been lost, make a backup. |
1668 | An unload log file creation directory or a HiRDB file system area for creation of unload log files does not exist. | Create an unload log file creation directory or a HiRDB file system area for unload log files. |
1669 | Unload log files created during the previous operation remain in the unload log file creation directory. | Move the unload log files to another area or delete unneeded unload log files. |
1670 | The type of the unload log file creation directory or HiRDB file system area for unload log files is invalid. | - Check that the path name of the unload log file creation directory is correct.
- Check that a HiRDB file system area for unload log files has been created for utilities.
|
KFPS01153-I L
Auto log unload service restart. server=aa....aa:create dir=bb....bb:reason=cccc
- The automatic log unloading facility will be restarted in server aa....aa.
- aa....aa: HiRDB server name
- bb....bb: Unload log file creation directory
- cccc: Reason code:
- 1662: The automatic log unloading facility was restarted because the pdlogatul -b command was executed.
- 1682: The automatic log unloading facility was restarted because the system log files were swapped, or because of normal or planned termination of HiRDB.
- S: Continues processing.
KFPS01154-I L
Auto log unload service stopped. server=aa....aa:create dir=bb....bb:reason=cccc
- The automatic log unloading facility was stopped in server aa....aa.
- aa....aa: HiRDB server name
- bb....bb: Unload log file creation directory
- cccc: Reason code:
- 1662: The automatic log unloading facility was stopped because the pdlogatul -t command was executed.
- S: Continues processing.
KFPS01155-W L
aa....aa changed auto log unload directory from bb....bb to cc....cc.reason=dddd
- Because an error occurred in the unload log file creation directory (directory name bb....bb) to be used by server aa....aa, the directory was switched from bb....bb to cc....cc.
- aa....aa: HiRDB server name
- bb....bb: Unload log file creation directory before the switch
- If the name of the unload log file creation directory before the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory before the switch are output.
- cc....cc: Unload log file creation directory after the switch
- If the name of the unload log file creation directory after the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory after the switch are output.
- dddd: Detail code (see the list of detail codes in the Action section)
- S: Continues processing.
- Action
- Take the action appropriate to the detail code, as shown below:
Detail code | Meaning | Action |
---|
1661 | A shortage of resources occurred (such as memory space, file descriptors, or lock segments). | Recheck the amount of memory that is required. In UNIX, change the values of the following operating system parameters as necessary:
|
1666 | A permission error occurred. | Grant the write privilege for the unload log file creation directory. |
1667 | An I/O error occurred. | Correct the error on the disk in which the unload log file creation directory is located. If the unload log files necessary for database recovery have been lost, make a backup. |
1668 | An unload log file creation directory or a HiRDB file system area for creation of unload log files does not exist. | Create an unload log file creation directory or a HiRDB file system area for unload log files. |
1669 | Unload log files created during the previous operation remain in the unload log file creation directory. | Move the unload log files to another area or delete unneeded unload log files. |
1670 | The type of the unload log file creation directory or HiRDB file system area for unload log files is invalid. | - Check that the path name of the unload log file creation directory is correct.
- Check that a HiRDB file system area for unload log files has been created for utilities.
|
KFPS01156-I L
aa....aa wait for auto log unloading.file group=bb....bb:create dir=cc....cc
- Server aa....aa is waiting for automatic log unloading to be completed. System log files of file group bb....bb are being unloaded at this time.
- aa....aa: HiRDB server name
- bb....bb: File group name of the system log files being unloaded currently
- cc....cc: Unload log file creation directory
- S: Continues processing.
KFPS01157-W L
Unable to use auto log unload service. server=aa....aa:reason=bbbb
- The automatic log unloading facility cannot be used in server aa....aa.
- aa....aa: HiRDB server name
- bbbb: Reason code:
- 1662: HiRDB system definition is invalid.
- 1663: Status file information is invalid.
- 1664: For a log application site HiRDB, the automatic log unloading facility cannot be started.
- S: Continues processing.
- Action
- Take one of the following actions:
- Reason code is 1662:
- Check if the value specified in the pd_log_auto_unload_path operand is correct. If it is, restart HiRDB normally and start the automatic log unloading facility.
- Reason code is 1663:
- If this message was preceded by an error message related to the status file, take the action recommended in that message. If there has been no error in the status file, restart HiRDB normally and start the automatic log unloading facility.
- Reason code is 1664:
- For a transaction execution site HiRDB, start the automatic log unloading facility.
- In all other cases:
- Save the following information and contact the customer support center:
- All files under %PDDIR%\spool
- HiRDB system definition files
- Event log (in UNIX, syslogfile)
- Execution results of the pdlogls -d sys command
KFPS01158-W L
Unable to restart auto log unload service. server=aa....aa
- The automatic log unloading facility cannot be restarted on server aa....aa.
- aa....aa: HiRDB server name
- S: Stops trying to restart the automatic log unloading facility, and resumes termination processing of the server.
- Action
- Check the reason code in message KFPS01150-E, which was output to the event log on the system manager unit (syslogfile in UNIX), to determine the cause, and then take corrective action.
- In addition, because the automatic log unloading facility has stopped, the system log file group remains on unload wait status. Execute either of the following commands to set it to unload completed status:
- pdlogunld command
- pdstart command (unloads using the automatic log unloading facility the next time the server is started)
KFPS01160-E L
Insufficient system log space. Transaction service stopped. Transactions terminate by force, server = aa....aa, output file name = bb....bb
- The free space percentage of the system log file became less than the warning value. The target server is aa....aa. The system log file free area monitoring facility suppresses the scheduling of new transactions to the aa....aa server and forcibly terminates all transactions on the server. This facility also outputs the system log file status information file to %PDDIR%\spool\pdjnlinf\bb....bb.
For details about monitoring the free area for system log files, see the HiRDB Version 9 System Operation Guide. - aa....aa: HiRDB server name
- bb....bb: Status information file name of the system log file
- S: Continues processing.
- O: Contact the HiRDB administrator.
- Action
- Take the following actions:
- Check the status of the system log file using the pdlogls command, and then increase the number of system log files created at the swap destination.
- Suppress the issuing of new transactions to the aa....aa server until the KFPS01161-I message is output.
- After taking these actions, eliminate the cause of the free area shortage in the system log file of server aa....aa.
- For details about the actions to be taken by the HiRDB administrator if the free space percentage for the system log files becomes lower than the warning value, see the description of monitoring the free area for system log files in the HiRDB Version 9 System Operation Guide.
- If Real Time SAN Replication is applicable and if a KFPS02178-E message was output before this message, take the action indicated in the KFPS02178-E message.
KFPS01161-I L
System log available space gained. Transaction service restart, server = aa....aa, rest = bb....bb%
- The free percentage of the system log file became greater than the warning value because new areas ready for system log output were acquired. The target server is aa....aa. Cancels scheduling suppression of new transactions by the free space monitoring facility for system log files. For details about monitoring the free area for system log files, see the HiRDB Version 9 System Operation Guide.
- aa....aa: HiRDB server name
- bb....bb: Percentage of remaining system log file space the system log can output.
- This percentage is based on a value of 100% for the entire system log file space.
- S: Continues processing.
- Action
- Take the following actions:
- Cancel the suppression of the issuing of new transactions.
- If no action was taken according to the KFPS01160-E message, take action immediately.
- When bb....bb is low, the cause of the system log file free space shortage was not resolved. If operation continues in this state, the problem of insufficient free space for the system log file may recur. For details about how to recover from insufficient free space, see the description of monitoring free space for system log files in the HiRDB Version 9 System Operation Guide.
KFPS01162-W L
Insufficient system log space, server = aa....aa, output file name = bb....bb
- The free percentage of the system log file became less than the warning value. The target server is aa....aa. The status information file of the system log file is output to %PDDIR%\spool\pdjnlinf\bb....bb.
- aa....aa: HiRDB server name
- bb....bb: Status information file name of the system log file
- S: Continues processing.
- O: Contact the HiRDB administrator.
- Action
- Check the status of the system log file using the pdlogls command and increase the number of status system log files created at the swap destination. For details about the actions to be taken by the HiRDB administrator if the free space percentage for the system log files becomes lower than the warning value, see the description of monitoring the free area for system log files in the HiRDB Version 9 System Operation Guide.
- After taking these actions, eliminate the cause of the free area shortage in the system log file of server aa....aa.
- If Real Time SAN Replication is applicable and if a KFPS02178-E message was output before this message, take the action indicated in the KFPS02178-E message.
KFPS01163-W L
Waiting for transaction completion, server = aa....aa, current transaction count = bb....bb
- The system manager is waiting for completion of the transaction. The target server is aa....aa. Because the RDAREA may perform an error shutdown if the transaction waiting for termination is forcibly terminated, do not forcibly terminate the transaction.
- aa....aa: HiRDB server name
- bb....bb: The number of transactions waiting for termination
- Action
- Suppress the issuing of new transactions to the aa....aa server until the KFPS01161-I message is output. For details about how to determine the transaction for which completion is pending, see the description of monitoring free space for system log files in the HiRDB Version 9 System Operation Guide.
KFPS01170-E L
Unable to read system log file, server=aa....aa, reason=bbbb(cc....cc)
- The update log of the system log file could not be read with discrepancies application of online reorganization.
- aa....aa: HiRDB server name
- bbbb: Reason code (see Action below)
- cc....cc: Detail information (see Action below)
- S: Terminates processing.
- Action
- See the reason code and detail information in the following table, and then take appropriate action. For details about re-executing updatable online reorganization, see the HiRDB Version 9 Staticizer Option Description and User's Guide.
Reason code (bbbb) | Detail information (cc....cc) | Meaning | Action |
---|
101 | Memory size to be allocated | Failed to secure the necessary memory area. | Re-evaluate the system virtual memory capacity. If there is a shortage, expand the virtual memory capacity. If the memory capacity cannot be extended, secure more free virtual memory by stopping other unnecessary resident programs or processes. |
106 | Internal information | Cannot access common memory HiRDB uses. | If this message is output when HiRDB is inactive, restart HiRDB, and then re-execute the pdorend command. If this message is output when HiRDB is active, either the common memory area was deleted or the access privilege is invalid. If a system call error message is output immediately before this message, take action according to that message. If the system call error message is not output, check the following items for problems:
- Is the person executing the updatable online reorganization the HiRDB administrator?
- Is the file in the spool directory in the HiRDB operation directory improperly falsified?
If the problem cannot be determined, contact the customer support center. |
112 | Internal information | Executed updatable online reorganization, but server did not start the unit. | Start the applicable unit. |
711 | Generation number | The generation number is missing from the file group of the system log file in the detail code. | Use the pdlogls -d sys command to check if the file group of the system log file with the applicable generation number exists. If the file group of the system log file does not exist, updatable online reorganization cannot continue because the system log file was overwritten and the required update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command. If the file group of the system log file exists, prepare the following data and contact the customer support center:
- Execution result of the pdls -d org -a command
- Execution result of the pdlogls -d sys command
- Applicable system log file or a backup file of the applicable system log file (except for the unload file)
|
1001 | 701 | Cannot find the file group of the system log file the system log target start point indicates. | Execute the pdls -d org -a command and check the file group name of the system log for the system log target start point. In addition, use the pdlogls -d sys command to check for the file group of the system log file. If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command. |
702 | Cannot open the system log file the system log target start point indicates. | See the KFPS01171-E message just output to determine the cause of the error and take appropriate action. Then, execute the pdorend command and re-execute updatable online reorganization. |
1605 | Generation information of the system log file the system log target start point indicates is invalid. | Execute the pdls -d org -a command and check the generation number and run ID of the file group for the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check if the generation number and run ID match the generation number and run ID of the file group of the system log file. If the generation numbers or run IDs do not match, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command. If the generation numbers and run IDs are the same, prepare the following data and contact the customer support center:
- Execution result of the pdls -d org -a command
- Execution result of the pdlogls -d sys command
- Applicable system log file or a backup file of the applicable system log file (except for the unload log file)
|
1653 | 701 | Cannot find the file group of the system log file the system log target point indicates. | Execute the pdls -d org -a command and check the file group name of the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check for the file group of the system log file. If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command. |
702 | Cannot open the system log file the system log target start point indicates. | See the KFPS01171-E message just output to determine the cause of the error and take appropriate action. Then, execute the pdorend command and re-execute updatable online reorganization. |
1602 | Found missing system log block(s) in the system log file input from the system log target point. | Execute the pdlogls -d sys command and check for the file group of the system log file including the system log block number of the input target for the KFPS01171-E message just output. If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command. |
1605 | Generation information of the system log file the system log target start point indicates is invalid. | Execute the pdls -d org -a command and check the generation number and run ID of the file group for the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check if the generation number and run ID match the generation number and run ID of the file group of the system log file. If the generation numbers or run IDs do not match, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command. If the generation numbers and run IDs are the same, prepare the following data and contact the customer support center:
- Execution result of the pdls -d org -a command
- Execution result of the pdlogls -d sys command
- Applicable system log file or a backup file of the applicable system log file (except for the unload log file)
|
KFPS01171-E L
Error occurred while reading system log file, server=aa....aa, file_group=bb....bb, system A/B=c, reason=dddd(ee....ee)
- An error occurred in the system log file input in updatable online reorganization.
- aa....aa: The HiRDB server name
- bb....bb: File group name of the system log file
- c: System where the error occurred (A or B)
- dddd: Reason code (see Action below)
- ee....ee: Detail information (see Action below)
- S: Continues processing.
- Action
- See the reason code and detail information in the following table, and then take appropriate action.
Reason code (dddd) | Detail information (ee....ee) | Meaning | Action |
---|
213 | Error code of the HiRDB file system | An open error occurred with the system log file | Check for the error cause and fix the error based on 5.1 Error codes returned from HiRDB file system access requests. For detail information other than error codes of the HiRDB file system, contact the customer support center. |
215 | Error code of the HiRDB file system | A read error occurred with the system log file. |
219 1652 | Internal code | Invalid log lock data was detected in the system log file input. | When the system log file is duplexed, processing continues using the system where no errors occurred. When the system log file is not duplexed, or an error occurs on both duplexed systems, updatable online reorganization cannot continue. To re-execute updatable online reorganization, first abort updatable online reorganization using the pdorend -u command, and then re-execute from the pdorbegin command. If this error message is repeatedly output even when re-executing updatable online reorganization, prepare the following data, and then contact the customer support center:
- All directories or files under %PDDIR%\spool
- The HiRDB system definition file
- The execution result of the pdlogls -d sys -e command executed on the server that caused the error
- The backup file created by executing the pdfbkup command on the system log file in the overwriting denied status for online reorganization
- Event log (in UNIX, syslogfile)
|
602 | Internal code | Invalid log record data was found in the system log file input. | When the system log file is duplexed, processing continues using the system where no errors occurred. When the system log file is not duplexed, or an error occurs on both duplexed systems, the systems abnormally terminate because updatable online reorganization cannot continue. To re-execute updatable online reorganization, first abort updatable online reorganization using the pdorend -u command, and then re-execute from the pdorbegin command. If this error message is repeatedly output even when re-executing updatable online reorganization, prepare the following data, and then contact the customer support center:
- All directories or files under %PDDIR%\spool
- The HiRDB system definition file
- The execution result of the pdlogls -d sys -e command executed on the server that caused the error
- The backup file on the server where the error occurred created by executing the pdfbkup command on the system log file in the overwriting denied status for online reorganization
- Event log (in UNIX, syslogfile)
|
1602 | System log number of the input target | Found missing system log block(s) in the system log file input. | Execute the pdlogls -d sys command and check for the file group of the system log file including the system log block number of the input target. If the file group of the system log file including the system log block number of the input target cannot be found, the file group of the applicable system log file may have been overwritten. If this causes updatable online reorganization to discontinue, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message. If there is a file group of the system log file that includes the system log block number of the input target, processing can continue by using the system where the error did not occur, if the system log file is duplexed. However, if the system log file is not duplexed, or if the error occurs on both duplexed systems, updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message. |
1605 | Generation information of the system log file# | Cannot process input of the update log record(s) because the generation information of the system log file does not match. | If the system log file is duplexed, processing can continue using the system where the error did not occur. If the system log file is not duplexed, or if the error occurs on both duplexed systems, there are cases in which updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message. |
1653 | Generation information of the system log file# | The generation information of the system log file does not match the system log target start point, so the information cannot be used in update log record input processing. | If the system log file is duplexed, processing can continue using the system where the error did not occur. If the system log file is not duplexed, or if the error occurs on both duplexed systems, updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately output. See the actions for the KFPS01170-E message. |
- #: Formats:
- AA....AA,BB....BB,CC....CC
- AA....AA: Run ID
- BB....BB: User run ID
- CC....CC: Generation number
KFPS01175-W L
Online DB Reorganization overwrite status in all log file group changed and retrying swap, server=aa....aa, type=bbb
- A system log file in the overwrite denied status for online reorganization was found, but because pd_log_org_no_standby_file_opr=continue was specified in the system definition, all system log files on the server were changed from the overwrite denied status for online reorganization to the overwrite permitted status for online reorganization, and the system log files were swapped.
- aa....aa: HiRDB server name
- bbb: Type of log file:
- sys: System log file
- S: Continues processing.
- Action
- After this message is output, all system log files enter the overwrite permitted status for online reorganization. Therefore, the update information required for discrepancies application of online reorganization is overwritten, and in some cases, updatable online reorganization cannot continue. In such cases, see the KFPS01170-E when it is output.
KFPS01180-E L
Skipped blocks detected while reading log. type: aaaa(xx....xx), previous read point: bb....bb,cc....cc, current read point: dd....dd, ee....ee, read direction: g
- A missing block was detected while reading the log.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the log file group that was read immediately before the missing block was detected
- cc....cc: Log block number that was read immediately before the missing block was detected
- dd....dd: Name of the log file group that has just been read
- ee....ee: Log block number that has just been read
- g: Log block read direction:
- f: Forward
- b: Backward
- Note
- If no log block was read, ********,******** is displayed for bb....bb,cc....cc.
- S: Resumes processing.
- Action
- Refer to the messages listed below to check the cause of the error; if a file error, recover from the error. If the data can be recovered, recover the data and then restart HiRDB. If the data cannot be recovered, restore the data from a backup and then restart HiRDB. If the cause cannot be identified, contact the customer support center:
- KFPS01181-E
- KFPS01183-E
- KFPS01184-E
KFPS01181-E L
Log read error. type:aaaa(xx....xx), read point: bb....bb,cc....cc, read direction: d, element file: ee....ee, system A/B: f, reason code=gggg-hh
- A log read error occurred.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: File group name
- cc....cc: Block number
- d: Log block read direction:
- f: Forward
- b: Backward
- ee....ee: File group name of the system log file
- f: File version resulting in the error:
- a: A
- b: B
- gggg: Reason code:
- 213: The file group being read contains a closed file.
- 214: The file group being read contains a shutdown file.
- 215: The file group being read contains a file that cannot be read.
- 209: An I/O error occurred in the file group that was being read.
- hh: HiRDB internal code
- S: Resumes processing.
- Action
- Check the cause of the error on the basis of the reason code displayed in this message or the KFPS01203-E message, if it has been output before this message.
KFPS01182-I L
Generation file groups changed for further reading of log blocks. type: aaaa(xx....xx), from: bb....bb,cc....cc, to: dd....dd,ee....ee, read direction: g
- File generations were changed for reading the log.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: File group name before change
- cc....cc: Generation number before change
- dd....dd: File group name after change
- ee....ee: Generation number after change
- g: Log block read direction:
- f: Forward
- b: Backward
KFPS01183-E L
Skipped generations detected while reading log blocks. type: aaaa(xx....xx), range: bb....bb,cc....cc to dd....dd,ee....ee, skipped generations: ff....ff to gg....gg, read direction: h
- A missing generation was detected while reading the log.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the first log file group from which log blocks are read
- cc....cc: Number of the first log generation from which log blocks are read
- dd....dd: Name of the last log file group from which log blocks are read
- ee....ee: Number of the last log generation from which log blocks are read
- ff....ff: Number of the first generation missing a generation
- gg....gg: Number of the last generation missing a generation
- h: Log block read direction:
- f: Forward
- b: Backward
- Note
- During recovery of the log service function, ********,******** is displayed for dd....dd,ee....ee. If only one generation is missing, the same information is displayed in ff....ff to gg....gg.
- S: Resumes processing.
KFPS01184-E L
Invalid log data detected while reading log. type:aaaa(xx....xx), read point: bb....bb,cc....cc, element file: dd....dd read direction: e, system A/B: f
- Invalid log data was detected while reading the log.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the log file group in which invalid log data was detected
- cc....cc: Number of the log block that was to be read
- dd....dd: File group name of the system log file
- e: Log block read direction:
- f: Forward
- b: Backward
- f: File version resulting in the error:
- a: A
- b: B
- S: Resumes processing.
- Action
- Because the log file may be damaged, stop using the log file and check the cause of the error.
KFPS01185-E L
Unable to read log file group. type: aaaa(xx....xx), read point: bb....bb,cc....cc, read direction: d, reason code=eeee-ff
- While reading log files, a file group was detected that cannot be read.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: File group name
- cc....cc: Generation number
- d: Log block read direction:
- f: Forward
- b: Backward
- eeee: Reason code:
- 1001: The indicated file group cannot be read, because the last location of the log was lost in the file group
- ff: HiRDB internal code
- S: Resumes processing.
KFPS01200-E L
Failure to open aaaa(xx....xx)log file. element file: bb....bb, system A/B: c, reason code= ddd-ee....ee
- The system failed to open log file aaaa(xx....xx). A file cannot be opened.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: File group name
- c: File version:
- a: A
- b: B
- ddd: Reason code
- ee....ee: HiRDB internal code
- S: Shuts down the erroneous file and resumes processing.
- O: Take an action given in the Operator's action column appropriate to the reason code, as listed in the table below.
- Action
- Take an action given in the HiRDB Administrator's action column appropriate to the reason code, as listed in the following table.
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
101 | Memory shortage occurred. | -- | Re-estimate the memory. |
201 | File name is invalid. | Consider the following causes:
- An invalid character was specified in the path name.
- The length of the HiRDB file name exceeds the maximum (30 characters).
Specify the file name correctly and re-execute the command. | -- |
202 | In UNIX: The specified file name is not a character special file. Or, there is no device that corresponds to this file. In Windows: This is not a direct disk; or there is no device that corresponds to this file. | -- | Re-evaluate the pdlogadpf operand specification. For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site. |
203 | The device specified in path has not been initialized for the HiRDB file system. |
207 | Maximum value was exceeded when a character special file was being opened. | Close files that are not being used by the log service function and reopen the file. | Re-evaluate the maximum number of files that can be opened per process, and re-create the kernel, if necessary. |
208 | There is no access privilege for the specified character special file. | -- | Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example.). |
209 | I/O error occurred. | Check the cause of the I/O error and take appropriate action. | -- |
210 | HiRDB file system versions do not match. | Re-create the HiRDB file system with the pdfmkfs command, and re-create the log file with the pdloginit command. |
211 | There is no access privilege for the specified file. | -- | Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example). |
212 | Specified file was not found. | -- | Re-evaluate the pdlogadpf operand specification. For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site. |
218 219 | Specified file cannot be used as a log file. | Delete the erroneous file with the pdlogrm command, then re-create the file with the pdloginit command. For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site. | -- |
220 | Specified file is not a log file. | -- | Re-evaluate the pdlogadpf operand specification. For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site. |
221 | Lock segment shortage occurred. | Re-evaluate the number of record lock segments specified during the construction of the OS system. |
222 | Attempt was made to open a log file, but it was being used by another process. | Check the applicable log file as to whether or not it is being used by another process. Reopen the file, if necessary. | -- |
229 | The possible causes are:
- Attempt was made to open a system log file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.
- Attempt was made to open a system log file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.
| -- | Specify Y for the pd_large_file_use operand, or omit the specification. |
- --: Not applicable
KFPS01201-E L
Failure to close aaaa(xx....xx) log file. element file: bb....bb, system A/B: c,reason code=dddd-ee
- The system failed to close log file aaaa(xx....xx). A file cannot be closed.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: System log file name
- c: File version:
- a: A
- b: B
- dddd: Reason code:
- 101: Memory shortage occurred.
- 209: I/O error occurred.
- 221: Lock segment shortage occurred.
- ee: HiRDB internal code
- S: Ignores the error and resumes processing.
- O: Check the cause of the file I/O error and correct the error.
- In the case of a lock segments shortage, re-evaluate the number of record lock segments specified during construction of the OS system.
- Action
- If a memory shortage occurred, the memory must be re-estimated.
KFPS01202-E L
Failure to write to aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee
- The system failed to write data into log file aaaa(xx....xx). Data cannot be written into a file.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: System log file name
- c: File version:
- a: A
- b: B
- dddd: Reason code:
- 209: I/O error occurred.
- 226: Shortage of disk space.
- ee: HiRDB internal code
- S: Shuts down the file that failed and continues processing.
- Action
- Take one of the following actions:
- When the reason code is 209:
Check for the cause of the I/O error in the file, eliminate the cause of the error, and then reallocate the file to HiRDB.
- When the reason code is 226:
Take one of the following actions:
Move the files HiRDB does not use from the disk with the memory shortage to another disk, or delete the files.
In UNIX, use character special files.
Specify the -i option in the pdfmkfs command and create a HiRDB file system area.
Replace the hard disk with a larger capacity disk, and then recover the HiRDB file system areas from backup files.
KFPS01203-E L
Failure to read from aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee
- An attempt to read the aaaa(xx....xx) log file failed. The file cannot be read.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: System log file name
- c: File version:
- a: A
- b: B
- dddd: Reason code:
- 209: I/O error occurred.
- ee: HiRDB internal code
- S: Ignores the error and resumes processing.
- O: Check the cause of the file I/O error, correct the error, then reallocate the file in HiRDB.
KFPS01204-E L
Error occurred while handling log element file of aaaa(xx....xx) log file. reason code=bbbb-cc
- An error occurred while processing log file aaaa(xx....xx) {open|close|read|write}.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code:
- 101: Memory shortage occurred.
- 103: Network error occurred.
- 105: A time-out occurred during communication or file I/O processing.
- cc: HiRDB internal code
- S: Terminates processing.
- Action
- When the reason code is 101:
Re-estimate the amount of required memory.
- When the reason code is 103:
Check for the cause of the network error, and then take appropriate action. Restart HiRDB.
- When the reason code is 105:
Check the status of the network or system. Reduce the load placed on the system. If a hardware error message is output to the disk that created the system log files, check the status of that disk.
Alternatively, restart HiRDB.
KFPS01205-E L
Failure to concurrent access aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee
- An error occurred while concurrently accessing (opening) log file aaaa(xx....xx).
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: File group name
- c: File version:
- a: A
- b: B
- dddd: Reason code:
- 101: Memory shortage occurred.
- 207: Number of open files exceeded the maximum.
- 208: There is no access privilege.
- 209: I/O error occurred when a log file created in the HiRDB file system was accessed.
- 210: File initialization version is invalid.
- ee: HiRDB internal code
- S: Stops HiRDB.
- Action
- Take action appropriate to the reason code, as listed below.
Reason code | Meaning | Action |
---|
101 | There is a memory shortage. | Re-estimate the amount of memory required. Add real memory if necessary. |
207 | The number of open files exceeded the maximum. | For HP-UX, use the sam command to change the value of the nfile operating system parameter. For Solaris, use the limit or ulimit command to change the maximum file descriptor count, rebuild the system, and then re-execute. For Linux, wait for the other processes to terminate, and then re-execute. |
208 | User has no access privilege. | Re-evaluate your file access privileges. For Windows, if this error occurred in an area using the raw I/O facility, check if a formatted disk was specified. |
209 | An I/O error occurred when accessing the system log file. | Take action according to errno of the KFPO00107-E message output immediately before this message. |
210 | Initialization version of the system log file is invalid. | Check the absolute path name of the system log file. When downgrading the initialization version, normally terminate HiRDB, re-create the system log file, and then start HiRDB. |
214 | A shortage of file lock segments occurred. | For HP-UX, use the sam command to change the value of the nflocks operating system parameter. For other than HP-UX, wait for other processes that are using locks to terminate, and then re-execute. |
KFPS01206-E E+L
Unable to open aaaa(bb....bb) log file because file record size is unavailable. element file: cc....cc, system A/B: d, record size=eeee, pd_log_rec_leng=ffff
- The record length for a system log file is inconsistent with the value specified in the pd_log_rec_leng operand; the system log file cannot be opened.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: Server name
- cc....cc: File group name of the system log file
- d: System in which the error occurred
- eeee: Record length for the system log file (in bytes)
- ffff: Value of the pd_log_rec_leng operand
- S: Resumes processing.
- O: Make the record length for the system log file equal to the value specified in the pd_log_rec_leng operand. For details on how to change the record length for a system log file, see the HiRDB Version 9 System Operation Guide.
KFPS01207-E E
HiRDB file system area sector size, record size or record count is invalid. reason code=aaaa, HiRDB file system area sector size=bb....bb, valid record size range=cc....cc
- The sector length of the HiRDB file system, a specified record length, or a specified record count is invalid.
- aaaa: Reason code
- bb....bb: Sector length of HiRDB file system area (bytes)
- cc....cc: Displays the range of specifiable record counts in a minimum to maximum format
- For a reason code 1611 or 1612, this code displays a ***
- S: Terminates processing.
- O: Take an action given in the Operator's action column appropriate to the reason code, as listed in the table below.
- Action
- Take an action given in the HiRDB Administrator's action column appropriate to the reason code, as listed in the following table:
Reason code | Meaning | Operator's action | HiRDB administrator's action |
---|
1604 | The value specified in the -n option of the pdloginit command is outside the range indicated by cc....cc. | Check the values specified in the -l and -n options of the pdloginit command. Re-execute the pdloginit command according to the HiRDB administrator's instructions. | Check the value specified in the pd_large_file_use operand, and review the values specified in the -l and -n options of the pdloginit command. |
1611 | The sector length of the HiRDB file system area is greater than 4,096 bytes. The HiRDB file cannot be created in the specified HiRDB file system area. | Re-execute the pdloginit command according to the HiRDB administrator's instructions. | Re-create the HiRDB file system area on a hard disk or partition whose sector length does not exceed 4,096 bytes. |
1612 | The value specified in the -l option of the pdloginit command is smaller than the sector length of the HiRDB file system area. | Re-execute the pdloginit command according to the HiRDB administrator's instructions. | Check and, if necessary, change the sector length of the HiRDB file system area and the value specified in the -l option of the pdloginit command. |
KFPS01211-I L
aa....aa log file group unload start. server=bb....bb:gen no=cc....cc
- Unloading of system log file aa....aa of server bb....bb by the automatic log unloading facility is starting.
- aa....aa: File group name of the system log file
- bb....bb: HiRDB server name
- cc....cc: Generation number of the system log file
- S: Continues processing.
KFPS01212-I L
aa....aa log file group unload completed. server=bb....bb:unload log file name=cc....cc
- Unloading of system log file aa....aa of server bb....bb by the automatic log unloading facility has been completed. The name of the created unload log file is cc....cc.
- aa....aa: File group name of the system log file
- bb....bb: HiRDB server name
- cc....cc: Unload log file name
- If the name of the unload log file exceeds 138 characters, the last 138 characters of the unload log file name are output.
- S: Continues processing.
KFPS01213-W L
aa....aa log file group already unloaded. Change log file group status to be unloaded.server=bb....bb:gen no=cc....cc
- An attempt was made to unload system log file aa....aa automatically, but the file had already been unloaded. The status of system log file aa....aa has been changed to unloaded.
- aa....aa: File group name of the system log file
- bb....bb: HiRDB server name
- cc....cc: Generation number of the system log file
- S: Continues processing.
KFPS01215-I L
File group bb....bb of aaaa(xx....xx) log opened
- bb....bb of log aaaa(xx....xx) was opened.
A log group was opened. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the opened file group
KFPS01216-I L
File group bb....bb of aaaa(xx....xx) log closed
- bb....bb of log aaaa(xx....xx) was closed.
A log group was closed. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the closed file group
KFPS01217-I L
File group bb....bb of aaaa(xx....xx) log became available
- Log file (bb....bb) of aaaa(xx....xx) is now usable by HiRDB.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the usable log file group
KFPS01218-I L
File group bb....bb of aaaa(xx....xx) log became unavailable
- Log file bb....bb of aaaa(xx....xx) is no longer usable by HiRDB.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the log file group that is no longer usable
KFPS01220-E L
Request to swap aaaa(xx....xx) log file unable to be executed because there is no standby log file group available
- A request to swap the aaaa(xx....xx) log file was issued, but no swappable system log file was found. Reasons no swappable system log files were found:
- There is no standby log file.
- A standby file group is on one of the following statuses:
- Waiting for unload
- Cannot overwrite (now acquiring synchronization point dump corresponding to the applicable log file)
- Reading data for HiRDB recovery
- Being used for command processing
- Waiting for extraction of data linkage information by the HiRDB Datareplicator
- Overwriting denied for online reorganization
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Terminates the system.
- Action
- Take one of the following actions:
- Place the log file on usable status, or add a log file.
- Unload the log file.
- If there is a reserved file, make it available in the online mode, then swap the files.
- Increase the number of log files.
For details, see the restarting procedures under When a HiRDB (unit) terminates abnormally due to a system log file shortage in the HiRDB Version 9 System Operation Guide.
KFPS01221-I L
aaaaaaaa assigned as current file group of bbbb(xx....xx) log file. generation number=cc....cc, first block number=dd....dd
- Log file group aaaaaaaa has been assigned as the current log file for HiRDB server bbbb(xx....xx).
- aaaaaaaa: Name of the assigned log file group
- bbbb: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- cc....cc: Log generation number
- dd....dd: First log block number in file
KFPS01222-I L
aa....aa released from bbbb(xx....xx) log file. generation number=cc....cc, first block number=dd....dd, last block number=ee....ee
- The bbbb(xx....xx) system log file is no longer current.
- aa....aa: File group name of the system log file that is no longer current
- bbbb: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- cc....cc: Log generation number
- dd....dd: First log block number in file
- ee....ee: Last log block number in file (0 means that no log item has been output)
KFPS01223-E L
Error occurred during aaaa(xx....xx) log swap processing. reason code=bbbb
- An error occurred while swapping log file aaaa(xx....xx).
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bbbb: Reason code:
- 101: Memory shortage occurred
- 103: Network error occurred; possible causes are as follows:
- Error in hardware, such as Ethernet board or cable
- Invalid network definition
- Target node is not active, or HiRDB is not running at that node
- Target process is not executing
- 105: Timeout error occurred
- S: Terminates the system.
- Action
- Reason code 101
Ensure that the memory estimate is correct.
- Reason code 103
Perform the following:
Use an operating system command to check the connection status of the server machine.
Use a HiRDB command to check the run status of each server.
- Reason code 105
Perform the following:
Reduce the system load.
If a hardware failure message was output on the disk where the system log file was created, check the disk status.
Determine whether the value specified in the pd_log_swap_timeout operand is too small, and, if necessary, increase the value.
KFPS01224-I L
aaaa(xx....xx) log does not have standby file group available for next swapping
- aaaa(xx....xx) does not have a swappable file group for the next swapping; a swappable log file group needs to be provided.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- O: Unload any log file group that has not been unloaded. If there is no such log file group but there is a reserve file group, open the reserve file group.
KFPS01225-I L
Request to swap aaa(xx....xx) log occurred, but no standby file group available. system opened file groups having been closed to get available standby
- The system needs to swap system log file aaa(xx....xx) but no file group is standing by as a swappable target. The system is looking for a reserve status file group as a swappable target.
- aaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Continues processing.
KFPS01226-E L
bb....bb file group of aaaa(xx....xx) log opened but unable to be assigned as current file group; now closing
- Log file bb....bb of aaaa(xx....xx) was opened, but it was closed again because this log file cannot be assigned as the current file.
A closed file was opened, but it was closed again because its log file group has not been unloaded and cannot be used as the current file. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of opened log file group
- S: Closes log file bb....bb and resumes processing.
KFPS01227-W E+L
aaaa (bb....bb) log does not have standby file group available for next swapping; stop datareplication and continues swapping
- Swapping failed because aaaa(bb....bb) file was on HiRDB Datareplicator extracting status. The system terminates HiRDB Datareplicator linkage and continues swapping of log files because pd_log_rpl_no_standby_file_opr=continue is specified.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- S: Resumes processing.
- O: HiRDB Datareplicator was terminated forcibly. To restart HiRDB Datareplicator linkage, the target database must be re-created. For details about what action to take, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- Action
- Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, restart data linkage. To restart data linkage, you must re-create the database on the reflection side.
KFPS01228-W L
Error occurred aaaa(bb....bb) log for waiting syncpoint acquisition opportunities. reason code=cccc
- When the pdlogswap or pdlogsync command was executed with the -w option specified, validation of a synchronization point dump was not completed within the monitoring interval time.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: Server name
- cccc: Reason code:
- 105: Timeout occurred while waiting for validation of synchronization point dump during execution of pdlogswap command with the -w option specified.
- S: Resumes processing
- O: Re-execute the pdlogswap command after taking appropriate action as described below. If the same event recurs when the pdlogswap command is executed or none of the events listed below applies, contact the customer support center.
- Action
- Check whether there is a transaction that is taking a long time to execute.
- Time-consuming transaction present:
- Transaction cannot be cancelled:
- Wait until the transaction terminates. After confirming that the synchronization point can be enabled, re-execute either the pdlogswap or pdlogsync command.
- To allow the synchronization point to be held until the current transaction terminates, specify a large enough value in the -t option and then re-execute either the pdlogswap or pdlogsync command.
- Transaction can be cancelled:
- Cancel the transaction and re-execute either the pdlogswap or pdlogsync command.
- No time-consuming transactions present:
- Re-execute either the pdlogswap or pdlogsync command.
KFPS01229-I L
Next aa....aa log file restart point, generation number=bb....bb, block number=cc....cc. restart end point, generation number=dd....dd, block number=ee....ee. last acquired syncpoint dump ffff/gg/hh ii:jj:kk
- Displays the system log input starting position, the system log input termination position, and the date and time when the synchronization point dump was last enabled for the next restarting of server name aa....aa.
If an error occurs in the synchronization point dump file or status file before the server is restarted, the system log input starting position indicated in this message may differ from the position at which the system log is actually input. - aa....aa: Server name
- bb....bb: System log generation number that will be the input starting position#1
- cc....cc: System log block number that will be the input starting position#1
- dd....dd: System log generation number that will be the input termination position#1
- ee....ee: System log block number that will be the input termination position#1
- ffff/gg/hh: Date the current synchronization point was enabled#2
- ii:jj:kk: Time the current synchronization point was enabled#2
- #1: If the value to be displayed in the generation number or block number cannot be determined, the system displays the symbol *******.
- #2: If an enabling date cannot be determined, the symbol ****/**/** is displayed; if an enabling time cannot be displayed, the symbol **:**:** is displayed.
- S: Resumes processing.
- O: If the server cannot be restarted unless a system log file is added, or when determining the number of system log files to be added, or when determining an approximate length of time required to restart the server next time, see both output information about this message and the execution results of the pdlogls command. If the generation number and block number of this message display ********, refer to the message output during the previous unit shutdown. For HiRDB/Single Server, this message is output to the message log file and the event log (in UNIX, syslogfile). For HiRDB/Parallel Server, the output target differs depending on the condition. The conditions and output targets are listed below.
Condition | Message output target |
---|
- Unit terminated abnormally
- Failure at server startup
- Failure at server shutdown
| Messages are output to the message log file and the event log (in UNIX, syslogfile) of the unit where the system manager resides. However, if a communication error occurs between the unit (or server) and the unit where the system manager resides, or if the unit where the system manager resides is stopped, messages will be output to the event log (in UNIX, syslogfile) of the affected unit. |
- Unit terminated forcibly
- Server terminated forcibly
| Messages will be output to the event log (in UNIX, syslogfile) of the affected unit. |
KFPS01230-E E+L
Unable to read log file reason=(aaaa, bbbbbbbb)
- The system was unable to execute HiRDB Datareplicator log input processing.
- aaaa: Reason code
- bbbbbbbb: Detail code
- The detail codes and operator's actions for reason code aaaa are listed in the table below.
- S: Terminates processing.
- O: Take action appropriate to the reason code and detail code, as shown below:
Reason code | Detail code | Explanation | Operator's action |
---|
101 | Size to be allocated | Memory shortage occurred. | Check the number of processes, take appropriate action, then re-execute. |
203 | Error code for HiRDB file system | Log file open error or read error occurred. | See 5.1 Error codes returned from HiRDB file system access requests to determine the cause of the error. If the displayed detail code is not found in the list of error cause codes, contact the customer support center. |
212 | 0 | Access to all files failed except for the one at the input startup point. | Execute the pdlogls command to determine the cause of the error on the basis of the result. |
405 | 101 | Memory shortage occurred during definition analysis. | Re-execute after the current process has terminated. If a system call error message was output immediately before this message, take action appropriate to that message. |
403 | Open error occurred in a definition file. | Check the cause of the error on the basis of the definition file open error message that was output immediately before this message. |
404 | Open error occurred in an analysis file. | Check the cause of the error on the basis of the analysis file open error message that was output immediately before this message. |
405 | Error was detected during analysis processing. | Check the cause of the error on the basis of the analysis error message that was output immediately before this message. |
414 | The number of valid log file groups was 0. | Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute. |
410 | 0 | File group names of the system log file were duplicated. | Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute. |
413 | 0 | The maximum file group count of the system log file was exceeded. | Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute. |
1602 | Block number | A missing block was detected in the log file. | The log file may have been overwritten. Check the cause. |
1653 | 0 | Log input location is invalid. | Check the contents of the definition file. If there is no error in the definition file, check that there was a file at the input startup point output by the pdls -d rpl -j command and that the file is accessible. If the file exists and is accessible, enter the pdls -d rpl -j and pdlogls -d sys commands. HiRDB Datareplicator linkage cannot be established unless the system log displayed by the pdls command as being extracted is not listed under the log block output status of all system log files displayed by the pdlogls command. Take an appropriate action according to the system administrator's instructions so that HiRDB Data-replicator linkage can be restarted. If the system log displayed by the pdls command as being extracted is listed under the log block output status of all system log files displayed by the pdlogls command, contact the customer support center. |
- Action
- Terminate HiRDB Datareplicator linkage, if it is in effect. To restart HiRDB Datareplicator linkage, the target database must be re-created. For details about what action to take, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- However, if reason code 203 was output, the system log file may temporarily have been unreferenceable. See the KFPS01231-W or KFPO00107-E message output immediately before, correct the temporary device busy or other problem with the disk that stores the system log file so that it can be referenced, and restart the HiRDB Datareplicator.
KFPS01231-W E+L+R
Error occurred while reading log element file, file group=aa....aa, system A/B: b, reason=(cccc,dd....dd)
- Error occurred while reading a file for system b in log file group aa....aa.
- aa....aa: Name of log file group
- b: System where the error occurred:
- a: System A
- b: System B
- cccc: Reason code
- dd....dd: Detail code
- The detail codes and operator's actions for reason code cccc are listed in the table below.
- S: Terminates processing.
- O: Take action appropriate to the reason code and detail code, as shown below:
Reason code | Detail code | Explanation | Operator's action |
---|
213 | HiRDB file system error code | Log file open error occurred. | See 5.1 Error codes returned from HiRDB file system access requests to determine the cause of the error. If the displayed detail code is not found in the list of error cause codes, contact the customer support center. |
215 | HiRDB system error code | Log file read error occurred. |
1602 | Log block number | A missing block was detected in the log file. | The log file may have been overwritten. Check the cause. |
KFPS01232-E E+L
Datareplication stopped for aaaa(bb....bb); reason code=cccc, continues processing.
- Log service aaaa(bb....bb) can no longer output data linkage information for reason cccc, but HiRDB operation will be continued as is.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cccc: Reason code indicating the nature of the error:
- 115: Cancellation of HiRDB Datareplicator extraction processing was detected
- 212: File for data linkage was not found
- S: Resumes processing.
- O: HiRDB Datareplicator linkage has been terminated forcibly. Take appropriate action based on the HiRDB Version 9 System Operation Guide and the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- Action
- To re-execute HiRDB Datareplicator linkage, the target database must be re-created.
- Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.
KFPS01233-E E+L
HiRDB Datareplicator access communication file for aaaa(bb....bb) is invalid; continues processing. reason code=cccc
- An error was detected by HiRDB Datareplicator in the file for data linkage. HiRDB operation will be continued, but data can no longer be linked by HiRDB Datareplicator.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cccc: Maintenance information
- S: Continues processing without changing the system log file's HiRDB Datareplicator extraction-completed or extracting status.
- O: Enter the pdls -d rpl command to determine whether or not HiRDB is writing data linkage information. If HiRDB is writing data linkage information, data can no longer be linked using HiRDB Datareplicator. Enter the pdrplstop command to terminate HiRDB Datareplicator linkage. Also, terminate both HiRDB Datareplicators at the data extraction source and target.
- Action
- To re-execute HiRDB Datareplicator linkage, the target database must be re-created.
- Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.
KFPS01234-I L
No extract database in aa....aa.
- Server aa....aa contains no database subject to data extraction by HiRDB Datareplicator. The system will no longer manage the system log file's extraction status (extraction-completed/extracting status) at this HiRDB server.
- aa....aa: HiRDB server name
- S: Continues system operation, removing the HiRDB Datareplicator extraction-completed/extracting status in the system log file at this HiRDB server.
- O: There is no problem if there is no database subject to data linkage at this HiRDB server. If the extraction system definition or extraction definition for HiRDB Datareplicator is invalid, data linkage cannot be continued. Execute the pdrplstop command to terminate HiRDB Datareplicator linkage. Also, terminate both HiRDB Datareplicators at the data extraction source and target.
- Action
- To re-execute HiRDB Datareplicator linkage, the target database must be re-created.
- If a HiRDB Datareplicator extraction system definition or extraction definition is invalid, referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, correct the invalid definition, and return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.
KFPS01235-E E+R+L
Log file generation may be skipping between log file group aa....aa (cc....cc, dd....dd) and bb....bb (ee....ee, ff....ff)
- The file group of the read system log files was switched from aa....aa to bb....bb by data extraction, but a system log file generation skipping error may have occurred during that time.
- aa....aa: File group name of the previous system log file that was read
- bb....bb: File group name of the system log file that was read
- cc....cc: Run ID of aa....aa (hexadecimal)
- dd....dd: Generation number of aa....aa (hexadecimal)
- ee....ee: Run ID of bb....bb (hexadecimal)
- ff....ff: Generation number of bb....bb (hexadecimal)
- S: Continues processing.
- O: A mismatch may have occurred between the extracted database and the target database. Use the pdhold command to put the extracted database in reference-possible backup hold status. Then, perform the target process up to the newest data and check for mismatches between the extracted database and the target database.
- If there are no mismatches
Resume updating of the extracted database. HiRDB Datareplicator linkage can continue.
- If there are mismatches
You must synchronize, and then initialize the data linkage environment between the extracted database and the target database. For details about how to handle a mismatch between databases, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- If the unit stops during normal startup and this message is output when no disk error occurred in the system log file, no mismatches occur between the databases.
KFPS01240-E L
Element file aa....aa unable to be used as bbbb(xx....xx) log file. file group: cc....cc, system A/B: d, reason code=eeee
- A file was found that cannot be used as a log file.
- aa....aa: Name of the system log file where the error occurred
- bbbb: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- cc....cc: Name of log file group resulting in the error
- d: File version:
- a: A
- b: B
- eeee: Reason code
- The table below lists the reason codes and actions to be taken.
- S: Releases this file and resumes processing.
- O: Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
223 | File is too small to collect the maximum amount of defined record data. | Obtain the estimated file size from the HiRDB administrator and determine whether or not the size is correct. If the file size is incorrect, re-create the file at the correct size. | Check the definition to determine whether or not the maximum record data length is correct. If it is incorrect, re-estimate the file size and change the definition. If the maximum record data length is correct, instruct the operator to re-create the file at the estimated size. |
601 | File failed to open. | Take appropriate action according to the KFPS01200-E or KFPS01203-E message that was output immediately before this message. | -- |
602 | Management information in the file failed to be read. |
603 | Management information is damaged in the file. | Initialize this file. |
604 | The HiRDB identifier recorded in the system log file is different from the HiRDB definition. Files of another system might also be corrupted. | Check with the HiRDB administrator as to whether the file can be used with this system. If the file can be used with this system, initialize it. | Check the file as to whether or not it is used with another system. If it is used with another system, change the definition so that this file will not be used with this system. |
605 | File configuration in the file is different from that of the current file configuration; the file configuration may have been changed. | Check with the HiRDB administrator as to whether or not the file configuration has been changed. If it has not been changed, initialize this file. | Check the definition and determine whether or not the log file group and element file using the corresponding file have been changed. If the file configuration has been changed, change it to the initial configuration in the definition. |
606 | File is the current file. | An error may have occurred in this file during the previous session. Unload the log information, then change the file status or initialize the file. | -- |
If other than the above, contact the HiRDB administrator. | If a unit shuts down between the time that it is made primary and startup processing finishes, the header information might not be written correctly before close processing. If not performing recovery using the system log, use the pdlogchg command to change the status. If performing recovery using the system log, use the pdlogunld command to unload, and then use the pdlogchg command to change the status. |
- --: Not applicable
- Note
- Use the following procedure to initialize a file:
- Delete the file with the pdlogrm command.
- Re-create the file with the pdloginit command.
- To change the file status, use the pdlogchg command; to unload log information, use the pdlogunld command.
KFPS01250-I L
aaaa(xx....xx) log file group bb....bb is not unloaded; unload.
- Log file group bb....bb of aaaa (xx....xx) has not been unloaded. Or, log information has not been unloaded from this log file group; unload the log information (otherwise, this log file group cannot be swapped).
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the log file group whose log information has not been unloaded
- S: Resumes log server process startup.
- O: Enter the pdlogunld command to unload the log information.
KFPS01251-I L
aaaa(xx....xx) log file group bb....bb is in invalid state; change file group state.
- The status of log file group bb....bb of aaaa(xx....xx) is invalid. Correct the file group's status.
The status of this log file group is invalid, because an error occurred during the previous online session. Log information cannot be collected unless the status is changed. Either unload the log information or change the file group status. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Name of the log file group on invalid status
- S: Resumes log server process startup.
- O: Either enter the pdlogunld command to unload the log information or enter the pdlogchg command to change the file group status.
KFPS01252-I L
aaaa(bb....bb) log file group cc....cc is not extracted; extract.
- Extraction by HiRDB Datareplicator of aaaa(bb....bb) with log file group cc....cc has not been completed. Use HiRDB Datareplicator to extract the system log. This log file group cannot be subject to swapping unless system log extraction is completed.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: Name of log file group whose extraction by HiRDB Datareplicator has not been completed
- S: Resumes processing.
- O: If HiRDB Datareplicator is not active, start it and extract the system log.
KFPS01253-I L
aaa(bb....bb) log file group cc....cc not reflected by Online DB Reorganization; retry Online DB Reorganization or cancel Online DB Reorganization
- The file group of the aaa(bb....bb) system log file did not terminate that online reorganization discrepancy application that was using the update log.
- aaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: File group name of the system log file
- S: Continues processing.
- Action
- Perform one of the following actions:
- Execute the pdorend command to continue online reorganization discrepancy application processing.
- Execute the pdorbegin -u or pdorend -u command to suspend updatable online reorganization.
KFPS01255-W L
Number of available file groups of aaaa(xx....xx) log is insufficient; open log file groups.
- The number of log file groups for aaaa(xx....xx) is less than the required minimum. Open more log file groups.
If operation is continued, the destination of log information cannot be changed in the future, because the number of available log file groups is less than the required value. Open more log file groups immediately. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Resumes processing.
- O: Enter the pdlogopen command to open file groups.
KFPS01256-E L
No standby file groups of aaaa(xx....xx) log are available.
- There are no log file groups available for aaaa(xx....xx).
The current log file group cannot be selected, because there is no available log file group for the destination of log information. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Outputs message KFPS01113-E and cancels log server process startup processing.
- O: Eliminate the cause of this error so that the current file group cannot be selected.
KFPS01257-E L
Unable to restore current aaa(xx....xx) log file group.
- For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used, all files in use when the system was previously online are initialized, and the current log file group cannot be recovered.
For a log application site, all system log files are initialized, and log applications cannot be started. - aaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Outputs a KFPS01113-E message, and stops HiRDB restart processing.
- O: Take the following actions:
- For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Execute forced normal startup of HiRDB and recover the database.
- For a log application site
After completing the preparation for log application, start the log application site.
KFPS01258-W L
Unable to swap current aaaa(xx....xx) log file group for a standby file group because no standby is available; ignores "rerun swap" and continues processing.
- Because there are no files that can be the target of a swap, the system log file represented by aaaa(xx....xx) is not swapped.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Determine whether there are system log files in unload wait status. If so, unload them.
KFPS01260-E L
Log generation file for system recovery not found; stops recovery processing. type: aaaa(xx....xx)
- Recovery processing was cancelled, because there was no log generation file subject to system recovery.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Terminates the system.
- Action
- Refer to the KFPS01240-E message in order to check the cause of the error.
KFPS01261-E L
Error occurred while reading log blocks; stos recovery processing. type: aaaa(xx....xx)
- Recovery processing was cancelled, because an error occurred while reading the log.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
S: Terminates the system. - Action
- Refer to the following messages that are output immediately after this message to check the cause of the error:
- KFPS01180-E
- KFPS01181-E
- KFPS01183-E
- KFPS01184-E
KFPS01262-I L
Log block reading started. type:aaaa(xx....xx), read start point: bb....bb,cc....cc,dd....dd
- Log read operation has started.
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: First file group name that was read
- cc....cc: First generation number that was read
- dd....dd: First block number that was read
KFPS01263-I L
Log block reading completed. type: aaaa(xx....xx), read end point: bb....bb,cc....cc,dd....dd
- Log read operation is completed (log was read during system recovery).
- aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- bb....bb: Last file group name that was read
- cc....cc: Last generation number that was read
- dd....dd: Last block number that was read
- Note
- If no log block was read, ********,********,******** is displayed for bb....bb,cc....cc,dd....dd.
KFPS01264-E L
Error occurred during inter-system adjustment for duplicated log files. type: aaaa(xx....x)
- An error occurred during inter-system adjustment for dual log files at the time of HiRDB recovery.
When dual log files are used, an error occurs in the last location of the log between file versions A and B depending on the HiRDB termination timing. Inter-system adjustment is performed to adjust such an error during HiRDB restart. - aaaa: Type of log file:
- sys: System log file
- xx....xx: HiRDB server name
- S: Resumes processing.
- O: Check the cause of the error on the basis of the following messages:
KFPS01265-I L
Log block reading started for database recovery. type: aaaa(bb....bb), read start point: cc....cc,dd....dd,ee....ee
- Log read processing for database recovery has been started.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: Name of the first file group to be read
- dd....dd: Number of the first generation to be read
- ee....ee: Number of the first block to be read
- S: Resumes processing.
KFPS01266-I L
Log block reading completed for database recovery. type: aaaa(bb....bb), read end point: cc....cc,dd....dd,ee....ee
- Log read processing for database recovery has been completed.
- aaaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: Name of the last file group read
- dd....dd: Number of the last generation read
- ee....ee: Number of the last block read
- Note
- If no log block was read, **..** is displayed for bb....bb, cc....cc, and ee....ee.
- S: Resumes processing.
KFPS01267-E E+L
Error occurred while database recovery for aaa(bb....bb). reason code=(cc....cc, dd....dd)
- An error occurred in database recovery during restart, or in the preparation for log application processing.
- aaa: Type of log file:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: Reason code
- dd....dd: Maintenance information
- S: Terminates abnormally.
- O: See the following table and take action.
- Action
- Take action appropriate to the reason code listed below.
- If a reason code not in the list is output, contact the customer support center.
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
107 | Error occurred during message queue processing. | Contact the HiRDB administrator. | Contact the customer support center. |
114 | Error was detected during message queue processing. | Run again. | If the error recurs, contact the customer support center. |
209 | I/O error occurred in the log file being input. | Contact the HiRDB administrator. | If this reason code is output, or a KFPS01203-E message was output before this message, investigate the cause. |
213 | A closed file was found in the log file being input. |
214 | A shutdown file was found in the log file being input. |
215 | A file that cannot be input was found in the log file being input. |
550 | After a transaction execution site terminated with a status other than normal, it was started using the pdstart dbdestroy command or the pdstart -i command, so the integrity of the log application site database cannot be guaranteed. | Contact the HiRDB administrator. | For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used: Collect the following data, and contact the customer support center:
- HiRDB system definition file
- Files under %PDDIR%\spool
- Event log (in UNIX, syslogfile)
For a log application site: After executing preparation for log application, restart the log application site. |
711 | A log file generation was skipped. | Check the log file definition to make sure that changes were made correctly. | If there is no error in the log file definition, collect the following data, and contact the customer support center:
- HiRDB system definition file
- Files under %PDDIR%\spool
- System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)
- Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)
- Event log (in UNIX, syslogfile)
|
1001 | No log file exists at the input start position. | Contact the HiRDB administrator. | If Real Time SAN Replication with the log-only synchronous method is not used, or for a transaction execution site when Real Time SAN Replication with the log-only synchronous method is used: Determine whether the log file definition was mistakenly changed. Also, confirm that the system log file was not initialized. If the system log file was initialized and HiRDB cannot be restarted, see the section on measures to be taken when HiRDB cannot be restarted due to an error in the current file of both systems in the manual HiRDB Version 9 System Operation Guide. If the above actions cannot resolve the problem, collect the following data, and contact the customer support center:
- HiRDB system definition file
- Files under %PDDIR%\spool
- System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)
- Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)
- Event log (in UNIX, syslogfile)
For a log application site: After executing preparation for log application, restart the log application site. |
1602 | An invalid log block was detected. | Contact the HiRDB administrator. | If Real Time SAN Replication with the log-only synchronous method is not used, or for a transaction execution site when Real Time SAN Replication with the log-only synchronous method is used: The log file may be corrupt. Use the following procedure for recovery: 1. Collect the following data, and contact the customer support center:
- HiRDB system definition file
- Files under %PDDIR%\spool
- System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)
- Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)
- Event log (in UNIX, syslogfile)
2. Recover the database using a method other than restart, and start HiRDB. For a log application site: After executing preparation for log application, restart the log application site. |
1610 | A missing log block was detected. |
KFPS01268-E L
Invalid log data detected while reading log. type:aa....aa(bb....bb), read point:cc....cc, dd....dd.
- Invalid log data was detected while loading a system log.
- aa....aa: File type:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: File group name of the system log file in which the invalid data was detected
- dd....dd: Block number of the system log that was to be loaded
- S: Terminates processing.
- Action
- The action to be taken differs depending on the abort code output before or after this message.
- When Psjnr38 is output
Take the action recommended when Psjnr38 is output.
- When Psjnr38 is not output
Save the files and system log files under %PDDIR%\spool and contact the customer support center.
KFPS01269-I L
Reading log block. type:aaaa(bb....bb), reading point:cc....cc, dd....dd, ee....ee
- Reports the system log file being loaded during a HiRDB restart.
- aaaa: File type:
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: File group name of the system log file being loaded
- dd....dd: Generation number of the system log being loaded
- ee....ee: Block number of the system log being loaded
- S: Continues processing.
KFPS01270-E E+L
Unable to use log file due to I/O error. element file: aa....aa, system A/B: b
- A log file cannot be used due to an I/O error.
- aaaa: Name of the system log file where the error occurred
- b: Erroneous file version:
- a: A
- b: B
- S: Resumes processing.
- O: Eliminate the cause of the error and reenter the command.
- Action
- Refer to the message that was output immediately before this message to check the cause of the error, and correct the error.
KFPS01271-I E+L
Unloading completed. generation number=aa....aa, start block number=bb....bb, end block number=cc....cc
- Unload processing is completed. Displays the range of unloaded block numbers.
- aa....aa: Generation number of the log file group from which log was unloaded
- bb....bb: First block number unloaded
- cc....cc: Last block number unloaded
- Note
- If no log block was unloaded, ******** is displayed for cc....cc.
KFPS01272-E E+L
Unable to unload log file. element file: aa....aa, system A/B: b, reason code=cccc-dd
- An attempt was made to unload a file group containing a system log file that cannot be unloaded.
- aa....aa: Name of the system log file where the error occurred
- b: Erroneous file version:
- a: A
- b: B
- cccc: Reason code
- dd: HiRDB internal code
- S: Resumes processing.
- O: Take action appropriate to the reason code, as listed below.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
220 | This file is not the system log file. | -- | Re-evaluate the system log file names in the file group. |
603 | The management information in the file is corrupted. | Suspend unloading of the applicable file group, and then disconnect from HiRDB. | -- |
605 | The configurations of the file and the definition file are different. | -- | Check if the definition related to the system log file was changed. |
1603 | The system log file is in unload completed status. | Re-evaluate the file group name specified in the command. |
1607 | The system log file is not used by HiRDB. | -- |
- --: Not applicable
KFPS01273-E E+L
Unable to change log file status. element file: aa....aa, system A/B: b,reason code=cccc-dd
- Cannot change the status of some system log files in the target file group.
- aa....aa: Name of the system log file where the error occurred
- b: Erroneous file version:
- a: A
- b: B
- cccc: Reason code (the table below lists the reason codes and actions to be taken)
- dd: HiRDB internal code
- S: Resumes processing.
- O: Take action appropriate to the reason code, as listed below.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
220 | This file is not the system log file. | -- | Re-evaluate the system log file names in the file group. |
603 | The management information in the file is corrupted. | Suspend unloading of the applicable file group, and then disconnect from HiRDB. | -- |
605 | The configurations of the file and the definition file are different. | -- | Check if the definition related to the system log file was changed. |
1603 | The system log file is in unload completed status. | Re-evaluate the file group name specified in the command. | -- |
1607 | The system log file is not used by HiRDB. |
- --: Not applicable
KFPS01274-E E+L
Failure to open log element file. element file: aa....aa, system A/B: b, reason code=cccc-dd
- Failed to open the system log file.
- aa....aa: System log file name
- b: Erroneous file version:
- a: A
- b: B
- cccc: Reason code
- dd: HiRDB internal code
- S: Resumes processing.
- O: Take action appropriate to the reason code, as listed below.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
101 | Memory shortage occurred. | Re-execute the command after the current process has terminated. | Re-estimate the memory size. |
201 | File name is invalid. | Consider the following causes:
- An invalid character was specified in the path name.
- The length of the HiRDB file name exceeds the maximum (30 characters).
Specify the file name correctly and re-execute the command. | -- |
202 | HiRDB file system area name specified in the path is not an HiRDB file system area. | Check the HiRDB file system name specified in the path and re-execute the command. | Re-evaluate the specification of the pdlogadpf operand file. |
203 | The device specified in the path has not been initialized for the HiRDB file system. | -- |
207 | Maximum value was exceeded when the HiRDB file system area specified in the path was opened. | -- |
208 | User does not have access privilege for the HiRDB file system area specified in the path. | Execute the command with a user ID that has access privilege for the specified HiRDB file system area. | Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example). |
209 | I/O error occurred. | Check the cause of the I/O error and take appropriate action. | -- |
210 | HiRDB file system versions do not match. | -- | Re-evaluate the specification of the pdlogadpf operand file. |
211 | There is no access privilege for the specified file. | Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored. | Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example). |
212 | Specified file was not found. | -- | Re-evaluate the specification of the pdlogadpf operand file. |
221 | Lock segment shortage occurred. | Re-evaluate the number of record lock segments specified during construction of the OS system. |
222 | The applicable system log file is being used by another process. | Check the run status of the applicable system log file or the file group to which the file belongs, and then re-execute the command. | -- |
- --: Not applicable
KFPS01275-E E+L
Minor error occurred while analyzing definitions for log service. file being analyzed: aaaaaaaa, record number=bbbbbbbbbb, reason code=cccc
- A minor error occurred while analyzing the log file-related definitions.
- aaaaaaaa: Name of definition file being analyzed
- bbbbbbbbbb: Record number resulting in the error
- cccc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)
- S: Resumes processing the log service function command.
- Action
- Check the log service function-related definitions.
Reason code | Explanation | Action |
---|
409 | One of the following errors was found in the specification of the -g option with the pdlogadpf operand:
- The -g option was not specified
- The length of the system log file group name is incorrect
| Correct the specification of the pdlogadpf operand, and then re-execute the command. |
410 | More than one pdlogadpf operand specified the same file group name. |
411 | One of the following errors was found in the specification of the -a option with the pdlogadpf operand:
- The -a option was not specified
- The file name was not specified
|
412 | One of the following errors was found in the specification of the -b option with the pdlogadpf operand:
- The -b option was not specified when duplexing
- The file name was not specified
|
422 | An error was found in the specification of the -d option with the pdlogadfg operand, or the -d option was not specified. | Stop the system if necessary, and then correct the definition content and restart. |
423 | An error was found in the specification of the -d option with the pdlogadpf operand, or the -d option was not specified. |
KFPS01277-E L
Log point information is invalid. info=aaaa
- Invalid log point information was detected.
- aaaa: System maintenance information
- S: Resumes processing.
- O: Check the items shown below and take appropriate action:
- Check that the correct backup file is specified in the pdrstr command; if it is not the correct file, specify the correct file name and re-execute the command.
- Refer to both the log point information file that was re-created from the backup file with the pdrstr command and the execution result of the pdlogls command, check whether the log file recorded in the log point information file exists, and report the result to the administrator.
- Action
- Check the items shown below and take appropriate action:
- If the log file recorded in the log point information file does not exist, check whether the log file specification in the server definitions was manipulated. If the log file that was used was removed from the definitions after that backup was made, add the file and re-execute the command.
If the above log file was deleted or the log file recorded in the log point information file was overwritten, the database cannot be recovered by specifying -L in the pdrstr command.
- If neither of the above applies, contact the customer support center.
KFPS01278-W L
Failure to processing log file group. type: aaa(bb....bb), file group: cc....cc, reason code=dddd-ee
- The cc....cc log file group, which is used by the bb....bb server, cannot be processed because status referencing has been disabled due to dddd.
- aaa: Log type (sys or lar)
- bb....bb: HiRDB server name
- cc....cc: Name of file group
- dddd: Reason code:
- 209: I/O error occurred in log file.
- 213: Open error occurred in log file.
- 215: Input is disabled for log file.
- 222: Another process is using this file group.
- 1601: Target log file does not exist.
- ee: System maintenance information
- S: Resumes processing and does not process the log file group.
- O: If the log file is not being used, no problem exists.
- During pdrstr (database recovery utility) execution:
If the log file was being used from the time the backup was made to the current time, the database may not be recovered correctly.
If the KFP01279-W message was output, consider the message contents, contact the administrator, take appropriate action, then re-execute the command.
- During pdlogchg (log file status change command) execution:
When the reason code is 222:
The memory status does not match the status of the system log file itself for the log file group. Close the log file group with the pdlogcls command and then reopen it with the pdlogopen command.
For all other reason codes:
Take appropriate action for the reason code and then re-execute the command. If the KFPS01279-W message is output, correct the error that is reported by that message and then re-execute the command.
- Action
- If the log file is not needed for execution of the pdrstr or pdlogchg command, no problem exists. If the log file is needed for execution of the above commands, check the items shown below and take appropriate action.
- If an error occurred in the log file group or the log file group was initialized after being used online, recover the log file if it is recoverable, then re-execute the command.
- Check that the log file description in the server definition is correct, correct any errors, then re-execute the command.
- If reason code 222 is output after the pdlogchg -z command is executed while HiRDB is active, the log file cannot be reused. Close the log file and then reopen it.
- If neither of the above applies, contact the customer support center.
KFPS01279-W L
Unable to use log file. element file: aa....aa, system A/B: b, reason code=ccc-dd
- The file status of the aa....aa log file cannot be referenced because of the reason indicated by cccc. The log file cannot be processed.
- aa....aa: Name of log file
- b: System in which the error occurred (a or b)
- cccc: Reason code
- dd: System maintenance information
- S: Resumes processing and does not process the log file.
- O: If the log file is not being used, no problem exists. If the KFPS01278-W message is not output for the file group of the log file, no problem exists. If neither of the above applies, determine the cause of the error from the reason code and contact the administrator.
- Action
- If the log file is not needed for execution of the pdrstr or pdlogchg command, no problem exists. If the log file is needed for execution of the above commands, check the cause from the reason code, recover the file from the information displayed in the KFPS01278-W message, then re-execute the command. Following are the reason codes:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
101 | Memory shortage occurred. | Re-execute the command after the current process has terminated. | Re-estimate the memory. |
201 | File name is invalid. | Consider the following causes:
- An invalid character was specified in the path name.
- The length of the HiRDB file name exceeds the maximum (30 characters).
Specify the file name correctly and re-execute the command. | -- |
202 | HiRDB file system area name specified in the path is not an HiRDB file system area. | Check the HiRDB file system name specified in the path and re-execute the command. | Re-evaluate the file specification of the pdlogadpf operand. |
203 | The device specified in the path has not been initialized for the HiRDB file system. | -- |
207 | Maximum value was exceeded when the HiRDB file system area specified in the path was opened. | -- |
208 | User does not have access privilege for the HiRDB file system area specified in the path. | Execute the command with a user ID that has access privilege for the specified HiRDB file system area. | Modify the access privileges for the HiRDB file system area using OS commands (chmod, for example). |
209 | I/O error occurred. | Determine the cause of the I/O error and take appropriate action. | -- |
210 | HiRDB file system versions do not match. | -- | Re-evaluate the file specification of the pdlogadpf operand. |
211 | User does not have access privilege for the specified file. | Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored. | Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example). |
212 | Specified file was not found. | -- | Re-evaluate the file specification of the pdlogadpf operand. |
221 | Lock segment shortage occurred. | Re-evaluate the number of record lock segments specified during startup of the OS system. |
222 | The applicable system log file is being used by another process. | Check the run status of the applicable system log file or the file group it belongs to, and then re-execute the command. | -- |
603 | The maintenance information in the file is corrupted. | Initialize this file. |
605 | The file configuration of the file does not match the current file. The file configuration may have been changed. | Check with the HiRDB administrator as to whether or not the file configuration has been changed. If it has not been changed, initialize this file. | Check the definition and determine whether or not the log file group and element file using the corresponding file have been changed. If the file configuration has been changed, change it to the initial configuration in the definition. |
1067 | The file is not used by HiRDB. | Check the corresponding file group. | -- |
- --: Not applicable
KFPS01280-E E+L
Unable to execute aa....aa command due to bbbb-cc
- Cannot execute the aa....aa command.
- aa....aa: Command name that could not be executed
- bbbb: Reason code
- cc: HiRDB internal code
- S: Terminates command execution.
- O: Take action appropriate to the reason code and re-execute the command, if necessary.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action | HiRDB Administrator's action |
---|
101 | Memory shortage occurred. | Re-execute the command after the current process has terminated (if a system call message has been issued immediately before this message, take action appropriate to that message). If one of the following commands was executed while HiRDB was active, also take the action called for:
- pdlogchg command
Mismatch between the memory status and the system log file's status may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.
- pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.
| Re-estimate the memory. |
102 | The shared memory library service function cannot be provided, because the number of shared memory segments attached to the read process would exceed the permitted maximum. | If a system call message has been issued immediately before this message, take action appropriate to that message. | Re-estimate the shared memory. |
103 | Network error occurred; possible causes are as follows:
- Error in hardware, such as Ethernet board or cable
- Invalid network definition
- Target process is not executing
| Check the cause of the error using the procedure described below and take appropriate action:
- Check the server machine connection status with the applicable OS command.
- Check the execution status of each server with the applicable HiRDB command.
If one of the following commands was executed while HiRDB was active, also take the action called for:
- pdlogchg command
A mismatch between the memory status and the system log file's status may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.
- pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.
| Re-estimate the shared memory. |
104 | The log server process is not online, or required information in the shared memory cannot be referenced. | Use the pdls command to examine the status information of the corresponding unit and server, and, after it is running, re-execute the command. If the standby-less system switchover (effects distributed) facility is being used, take the following actions:
- If the unit where the system manager resides is running
The corresponding server might be temporarily stopped due to a system switchover. Use the pdls command to examine the server status information, and, after it is running, re-execute the command.
- If the unit where the system manager resides is stopped
(a) If executed with the -u option specified The corresponding server is not running on the unit specified in the -u option. Use the pdls command to investigate the unit that the server is running on, and specify the unit identifier of the unit in the -u option. (b) If executed without the -u option specified The corresponding server is not running on a regular unit. Use the pdls command to investigate the unit that the server is running on, and specify the unit identifier of the unit in the -u option.
| -- |
105 | Timeout was detected during command execution. | If the corresponding HiRDB unit is not online, wait until it is placed online and re-execute the command. If the corresponding HiRDB unit is already online and a reason code is displayed by executing the pdlogswap command with the -w option specified, check for any transaction that has been executing for a long time.
- If there is a transaction that has been executing for a long time:
(a) If the transaction cannot be cancelled:
Wait until the transaction has terminated, make sure that the synchronization point dump can be validated, then re-execute the pdlogswap command.
Re-execute the pdlogswap command with a sufficiently large value specified in the -t option so that validation of the synchronization point dump can be delayed until the current transaction has terminated. (b) If the transaction can be cancelled:
Cancel the transaction and re-execute the pdlogswap command.
- If there is no transaction that has been executing for a long time:
Re-execute the pdlogswap command.
| -- |
106 | Shared memory cannot be used. | Take action appropriate to the system call error message that was output immediately before this message. | -- |
107 | System call error occurred. | Refer to the system call error message that was output immediately before this message to check the cause of the error. | -- |
108 | Specified option is invalid for non-dual log file. | Specify only those options permitted for non-dual log file and re-execute the command. | -- |
110 | Command specification is not valid in the execution environment of the target system. | Check the option specified with -d. Or, check the execution environment of the target system. | -- |
116 | The pdlogswap command with the -w option specified cannot be executed because the system is waiting for validation of a synchronization point dump for the previous pdlogswap command that was executed with the -w option specified. | Check for any transaction that has been executing for a long time.
- If there is a transaction that has been executing for a long time:
(a) If the transaction cannot be cancelled:
Wait until the transaction has terminated, make sure that the synchronization point dump can be validated, then re-execute the pdlogswap command.
Re-execute the pdlogswap command with a sufficiently large value specified in the -t option so that validation of the synchronization point dump can be delayed until the current transaction has terminated (b) If the transaction can be cancelled:
Cancel the transaction and re-execute the pdlogswap command.
- If there is no transaction executing for a long time:
Re-execute the pdlogswap command.
| -- |
201 | File name is invalid. | Consider the following causes:
- An invalid character was specified in the path name.
- The length of the HiRDB file name exceeds the maximum (30 characters).
Specify the correct file name and re-execute the command. | -- |
202 | The specified HiRDB file system area was not found. | Check the specified HiRDB file system area and re-execute the command. | -- |
203 | The specified device has not been initialized for the HiRDB file system. | Check the file name. If the file name is correct, initialize the device for the HiRDB file system. | -- |
204 | Specified file already exists. | Check the file name. If the file name is correct, delete the file with the pdlogrm command and re-execute the pdloginit command. | -- |
205 | Area necessary for file creation cannot be allocated. | Use a different device to create the file. Or, delete any unneeded file or back up the file, re-create the HiRDB file with the pdfmkfs command, restore the file, then create the file. | Re-estimate the file size. |
206 | Maximum number of files specified during file system initialization was exceeded. |
207 | In UNIX, the number of character special files that can be opened has been exceeded. In Windows, the number of direct disks that can be opened has been exceeded. | -- |
208 | There is no access privilege for the specified HiRDB file system area. | Execute the command with a user ID that has access privilege for the specified HiRDB file system area. | Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example). |
209 | I/O error occurred while accessing a log file in the HiRDB file system. | Investigate the cause of the I/O error and take appropriate action. If the the pdloginit command could not be executed, create the HiRDB file system area on a different disk device or partition from the one where the I/O error occurred, and re-execute the command. | -- |
210 | HiRDB file system versions do not match. | Re-create the HiRDB file system. | -- |
211 | There is no access privilege for the specified file. | Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored. | Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example). |
212 | Specified file was not found. | Specify the correct file name and re-execute the command. | -- |
216 | Specified file is not a log file or synchronization point dump file. |
217 | Specified file is not an unload log file. |
221 | Lock segment shortage occurred. | -- | Re-evaluate the number of record lock segments specified during construction of the OS system. |
222 | Attempt was made to use a log file, but it was being used by another process. | Check if the file specified in the command is being used by another process. Re-execute the command, if necessary. If one of the following commands was executed while HiRDB was active, also take the action called for:
- pdlogopen, pdlogcls, or pdlogswap command
Re-execute the command.
- pdlogchg command
A mismatch between the memory status and the system log file's state may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.
- pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.
| -- |
224 | Specified file is on unload wait status. | Check the file name. If the file name is correct, either place the file on unloaded status with the pdlogunld or pdlogchg command or re-execute pdlogrm specifying the -u option. | -- |
225 | Attempt made to create a file in an HiRDB file system area that is not for system files. | Check the usage of the HiRDB file system area by specifying the HiRDB file system area name in the pdfstatfs command, and create the file in an HiRDB file system area for system files. | -- |
227 | Specified file is on extracting status. | Check the file name. If the file name is correct, either use the pdlogchg command to place the file on extraction-completed status or re-execute the pdlogrm command with the -u option specified. | -- |
228 | The specified file is in the overwriting denied status for online reorganization. | Re-evaluate the file name. If the file name is correct, use the pdlogchg command to put the file in the overwriting permitted status for online reorganization, or execute the pdlogrm -u command. | -- |
301 | Specified file already exists. | Use an operating system command to re-execute the command with the correct file name. | -- |
302 | Specified file is a directory. |
303 | Error occurred while opening an unload log file. | Refer to the open system call error message that was output immediately before to check the cause of the error. | -- |
304 | Error occurred while closing an unload log file. | Refer to the close system call error message that was output immediately before to check the cause of the error. | -- |
305 | Error occurred while accessing an unload log file. | Refer to the write system call error message that was output immediately before to check the cause of the error. | -- |
306 | Error occurred in an unload log file created in a HiRDB file system area. | Check the cause of the error based on the preceding KFPS01300-E message. | -- |
307 | Error occurred while reading an unload log file. | Investigate the error on the basis of the error message for the read system call output immediately before. | -- |
403 | Definition file open error occurred. | Refer to the definition file open error message that was output immediately before to check the cause of the error. | -- |
404 | Analysis file open error occurred. | Refer to the analysis file open error message that was output immediately before to check the cause of the error. | -- |
405 | Error was detected during definition analysis processing. | Check the cause of the error on the basis of the analysis error message that was output immediately before. | -- |
410 | A duplication error was detected in the file group name of the system log file during definition analysis processing. | Check if the file group name specified in the -g option of the pdlogadpf operand was duplicated. | -- |
413 | A limit error was detected in the file group count of the system log file during definition analysis processing. | Check if the pdlogadpf operand number exceeds the limit of the file group count for system log files. | -- |
414 | Number of valid log file group definitions is less than the minimum number of generations necessary to start the system. A valid log file group definition is an error-free pdlogadfg operand for which ONL is specified. | Revise the pdlogadfg operand for the corresponding HiRDB server definition and restart the system. | -- |
417 | An error was detected during definition analysis processing. | Find the error cause based on the analysis error message output immediately before this message. | -- |
701 | File group was not found. | Check the status of the file group with the pdlogls command and re-execute the command, if necessary. If a definition file analysis error has been output immediately before this message, refer to that message to check the cause of the error. | -- |
702 | A file group failed to open. | Refer to the KFPS01200-E or KFPS01201-E message that was output to the log file to check the cause of the error, and take an appropriate action. | -- |
703 | A file group failed to close. |
704 | Specified file group has already been opened. | Check the status of the file group with the pdlogls command, specify the correct file group name, then re-execute the command. | -- |
705 | Specified file group has already been closed. |
706 | Specified file group cannot be closed. |
707 | Specified file group is being used for system recovery processing or by the pdlogunld or pdlogchg command. | Check the status of the file group with the pdlogls command, specify the correct file group name, then re-execute the command. | -- |
708 | Specified file group cannot be closed, because there would be no overwritable file group if it is closed. | -- | -- |
709 | File open processing was cancelled, because the same generation of the file group already exists. | Delete the physical files comprising the corresponding file group with the pdlogrm command and re-create the physical file with the pdloginit command | -- |
710 | Specified file group is the current file group. | Check the status of the file group with the pdlogls command and re-execute the command, if necessary. | -- |
712 | The system log file could not be closed because the percentage of free system log files was less than the warning value. | Increase the percentage of free system log files, and then re-execute the pdlogcls command. For details about the free space percentage for system log files, see the HiRDB Version 9 System Operation Guide. | -- |
1101 | An attempt to open the target file failed. | Follow the instructions in the KFPS01240-E message. | -- |
1301 | Specified resource group name was not found. | Check the resource group name with the pdlogls command. | -- |
1601 | There is no log file that can be unloaded or whose status can be changed. | Check the specified file group name. | -- |
1602 | Missing block was detected in a log file. | The log file may have been damaged. Cancel unloading of the corresponding file group and contact the HiRDB administrator. | The system log file cannot be unloaded. Acquire a backup so that the database can be recovered without using the unload log of that system log file. Also, to help with investigating the cause, acquire the system log file for which the unload failed, and contact the customer support center. |
1603 | Specified file group has already been unloaded. | Check the specified file group name. If the specified file group is correct and the pdlogls command indicates that this file group is waiting to be unloaded, the previously entered pdlogunld or pdlogchg command may have caused an error that prevented the status from being updated in memory (the unload processing itself was successful). In such a case, close the affected file group with the pdlogcls command, then reopen the file group with the pdlogopen command to correct the status mismatch. | -- |
1604 | Specified -n option value in the pdloginit command is outside the range 12 to104,857,600. | Specify a value in the -n option in the range 12 to 104,857,600 and re-execute the pdloginit command. | -- |
1606 | During the execution of the command, HiRDB assumed one of the following states:
- HiRDB starting processing
- HiRDB terminating processing
- HiRDB running
This command is terminated to protect the system log file. | -- | Use the pdls -d svr command to check the operating status of HiRDB. If HiRDB is shut down, re-execute the pdlogchg or pdlogunld command. If this message is output during the execution of the pdlogunld command, any unload log file that was created cannot be used for database recovery. |
1607 | The specification pd_log_unload_check=N is specified and HiRDB is operating; the status of the file group cannot be changed. | -- | Specify the -R option in the pdlogchg command; specify the -f option in the pdlogunld command. |
1609 | Specified file group is in extraction-completed status. | Check the name of the specified file group. If the specified file group is correct and the pdlogls command displays that this file group is on extracting status, an error may have occurred during the previous pdlogchg command execution that makes it impossible to update the status in memory. In such a case, this conflict can be resolved by closing the corresponding file group with the pdlogcls command and then reopening it with the pdlogopen command. | -- |
1612 | The value specified in the -l option of the pdloginit command is out of the 1024 to 4096 range. | Change the value specified in the -l option to fall within the 1024 to 4096 range and re-execute the pdloginit command. | -- |
1613 | The sector length of the HiRDB file system area, the specified record length, or the specified record count is invalid. | Check the cause of the error based on a preceding KFPS01207-E message. | -- |
1614 | The name of a HiRDB file specified in the pdloginit command is invalid. | Specify the system log file name using the absolute path name, and then re-execute the pdloginit command. | -- |
1615 | The applicable file group is in the overwriting permitted status for online reorganization. | Re-evaluate the specified file group name. If the specified file group name is correct and the pdlogls command indicated this file group is in the overwriting denied status for online reorganization, the previously executed pdlogchg command may have caused an error that prevented updating of the memory status. In this case, close the applicable file group using the pdlogcls command, and then open the group using the pdlogopen command (the mismatch between the files and memory is resolved). | -- |
1616 | Even though pd_large_file_use=N is specified, an attempt was made to use the pdloginit command to create a system log file in a HiRDB file system area created with the pdfmkfs -a command. | -- | If you want to create a file in a HiRDB file system area created with the pdfmkfs -a command, specify Y in pd_large_file_use, or omit the specification. |
1660 | The directory that is the output target of the unload log file for the automatic log unloading facility cannot be used. | When a directory is specified as the output target for the unload log file: There is a shortage of free disk space in the unload log file creation directory, or a disk failure occurred. Allocate more free disk space, or recover from the disk failure.
When a HiRDB file system area is specified as the output target for the unload log file: The unload log file cannot be created, for reasons such as a shortage of space in the HiRDB file system area, or the number of extensions reaching its limit. After saving the unload log file, for example by making a backup of the HiRDB file system area with the pdfbkup command, use the pdfmkfs command to re-create the HiRDB file system area. | -- |
1664 | The command cannot be executed on a log application site. | The aa....aa command can be executed only on a transaction execution site. Check the site that corresponds to command execution. | -- |
1670 | None of the unload log file creation directories can be used. | Take action by referring to the reason code of the KFPS01152-W message. | -- |
1676 1677 | Automatic log unloading facility cannot be used. | - If HiRDB was started normally:
- Check if the following operands were specified in the server definition of the applicable server when HiRDB was started:
- pd_log_auto_unload_path
- pd_log_unload_check=Y
- If HiRDB was shut down by planned termination or was restarted:
- Check if the automatic log unloading facility was used successfully during the previous operation of HiRDB. Also check if the following operand was specified in the server definition of the applicable server when HiRDB was started:
| -- |
1678 | Automatic log unloading facility is already running. | Use the pdlogatul command to check if the automatic log unloading facility is running. | -- |
1679 | Automatic log unloading facility has already stopped. | Use the pdlogatul command to check if the automatic log unloading facility has stopped. | -- |
1680 | During monitoring for automatic log unloading stop, the automatic log unloading facility stopped for one of the following reasons:
- None of the unload log file creation directories can be used.
- Unload log file name is not unique.
- Resource shortage occurred.
| Determine why the automatic log unloading facility stopped based on other output messages, take appropriate action, and then restart the automatic log unloading facility (by executing the pdlogatul -b command). Then, re-execute the pdlogatul -t -w command. | -- |
1681 | Because a timeout occurred during monitoring for automatic log unloading stop, monitoring was halted and the automatic log unloading facility was stopped. | Check if an I/O delay has occurred on the disk where the unload log creation directory is located. Then, restart the automatic log unloading facility (by executing the pdlogatul -b command) and re-execute the pdlogatul -t -w command. | -- |
- --: Not applicable
KFPS01281-E E
Invalid command format.
- Command format is invalid.
- S: Cancels command execution.
- O: Check the command format and re-execute the command.
KFPS01282-E E
bb....bb specified with aa option not found.
- bb....bb specified in option aa was not found.
- aa: Option code:
- -g: Option for specifying a file group name
- bb....bb: File group name
- S: Cancels command execution.
- O: Specify the correct option argument and re-execute the command.
KFPS01283-W E
Minor error occurred during aa....aa command execution. reason code=bbbb-cc
- A minor error occurred while executing command aa....aa.
Command processing terminated normally, but the minor error indicated by the reason code occurred during execution. - aa....aa: Name of the command resulting in the minor error
- bbbb: Reason code
- cc: HiRDB internal code
- S: Resumes processing.
- O: Take action appropriate to the reason code, as listed below, and re-execute the command, if necessary.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Operator's action |
---|
1102 | Some of the files to be opened could not be opened (in this case, the opening of successfully opened files is valid). | If necessary, take action according to the KFPS01240-E message output to the log file. |
1103 | All files to be opened are already open. | If necessary, use the pdlogls command (specify the -e option) to check the status of the files comprising the file group, specify the correct file group name, A system or B system, and then reenter the command. |
1104 | All files to be closed are already closed. |
KFPS01284-I E
Usage: pdlogsync -d sys [-s servername] [-w [-t wait time]]
- The pdlogsync command contains an input format error (HiRDB/Single Server).
- S: Terminates processing.
- O: Enter the correct command.
KFPS01284-I E
Usage: pdlogsync -d sys -s servername [-w [-t wait time]]
- The pdlogsync command contains an input format error (HiRDB/Parallel Server).
- S: Terminates processing.
- O: Enter the correct command.
KFPS01285-E E
Command unable to be executed due to swap processing.
- Command cannot be executed because the system log file is being processed.
- S: Cancels command processing.
- O: Re-execute the command after swap processing is completed.
KFPS01286-E E
Unable to perform swapping because no standby log file group is available.
- Files cannot be swapped because there is no standby log file group.
- S: Cancels the swap command.
- O: Place a file group on unloaded status with the pdlogunld or pdlogchg command in order to provide a standby log file group. Or, place a reserve log file on online status with the pdlogopen command in order to provide a standby log file group. Then, re-execute the command, if necessary.
KFPS01290-I E
Usage: pdlogswap -d sys [-s server_name] [-w [-t wait_time]]
- Displays the format of the pdlogswap command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
- S: Resumes processing.
KFPS01290-I E
Usage: pdlogswap -d sys -s server_name [-w [-t wait_time]]
- Displays the format of the pdlogswap command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
- S: Resumes processing.
KFPS01291-I E
Usage: pdlogls -d {sys [-s server_name] [-g file_group_name] [-e] [-C [-H]] [-E]|spd [-s server_name] [-g file_group_name] [-e] [-l]}
- Displays the format of the pdlogls command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01291-I E
Usage: pdlogls -d {sys -s server_name [-u unit_id] [-g file_group_name] [-e] [-C [-H]] [-E]|spd -s server_name [-g file_group_name] [-e] [-l]}
- Displays the format of the pdlogls command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01292-I E
Usage: pdloginit {-d sys [-s server_name] -f file_name -n record_count [-l record_size] |-d spd [-s server_name] -f file_name -n record_count}
- Displays the format of the pdloginit command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01292-I E
Usage: pdloginit {-d sys -s server_name [-u unit_id] -f file_name -n record_count [-l record_size] | -d spd -s server_name [-u unit_id] -f file_name -n record_count} [-D]
- Displays the format of the pdloginit command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01293-I E
Usage: pdlogrm -d sys|spd [-s server_name] -f file_name [-u]
- Displays the format of the pdlogrm command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01293-I E
Usage: pdlogrm -d sys|spd -s server_name [-X unit_id] -f file_name [-u] [-D]
- Displays the format of the pdlogrm command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01294-I E
Usage: pdlogopen -d sys|spd [-s server_name] -g file_group_name [-a] [-b]
- Displays the format of the pdlogopen command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01294-I E
Usage: pdlogopen -d sys|spd -s server_name -g file_group_name [-a] [-b]
- Displays the format of the pdlogopen command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01295-I E
Usage: pdlogcls -d sys|spd [-s server_name] -g file_group_name [-a] [-b]
- Displays the format of the pdlogcls command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01295-I E
Usage: pdlogcls -d sys|spd -s server_name -g file_group_name [-a] [-b]
- Displays the format of the pdlogcls command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01296-I E
Usage: pdlogunld -d sys [-s server_name] -g file_group_name [-o output_file_name] [-n] [-f] [-k file_kind] [-i init_size [,expand_size]]
- Displays the format of the pdlogunld command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01296-I E
Usage: pdlogunld -d sys -s server_name [-u unit_id] -g file_group_name [-o output_file_name][-n] [-f] [-k file_kind] [-i init_size [,expand_size]]
- Displays the format of the pdlogunld command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01297-I E
Usage: pdlogchg{-d sys [-s server_name] -g file_group_name [-R|-G] | -z log_point_information [-x host_name]}
- Displays the format of the pdlogchg command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.
KFPS01297-I E
Usage: pdlogchg {-d sys -s server_name [-u unit_id] -g file_group_name [-R|-G] | -z log_point_information [-x host_name]}
- Displays the format of the pdlogchg command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.
KFPS01299-I E
Usage: pdlogatul -d sys [-s server_name][-b| -t| -i]
- Displays the format of the pdlogatul command in a HiRDB/Single Server. This message is output when the command is entered incorrectly.
- S: Continues processing.
KFPS01299-I E
Usage: pdlogatul -d sys -s server_name [-b| -t| -i]
- Displays the format of the pdlogatul command in a HiRDB/Parallel Server. This message is output when the command is entered incorrectly.
- S: Continues processing.
KFPS01300-E E+L
aa....aa error occurred, file=bb....bb
- An I/O error occurred in an unload log file created in a HiRDB file system area.
- aa....aa: Error detail:
- Close: File close error
- Open: File open error
- Read: File loading error
- Write: File write error
- bb....bb: Name of the unload log file in which the error occurred
- If the path name of the unload log file exceeds 150 characters, the last 150 characters of the unload log file path name are output.
- S: Continues processing.
- O: Take action appropriate to the message that is output after this message. Eliminate the cause of the error, and then re-execute the command.
KFPS01301-E E+L
System call error, func=aa....aa, errno=bb....bb
- A system call error occurred in an unload log file created in a HiRDB file system area.
- aa....aa: Name of the system call in which the error occurred
- bb....bb: errno of the system call in which the error occurred
- S: Terminates processing.
- O: Check the error number (errno: external integer variable indicating error status) and refer to errno.h or to the applicable OS manual to correct the error. Then, re-execute the pdlogunld command.
KFPS01302-E E+L
File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)
- An error occurred during an I/O operation for an unload log file created in a HiRDB file system area.
- aa....aa: Error cause:
- File-format:
- Specified file format does not match the actual file format.
- File-lock:
- Specified file is read/write-disabled because it has been locked by another utility.
- Invalid-device:
- The entry type of the specified file is invalid. Entry types that can be identified by the system consist of a single alphabetic character enclosed in parentheses. In UNIX, this alphabetic character is the same as the entry for the mode output using the OS ls -l command.
- Invalid-environment:
- Because the setting obtained by the uname system call is invalid, a streaming tape device cannot be used (check that the OS has been installed correctly or that the OS version is compatible with the HiRDB and related products).
- Invalid-parameter:
- Combination of specified parameters is invalid.
- Invalid-path:
- Path name of the unload log file is invalid.
- Invalid-permission:
- Permission for the specified file is invalid.
- No-file:
- File that is to be opened for loading does not exist, or file that was being written was erased.
- No-space:
- There is not enough space in the file to be written (check the file size or if the maximum number of size increases has been reached).
- Unmatch-entry:
- For a file with a header, the entry in the header does not match the specification in the control information file (the mismatching entry name is displayed in parentheses).
- bb....bb: Name of the system function in which the error occurred
- If the error occurred in a HiRDB file system area, the function name of the HiRDB file system area is displayed. Otherwise, *** is displayed.
- cc....cc: Error number returned by the system function (errno)
- If the error occurred in a HiRDB file system area, the error code of the HiRDB file system area is displayed. For details on the error codes, see 5.1 Error codes returned from HiRDB file system access requests.
- In all other cases, 0 is output.
- dd....dd: Name of the source file and row number in which the error was detected
- S: Terminates processing.
- O: After determining the error cause and error number and correcting the error, re-execute the pdlogunld command.
KFPS01303-E E+L
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc
- An error occurred during access to an unload log file created in a HiRDB file system area.
- aa....aa: Error detail:
- close: File close error
- create: Fire creation error
- expand: File expansion error
- fstat: File information acquisition error
- open: File open error
- read: File read error
- write: File write error
- bb....bb: Error code
- For details on the error codes, see 5.1 Error codes returned from HiRDB file system access requests.
- cc....cc: Name of the unload log file in which the error occurred
- If the path name of the unload log file exceeds 150 characters, the last 150 characters of the unload log file path name are output.
- S: Terminates processing.
- O: Refer to the error code to eliminate the cause of the error, then re-execute the command.
KFPS01362-I L
Log block reading started, type=aaa(bb....bb), read start point=cc....cc, dd....dd, ee....ee, ff....ff, gg....gg
- Reading of the system log has started.
- aaa: File type
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: File group name of the system log file at read startup
- dd....dd: Run ID of the system log at read startup
- ee....ee: User run ID of the system log at read startup
- ff....ff: Generation number of the system log at read startup
- gg....gg: Block number of the system log at read startup
- S: Continues processing.
KFPS01363-I L
Log block reading completed, type=aaa(bb....bb), read end point=cc....cc, dd....dd, ee....ee, ff....ff, gg....gg
- Reading of the system log has finished.
- aaa: File type
- sys: System log file
- bb....bb: HiRDB server name
- cc....cc: File group name of the system log file at read completion
- dd....dd: Run ID of the system log at read completion
- ee....ee: User run ID of the system log at read completion
- ff....ff: Generation number of the system log at read completion
- gg....gg: Block number of the system log at read completion
- Note: If no log blocks are input, ******** is displayed for cc....cc, dd....dd. ee....ee, ff....ff, and gg....gg.
- S: Continues processing.
KFPS01380-I E
Usage: pdlogucat [-k std|csv] unload_log_file_name
- The usage of the pdlogucat command is displayed. This is output if there is an error in the command format.
- S: Terminates processing.
KFPS01390-I L
Unable to expand sys(aa....aa) log file, file group=bb....bb, system A/B=c, reason=dddd
- The system log file cannot be expanded.
- aa....aa: HiRDB server name
- bb....bb: File group name of the system log file
- c: System classification
- a: System A
- b: System B
- dddd: Reason code
- S: Continues processing.
- O: Take corrective action by referring to the operator action that corresponds to the appropriate reason code in the following table.
- Action
- Take corrective action by referring to the HiRDB administrator action that corresponds to the appropriate reason code in the following table.
Reason code | Explanation | Operator action | HiRDB administrator action |
---|
101 | A memory shortage occurred. As a result, this system log file will no longer be expanded. | -- | Check the required amount of memory again. |
205 | The disk is full. | -- | Free up disk space as necessary. |
209 | An I/O error occurred. As a result, this system log file will no longer be expanded. | Refer to the messages output before and after this message, identify the cause of the error, and then take corrective action. | To allow the system log file to be expanded, take one of the following actions:
- Execute the pdlogcls command to close the system log file.
- Execute the pdfmkfs -a command to re-create HiRDB file system area.
- Execute the pdloginit command to re-create the system log file.
|
221 | A lock segment shortage occurred. As a result, that system log file will not be expanded. | -- | Revise the number of lock segments specified for OS system startup. |
1690 | The HiRDB file system area that contains this system log file cannot be expanded (this HiRDB file system area was created by specifying the pdfmkfs command without the -a option). As a result, this system log file will no longer be expanded. | -- | To allow the system log file to be expanded, take one of the following actions:
- Execute the pdlogcls command to close the system log file.
- Execute the pdfmkfs -a command to re-create HiRDB file system area.
- Execute the pdloginit command to re-create the system log file.
|
1691 | The initial size of the system log file exceeds the maximum expansion size specified in the pd_log_auto_expand_size operand. As a result, this system log file will no longer be expanded. | Use the pdfls command to check the number of records of corresponding system log files. | Check the following specification values, and revise them if necessary.
- -n option of pdloginit command
- Maximum expansion size of pd_log_auto_expand_size operand
|
1692 | The maximum capacity of the system log file has been reached. As a result, this system log file will no longer be expanded. | -- | If necessary, revise the total capacity and generation number of the system log file. |
1694 | The maximum expansion capacity of the system log file has been reached. As a result, this system log file will no longer be expanded. | -- | If necessary, revise the maximum expansion size specified in the pd_log_auto_expand_size operand. |
- Legend:
- --: Not applicable.
KFPS01391-I L
Sys(aa....aa) log files expansion bb....bb, {output file name=cc....cc|expanded size=dd....dd}
- Starts or terminates automatic extension of the system log file. Displays cc....cc and dd....dd when starting or terminating automatic extension, respectively.
- aa....aa: HiRDB server name
- bb....bb: Processing type
- start: Processing start
- complete: Processing termination
- cc....cc: Status information file name of the system log file
- When automatic extension starts, the status information file of the system log file is output under %PDDIR%\spool\pdjnlinf\.
- dd....dd: Number of expanded records
- When multiple file groups automatically expand, the sum of the number of records for each expanded file group is displayed.
- If the number of expanded records is 1,000,000,000 or greater, K is added, and the numerical values obtained with the following formula are displayed.
sum of number of records of each expanded file group
1000![[Figure]](figure/zueng011.gif)
- S: Continues processing.
KFPS01392-W L
Unable to use sys(aa....aa) log files expansion, reason code=bbbb
- The system log file automatic extension facility cannot be applied on this server.
- aa....aa: HiRDB server name
- bbbb: Reason code
- S: Continues processing.
- Action
- Take action according to the reason code, as listed below:
Reason code | Explanation | HiRDB administrator action |
---|
1693 | N is specified in the pd_large_file_use operand, so the automatic extension facility has been disabled. | Either specify Y in the pd_large_file_use operand or omit the specification. |
KFPS01393-E L
Unable to expand sys(aa....aa) log file, file group=bb....bb, code=cccc
- An attempt was made to expand the system log file. However, expansion was not possible for one of the following reasons, and processing was interrupted.
(1) If the KFPS01390-I message was output prior to this message: - The error cause is displayed in message KFPS01390-I.
- (2) If the KFPS01390-I message was output prior to this message:
- Input / output processing to the system log file was centralized, for a reason such as the execution of an update transaction.
- A communication error occurred.
- A memory shortage occurred.
- aa....aa: HiRDB server name
- bb....bb: System log file group name
- cccc: HiRDB internal code
- S: Terminates abnormally.
- Action
- If the KFPS01390-I message was output prior to this message, take the action indicated in that message.
- If the KFPS01390-I message was not output, take corrective action according to When a HiRDB (unit) terminates abnormally due to a system log file shortage in the HiRDB Version 9 System Operation Guide.
KFPS01800-I L
Now starting HiRDB unit aaa
- Indicated HiRDB unit is being started.
- aaaa: Unit identifier
- S: Resumes HiRDB system startup processing.
KFPS01801-E E+L
Unable to start HiRDB unit due to improper operational environment. reason code=aa....aa
- A HiRDB unit cannot be started, because its operating environment has not been set up.
- aa....aa: Cause of the startup error
- S: Cancels HiRDB startup processing.
- Action
- Take the following actions, and then start HiRDB. Contact the customer support center if a reason code other than the following is output:
Reason code | Cause | Action |
---|
ENV_PDDIR | The environment variable PDDIR is not set, or the directory it resides in cannot be referred to. | Set environment variable PDDIR. |
MEMORY | There is a process private memory or shared memory shortage. | See the descriptions for SHM_EINVAL, SHM_ENOMEM, or SHM_ENOSPC. |
PAUSE | An error occurred such that HiRDB processing could not continue, and the process server process was suspended. | Refer to the message output immediately before this message in the command input window and the event log (in UNIX, syslogfile). Alternatively, refer to the corrective actions in message KFPS00715-E. |
PROGRAM | There are no prerequisite programs. | Install the prerequisite programs. |
RPL_FILE | There is no data linkage file for HiRDB Datareplicator, the user does not have access privileges, or the content is invalid. | See the KFPS01889-E message output immediately before this message to recover from the error in the data linkage file for HiRDB Datareplicator. Representative error factors and actions:
- function-value = SYSTEM CALL(stat) ERROR, error = 2
There is no data linkage file. If there is an error in the value specified in the pd_rpl_hdepath operand, which is the name of the HiRDB Datareplicator directory where data is to be extracted, modify the pd_rpl_hdepath operand, and then restart HiRDB. If the disk to be used for the data linkage file is unmounted, remount the file and restart HiRDB Datareplicator and HiRDB. If there is no data linkage file, synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB.
- function-value = SYSTEM CALL(open) ERROR, error = 13
The user does not have access privileges to the data linkage file. Check your access privileges to the data linkage file. If you do not have access privileges, establish access privileges, and then restart HiRDB Datareplicator and HiRDB.
- function-value = FILE ERROR
The data linkage file is invalid. Synchronize to the target database, re-create the data linkage file, and then re-execute HiRDB Datareplicator and HiRDB.
|
RPL_INSTALL | Possible causes:
- An error such as a failure on the HiRDB Datareplicator installation disk prevents access to the HiRDB Datareplicator installation directory.
- The HiRDB addressing mode and the HiRDB Datareplicator addressing mode do not match.
- HiRDB Datareplicator is not installed.
| Check the following items and take appropriate action:
- Check if an error such as a failure on the HiRDB Datareplicator installation disk on a server machine with the unit that output this message prevents access to the HiRDB Datareplicator installation directory. If an error is found, eliminate the cause, and then re-execute.
- Check if the addressing mode of the unit that output this message and the address mode of HiRDB Datareplicator match. If they do not match, replace HiRDB Datareplicator with a HiRDB Datareplicator that has the same address mode as the HiRDB addressing mode.
- Check if HiRDB Datareplicator is installed on the server machine containing the unit that output this message. If HiRDB Datareplicator is not installed, install it, and then re-execute.
|
RPL_STOP | HiRDB Datareplicator suspended data linkage to HiRDB. | Find the cause of data linkage being stopped and eliminate the problem. Then, start HiRDB Datareplicator. For details about how to locate the cause, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide. |
SETUP | In UNIX, the system is not set up. In Windows, the HiRDB service has stopped. | In UNIX, use the pdsetup command to set up HiRDB. In Windows, the HiRDB service might not be started. Start the service, then restart HiRDB. |
SHM_EINTR | A signal was received during the shared memory securing process. | Check the cause of the signal, take appropriate action, and then restart HiRDB. |
SHM_EINVAL | In UNIX The shared memory size exceeded the system limit. In Windows The size of the installation drive is insufficient, so work files for shared memory could not be allocated. | In UNIX Increase the maximum segment size in system shared memory, and then re-create the kernel. In Windows On the HiRDB installation drive, allocate sufficient free space for the shared memory. |
SHM_EMFILE | The number of open files exceeded the number of file tables the system can open. | Decrease the number of open files or increase the number of file tables the system can open and re-create the kernel. |
SHM_ENOMEM | In UNIX Memory equal to the shared memory size was not found in the system. In Windows Consider the following causes:
- There is insufficient memory in the system to equal the size of the shared memory.
- If a paging file was allocated at the location where the shared memory was allocated, the HiRDB service was not started.
| In UNIX Increase system memory. In Windows A KFPO00107-E or KFPO00113-E message was output before this message was output. Refer to the explanation given in the KFPO00107-E or KFPO00113-E message and take appropriate action. |
SHM_ENOSPC | In UNIX The number of shared memory identifiers exceeds the maximum defined in the system. In Windows The installation drive does not contain a disk area to allocate only the shared memory. | In UNIX Decrease the number of shared memory buffers or increase the maximum number of shared memory identifiers and re-create the kernel. In Windows A KFPO00107-E or KFPO00113-E message was output before this message was output. Refer to the explanation given in the KFPO00107-E or KFPO00113-E message and take appropriate action. |
SHM_EOVER | The shared memory size exceeded 2 GB. Detail code:
- lck: Lock server
- trn: Transaction control
- jnl: Log server
- tjl: Transaction log server
- aud: Security audit
- controlNo display: Unit controller
| 32 bit mode See the section on formulas for calculating shared memory used by unit controllers in the HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the shared memory for all unit controllers less than 2 GB.
- lck
Decrease the value of the pd_max_access_tables, pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, pd_ha_max_act_guest_servers, pd_lck_hash_entry, pd_lck_pool_size, pd_lck_pool_partition, pd_fes_lck_pool_size, pd_fes_lck_pool_partition, or pd_max_open_holdable_cursors operand.
- trn
Decrease the value of the pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, or pd_ha_max_act_guest_servers operand. Alternatively, decrease the number of front-end servers and the number of back-end servers.
- jnl
Decrease the value of the pd_log_rec_leng, pd_log_max_data_size, pd_log_write_buff_count, pd_stj_buff_size, pd_max_users, pd_max_reflect_process_count, pd_ha_max_act_guest_servers, pdlogadfg -d sys, pdlogadfg -d spd, or pdlogadpf -d spd operand. Alternatively, decrease the number of servers in the unit with the error.
- tjl
Decrease the value of the pd_log_rec_leng, pd_log_max_data_size, pd_log_rollback_buff_count, pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, or pd_ha_max_act_guest_servers operand.
- aud
Decrease the value of the pd_aud_async_buff_size or pd_aud_async_buff_count operand.
64 bit mode
- jnl
See the section on formulas for calculating shared memory used by unit controllers in the HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the shared memory for each server less than 2 GB. For HiRDB/Parallel Server, calculate using 1 as the value for number-of-servers-in-unit+D and number-of-FES-in-unit.
|
SHM_CALC *** | An internal conflict occurred during calculation of the shared memory size. *** indicates the HiRDB internal information. | Save the files under %PDDIR%\spool, save the event log (in UNIX, syslogfile), and contact the customer support center. |
VERSION | The operating system version does not match. | Replace the current version of the operating system with the correct version. |
AHA_INSTALL | HiRDB Advanced High Availability is not set up. | HiRDB Advanced High Availability is necessary when using the standby less system switchover facility. Either introduce HiRDB Advanced High Availability or delete the pd_ha_agent operand. |
AHA_VR | The system definition specifies that the standby-less system switchover (effects distributed) facility be used, but the version of the HiRDB Advanced High Availability that is set up in the server machine that allocated the unit that output the message is invalid. | Take one of the following actions:
- See the KFPS05620-I message, and check the version of the HiRDB Advanced High Availability that has been set up. If the version is incorrect, set up the correct version of HiRDB Advanced High Availability and re-execute.
- Reconsider the use of the standby-less system switchover (effects distributed) facility.
|
NONALTSVUNIT | Can only be executed by an alternate BES unit. | Execute using an alternate BES unit. |
NRF_INSTALL | A recovery-unnecessary front-end server is set (there is a front-end server with the -k stls option specified in the pdstart operand), but HiRDB Non Recover FES is not specified on the server machine with the unit that output the message. | To set a recovery-unnecessary front-end server, HiRDB Non Recover FES is required. Introduce HiRDB Non Recover FES, or remove the pdstart operand with the -k stls option. |
DRL_INSTALL | In the system definition pd_rise_pairvolume_combination operand, syssync is specified, but HiRDB Disaster Recovery Light Edition is not set up in the server of the unit that output the message. | Take one of the following actions:
- Determine whether HiRDB Disaster Recovery Light Edition is installed, and if it is not installed, install it.
- Determine whether HiRDB Disaster Recovery Light Edition is set up in the HiRDB working directory, and if it is not set up, execute the pdopsetup command to set it up.
- Reconsider whether Real Time SAN Replication with the log-only synchronous method is to be used. If Real Time SAN Replication with the log-only synchronous method is not to be used, specify other than syssync in the system definition pd_rise_pairvolume_combination operand.
|
RECOVERY | The possible causes are as follows:
- You executed the command pdstart -r -t, and then executed the command pdstart -r -t [-q] on the standby system of a unit running with the shared resource automatic activation facility enabled.
- You executed the command pdstart -r -t in a standby-less system switchover (1:1) configuration, and then executed the command pdstart -q -c on a unit running with the shared resource automatic activation facility enabled.
| If the running HiRDB system has already been started with the command pdstart -r, execute recovery processing on the running system. If the running HiRDB system was started normally, terminate the running HiRDB system normally, and then restart by executing the command pdstart -r -t. |
- Note
- If the reason code is RPL_STOP or RPL_FILE, the KFPS04624-I message showing the server name is output before this message (KFPS01801-E) for each server in which the error occurred.
KFPS01802-E E
Unable to start HiRDB unit because another HiRDB with the same ID operating
- Specified HiRDB unit cannot be started, because a HiRDB with the same HiRDB identifier is running.
- S: Cancels HiRDB startup processing.
- P: Restart after the current HiRDB has terminated. Or, change the HiRDB identifier and restart.
KFPS01803-I L
HiRDB unit aaaa start mode determined. start mode: bb....bb
- The unit startup mode was selected.
- aaaa: Unit identifier
- bb....bb: Startup mode:
- R: Restart
- R(P): Restart after planned termination
- S: Normal startup
- S: Resumes processing.
KFPS01812-E E+L
Error occurred while starting server aa....aa. reason code=bb....bb
- An error occurred while starting server aa....aa.
- aa....aa: Name of the server resulting in the error
- bb....bb: Cause of the error
- COMMUNICATION: Inter-process communication error occurred.
- CONFIGURATION: Error occurred during definition analysis.
- EXIST: Server with the same name or service group name is already running.
- FORK FAILED: Server startup failed.
- LOCK: Lock processing failed.
- MAX PROCESSES: Number of processes exceeded the specified maximum.
- MEMORY: Memory shortage occurred.
- NO RPC ENVIRONMENT: RPC environment has not been started.
- NO SCHEDULER: Scheduler is engaged in termination processing or is inactive.
- NO SERVER: Server terminated (normally or abnormally).
- NO SERVICE PRODUCER: Process server process has not been started.
- PRC ERROR: Error occurred in process server process.
- SCD NOT UP: Scheduler process has not been started.
- SERVER DOWN: Server terminated abnormally.
- SHARED MEMORY: Shared memory could not be secured.
- STOPPING NOW: Server is now terminating.
- VERSION INVALID: Version is invalid.
- S: Continues HiRDB processing. However, terminates HiRDB processing in cases such as HiRDB startup where the HiRDB process can no longer run.
- Action
- Eliminate the cause of the error and restart the server.
- CONFIGURATION: Check the definition.
- COMMUNICATION: Check the cause of the network error.
- FORK FAILED: Check the amount of memory (pd_sds_shmpool_size, pd_dic_shmpool_size, pd_bes_shmpool_size, SHMMAX, for example) and the number of processes (pd_process_count, pd_max_server_process, for example).
- MAX PROCESSES: Check the maximum number of server processes defined in the system common definition.
- MEMORY: In UNIX, check the real memory size or the swap area size. In Windows, check the Windows real memory size or the virtual memory size.
- NO RPC ENVIRONMENT: Check if pd_rpc_open() has been issued.
- NO SERVER: If the server terminated abnormally, check the cause.
- PRC ERROR: Take the same action as for COMMUNICATION or VERSION INVALID.
- SERVER DOWN: Check the cause of abnormal termination of the server.
- SHARED MEMORY: Check the messages output to the event log (in UNIX, syslogfile) before or after this error occurred, and take appropriate action. If this problem recurs, contact the customer support center.
- VERSION INVALID: Check the versions of the libraries and processes.
KFPS01813-I L
Server aa....aa started[ on unit bbbb]
- Server aa....aa has been placed in online mode by unit bbbb. This is output on unit bbbb when the server is activated by the unit that is applying the standby-less system switchover (effects distributed) facility.
- aa....aa: Name of the server whose startup has been completed
- bbbb: Unit identifier of the server activation target unit
- S: Resumes HiRDB processing.
KFPS01814-I L
HiRDB unit aaaa previous operation not terminate normally; perform normal start
- Attempt was made to start HiRDB normally, but HiRDB had not terminated normally at the previous session.
- aaaa: Unit identifier
- S: Starts HiRDB forcibly.
KFPS01815-E E+L
Error occurred in OS while executing aa....aa. function value=bb....bb, errno=cc....cc
- An error occurred in a system function in the operating system.
- aa....aa: Name of the system call or subroutine resulting in abnormal termination
- bb....bb: Return value of the system call or subroutine resulting in abnormal termination
- cc....cc: Value of errno set during abnormal termination
- S: Cancels processing.
- Action
- Check the value of errno and refer to errno.h or to the applicable OS manual to eliminate the cause of the error. For representative errors, see 4.3 System call return codes.
KFPS01818-E E
Stops activating server aa....aa because the server not in halt state
- Server startup was cancelled, because an active server was specified.
- aa....aa: Name of active server
- S: Cancels server startup processing.
- O: Check the name of the server to be started.
KFPS01819-I L
Server aa....aa. failed information. process ID=bb....bb, C-PID=cc....cc(dd....dd), TIME=eeffgg, PROGRAM=hh....hh
- This message provides additional information concerning termination of a server process. This message is not displayed if the server is not connected to a client or if this is an internal server used by HiRDB.
- aa....aa: Name of the terminated server
- bb....bb: Process ID at the terminated server
- cc....cc: Process ID of the client (a UAP or a utility) that was connected to a server process. However, in the following cases, 0 is displayed:
- A server process that is not connected to a client
- A server process that is connected to a client linked to a client library version prior to 04-00
- A server process that is connected to a Type 4 JDBC Driver
- dd....dd: IP address of the client (a UAP or a utility) that was connected to a server process. In the case of a server process that is not connected to a client, 0.0.0.0 is displayed.
- eeffgg: Time (hour, minute, second) the service request was accepted; for a server process that was not connected to a client, 999999 is displayed.
- hh....hh: UAP identification information (this is the UAP name specified in PDCLTAPNAME in the client environment definition. If PDCLTAPNAME is not set, Unknown is displayed. For a utility, the name of the utility command is displayed. If the UAP was running on a utility server process or the UAP identification information cannot be obtained due to an error, this information may be left blank)
- S: Cancels server startup processing.
- O: Check the name of the server to be started.
- Action
- Use this message to investigate the cause of the error indicated by the error message output before this message.
KFPS01820-E E+L
Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e, critical mask=ff....ff, end state=gg....gg, server type=hhh
- Server aa....aa was terminated.
When using the facility for changing a process down message when canceling a transaction (the pd_cancel_down_msgchange operand in the system definition is set to Y or omitted), message KFPS01852-W is output instead of message KFPS01820-E. For details, see Facility for changing the process-down message when a transaction is cancelled in the HiRDB Version 9 System Operation Guide.
Note that the process termination statuses listed below are examples. A process termination status other than these might appear. Value of gg....gg | Explanation |
---|
007f 0009 | A request to forcibly terminate the server process was received. If the pdcancel command was executed, this message was output. Based on the messages that were output before or after this message, investigate the reason that the process received a forcible termination request (including executing the pdcancel command) and take any appropriate action. However, if during execution of a UAP or utility related processes or the units on which the related processes exist abnormally terminate, no other messages except this message are output. |
0003 0083 | A request to forcibly terminate the server process was received. Investigate the reason the process received a forcible termination request from the status of the executed transaction and the messages output before and after this message. Then, take appropriate action. |
0006 0086 0100 0200 0300 0400 0800 | Abnormal termination was due to an abnormality detected during processing. Investigate the cause of the abnormal termination from the messages output before and after this message, and take appropriate action. |
8000 | Due to a memory shortage, process activation failed or the process terminated abnormally. Take one of the following actions:
- Reduce the number of other processes running on the same server machine.
- Increase the swap area.
- Increase the real memory.
- In Windows, another possibility is that a desktop heap shortage has occurred. See the HiRDB Version 9 Installation and Design Guide, and then revise the value specified for the desktop heap.
|
c000 | A connect system call was issued; however, a connection was not established because the destination system was down or there was a network failure. |
c100 | The second and subsequent SQL response transmissions could not be sent because either the destination system was down or there was a network failure. |
c200 | During a transaction in which control was held by the HiRDB client, a timeout was detected by the HiRDB client environment definition PDSWAITTIME. |
c300 | An error occurred at the remote system during communication processing; the remote communication socket was closed. |
c400 | If the client had control and no transaction was being processed, a timeout was detected by the client environment definition PDSWATCHTIME. Or, a timeout was detected in the pd_watch_pc_client_time set in the HiRDB system while connecting a Windows edition of the HiRDB client. |
c500 | Acquisition of special file (FIFO) failed during server startup. |
c600 | The possible causes are as follows:
- The maximum number of transactions that can be processed concurrently by HiRDB has been exceeded.
- There is a server in new transaction scheduling suppressed status.
Use the command pdls -d svr to identify the server in new transaction scheduling suppressed status and eliminate the cause of the error. If there is no server in new transaction scheduling suppressed status, many rollbacks might have occurred. In that case, wait for the rollbacks to be completed, and then re-execute the UAP. |
c700 | Abnormal termination of the client that requested the SQL statement was detected during execution of the SQL statement by the HiRDB server. |
c800 | SQL request transmission failed due to a network failure between the server and the system manager. |
c900 | The second and subsequent SQL request receptions could not be received because a network failure occurred between the source and the system manager. |
d000 | Because the parent process was forcibly terminated during processing of a transaction, the child process was forcibly terminated. |
d100 | Server processing was canceled because UAP processing did not terminate within the monitoring time limit set in the PDSWAITTIME, PDSWATCHTIME, or PDCWAITTIME client environment definition. Alternatively, related server processing was canceled because the pdcancel command was executed. |
d200 | The maximum number of transactions that can be processed concurrently by a UAP, or an XDS client of a UAP, under the OLTP environment has been exceeded. Because many rollbacks might have occurred, wait for the rollbacks to be completed, and then re-execute the UAP. |
d300 | An error was detected, but the HiRDB server process was terminated without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was in effect. |
d500 | An error occurred during transaction completion processing. |
d600 | The HiRDB server process made a transaction branch request to a server that is stopped, or is in the process of stopping or switching over. As a result, the HiRDB server process was forcibly terminated. |
d700 | The HiRDB server process made a transaction branch request to a server that is in the process of starting up or switching over (a switchover target). As a result, the HiRDB server process was forcibly terminated. |
d800 | A front-end server process failed in its attempt to connect to and retransmit a rollback request to a back-end server or dictionary server within the rollback instruction retransmission time limit specified in the pd_trn_rollback_watch_time operand. As a result, the front-end server process terminated abnormally. |
000f ff00 | The HiRDB server process was forcibly terminated using the pdkill command (in UNIX, the OS kill command). |
008b | An operating system stack overflow may have occurred during HiRDB operation. The following lists the causes and actions for a stack overflow: Cause 1 Consider the following causes:
- A user-defined routine that issues many calls or repeats them infinitely was executed
- A column defined using a nesting of user-defined data types or many inheritances was specified in an SQL statement
- There are too many nesting levels of IF or WHILE statements or scalar functions
Action for cause 1
- Consider the above SQL causes and take action if possible.
- Consider the value of the maxssiz kernel parameter, and increase the stack size.
Cause 2 Stack extension failed due to an operating system memory shortage. Action for cause 2 Terminate unneeded programs, and increase the free memory area. |
- aa....aa: Name of the terminated server
- bb....bb: Process ID of the terminated server
- cc....cc: Service group name of the terminated server
- However, for some server processes, there is no service group name. In that case, spaces are displayed.
- dd....dd: Internal information
- e:
- N: Not on critical status
- Y: On critical status
- As HiRDB shares information among multiple processes, it references and updates the management table in the shared memory. If a process updating the shared memory terminates abnormally, the table information will lose integrity, and subsequent processing by other processes cannot be performed. For this reason, forcible termination in this type of processing space (referred to as the critical space) should be restricted as much as possible. If a failure occurs because abnormal termination in this space could not be suppressed, terminate HiRDB, and the integrity of the table information will recover when it is restarted.
- ff....ff: Critical information
- gg....gg: Process termination status returned with wait(2)
- hhh: Server type (*** is displayed for any server other than a HiRDB server)
- S: Terminates processing at the server resulting in the error and restarts the server, if necessary.
- Action
- gg....gg is c800:
- Use the pdls command to determine if the status information of the unit of the relevant server became STOP(A). If the status information became STOP(A), a network failure may have occurred between the unit and the system manager. Stop the unit with the pdstop -z command, determine the cause of the network failure, and take appropriate action. Then, restart the unit.
- gg....gg is c900:
- Check whether a KFPS01820-E message was displayed where gg....gg is "c800" in the transmission source. If one was displayed, investigate the reason for the transmission source stopping, and take action.
- gg....gg is d600 or d700:
- Check the status of the server.
- If the server is in the process of stopping, wait for it to finish stopping, and then start the server and re-execute the transaction.
- If the server is in the process of starting, wait for the server to finish starting, and then re-execute the transaction.
- If the server is in the process of switching over, wait for the server to finish switching over, and then re-execute the transaction.
- Other than the above:
- Refer to the message that was output before this message or to the troubleshooting information (dump, trace, etc.) to check the cause of the server termination, and take appropriate action. Then, restart the server, if necessary. Troubleshooting information is not output if gg....gg is c000, c100, c200, c300, c400, c500, c600, c700, c800, c900, d000, d100, d200, d300, d500, d600, d700, or d800.
KFPS01821-E E+L
Unable to continue HiRDB unit processing because serious error occurred; stops HiRDB unit aaaa
- HiRDB is being terminated because an error occurred and HiRDB processing cannot be resumed.
- aaaa: Unit identifier
- S: Upon termination of HiRDB, restarts HiRDB if possible.
- O: Eliminate the cause of the error on the basis of the message that was output before this message. Restart HiRDB, if necessary.
KFPS01823-E E+L
System version invalid; stops unit startup
- Because the system version is invalid, the unit is being terminated.
- S: Cancels unit startup processing.
- Action
- Check the versions of library and server and restart.
KFPS01824-E E+L
HiRDB ID invalid; stops unit startup
- An invalid HiRDB identifier was specified in the definition or no HiRDB identifier was specified.
- S: Cancels unit restart processing.
- O: Specify the correct HiRDB identifier and restart HiRDB.
KFPS01826-I L
HiRDB dir = aa....aaHiRDB vrs = bb....bbunit run ID = cc....ccHiRDB ID = ddddunit ID = eeee
- Displays the environment in which the unit is being started normally. In the case of a unit restart, the previous environment is displayed.
- aa....aa: HiRDB directory name
- bb....bb: HiRDB version
- If HiRDB is in the 64-bit mode, (64) is displayed after the version number.
- When using a POSIX library version, (POSIX) is displayed after the version number.
- Example: HiRDB version 07-00, POSIX library version, and 64-bit mode HiRDB:
- '07-00(64)(POSIX)'
- cc....cc: Unit run ID (if the pdstart -r command was used, 00....00 is displayed)
- dddd: HiRDB identifier
- eeee: Unit identifier
- S: Resumes processing.
- O: Check the execution environment.
KFPS01827-E E
Unit ID invalid; stops unit startup
- An invalid unit identifier was specified in the definition, or no unit identifier was specified.
- S: Cancels unit startup processing.
- O: Specify the correct unit identifier in the unit control information definition and restart HiRDB.
KFPS01828-E E+L
System definition parameter aa....aa missing; stops unit startup
- An operand required in the HiRDB system definition is missing.
- aa....aa: Name of the operand required in the HiRDB system definition
- S: Terminates abnormally.
- Action
- Add the required operand and restart HiRDB.
KFPS01829-E E
aa....aa invalid; stops unit startup
- aa....aa for unit restart processing does not match the information used during normal startup.
- aa....aa:
- HiRDB dir:
- HiRDB directory
- HiRDB ID:
- HiRDB identifier
- Master file name:
- First HiRDB file name in the master directory RDAREA
- System Version:
- System version
- Unit ID:
- Unit identifier
- Server Number:
- Number of servers
- Utility exec mode:
- Utility execution mode
- S: Terminates abnormally.
- Action
- Revise the items indicated as the cause in aa....aa, and restart HiRDB.
- System Version:
- HiRDB version
- HiRDB ID:
- The pd_system_id operand of the system common definition
- HiRDB dir:
- The -d option of the pdunit operand of the system common definition
- Unit ID:
- The pd_unit_id operand of the unit control information definition
- Master file name:
- The pd_master_file_name operand of the system common definition
- Server Number:
- Number of pdstart operands specified in the system common definition or pd_mlg_msg_log_unit operands in the system common definition
- Utility exec mode:
- The pd_utl_exec_mode operand of the system common definition
KFPS01830-I L
Server aa....aa recovery process start
- Recovery processing has started during a HiRDB server restart.
- aa....aa: Server name
- S: Resumes processing.
KFPS01831-I L
Server aa....aa recovery process end
- Recovery processing during a HiRDB server restart has been completed.
- aa....aa: Server name
- S: Resumes processing.
KFPS01832-I E+L
Data replication restart. unit ID = aa....aa, reason code = bb....bb
- HiRDB Datareplicator linkage has been restarted.
- aa....aa: Unit identifier
- bb....bb: Reason for restarting HiRDB Datareplicator linkage:
- FORCE:
- HiRDB Datareplicator linkage was established in the previous session, but HiRDB was started by the pdstart -i command.
- STATUS:
- Initialization or error occurred in the file for data linkage by HiRDB Datareplicator or in a HiRDB system status file.
- S: Terminates HiRDB Datareplicator linkage and then restarts it.
- Action
- If necessary, initialize the file for data linkage by HiRDB Datareplicator and re-create the target database.
KFPS01833-E E+L
Cancels processing because the same command running
- Another process is running the same command. This message might be output if the same command is executed immediately after this command terminates abnormally.
Also, if the standby-less system switchover (effects distributed) facility is being used and the pdstbegin operand is specified, this message might be output when the unit or server is started. - S: Terminates processing.
- O: Revise the options specified in the command, and re-execute the command.
- Action
- After the command process terminates, re-execute the command. If the command terminates abnormally, wait a brief period before re-executing the command.
- If this message was output when a unit or server using the standby-less system switchover (effects distributed) facility was started, use the pdls -d stj command to determine whether statistical information was output. If statistical information was not output, use the pdstbegin command to output statistical information.
KFPS01833-I E+L
Unable to continue data replication. unit ID=aaaa, reason code=bb....bb
- The system was unable to continue HiRDB Datareplicator linkage.
- aa....aa: Unit identifier
- bb....bb: Reason for discontinuing HiRDB Datareplicator linkage:
- DEFINITION:
- HiRDB Datareplicator linkage was established in the previous session, but N was specified in the pd_rpl_init_start operand of the system common definition.
- RPL_FILE:
- An error occurred in the file for data linkage by HiRDB Datareplicator.
- RPL_STATUS:
- The file for data linkage by HiRDB Datareplicator was initialized.
- S: Terminates data linkage and resumes HiRDB startup processing.
- Action
- To re-execute HiRDB Datareplicator linkage, eliminate the cause of the error, synchronize the target HiRDB, then execute the pdrplstart command to restart HiRDB Datareplicator linkage.
- If HiRDB is to be terminated but HiRDB Datareplicator linkage is to be always established, specify Y in the pd_rpl_init_start operand in the system common definition.
- If the reason code is RPL_STATUS or RPL_FILE, the KFPS04624-I message showing the server name is output before this message (KFPS01833-I) for each server in which the error occurred.
KFPS01834-E E+L
Error occurred in status file while data, duplication unit ID=aaaa reason code=bb....bb
- Error was detected in the status file while using the HiRDB Datareplicator linkage facility.
- aaaa: Unit identifier
- bb....bb: Reason code:
- COMMUNICATION: Inter-process communication error occurred
- SERVER NOT UP: Status server process has not been started
- I/O ERROR: I/O error occurred
- OTHER: Other error occurred
- S: Terminates HiRDB.
- Action
- Eliminate the cause of the error on the basis of the message that was output before this message.
KFPS01835-E E+L
Error found in system configuration for fall-back operation. reason code=aa....aa
- The system definition regarding reduced activation operation contains an error.
- aa....aa: Reason code
- UNIT ID ERROR unit-identifier:
- The unit identifier coded in the pd_start_skip_unit operand is not found in the system configuration.
- DUPLICATE UNITID:
- The same unit identifier cannot be specified multiple times in the pd_start_skip_unit operand.
- MGR UNIT NOT SKIPPED:
- A unit in which the System Manager is located cannot be specified in the pd_start_skip_unit operand.
- DIC UNIT NOT SKIPPED:
- A unit in which the Dictionary Server is located cannot be specified in the pd_start_skip_unit operand.
- NECESSARY ONE FES FOR FALL-BACK:
- Reduced activation operation requires one or more active front-end servers.
- NECESSARY ONE BES FOR FALL-BACK:
- Reduced activation operation requires one or more active back-end servers.
- S: Terminates processing.
- Action
- Check the specification of the pd_start_level and pd_start_skip_unit operands and restart HiRDB.
KFPS01836-W E+L
Fall-back operation ignored, because of restarting with "pdstart aa"
- When operating HiRDB with reduced activation, the aa option cannot be specified with the pdstart command. Specification of the reduced activation mode is ignored.
- aa: pdstart command option
- For details about pdstart command options, see the manual HiRDB Version 9 Command Reference.
- S: Resumes processing.
- Action
- To perform reduced activation:
- Execute the pdstart command without specifying the aa option.
- To activate while specifying the aa option:
- If a unit cannot be started, place it in startable status.
KFPS01837-I E+L
Unit startup skipping for fall-back operation. unit ID=aa....aa
- The HiRDB system is started on a reduced activation basis by skipping the HiRDB unit indicated by the unit identifier.
- aa....aa: Unit identifier
- S: Resumes processing.
KFPS01838-W E+L
Fall-back operation ignored, because no startup skip HiRDB unit
- This system configuration does not contain any units that can be skipped; the reduced activation operation mode is ignored.
- S: Resumes processing.
- Action
- Change the pd_start_level operand in the system common definition to 0 (do not apply the reduced activation mode). To start the HiRDB on a reduced activation basis, change to a reduced-startup-capable system configuration by assigning front-end and back-end servers to multiple units.
KFPS01839-E E+L
Error found in system configuration for pd_system_expand_unit. unit=aaaa, reason code=bb....bb
- The specification of the pd_system_expand_unit operand is invalid.
- aaaa: Unit identifier
- However, if bb....bb (reason code) is FES UNIT or BES UNIT, **** is displayed.
- bb....bb: Reason code
- UNIT ID ERROR:
- The unit identifier described in the pd_system_expand_unit operand is not included in the system configuration.
- DUPLICATE UNIT ID:
- Identical unit identifiers were described multiple times in the pd_system_expand_unit. The same unit identifier cannot be described in this operand more than once.
- MGR UNIT:
- The unit with the system manager is specified in the pd_system_expand_unit operand.
- DIC UNIT:
- The unit with the dictionary server is specified in the pd_system_expand_unit operand.
- FES UNIT:
- Units with front-end servers exist in HiRDB when expansion units are excluded (all basic units).
- BES UNIT:
- Units with back-end servers exist in HiRDB when expansion units are excluded (all basic units).
- S: Terminates processing.
- Action
- Perform one of the following actions as applicable, and then re-execute the pdconfchk command or HiRDB start processing:
- If bb....bb (reason code) is UNIT ID ERROR or DUPLICATE UNIT ID:
Re-examine the pd_system_expand_unit operand specification and eliminate the cause of the error.
- If bb....bb (reason code) is different from those mentioned above:
Re-examine the system configuration and eliminate the cause of the error.
KFPS01840-I L
Now terminating HiRDB unit aaaa
- HiRDB is being terminated.
- aaaa: Unit identifier
- S: Resumes HiRDB processing.
KFPS01841-I S
HiRDB unit aaaa terminated, mode=bb....bb
- HiRDB unit aaaa terminated. The termination mode is bb....bb.
- aaaa: Unit identifier
- bb....bb: Termination mode:
- FORCE: Forced termination
- NORMAL: Normal termination
- PLAN: Planned termination
- S: Terminates HiRDB processing.
KFPS01842-I L
Now terminating server aa....aa
- Server is being terminated.
- aa....aa: Name of the server being terminated
- S: Resumes HiRDB processing.
KFPS01843-I S
Server aa....aa terminated
- Server has been terminated.
- aa....aa: Name of the terminated server
- S: Resumes HiRDB processing.
KFPS01844-E E+L
Error occurred while terminating server aa....aa. reason code=bb....bb
- An error occurred during server termination processing. Either the server could not be terminated, or the server abnormally terminated during termination processing.
- aa....aa: Name of the server resulting in the error
- bb....bb: Cause of the error:
- ABNORMAL:
- pdstop command was used to terminate HiRDB, but a server had not terminated normally.
- ABORT:
- Server terminated abnormally (pdstop).
- ABORTING:
- Server abnormal termination processing (pdstop -s) is underway.
- COMMUNICATION:
- Inter-process communication error occurred.
- CRITICAL:
- Forced termination has been placed on hold due to critical status.
- EXIT:
- System is inactive (there is no server), or termination processing is underway.
- MEMORY:
- Memory shortage occurred.
- PROTOCOL:
- pd_rpc_mainloop cannot be issued.
- STARTING: Server is starting.
- S: Resumes HiRDB processing.
- O: Check whether there are servers that are not terminated. If there are servers that are not terminated, eliminate the cause of the error and terminate the servers again. Note that only forced termination (pdstop -s -f or pdstop -f) may be accepted, depending on the previous termination status.
KFPS01845-E E+L
Commands unable to enter because HiRDB inactive
- Commands cannot be entered because HiRDB is inactive.
- S: Terminates the entered command.
KFPS01846-E E+L
Unable to terminate the unit normally; some servers forced to terminate
- The system cannot be terminated normally, because a server was terminated forcibly.
- S: Terminates the command.
- O: Restart the server indicated as ABNORMAL in the KFPS01844-E message and terminate it normally. Or, terminate the system forcibly.
KFPS01847-E E+L
Unable to terminate the unit; some servers being started or terminated
- The system cannot be terminated, because a server is engaged in startup or termination processing.
- S: Terminates the command.
- O: Wait until the server startup or termination processing has been completed. Or, enter the pdstop -f command.
KFPS01849-W S+L
Now waiting for termination of server aa....aa
- The system is waiting for termination of a server.
- aa....aa: Name of the server for which the system is waiting for termination
- S: Places system termination on hold until the displayed server has terminated.
- O: Terminate the displayed server.
KFPS01850-I S
HiRDB system terminated. mode=aa....aa
- The HiRDB system terminated. The termination mode is aa....aa.
- aa....aa: Termination mode:
- NORMAL: Normal termination
- PLAN: Planned termination
- FORCE: Forced termination
- S: Terminates processing.
- In the following cases, it is possible that a unit that is not the system manager did not terminate, even though this message was output:
- The pdstop command did not terminate normally
- Message KFPS05121-E or KFPS05227-W was output to the event log (in UNIX, syslogfile) on the unit where the system manager resides
- Action
- Before the next time HiRDB starts, check the event log (in UNIX, syslogfile) of the unit that is not the system manager to see whether message KFPS01841-I was output. If message KFPS01841-I was not output, the unit has not terminated. Take corrective action according to any other messages that were output.
KFPS01851-E E+L
Server aa....aa initialization error occurred; return code=bb....bb
- A server initialization error occurred.
- aa....aa: Server name in the HiRDB/Single Server or HiRDB/Parallel Server (front-end server)
- bb....bb: Error code
- S: In the case of a HiRDB/Single Server, terminates abnormally; in the case of the front-end server, sets the status displayed by the pdls command to SUSPEND.
- Action
- For a HiRDB/Single Server, re-execute the pdstart command; for a HiRDB/Parallel Server, execute the pdstart -a command.
KFPS01852-W E+L
Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e, critical mask=ff....ff, end state=gg....gg, server type=hhh
- Server aa....aa stopped.
This message is output when you are using the facility for changing a process down message when canceling a transaction (by specifying Y in the pd_cancel_down_msgchange operand in the system definition), and the server stops for one of the reasons listed below. If you are not using the facility for changing a process down message when canceling a transaction, message KFPS01820-E is output rather than this message. - Client allocation was accompanied by a forcible termination request, causing the HiRDB server executing the transaction to terminate. (This applies to UAPs that use DBPARTNER or DABroker to access HiRDB and UAPs that use ODBC to access HiRDB. This also includes cases where the applicable UAP is stopped by pressing Ctrl+C on the keyboard.)
- A UAP failed, causing the HiRDB server process executing the transaction to terminate. (If the XA interface is being used, this message is not changed.)
- The pdcancel command was executed, causing the HiRDB server process executing the transaction to terminate (including utility server processes).
- When control is on the HiRDB client side, a client environment definition PDSWAITTIME timeout was detected during a transaction, causing the HiRDB server process to terminate.
- When control is on the HiRDB client side, a client environment definition PDSWATCHTIME timeout was detected not during a transaction, or when connected to a Windows edition HiRDB the system definition pd_watch_pc_client_time operand timeout was detected, causing the HiRDB server process to terminate.
- The pdfgt command was executed, forcibly terminating the transaction and causing the HiRDB server process to terminate.
- The facility for monitoring the free area for the system log file was used to specify safe in the system definition pd_log_remain_space_check operand, and the log size exceeded the threshold value, causing the HiRDB server process to terminate.
- When a HiRDB server process failed due to an error, the server process terminated to perform transaction and utility recovery. (The server process that failed due to an error does not affect this message.)
- For HiRDB/Parallel Server, when a unit was forcibly terminated, a unit shut down, or a system switchover occurred, the HiRDB server process terminated so another unit could perform transaction and utility recovery.
- aa....aa: Terminated server name
- bb....bb: Terminated server ID
- cc....cc: Service group name of terminated server
- However, for some server processes, there is no service group name. In that case, spaces are displayed.
- dd....dd: Internal information
- e:
- N: Not in critical status
- Y: In critical status
- ff....ff: Critical information
- gg....gg: Process termination status returned by wait(2) (for a HiRDB command, **** is displayed). For details, see KFPS01820-E.
- hhh: Server type (if other than a HiRDB server, *** is displayed)
- S: Reactivates the user server process as necessary. Does not terminate HiRDB (for HiRDB/Parallel Server, the unit) at this time.
- O: If put is specified in the pd_cancel_dump operand, the error information is output. If the error information is not required, delete it.
KFPS01853-W E
Hostname = aa....aa, unable to execute cc....cc command, unit state not bb....bb
- The system was unable to execute the entered command because the unit was not on status bb....bb at host aa....aa.
- aa....aa: Name of the host where the system was unable to execute the command
- bb....bb: Status in which command can be entered:
- OFFLINE: Offline status
- ONLINE: Online status
- cc....cc: Name of the entered command
- S: Terminates the command.
- O: Reenter the command after the system or unit status is displayed. The pdstart command cannot be executed while the unit is active (or engaged in startup processing); the pdstop command cannot be executed while the unit is inactive (or engaged in termination processing). Check that the unit is inactive or active, as applicable, before entering the command.
- This message is displayed when the unit status does not meet the command's execution requirements. This is similar to message KFPS01863-E, and whichever message is output, both the HiRDB processing and corrective action by the operator are the same.
KFPS01854-E E+L
Unable to start standby,online unit notup.
- The running system unit did not start when the rapid system switchover facility was used to start the standby system.
- S: Terminates HiRDB processing.
- Action
- Check if the running system unit started normally. When the running system unit starts normally, ACTIVE is displayed in STATUS of the pdls command execution results or the KFPS05210-I or KFPS05110-I message is output.
- When using Hitachi HA Toolkit Extension, check if service processing for Hitachi HA Toolkit Extension started. If the running system unit started without service processing starting, both systems were started as standby systems. For details on how to start service processes, see the manual Hitachi HA Toolkit.
KFPS01855-E E+L
Unable to stop alternate server or original server aa....aa
- The standby less system switchover facility cannot independently terminate alternate BES and normal BES.
- aa....aa: Name of alternate BES or normal BES
- S: Terminates processing.
- Action
- To stop alternate BES or normal BES, terminate the alternate BES unit or the normal BES unit.
KFPS01856-E E+L
Unable to stop server aa....aa by force ,server not bb....bb
- Because server aa....aa is not bb....bb, it cannot be forcibly terminated.
- aa....aa: Server name
- bb....bb: Error cause
- IN HAGROUP: Target standby-less system switchover (effects distributed) facility
- ONLINE: Online
- S: Terminates processing.
- Action
- Based on the cause of the error, take appropriate action.
- Error cause is IN HAGROUP
Servers for which the standby-less system switchover (effects distributed) facility does not apply cannot be forcibly terminated. Revise the command option specification. To stop the server, execute a normal termination (pdstop -s command).
- Error cause is ONLINE
The server may already be stopped. Execute the pdls command to check the running status of the server.
KFPS01857-E E+L
Operand combination invalid, operand=aa....aa
- The combination of operands aa....aa specified in the system definition is invalid. If there are multiple invalid combinations in the system definition, this message is output multiple times.
- aa....aa: Invalid combination of operand names
- {pd_lock_uncommited_delete_data, pd_indexlock_mode|
- pd_max_tmp_table_rdarea_no, pd_max_rdarea_no|
- pd_max_tmp_table_rdarea_no, pd_max_temporary_object_no}
- S: If this message is output during execution of the pdstart command, start processing terminates abnormally. After that, message KFPS00715-E is output with reason code=20, and HiRDB enters PAUSE status (the restarting of the process server process is suspended).
- If this message was output during execution of the pdconfchk command, command processing terminates.
- Action
- Refer to the manual HiRDB Version 9 System Definitions to check consistency between operands, and then revise the specified value for each operand. Then, re-execute the command. Also, if this message is output during execution of the pdstart command, execute the pdconfchk once, check whether this message is output, and then re-execute the pdstart command.
KFPS01860-E E
Command format aa....aa invalid
- Indicated command is invalid.
- aa....aa: Format of the command:
- pdstop [-f]: System termination command
- pdstop [-f] -s server_name: Server termination command
- pdstart: System startup command
- pdstart -s server_name: Server startup command
- S: Terminates the command.
- O: Reenter the command.
KFPS01861-E E
Error occurred during command execution. reason code=aa....aa
- A command error occurred.
- aa....aa: Nature of the command error:
- COMMUNICATION:
- Inter-process communication error occurred.
- DEFINE FILE:
- Definition file error occurred.
- INITIALIZING:
- Command cannot be accepted because startup processing requested by pdstart is underway (reenter the command after HiRDB startup is completed).
- MEMORY:
- Memory shortage occurred.
- PARAM:
- Argument is invalid.
- RPL STATUS:
- HiRDB Datareplicator linkage startup or termination processing failed.
- SERVER NAME LEN:
- Length of the server name is invalid.
- SHARED MEMORY:
- Shared memory access failed.
- STATUS:
- Server addition or deletion failed.
- TIMEOUT:
- System initialization processing did not terminate within the specified time, or an invalid system definition was detected at the system server.
- UTILITY:
- The command cannot be received because the utility is running. Wait for the utility to terminate, and then re-execute the command.
- S: Terminates the command.
- O: Eliminate the cause of the error and reenter the command.
- pdstop -s command:
- Check for any server that has not terminated. Only the pdstop -s -f or pdstop -f command may be accepted, depending on the previous termination status.
- SHARED MEMORY:
- This message may be output when an operation command is entered while the system startup process is running. If necessary, re-execute the command.
- TIMEOUT:
- Perform the following procedure:
- If HiRDB start processing continues, ignore this message except for the unit(s) displayed in the additional information of this message when 1 is specified to the pd_start_level operand in the system definition.
- If the following conditions hold after this message is output, execute the pdstop -f command:
The pdstart command did not terminate and is not responding.
The command pdls -d ust shows a unit in STARTING status for an extended period of time.#
- If an error message or a warning message is output to the event log (in UNIX, syslogfile) of the unit where the system manager resides before or after this message was output, follow the actions given in that message.
- If an error message or a warning message is output to the event log (in UNIX, syslogfile) of the unit indicated in the additional information of this message before or after this message was output, follow the actions given in that message.
- Increase the value specified in the pd_start_time_out operand.
- Re-execute the pdstart command.
- If the pdstart command outputs this message again after performing step 6, repeat steps 1 through 6.
- #
- Check whether a previously-executed pdstart command terminated abnormally, or was stopped using the OS's kill command or by a similar means.
- RPL STATUS:
- Take action on the basis of the message that was output immediately before.
- COMMUNICATION:
- Eliminate the cause of the error according to the description in Table 4-1 Frequently occurring causes and required action for RPC-related errors, and then re-execute the command.
KFPS01862-E E+L
Enter server name
- Asks that a server name be entered.
- S: Terminates the command.
- O: Reenter the command with a server name entered as the command argument.
KFPS01863-E E
Hostname=aa....aa, unable to execute cc....cc command, unit state not bb....bb
- Because the unit status at host aa....aa is not bb....bb, the command cannot be executed.
- aa....aa: Name of the host at which the command could not be executed
- bb....bb: Status in which the command can be executed:
- OFFLINE: Offline
- ONLINE: Online
- cc....cc: Name of the entered command
- S: Terminates the command.
- O:
- Reenter the command after the system or unit status is displayed. The pdstart command cannot be executed while the unit is active (or engaged in startup processing); the pdstop command cannot be executed while the unit is inactive (or engaged in termination processing). Check that the unit is inactive or active, as applicable, before entering the command.
- On a system switchover configuration unit, if this message was output during execution of the pdstart command, the unit might be waiting for a running system to start. Use the HA monitor monshow command to check the status of the unit, and then take action depending on its state.
- This message is displayed when the unit status does not meet the command's execution requirements. This is similar to message KFPS01853-W, and whichever message is output, both the HiRDB processing and corrective action by the operator are the same.
KFPS01864-E E+L
Timeout occurred during execution of command aa....aa
- A command resulted in a timeout.
- aa....aa: Command name:
- pdstop: Termination command
- S: Terminates the command.
- Action
- Determine the cause of the abnormal termination, and then restart HiRDB. In UNIX, if a dump was output to the core file, save the dump.
KFPS01865-E L
Server failed: cancels execution of aa....aa command
- Server terminated abnormally, so command processing is being cancelled.
- aa....aa: Name of the entered command
- pdstop: System termination command
- S: Terminates the command.
- Action
- Determine the cause of the abnormal termination, and then restart HiRDB. In UNIX, if a dump was output to the core file, save the dump.
KFPS01866-E E+L
Server aa....aa specified twice
- The same name was specified more than once in a list of input commands.
- aa....aa: Duplicated server name
- S: Terminates the command.
- O: Delete the duplicated name from the list of input commands and reenter the commands.
KFPS01867-E E
Unable to continue processing because shared memory unused
- Because shared memory cannot be used, processing cannot continue.
- S: Terminates the command.
- O: Check whether or not the system is active and reenter the command.
KFPS01868-E E+L
Server name aa....aa invalid
- Invalid server name was found.
- aa....aa: Invalid server name
- S: Terminates the command.
- O: Correct the command argument and reenter the command.
KFPS01869-E E
Unable to accept the command because the unit failed or not installed
- Because the system has not been installed or the system is inactive, the command cannot be accepted.
- S: Terminates the command.
- O: Check whether or not the system is active and reenter the command.
KFPS01870-E E+L
Unable to analyze the definition file due to insufficient memory
- A memory shortage occurred in a process during definition file analysis processing.
- S: Cancels definition file analysis processing.
- Action
- Reduce either the number of processes or the amounts of memory available to other processes and restart HiRDB.
KFPS01871-E E+L
Communication error occurred. server name=aa....aa, return code=bb....bb
- A communication error occurred.
- aa....aa: Name of the server resulting in the error
- bb....bb: Return value set when error control return occurred
- S: Cancels the corresponding server processing.
- O: Eliminate the cause of the error on the basis of the message output before this message, then restart HiRDB, if necessary.
KFPS01872-I L
HiRDB is placed in the standby state
- HiRDB has been placed in standby status.
- S: Resumes processing.
KFPS01873-E L
HA monitor has been stopped
- The HA monitor or the Hitachi HA Toolkit Extension is currently stopping.
- S: Terminates abnormally.
- O: Start the HA monitor or the Hitachi HA Toolkit Extension, and then restart HiRDB.
KFPS01874-E L
Cannot connect to HA monitor. reason=aa....aa
- Connection cannot be established with the HA monitor or the Hitachi HA Toolkit Extension.
- aa....aa: Reason that a connection could not be established with the HA monitor or the Hitachi HA Toolkit Extension
- HA NOEXIST: The HA monitor or the Hitachi HA Toolkit Extension was not found or is inactive.
- PDDIR LEN: The length of the character string set in the PDDIR environment variable exceeded the maximum.
- DUPLICATE: An attempt was made to start another server with the same name.
- S: Terminates abnormally.
- O: Restart HiRDB after correcting the error.
KFPS01875-E L
System error detected during communication with HA monitor. error code=aaaa, detail code=bbbb
- System error was detected during the HA monitor or Hitachi HA Toolkit Extension communication processing.
- aaaa: Return code for the HA monitor or Hitachi HA Toolkit Extension
- bbbb: Detail return code from the HA monitor or Hitachi HA Toolkit Extension
- S: For units for which the standby-less system switchover facility is applicable, stops the server. Abnormally terminates any others.
- Action
- See the HA monitor or Hitachi HA Toolkit Extension message that was output before or after this message, and take appropriate action as indicated in the message. If no the HA monitor or Hitachi HA Toolkit Extension message was output, contact the customer support center.
KFPS01877-I L
HiRDB stop request issued from HA monitor; stops HiRDB. reason=aa....aa
- HiRDB will be terminated because a HiRDB termination request was issued from the HA monitor or the Hitachi HA Toolkit Extension.
- aa....aa: HiRDB's internal termination cause code (maintenance information)
- S: Terminates abnormally.
- O: See the HA monitor or Hitachi HA Toolkit Extension message.
KFPS01878-I L
HiRDB restart request issued from HA monitor; stops HiRDB temporarily. reason=aa....aa
- HiRDB will be terminated temporarily because a HiRDB restart request was issued from the HA monitor or the Hitachi HA Toolkit Extension. If the HA monitor is being used, the running system unit was activated before the unit terminated.
- aa....aa: HiRDB's internal termination cause code (maintenance information)
- S: Takes one of the following actions, depending on the startup method used after termination:
- Automatic startup: Terminates HiRDB, then starts it automatically.
- Manual startup: Terminates HiRDB.
- O: If manual startup is used after termination, enter the pdstart command to restart HiRDB.
- If the HA monitor is being used, when the running system unit is started, it is possible that a KFPS01878-I or KFPS00715-E message will be output and the start will fail. If the running system unit cannot be started, use the following procedure to start it:
- Determine whether the unit is stopped using the HA monitor's monshow command. (When the monshow command is executed, stopped systems are not displayed. If the status of a unit is displayed, this indicates that the unit is not stopped.)
- Use the pdrpause command to restart the HiRDB process server process.
- Use the pdstart command to start the running system unit.
KFPS01879-I L
HiRDB standby state released, status=aa
- Standby status of HiRDB was released.
- aa: HiRDB status code (maintenance information)
- S: Continues processing.
KFPS01880-W E
Statistics already output stopped
- The output of statistics information is already stopped.
- S: Ignores the command that was entered.
- O: Check whether statistics information is being output. Re-execute the pdstend command as necessary. To determine whether statistics information is being output, execute the pdls -d command.
- When adding or changing specifications for the statistics information to be output to the statistics log file, use either the pdstbegin or pdstend command to specify the contents of the statistics information to be added or changed, and then execute the command.
KFPS01881-I E+S
Usage: pdstbegin{[-k statistics_type [,statistics_type]....] [-m time_interval] [-x host_name [,host_name]....] [-a| -s server_name[,server_name].... ] [-w]}
- Displays the format of pdstbegin and pdstend commands.
KFPS01882-E E
Command argument invalid
- A command argument is invalid. Or, an unnecessary argument was specified in the command.
- S: Cancels command processing.
- O: Correct the command argument and reenter the command.
KFPS01883-E E
Cancels processing because the same command running
- This message is output in the following two cases:
- The same command process is already running. This message might be output if a command is re-entered immediately after the command terminates abnormally.
- This message might be output when a unit or server is started when both of the following conditions are satisfied:
- The standby-less system switchover (effects distributed) facility is used
- The pdstbegin operand is specified
- S: If 1, terminates the command processing.
- If 2, continues the command processing.
- O: If 1, wait for the executing command process to terminate, and then re-enter the command. If the command terminates abnormally, re-enter the command after a while.
- If 2, use the pdls -d stj command to determine whether output of the current statistical information has started. If output of statistical information has not started, execute the pdstbegin command to start the output of statistical information.
KFPS01884-E E
Statistics already output
- Statistical information has already been output to the statistics log file.
- S: Ignores the entered command.
- O: To determine whether statistics information is being output, execute the pdls -d stj command. When adding or changing specifications for the statistics information to be output to the statistics log file, use either the pdstbegin or pdstend command to specify the contents of the statistics information to be added or changed, and then execute the command.
KFPS01885-E E
Cancels the comand because shared memory for statistics in server aa....aa unable to be allocated
- Allocation of shared memory needed to obtain statistical information for server aa....aa failed, so the command's processing is being cancelled.
- aa....aa: Name of the server for which allocation of shared memory was attempted
- S: Cancels command processing.
- O: Reenter the pdstbegin command without creating a statistics log file for the corresponding server.
KFPS01886-W R+S
Cancels system active statistics log output. reason code=aa....aa
- System activity statistical information cannot be output to the log.
- aa....aa: Reason code:
- MAX PROCESSES:
- The maximum number of server processes that can be started at the same time in HiRDB has been exceeded.
- S: Resumes processing.
- This statistical information will be output the next time system activity statistical information is output. This error does not affect HiRDB's current online activity.
- Action
- If MAX PROCESSES is displayed in the reason code, the specified maximum number of concurrently activated server processes (the pd_max_server_process operand) may be too small. Re-evaluate the specified value of the pd_max_server_process operand, and then set the correct value.
KFPS01888-W E+L
Too small aa....aa. pd_max_users assumed. server=bb....bb
- Value specified in pd_max_bes_process or pd_max_dic_process was less than the value of pd_max_users in the system common definition. The system assumes the value of pd_max_users.
- aa....aa: Name of the definition for which the value of pd_max_users was assumed:
- pd_max_bes_process:
- Maximum number of startup processes in the back-end server
- pd_max_dic_process:
- Maximum number of startup processes in the dictionary server
- bb....bb: Server name
- S: Resumes processing.
- Action
- Check the value specified for the corresponding pd_max_bes_process or pd_max_dic_process.
KFPS01889-E E+L
Error occurred in HiRDB Datareplicator while executing aa....aa. server ID=bb....bb, function value=cc....cc, errno=dddd
- Error occurred in HiRDB Datareplicator linkage.
- aa....aa: Name of abnormally terminated subroutine
- bb....bb: Server name
- cc....cc: Reason code set by the abnormally terminated subroutine:
- INTERNAL ERROR:
- Error occurred during internal processing.
- SEQUENCE ERROR:
- Error was detected in the function issuance order.
- PARAMETER ERROR:
- Argument was invalid.
- FILE ERROR: HiRDB-Datareplicator-directory-name:
- File for data linkage was invalid (up to 64 characters of the directory name are displayed).
- SYSTEM CALL (system-call-name) ERROR:
- System call error occurred.
- FILE LOCK ERROR
- A reference privilege or update privilege could not be acquired for the data linkage file.
- dddd: errno value specified by the abnormally terminated subroutine
- S: Suspends HiRDB Datareplicator linkage if HiRDB is starting. Continues HiRDB Datareplicator linkage if the pdls -d rpl command is running or if HiRDB is operating.
- Action
- If the reason code is FILE ERROR or SYSTEM CALL ERROR, check the Datareplicator execution environment of HiRDB and HiRDB Datareplicator. If the pdls -d rpl command was executed during system switchover of the unit, this message may be output. Re-execute the command after the system switchover is complete.
- Also, if this message is output while HiRDB is running, refer to the event log (in UNIX, syslogfile) or execute the pdls -d rpl command to check the data linkage status. If the KFPS05141-I message is not output, data linkage was not interrupted, so you do not need to recover data linkage. If any other reason code is displayed, contact the customer support center.
KFPS01890-I L+S
Statistics: ID=aa....aa, number of events=bb....bb, average=cc....cc, max=dd....dd, min=ee....ee
- Displays statistical information about an event.
- aa....aa: Event ID
- bb....bb: Number of times this event occurred
- cc....cc: Average value of the event
- dd....dd: Maximum value of the event
- ee....ee: Minimum value of the event
- S: Terminates the command.
KFPS01891-E E+L
Invalid value for variable aa....aa in definition file.
- An operand specification value in the HiRDB system definition contains an error.
aa....aa: Name of the HiRDB system definition operand - S: Terminates the HiRDB startup processing.
- Action
- Review the value specified in the aa....aa operand and start HiRDB.
KFPS01892-E E
aa....aa invalid; stops unit startup. server ID=bb....bb, old value=cc....cc, new value=dd....dd
- The unit cannot be restarted because a specification value in operand aa....aa was changed.
The value of operand aa....aa cannot be changed after abnormal termination or forced termination. - aa....aa: Name of the HiRDB system definition operand
- bb....bb: Server name
- if aa....aa is a system common definition operand or a unit control information definition operand, ******** is displayed.
- cc....cc: Old value of operand aa....aa
- dd....dd: New value of operand aa....aa
- S: Terminates startup processing for the unit.
- Action
- Take a corrective actions according to the information displayed in aa....aa:
- Displayed as pd_max_users:
- Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit.
- Displayed as pd_max_bes_process or pd_max_users:
- Take action according to the following table:
Condition | Action |
---|
pd_max_bes_process operand omitted | Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit. |
pd_max_bes_process operand specified | cc....cc > pd_max_users | Reset the value of the pd_bes_process operand to the previous value (the value of cc....cc) and restart the unit. |
cc....cc pd_max_users | Reset the values of the pd_max_users and pd_max_bes_process operands to the previous value (the value of cc....cc) and restart the unit. |
- Note
- When changing the value of the pd_max_bes_process operand, determine which server definition is to be changed on the basis of the server name indicated in bb....bb.
- Displayed as pd_max_dic_process or pd_max_users
- Take action according to the following table:
Condition | Action |
---|
pd_max_dic_process operand omitted | Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit. |
pd_max_dic_process operand specified | cc....cc > pd_max_users | Reset the value of the pd_max_dic_process operand to the previous value (the value of cc....cc) and restart the unit. |
cc....cc pd_max_users | Reset the values of the pd_max_users and pd_max_dic_process operands to the previous value (the value of cc....cc) and restart the unit. |
- When pd_max_list_users is displayed:
- Return the value of the pd_max_list_users operand to what it was before the change (value cc....cc). Then, restart the unit.
- When pd_max_list_count is displayed:
- Return the value of the pd_max_list_count operand to what it was before the change (value cc....cc). Then, restart the unit.
- When pd_max_reflect_process_count is displayed:
- Return the value of the pd_max_reflect_process_count operand to what it was before the change (value cc....cc). Then, restart the unit.
- When pd_ha_max_act_guest_servers is displayed:
- Return the value of the pd_ha_max_act_guest_servers operand to the value before the change (value of cc....cc). Then, restart the unit.
KFPS01893-E E
Error occurred during pd_ha_restart_failure command execution
- The command specified in the pd_ha_restart_failure operand of the unit control information definition cannot be started or it terminated abnormally.
- S: Terminates unit startup processing
- Action
- Check the command and the definition.
- Either enter the pdstart command and restart the unit or switchover systems.
KFPS01894-I L
Master_file_name = aa....aa
- Displays the environment of a normally started unit (for a restarted unit, displays its previous environment).
- aa....aa: First HiRDB file name in the master directory RDAREA
- S: Resumes processing.
- O: Check the execution environment.
KFPS01895-E E
Error found in system definition, file=aa....aa, line=bb....bb, option=c
- An error was found in the indicated definition.
- aa....aa: Definition file name
- bb....bb: Line number
- c: Option name
- S: Terminates abnormally.
- O: Contact the HiRDB system administrator.
- Action
- Correct the error in the definition file and re-execute HiRDB.
KFPS01896-E E+L
Error found in system configuration. reason code=aa....aa
- An error was found in the specification of an operand related to system configuration specified in the HiRDB system definition.
- aa....aa: Reason code
- S: Terminates abnormally.
- Action
- Take action according to the reason code, and then start HiRDB.
Reason code | Action |
---|
CURRENT PDDIR ERR directory-name | The HiRDB directory name specified in the environment variable PDDIR and the HiRDB directory specified in the -d option of the pdunit operand do not match. Make the HiRDB directory names match. Note that the displayed directory name is the HiRDB directory name specified in the -d option, and that a maximum of only 63 characters are displayed. |
CURRENT UNIT ID ERR unit-identifier | - The unit identifier specified in the -u option of the pdstart operand and the unit identifier specified in the -u option of the pdunit operand do not match. Make the unit identifiers match.
- The unit identifiers specified in the -u option of the pdstart operand were duplicated. Take action to resolve the unit identifier duplication in the system.
|
DUPLICATE DIC | Multiple DICs are specified in the -t option of the pdstart operand. Specify only one DIC in the system. |
DUPLICATE HOSTNAME host-name | The host name specified in the -x or -c option of the pdunit operand is the same as the host name specified in the -x or -c option of another pdunit operand. Specify a different host name in the -x and -c options of each pdunit operand. |
DUPLICATE HOSTNAME unit-identifier | The host names specified in the -x option and -c option of the pdunit operand were duplicated. Specify the host name of the primary system in the -x option and specify the host name of the secondary system in the -c option. Specify different host names for the primary system and secondary system. When not using the system switchover facility, do not specify the -c option. |
DUPLICATE MGR | Multiple MGRs are specified in the -t option of the pdstart operand. Specify only one MGR in the system. |
DUPLICATE PDDIR directory-unit-identifier | HiRDB directories specified in the -d option of the pdunit operand were the same. For mutual system switchover configurations, specify a different HiRDB directory for each unit. Windows does not distinguish between upper case and lower case letters, so errors occur when HiRDB directory names differ only in the case of the letters in the name. |
DUPLICATE SERVER ID server-name | The server names specified in the -s option of the pdstart operand were the same. Take action to resolve the server name duplications in the system. Windows does not distinguish between upper case and lower case letters, so errors occur when HiRDB directory names differ only in the case of the letters in the name. |
DUPLICATE UNIT ID unit-identifier | The unit identifiers specified in the -u option of the pdunit operand were the same. Take action to resolve the unit identifier duplications in the system. |
FES SAME UNIT | Multiple front-end servers were defined in the same unit. Only one front-end server can be defined in a unit. |
INVALID Datareplicator environment | The execution environment of HiRDB Datareplicator is invalid. Check the execution environment of HiRDB Datareplicator. |
MISSING pdunit host-name | - If the pdunit operand is specified:
- The host name specified in the -x option of the pdstart operand, or the unit identifier specified in the -u option of the pdstart operand, are not specified in the pdunit operand. Specify the host name or unit identifier in the pdunit operand. Note that this is case sensitive (uppercase and lowercase letters are distinguished).
- If the pdunit operand is omitted:
- The standard host name is not specified in the pdstart -x option. Specify the standard host name in the pdstart -x option (if the pdunit operand is omitted, the pdstart -u option cannot be specified).
|
NEED TO SPECIFY pd_rpl_hdepath | The pd_rpl_hdepath operand is not specified. When using HiRDB Datareplicator, specify the extracted HiRDB Datareplicator directory in the pd_rpl_hdepath operand. |
NEED TO SPECIFY pdunit -c host-name | The -c option of the pdunit operand was not specified. Specify this option for system switchovers that do not inherit IP addresses. On a unit using standby-less system switchover (effects distributed), this message is sometimes output if N is specified in the pd_ha_ipaddr_inherit operand of the system common definition or unit control information definition. In this case, omit the pd_ha_ipaddr_inherit operand. If the system contains units using standby-less system switchover (effects distributed) and switchover units that do not inherit IP addresses, omit the pd_ha_ipaddr_inherit operand in the system common definition and the pd_ha_ipaddr_inherit operand in the unit control information definition on the units using standby-less system switchover (effects distributed), and specify N in the pd_ha_ipaddr_inherit operand in the unit control information definition on the switchover units that do not inherit IP addresses. |
NO BES | There is no back-end server specification. The system requires at least one back-end server. Re-evaluate specification of the -t option in the pdstart operand. |
NO DIC | There is no directory server specification. The system requires at least one directory server. Re-evaluate specification of the -t option in the pdstart operand. |
NO FES | There is no front-end server specification. The system requires at least one front-end server. Re-evaluate specification of the -t option in the pdstart operand. |
NO MGR | There is no system manager specification. The system requires one system manager. Re-evaluate specification of the -t option in the pdstart operand. |
OUT OF SYSTEM | The host name of the host that executes HiRDB was not specified in the -x option of the pdunit operand. Re-evaluate the specification of the -x option in the pdunit operand. |
SDS SAME UNIT | Multiple single servers were defined in the same unit. Re-evaluate the specification of the pdstart operand. |
UNABLE TO SPECIFY pdunit -c unit-identifier | The -c option of the pdunit operand can be specified only when using a system switchover facility that does not inherit IP addresses. Delete the -c option when it does not apply. |
UNKNOWN HOSTNAME host-name (/etc/hosts) unit-identifier | The host name specified in the pdunit operand cannot be resolved. Change the host name specified in the pdunit operand, or else add it to the hosts file or register it on a DNS so that the name will be resolved. If a DNS is used, this reason code message is output even if the DNS is set correctly. In this case, ignore the message. In HiRDB Single Server, **** might be output as the unit identifier. |
INVALID pdcltgrp client-group-name | The group name specified in the -g option of the pdcltgrp operand is invalid. Re-evaluate the specification of the -g option. For details about client groups, see the HiRDB Version 9 System Operation Guide. |
NUMBER OF pdcltgrp EXCEEDS THE LIMIT | The number of user-specified pdcltgrp operand specifications exceeded 10. Reduce the number of specifications to 10 groups or less. |
EXCEEDED pd_max_users | The total number of minimal-guarantee connections for each client group specified by the pdcltgrp operand exceeded the value of the pd_max_users operand. Either decrease the total number of minimal-guarantee connections or increase the value of the pd_max_users operand. |
DUPLICATE pdcltgrp client-group-name | The client group name specified by the pdcltgrp operand was duplicated. Take action to resolve the client group name duplication. |
NUMBER OF SERVER EXCEEDS THE LIMIT | The number of servers exceeded the limit of servers in a unit (34). Re-evaluate the specification of the pdunit operand and reduce the number of servers defined in a unit. |
UNABLE TO SPECIFY pd_ha_agent | An error was found in the preconditions for using the rapid system switchover facility. Specify the following operands to use the rapid system switchover facility:
- pd_ha = use
- Do not specify pd_ha_unit
- pd_ha_ipaddr_inherit = N
- pd_ha_acttype = server
If the standby-less system switchover or standby-less system switchover (effects distributed) is used, the following operands must be specified. Check the contents specified for each operand.
- pd_ha = use
- pd_ha_unit is not specified.
- pd_ha_acttype = server
|
INVALID pd_max_users_wrn_pnt operand | An error was found in the specification of the pd_max_users_wrn_pnt operand. Specify a value in the specifiable range. |
INVALID pd_aud_file_wrn_pnt operand | An error was found in the specification of the pd_aud_file_wrn_pnt operand. Specify a value in the specifiable range. |
NUMBER OF CONNECT USERS EXCEEDS THE LIMIT | The sum of the values specified in the pc_max_users operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_users operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_users operand. |
NUMBER OF PROCESSES EXCEEDS THE LIMIT, server = server-name | - The applicable server is a back-end server:
The sum of the values specified in the pd_max_bes_process operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_bes_process operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_bes_process operand.
- The applicable server is a dictionary server:
The sum of the values specified in the pd_max_dic_process operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_dic_process operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_dic_process operand.
|
NEED TO SPECIFY pd_rise_pairvolume_combination | There is no specification of the pd_rise_pairvolume_combination operand. If Y is specified in the pd_rise_use operand, specify the pd_rise_pairvolume_combination operand. |
NEED TO SPECIFY pd_hostname | There is no pd_hostname operand specification. If Y is specified in the pd_rise_use operand, specify the pd_hostname operand. |
INVALID pd_mode_conf | The specification of the pd_mode_conf operand is invalid. If Y is specified in the pd_rise_use operand, specify MANUAL1 or MANUAL2 in the pd_mode_conf operand. |
INVALID pd_dbsync_point | The specification of the pd_dbsync_point operand is invalid. If hybrid or syssync is specified in the pd_rise_pairvolume_combination operand, commit cannot be specified in the pd_dbsync_point operand. |
NEED TO SPECIFY pd_rise_fence_level | There is no specification of the pd_rise_fence_level operand. If Y is specified in the pd_rise_use operand and sync, hybrid, or syssync is specified in the pd_rise_pairvolume_combination operand, the pd_rise_fence_level operand must be specified. |
INVALID KIND | The specification of the -k option of the pdstart operand in the system common definition is invalid. Alternatively, multiple function names are specified in the -k option. Revise the -k option. |
INVALID pdstart -k stls | The specification of the -k option of the pdstart operand in the system common definition is invalid. Possible causes are as follows:
- A server other than a front-end server is specified in the pdstart -t operand.
- The operand pdstart -k stls is specified on a unit where there is a server other than a front-end server.
- Make sure that the operand pdstart -k stls is not specified for a server on a unit that also holds a server other than a front-end server.
|
INVALID pdstart -c | The alternate BES name specified in the system common definition pdstart -c operand is invalid. Revise the alternate BES name specified in the system common definition pdstart -c operand. This reason code may be accompanied by maintenance information. |
INVALID pdstart -t | A server other than a back-end server was defined on the unit specified in the system common definition pdstart -c operand. A server other than a back-end server cannot be defined on a unit specified in the pdstart -c operand. Revise the pdstart -c operand specification and the server type on the alternate BES unit. This reason code may be accompanied by maintenance information. |
INVALID HiRDB port: error about host-name:host-name | Different port numbers (the -p option of the pd_name_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied. For units using standby-less system switchover, specify the same HiRDB port number (the -p option of the pd_name_port operand or pdunit operand) on the normal BES unit and alternate BES unit. |
INVALID scd port: error about host-name:host-name | Different scheduler port numbers (the -s option of the pd_scd_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied. For units using standby-less system switchover, specify the same scheduler port number (the -s option of the pd_scd_port operand or pdunit operand) on the normal BES unit and alternate BES unit. |
INVALID tm port: error about host-name:host-name | Different transaction server port numbers (the -t option pd_trn_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied. For units using standby-less system switchover, specify the same transaction server port number (the -t option of the pd_trn_port operand or pdunit operand) on the normal BES unit and alternate BES unit. |
NO SERVER IN HAGROUP UNIT unit-identifier | There is no primary system server among the units in the HA group. Define primary system server. |
INVALID SERVER IN UNIT unit-identifier | There is a server other than a back-end server defined among the units of an HA group or in normal BES units for which server was specified in the pd_ha_agent operand. Define only back-end servers among the units of an HA group or in normal BES units for which server was specified in the pd_ha_agent operand. |
INVALID pd_ha_agent unit-identifier | For the units in an HA group, activeunits was not specified in the pd_ha_agent operand. Specify activeunits in the unit control information definition pd_ha_agent operand of the unit specified in the pdhagroup -u operand. |
NEED TO SPECIFY pdstart -g: server-name | There is no HA group specification among the servers of the units in an HA group. Specify the HA group identifier that the unit belongs to in the pdstart -g operand for the servers in the units specified in the pdhagroup -u operand. |
INVALID pdstart -g: server-name | The servers of the units in the HA group are not included in the same HA group as the unit. Specify the HA group identifier that the unit belongs to in the pdstart -g operand for the servers in the units specified in the pdhagroup -u operand. |
INVALID pdhagroup -u unit-identifier | The unit specified in the pdhagroup -u operand was not defined in the pdunit -u operand. Revise the specification of the pdhagroup -u operand and the pdunit -u operand. |
INVALID HiRDB port: error about HA group-identifier | The HiRDB port numbers (the -p option of the pd_name_port operand or pdunit operand) of the units in an HA group are different. Specify the same HiRDB port number (the -p option of the pd_name_port operand or pdunit operand) for all units in the HA group. |
INVALID scd port: error about HA group-identifier | The scheduler port numbers (the -s option of the pd_scd_port operand or pdunit operand) of the units in an HA group are different. Specify the same scheduler port number (the -s option of the pd_scd_port operand or pdunit operand) for all units in the HA group. |
INVALID trn port: error about HA group-identifier | The transaction server port numbers (the -t option pd_trn_port operand or pdunit operand) of the units in an HA group are different. Specify the same transaction server port number (the -t option pd_trn_port operand or pdunit operand) for all units in the HA group. |
INVALID pdunit -d: error about HA group-identifier | The HiRDB directories of the units in the HA group are different. Specify the same HiRDB directory in the pdunit -d operand for all units in the HA group. |
UNABLE TO SPECIFY pdstart -g server-name | The pdstart -g operand was specified for servers in units not included in the HA group. The pdstart -g operand can only be specified for servers in units specified in the pdhagroup -u operand. Revise the pdhagroup -u operand and the pdstart operand. |
NEED TO ADD unit-identifier TO pdhagroup -u | Units for which activeunits was specified in the pd_ha_agent operand were not specified in the pdhagroup -u operand, and activeunits is specified in the unit control information definition pd_ha_agent operand of units not included in the HA group. Revise the pdhagroup -u operand and the pd_ha_agent operand. |
UNABLE TO SPECIFY pd_ha_max_act_guest_servers | The pd_ha_max_act_guest_servers operand was specified for units not included in the HA group. The pd_ha_max_act_guest_servers operand can be specified only for units specified in the pdhagroup -u operand. Revise the pdhagroup -u operand and the pd_ha_max_act_guest_servers operand. |
UNABLE TO SPECIFY SAME SYSTEM pdstart -c, pdstart -g | A server with the pdstart -c operand specified and a server with the pdstart -g operand specified are mixed within the same system. The standby-less system switchover (1:1) cannot be mixed in the same system with the standby-less system switchover (effects distributed). Revise the pdstart operand. |
INVALID pd_rpl_reflect_mode operand | The specification of the pd_rpl_reflect_mode operand is invalid. With HiRDB/Single Server, uap cannot be specified in the pd_rpl_reflect_mode operand. Refer to the manual HiRDB Datareplicator Version 8, revise the transaction reflection formula, and revise the system common definition pd_rpl_reflect_mode operand. |
INVALID pd_hostname | The host name specified in the pd_hostname operand cannot be converted to an IP address. Check the following items, and correct any error:
- Error in the hosts file setting
- Invalid privilege to the hosts file
- Setting error in the file that contains the DNS or NIS settings (nsswitch.conf, resolv.conf, etc.)
- Invalid privilege to the file that contains the DNS or NIS settings (nsswitch.conf, resolv.conf, etc.)
Also, if DNS or NIS is being used, a communication error might occur with the DNS server or NIS server. |
INVALID pd_aud_max_generation_size | The specification of the pd_aud_max_generation_size operand is invalid. In the pd_aud_max_generation_size operand, specify a value sufficient to store at least one audit trail record. For the maximum length of audit trail records, see the description of the pd_aud_max_generation_size operand in the manual HiRDB Version 9 System Definition. |
INVALID pd_aud_async_buff_size | The specification of the pd_aud_async_buff_size operand is invalid. In the pd_aud_async_buff_size operand, specify a value greater than the maximum audit trail record size. For the maximum length of audit trail records, see the description of the pd_aud_max_generation_size operand in the manual HiRDB Version 9 System Definition. |
DUPLICATE pdhagroup -g HA group-identifier | The HA group identifier specified in the -g option of the pdhagroup operand is the same as the HA group identifier specified in the -g option of another pdhagroup operand. In the pdhagroup -g operand of each HA group, specify a HA group identifier that is unique in the system. |
DUPLICATE pdhagroup -u unit-identifier | The unit identifier specified in the -u option of the pdhagroup operand is the same as the unit identifier specified in the -u option of another pdhagroup operand. Take action to resolve the unit identifier duplications in different HA groups. |
UNABLE TO SPECIFY SAME UNIT pdxds, 1:1 standby-less | The pdxds operand and 1:1standby-less system switchover are mixed within the same system. XDS and 1:1standby-less system switchover cannot be mixed in the same system. Revise the pdxds, pd_ha_agent, and pd_ha_unit operands in the system common definition. |
UNABLE TO SPECIFY SAME UNIT pdxds, effects distributed standby-less | The pdxds operand and standby-less system switchover (effects distributed) are mixed within the same system. XDS and standby-less system switchover (effects distributed) cannot be mixed in the same system. Revise the pdxds, pd_ha_agent, and pd_ha_unit operands in the system common definition. |
UNABLE TO SPECIFY SAME SYSTEM pdxds, real time SAN replication | The pdxds operand and Real Time SAN Replication are mixed within the same system. XDS and Real Time SAN Replication cannot be mixed in the same system. Revise the pdxds and pd_rise_use operands in the system common definition. |
DUPLICATE pdxds -s XDS-server-name | The XDS server name in the pdxds -s operand is duplicated. In the pdxds -s operand in the system common definition, specify an XDS server name that is unique in the system. |
DUPLICATE pdstart -s, pdxds -s XDS-server-name | The XDS server name in the pdxds -s operand is the same as the server name in the pdstart -s operand. In the pdxds -s operand in the system common definition, specify an XDS server name that is different from the server name in the pdstart -s operand. |
INVALID SERVER pdxds -r server-name | The server name in the pdxds -r operand does not exist in the pdstart operand. Specify the server name in the pdstart -s operand in the pdxds -r operand in the system common definition. |
KFPS01897-E E
Error found in system definition. file=aa....aa, line=bb....bb
- An error was found in the indicated definition.
- aa....aa: Definition file name
- bb....bb: Line number
- S: Terminates abnormally.
- Action
- Correct the definition file and re-execute HiRDB.
KFPS01898-E E+L
Error occurred while starting server, server ID=aa....aa, server type=bbb, reason code=cc....cc
- An error occurred while starting a HiRDB server.
- aa....aa: Server name
- bbb: Type of server
- cc....cc: Cause:
- CONFIGURATION:
- Error occurred during definition analysis.
- SERVER INIT ERROR:
- Error occurred during initialization of the HiRDB server.
- SERVER START ERROR:
- Error occurred during activation of a server process.
- S: CONFIGURATION displayed as the cause:
- Resumes processing.
- SERVER INIT ERROR or SERVER START ERROR displayed as the cause:
- Terminates the unit abnormally.
- Action
- For errors that occurred during definition analysis, correct the content of the definition file and use the server start command to start the server on which the error occurred. If the error occurs when initializing the HiRDB server or activating a server process, take action according to the messages outputbefore or after this message.
KFPS01899-E E
Error occurred while initializing server, server ID=aa....aa, server type=bbb, reason code=cc....cc
- An error occurred while initializing a HiRDB server.
- aa....aa: Server name
- bbb: Type of server
- cc....cc: Cause:
- CONFIGURATION: Error occurred during definition analysis.
- S: Terminates abnormally.
- Action
- Correct the error in the definition file and re-execute HiRDB.
KFPS01902-E E
Unable to start message log service due to insufficient memory
- The message log server process cannot be started due to insufficient process private area.
- S: Cancels processing.
- Action
- Terminate any unneeded processes and restart HiRDB.
KFPS01903-E E
Unable to start message log service due to communication failure
- The message log server process cannot be started due to a communication error.
- S: Cancels processing.
- Action
- If an error is found in the access privileges or settings defined in the hosts file, correct the hosts file. Check for the cause of the communication error, eliminate the cause, and then restart HiRDB.
- The port number specified in the -m option of the pd_mlg_port operand or pdunit operand might be the same as the port number of another definition or program. If they are the same, revise the values in the port number settings so that they are not duplicated, and then restart HiRDB.
KFPS01910-I E+L
Message log file changed over from aa....aa to bb....bb
- The message log obtained after this message will be output to the indicated message log file.
- aa....aa: Name of the current message log file#
- bb....bb: Name of the new message log file#
- Note
- To retain multiple generations of the message log file, save the current message log file immediately after output of this message.
- #: The message log file name is displayed by the absolute path. If the path exceeds 89 characters, only the last 89 characters are displayed.
- S: Resumes processing.
KFPS01911-E E+L
Error occurred while preprocessing message log file aa....aa
- An error occurred in the message log file due to the cause indicated in the KFPO00107-E message (reporting a start or open system call error) that was output before this message.
- aa....aa: Name of the message log file resulting in the error
- The message log file name is displayed by the absolute path. If the path exceeds 165 characters, only the last 165 characters are displayed.
- S: Cancels processing.
- Action
- Eliminate the cause of the message log file error and restart HiRDB.
KFPS01912-E E+L
Error occurred while opening message log file aa....aa
- A message log file open error occurred due to the cause indicated in the KFPO00107-E message (reporting an open system call error) that was output before this message.
- aa....aa: Name of the message log file resulting in the error
- The message log file name is displayed by the absolute path. If the path exceeds 171 characters, only the last 171 characters are displayed.
- S: Cancels processing.
- Action
- Eliminate the cause of the message log file error and restart HiRDB.
KFPS01913-E E
Error occurred during message log file changeover; message log output destination changed to standard error output
- An error occurred during message log file swapping. The output destination of the message log is being changed to the standard error.
- S: Changes the output destination of the message log to standard error, and then continues processing.
- Action
- Check the KFPS01912-E message output before this message for the cause of the error and correct the error so that the message log file can be opened.
KFPS01914-E E
I/O error occurred in message log file aa....aa; message log output destination changed to standard error output
- Because an I/O error occurred in log file aa....aa, the message log output destination was changed to the standard error.
- aa....aa: Name of the message log file resulting in the error
- S: Changes the output destination of the message log to standard error, and then continues processing.
- Action
- Check the cause of the I/O error (such as a full disk) and correct the error.
KFPS01915-I E+L
Message log output destination changed from standard error output to message log file aa....aa
- A message log file was opened successfully (by retry), and the message log output destination was changed from the standard error to the message log file.
- aa....aa: Name of the message log file after change
- The message log file name is displayed by the absolute path. If the path exceeds 131 characters, only the last 131 characters are displayed.
- S: Changes the message log output destination to the message log file and resumes processing.
KFPS01920-E E+L
Unable to handle program version aa....aa that requested message log output in this system. request source process ID=bb....bb
- The version of the message log service function that is being used by the program that issued the message log output request does not match the version of the message log server process. For this reason, the message log output request cannot be accepted.
- aa....aa: Version of the message log service function that is being used by the program that issued the message log output request
- bb....bb: Process ID of the source requesting output of message log
- S: Resumes processing.
- Action
- If the program requesting output of message log is a system program, contact the customer support center.
KFPS01921-I L
"Extended SYSLOG function" applied, func=aa....aa, code=bb
- The extended syslog facility is applied.
- aa....aa: Facility that applies one of the following
- High-availability: Improved reliability of the syslogfile
- High-availability and Code conversion: syslogfile with improved reliability and syslogfile character encoding conversion (converts SJIS to UTF-8)
- bb: Detail code
- 01: The character encoding# used by HiRDB is not SJIS.
- 02: The character encoding# used by HiRDB is SJIS.
- 03: The character encoding conversion of syslogfile cannot be used for one of the following reasons:
- The Hitachi encoding conversion has not been installed.
- The Hitachi encoding failed to initialize. Memory may be insufficient.
- 04: The character encoding# that HiRDB uses is SJIS. However, because the extended syslog facility does not support a character encoding conversion facility, syslogfile character encoding conversion cannot be used.
- #
- The character encoding that HiRDB uses is a character code classification in which the -c option of the pdsetup command is specified.
- S: Continues processing.
- Action
- If you want to use syslogfile character encoding conversion and you are on an OS that supports it, detail codes and actions are shown below.
Detail code | Action |
---|
01 02 | No action is necessary. |
03 | - If Hitachi encoding conversion has not been installed:
- Stop HiRDB, install Hitachi encoding conversion, and then restart HiRDB.
- If Hitachi encoding conversion has been installed:
- If there is a memory shortage, resolve it and then restart HiRDB.
- For situations other than those described above, stop HiRDB, install Hitachi encoding conversion, and then restart HiRDB. If you still have problems, contact the customer support center.
|
04 | If you use syslogfile character encoding conversion, stop HiRDB, install the extended syslog facility that supports the character encoding conversion facility, and then restart HiRDB. |
KFPS01933-E E
Unable to output message aa....aa due to invalid parameter
- Message log cannot be output, because a parameter is invalid for the message log service function.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- S: Resumes processing.
- Action
- Record this message log and the message ID of the message log that could not be output, and contact the customer support center.
KFPS01943-E E
Unable to output message aa....aa due to invalid parameter
- Message log cannot be output, because a parameter is invalid for the message log service function.
- aa....aa: Message ID of the message log that cannot be output
- S: Resumes processing.
- Action
- Record this message log and the message ID of the message log that could not be output, and contact the customer support center.
KFPS01944-E E
Unable to output message aa....aa; invalid parameter for message log service
- Message log aa....aa cannot be output, because a parameter is invalid for the message log service function.
- aa....aa: Message ID of the message log that cannot be output
- S: Resumes processing.
- Action
- Record this message log and the message ID of the message log that could not be output, and contact the customer support center.
KFPS01945-E E+L
failed in output of log message to JP1; output to JP1 is restrained. maintenance info: aa....aa
- Output to the Job Management Partner 1 event server was suppressed because log message output to the Job Management Partner 1 event server failed.
- aa....aa: Maintenance information
- S: Suppresses output to the Job Management Partner 1 event server.
- P: Contact the HiRDB administrator.
- Action
- If messages must be output to the Job Management Partner 1(Job Management Partner/Base or Job Management Partner/System Event Service) event server, investigate the cause of the failed connection and eliminate it.
KFPS01946-I S+L
Restarts log message output to JP1.
- Output of log messages to the Job Management Partner 1 event server was restarted because log message output to the Job Management Partner 1 event server succeeded.
- S: Resumes processing.
KFPS01947-E E+L
I/O error occurred during output of log message to JP1. maintenance info: aa....aa
- An I/O error occurred when a log message was being output to the Job Management Partner 1 event server.
- aa....aa: Maintenance information
- S: Resumes processing.
- P: Contact the HiRDB administrator.
- Action
- If messages must be output to the Job Management Partner 1 (Job Management Partner/Base or Job Management Partner/System Event Service) event server, investigate the cause of the failed connection and eliminate it.
KFPS01948-E E+L
Unable to connect to event server of JP1
- A connection to the Job Management Partner 1 event server cannot be established.
There is a specification to notify Job Management Partner 1 of HiRDB events (Y is specified in the pd_jp1_use operand), but a connection could not be established with the Job Management Partner 1 event server. - S: Resumes processing.
- Action
- If message output to the Job Management Partner 1 (Job Management Partner/Base or Job Management Partner/System Event Service) event server is necessary, investigate the cause of the failed connection and eliminate it. If this is not necessary, specify not to notify Job Management Partner 1 of HiRDB events (specify N in the pd_jp1_use operand), and restart HiRDB.
KFPS01950-I E+S
Usage: pdcat [-ab] [-c E |W |I |Q] [-x host name] [-d start date] [-t start time] [-T stop time] [-n record number] [message log file name]
- Displays the format of the pdcat command. This message is output when a specified command option or argument is invalid.
- O: If a command option or argument is invalid, reenter the command specified correctly.
KFPS01951-E E
Insufficient memory
- A shortage occurred in the process private area while executing a message log service function command.
- S: Cancels processing.
- Action
- Terminate any unneeded process.
KFPS01952-E E
Error occurred during message log service. maintenance information= aa....aa
- The message log service function resulted in an error.
- aa....aa: Maintenance information
- S: Cancels processing.
- Action
- Record this message and contact the customer support center.
KFPS01953-E E
Failed in obtaining message log file storage directory
- The system failed to obtain the message log file storage directory.
- S: Cancels processing.
- O: Set the PDDIR environment variable and re-execute.
KFPS01954-E E
Unable to open message log file aa....aa
- The indicated message log file cannot be opened, because it was not found or the read privilege has not been defined for the message log file.
- aa....aa: Name of message log file
- S: Cancels open processing for the corresponding message log file.
- O: Take appropriate action and re-execute.
- Action
- If the read privilege has not been defined for the corresponding message log file, define the privilege.
KFPS01955-E E
I/O error occurred in message log file aa....aa
- An error occurred in the message log file due to the cause indicated by the KFPO00107-E message that was output before this message.
- aa....aa: Message log file name
- S: Cancels processing.
- Action
- Eliminate the cause of the message log file error and re-execute.
KFPS01956-E E
I/O error occurred in message log file aa....aa
- Processing of the indicated file was cancelled due to a disk I/O error.
- aa....aa: Name of message log file
- S: Cancels all types of processing involving the corresponding file.
KFPS01957-E E
File aa....aa is not a message log file
- File aa....aa is not a message log file.
- aa....aa: Name of the file that was to be processed
- S: Aborts processing involving the applicable file.
KFPS01958-E E
Unable to handle the version (aa....aa) of the message log file (bb....bb) in this command
- The system failed to obtain the last update time because the applicable message log file was not found, or for some similar reason.
- aa....aa: Name of message log file
- bb....bb: Version number of the message log file
- S: Cancels all types of processing involving the corresponding file.
- Action
- Contact the customer support center.
KFPS01959-E E
No message log to output
- There is no message log to be output.
KFPS01968-E E
Unable to find message log file (aa....aa)
- Specified file was not found.
- aa....aa: Name of specified file
- S: Ignores the specified file and resumes processing.
- Action
- Record this message and contact the customer support center.
KFPS01971-E E
Communication failure occurred
- Command cannot be executed due to a communication error.
- S: Cancels processing.
- Action
- Refer to the message that was output immediately before this message to check the cause of the communication error, and correct the error.
KFPS01972-E E
Message log server inactive or terminated
- Because the message log server is not active or is engaged in termination processing, an entered command cannot be executed.
- S: Cancels processing.
- Action
- Start HiRDB with the pdstart command.
KFPS01973-E E
Versions of message log server and command are different
- A command cannot be executed, because its version does not match the version of the message log server.
- S: Cancels processing.
- Action
- Check the HiRDB installation method for an error.
KFPS01974-E E
Real-time output function active
- The realtime output function is active.
KFPS01975-E E
Real-time output function inactive
- The realtime output function is not active.
KFPS01976-E E
Unable to set environmental variable aa....aa
- Environment variable aa....aa has not been set.
- aa....aa: Name of the environment variable that has not been set
- S: Cancels processing.
- O: Set the environment variable and re-execute.
KFPS01977-E E
Name server inactive; unable to execute command
- A command cannot be executed, because the name server is not active.
- Action
- Start HiRDB with the pdstart command.
KFPS01978-E E
Invalid command argument
- A command argument is missing, or too many command arguments were specified.
- S: Cancels command processing.
- O: Reenter the command according to the command usage displayed immediately after this message log.
KFPS01979-E E
Mandatory option flag not specified or option flags specified in incorrect combination
- A required option flag is missing, or the combination of option flags is invalid.
- S: Cancels command processing.
- O: Reenter the command according to the command usage displayed immediately after this message log.
KFPS01980-E E+S
*** Unable to output message (aa....aa) due to memory shortage; component (bbb) ****
- Message log cannot be output due to a memory shortage.
- aa....aa: Message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Terminate any unneeded processes. Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
KFPS01981-E E+S
*** Unable to output message (aa....aa) due to memory shortage; component (bbb) ****
- Message log cannot be output due to a memory shortage or communication error.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Terminate any unneeded processes. Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
KFPS01983-E E+S
*** Unable to output message (aa....aa) due to message log file version different; component (bbb) ****
- Message log cannot be output, because the version of the message log file does not match the version of the program that issued the request.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Relink the executed program. Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
KFPS01984-E E+S
*** Unable to output message(aa....aa) due to message log file not found; component (bbb) ****
- Message log cannot be output, because the message log file was not found.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Ensure that the PDDIR environment variable has been specified correctly. Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
KFPS01985-E E+S
*** Unable to output message (aa....aa) due to message log file I/O error; component (bbb) ****
- Message log cannot be output, because an I/O error occurred in the message log file.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
- If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS01986-E E+S
*** Unable to output message (aa....aa) due to message log file access denied; component (bbb) ****
- Message log cannot be output, because no access privilege has been defined for the message log file.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- If there is no read permission for the message log file, provide read permission. If there is no retrieval permission for the directories on the message log file path, provide retrieval permission. Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
KFPS01989-E E
Unable to make message log file: file (aa....aa) version error. file=bb....bb, command=cc....cc
- Message log file cannot be created, because the entered command cannot process this version of the message log file (which is later than the command's version).
- aa....aa: Name of the file resulting in the error
- bb....bb: File version
- cc....cc: Command version
- S: Cancels command execution.
- Action
- Record this message and contact the customer support center.
KFPS01990-E E+S
*** Unable to output message (aa....aa) due to parameter too many; component (bbb) ****
- Message log cannot be output due to an invalid parameter.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
- If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS01991-E E+S
*** Unable to output message (aa....aa) due to parameter not enough; component (bbb) ***
- Message log cannot be output due to an invalid parameter.
aa....aa: Serial number assigned to the message ID of the message log that cannot be output
bbb: Name of the component that issued the message log output request - S: Resumes processing.
- Action
- Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
- If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS01992-I E+S
*** Unable to output message (aa....aa) due to message too long; component (bbb) ***
- A message was truncated, because the edited message length exceeded the maximum length.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS01993-E E+S
*** Unable to output message (aa....aa) due to invalid argument; component (bbb) ***
- Message log cannot be output due to an invalid parameter.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | KFPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
- This message may be output with a KFPA message ID if an attempt was made to re-execute the FETCH statement after an error occurred when the FETCH statement was executed during UAP processing. In such a case, correct the UAP.
- If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS01996-E E+S
*** Unable to output message (aa....aa) due to message not found; component (bbb) ***
- Message log cannot be output, because the message log file does not contain a message log.
- aa....aa: Serial number assigned to the message ID of the message log that cannot be output
- bbb: Name of the component that issued the message log output request
- S: Resumes processing.
- Action
- Check the appropriate message according to the message ID cross-reference table and the message ID:
Component name | First 4 digits of message ID |
---|
bac, cpy, jar, rec | KFPR |
bpp, cit, cpp | KFPZ |
dbh | KFPH |
dfc | FKPB |
dic | KFPD |
dsa, sta | KFPK |
exp, int, mod | KFPX |
goi, ric | KFPN |
ios | KFPI |
osl | KFPO |
lod, rld | KFPL |
sqa | KFPA |
utl | KFPU |
Other | KFPS |
- If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.
KFPS02101-I L
pd_spd_syncpoint_skip_limit is too small,assumed limit 2,server=aa....aa
- Either 1 was specified in the pd_spd_syncpoint_skip_limit operand of the aa....aa server or the result of the autocalculation was less than 2. 2 is assumed in the pd_spd_syncpoint_skip_limit operand, and processing resumes.
- aa....aa: Server name
- S: Continues processing.
- Action
- When 1 is specified in the pd_spd_syncpoint_skip_limit operand, correct the specified value. If this message was output by autocalculation, see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 9 System Operation Guide to determine whether or not to stop using autocalculation.
KFPS02102-E E+L
Unable to start syncpoint dump service aa....aa. reason code=bb....bb
- The synchronization point dump service cannot be started on the aa....aa server.
- aa....aa: Server name
- bb....bb: Reason code
- The table below lists the reason codes and the actions to be taken.
- S: Terminates HiRDB.
- Action
- Take action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action | Remarks |
---|
6 | Shared memory pool too small to process the request | Contact the customer support center. | -- |
8 77 88 | Memory shortage | Check the utilization status of the process private area and shared memory. |
9 | Analysis information file open error | Check the synchronization point dump file-related definitions. |
10 105 | Unresumable error during analysis processing |
15 36 | Network error | Check the cause of the error, take appropriate action, then restart the system. |
24 | Definition read failure | Take action appropriate to the message that was output before. |
28 | Memory shortage | Check the utilization status of the process private area and shared memory. |
33 34 | Internal conflict in name service function | Contact the customer support center. |
35 | Timeout | Check the cause of the error, take appropriate action, then restart the system. |
37 | Unable to use the name service function | Check the server execution status with a HiRDB command. |
38 50 79 | Inter-process communication error | Check the cause of the error, take appropriate action, then restart the system. |
41 | Status file I/O error |
43 | Unable to allocate work area | Check the utilization status of the process private area and shared memory. |
44 | Insufficient buffer sectors | Check the server definition. |
45 | Unable to allocate the requested size of records (insufficient status file capacity) |
47 | Inactive status server | Check the execution status of the status server with a HiRDB command. |
52 | Swapping error | Check the cause of the error, take appropriate action, then restart the system. |
72 | Status write error |
73 | Status read error |
74 | Definition analysis error | Refer to the KFPU message output immediately before, and take the appropriate action. If no message was output, contact the customer support center. |
76 | Internal file write error | Check the cause of the error, take appropriate action, then restart the system. |
89 | Duplicated definition file name | Check the server definition, correct the error, then restart the system. |
92 | File open error | Check the cause of the error, take appropriate action, then restart the system. | Details of the error are displayed in the KFPS-02122-W message. |
94 | Analysis error | Check the definition file, correct the error, then restart the system. | -- |
104 | In UNIX: Insufficient message queue In Windows: The size of the installation drive is insufficient. | In UNIX: Reconfigure the kernel (change the value of the msgmni message-related parameter). In Windows: On the HiRDB installation drive, allocate sufficient free space for the shared memory. |
119 | The specification values of the normal synchronization point dump file in the system definition for a transaction execution site and a log application site do not match. | Revise the specification values of the normal synchronization point dump file in the system definition for the transaction execution site and the log application site. |
120 | The synchronization point dump file in use does not exist. | Take the action indicated in the KFPS02181-E message. |
- --: Not applicable
KFPS02103-I L
Assumed pd_spd_syncpoint_skip_limit, value=aa....aa, server=bb....bb
- The value specified in the pd_spd_syncpoint_skip_limit operand was automatically calculated so that HiRDB restart processing does not take too long. Another possibility is that the result of the automatic calculation exceeded 100,000, so the value specified in the pd_spd_syncpoint_skip_limit operand is assumed to be 100000.
- aa....aa: Specification value calculated automatically
- bb....bb: Server name
- S: Continues processing.
- Action
- Refer to Monitoring UAP status (skipped effective synchronization point dump monitoring facility) in the HiRDB Version 9 System Operation Guide, and investigate whether or not to stop automatic calculation.
KFPS02104-W L
Unable to recover the previous syncpoint dump service status from status file; continues recovery processing without status file, reason code=aa....aa
- The previous synchronization point dump could not be restored from the status file. Recovery will be resumed without a status file.
- aa....aa: Reason code
- The table below lists the reason codes and the actions to be taken.
- S: Starts the server normally, but does not collect a synchronization point dump because restart from the system log is not possible.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
46 | Status record required for recovery does not exist. | Check the server definition. |
90 | Invalid status file contents |
93 | Invalid resource run ID | Check the definition as to whether it is the same as the one used during previous HiRDB session. |
KFPS02105-W L
Error occurred while terminating syncpoint dump service; continutes processing.reason code=aa....aa
- An error occurred while terminating the synchronization point dump service, but processing is continuing.
- aa....aa: Reason code
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
28 | Process private area cannot be allocated. Shared memory is insufficient. | Check the utilization status of the process. private area and shared memory. |
35 | Timeout occurred. | Check the cause of the error, take appropriate action, then restart the system. |
36 | Network error occurred. |
37 | Name service function cannot be used. | Check the server execution status with a HiRDB command. |
38 | Inter-process communication error occurred. | Check the cause of the error before the next startup, take appropriate action, then restart the system. |
KFPS02110-E L
Process-specific area found insufficient while performing syncpoint dump service for aa....aa service.
- A process private area shortage occurred during execution of synchronization point dump service on the aa....aa server.
- aa....aa: Server name
- S: Terminates HiRDB.
- Action
- Check the utilization status of the process private area and restart HiRDB.
KFPS02111-E L
Error occurred while performing syncpoint dump service for aa....aa service.reason code=bb....bb function: cc....cc
- An error occurred during synchronization point dump acquisition on the aa....aa server.
- aa....aa: Server name
- bb....bb: Reason code
- cc....cc: Name of the function resulting in the error
- S: Terminates abnormally.
- Action
- Take a corrective action by referring to the list of reason codes and restart HiRDB. If necessary, collect error information and contact the customer support center.
Reason code | Explanation | Action |
---|
4 | Shared memory cannot be accessed. | Contact the customer support center. |
11 | Argument is invalid. |
12 | Function issuance sequence error occurred. |
13 | Fatal or unexpected error occurred. | See -303 in 4.1 Detail codes for RPC-related errors. |
14 | Memory shortage occurred. | Check the memory usage. |
15 | Network error occurred. | Check the cause of the error with the procedure listed below and take appropriate action:
- Check the server machine connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
16 | Transfer timeout occurred. |
17 | Input parameter length exceeded the maximum. |
18 | Returned response is too long to fit in the area at the calling source. |
19 | Specified service function has not been registered. |
20 | Server is being terminated. |
21 | Process that provides the specified service function was not found. |
22 25 | Unexpected error occurred. |
23 | RPC environment is not active. |
26 | Name information retrieval error occurred. | Contact the customer support center. |
27 | Specified argument is invalid. |
28 | Process private area cannot be allocated. Shortage occurred in the shared memory. | Check the utilization status of the process private area and shared memory. |
29 | Versions do not match between function and shared memory or between function and server. | Check the cause of the error with the following procedure, and take appropriate action:
- Check the server machine connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
30 33 34 | Internal conflict was detected in the name service function. | Contact the customer support center. |
31 | Function parameter error occurred. | Check the cause of the error with the following procedure, and take appropriate action:
- Check the server machine connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
32 | Function issuance sequence error occurred. |
35 | Timeout occurred. | Check the cause of the error, take appropriate action, then restart the system. |
36 | Network error occurred. |
37 | Name service function cannot be used. | Check the server execution status with a HiRDB command. |
38 79 | Inter-process communication error occurred. | Check the cause of the error before the next startup, take appropriate action, then restart the system. |
39 | Status is invalid (the server is inactive, engaged in abnormal termination, or engaged in forced termination). |
80 84 86 87 | Specified array size exceeds the defined maximum size. | Contact the customer support center. |
81 82 | Area cannot be allocated. | Check the memory usage. |
83 | Error occurred during data conversion. | Contact the customer support center. |
85 | Text received from function is too short to set in arguments. |
109 110 | A timeout was detected during database buffer sweep-out processing. | Save the maintenance data under %PDDIR%\spool and contact the customer support center, then restart the system. |
111 112 | A timeout occurred during database buffer synchronization processing. |
KFPS02112-W L
Minor error occurred while analyzing definitions for syncpoint dump service. file being analyzed:aa....aa, record number=bb....bb, reason code=cc....cc
- A minor error occurred while analyzing definitions for the synchronization point dump service.
- aa....aa: Name of the definition file being analyzed
- bb....bb: Number of the record that had the error
- cc....cc: Reason code that shows the contents of the error
- S: Ignores the pdlogadfg or pdlogadpf operand definition statement that was in error, and starts the synchronization point dump service or continues restart processing (operates as though there were no definition statement).
- Action
- Refer to the following reason code list, and revise the definition related to the synchronization point dump service.
Reason code | Explanation | Action |
---|
411 | There is an error in the -a option specification of the pdlogadpf operand.
- The length of the path specified in the -a option exceeds the maximum number of characters.
- The length of the HiRDB file name specified in the -a option exceeds the maximum (30 characters).
| As necessary, stop the system, revise the definition, and restart. |
412 | There is an error in the -b option specification of the pdlogadpf operand (when duplexed synchronization point dump is used).
- The length of the path specified in the -b option exceeds the maximum number of characters.
- The length of the HiRDB file name specified in the -b option exceeds the maximum (30 characters).
|
KFPS02113-E L
Error occurred while analyzing definitions for syncpoint dump service. server=aa....aa, reason code=bb....bb, cc....cc
- An error occurred during analysis of the system definition related to a synchronization point dump file.
- aa....aa: Server name
- bb....bb: Reason code
- cc....cc: The following value is displayed, on the basis of the reason code:
- If the reason code is UNMATCH_DEFINITION
definition=dd....dd
dd....dd: Name of the operand with an unmatched definition
- If the reason code is UNMATCH_FILEGROUP
filegroup=ee....ee
ee....ee: Unmatched logical file name
- If the reason code is UNDEFINE_FILEPATH
filegroup=ff....ff
ff....ff: Logical file name for which no physical file name is defined
- S: Continues processing.
- Action
- Take action on the basis of the reason code.
Reason code | Explanation | Action |
---|
UNMATCH_DEFINITION | The value specified in the dd....dd operand differs between the transaction execution site and the log application site. | Set the value specified in the dd....dd operand for the log application site to match the value of the dd....dd operand for the transaction execution site. |
UNMATCH_FILEGROUP | A secondary synchronization point dump file group that matches the primary synchronization point dump file group is not defined for the log application site, or a secondary synchronization point dump file group that corresponds to a primary synchronization point dump file group that is not defined for the transaction execution site is defined for the log application site. | Make all of the log application site secondary synchronization point dump file group names match the transaction execution site primary synchronization point dump file groups. |
UNDEFINE_FILEPATH | A secondary synchronization point dump file that corresponds to a primary synchronization point dump file group is not defined for the log application site. | Define all secondary synchronization point dump files required to start the log application site. |
KFPS02114-E L
File error occurred while getting information while getting information necessary for aa....aa service recovery.
- A file error occurred while collecting the information required for recovery of server aa....aa.
- aa....aa: Name of the server resulting in the error
- S: Terminates HiRDB.
- Action
- Check both the error messages that were output before this message and the file status, then restart HiRDB.
KFPS02115-E L
File error occurred while getting syncpoint dump for aa....aa service
- A file error occurred while collecting a synchronization point dump for server aa....aa.
- aa....aa: Name of the server resulting in the error
- S: Terminates HiRDB.
- Action
- Check both the error messages that were output before this message and the file status, then restart HiRDB.
KFPS02118-I L
Syncpoint dump file group aa....aa for bb....bb service has been opened
- A synchronization point dump file for the bb....bb server was opened.
- aa....aa: File group name of the synchronization point dump file
- bb....bb: Server name
- S: Resumes processing.
KFPS02119-I L
Syncpoint dump file group aa....aa for bb....bb service has been closed
- A synchronization point dump file for the bb....bb server was closed.
- aa....aa: File group name of the synchronization point dump file
- bb....bb: Server name
- S: Resumes processing.
KFPS02122-W L
Error occurred while opening syncpoint dump file group for aa....aa service.file group name: bb....bb,reason code=cccc
- An error occurred while opening a synchronization point dump file group for server aa....aa.
- aa....aa: Name of the server resulting in the error
- bb....bb: Name of the file group resulting in the error
- cccc: Reason code (the table below lists the reason codes and the actions to be taken)
- S: Resumes processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
59 | File status flag is invalid. | Contact the customer support center. |
61 | The HiRDB file name is invalid. | Check and, if necessary, revise the server definition. |
62 | A synchronization point dump file was not created in the HiRDB file system area for system files. | Create a synchronization point dump file in the HiRDB file system area for system files. If Real Time SAN Replication is used, make the path to reference the synchronization point dump file on the remote site the same as on the main site. For a log application site, confirm that the path specified in the pdlogadpf -d ssp operand matches the path of the secondary synchronization point dump file created in the preparation for log application. |
63 | A synchronization point dump file could not be found. |
64 | File system versions do not match. | Check the HiRDB execution environment. |
65 | File system lock error occurred. |
66 | Shortage occurred in file system lock segments. | Check the memory usage. |
67 107 | Number of file systems opened exceeded the maximum. | Either close unneeded files or check the maximum number of files that can be opened and re-create the kernel, if necessary. |
68 | There is no access privilege for the corresponding HiRDB file system area. | Modify the access privileges for the corresponding HiRDB file system area using OS commands (chmod, for example). |
69 | There is no access privilege for the corresponding file. | Modify the access privileges for the HiRDB file system area where the corresponding file is stored using OS commands (chmod, for example). |
70 | File system I/O error occurred. | Check the cause of the I/O error and take appropriate action. |
71 | Memory shortage occurred in the file system. | Check the memory usage. |
88 | Memory shortage | Check the usage of the process private area. |
92 | File test error occurred (synchronization point dump file has not been initialized or is being used by another server or HiRDB). | Check the cause of the error with the following procedure, and take appropriate action:
- Re-evaluate the pdlogadpf operand of the synchronization point dump file or the system common definition.
- Initialize the HiRDB file system area for the synchronization point dump file, and then re-execute.
|
97 | Invalid size | Check the size of the synchronization point dump file. |
98 | I/O error | Check the cause of the I/O error and take appropriate action. |
106 | Invalid file name | Consider the following causes:
- An invalid character is specified in the file name.
- The length of the HiRDB file name exceeds the maximum (30 characters).
Check the file name specified in the server definition or the command operand. |
108 | Unregistered file name maximum | Use the pdlogadpf command to register the file name corresponding to the target file group. |
121 | The possible causes are as follows:
- An attempt was made to open a synchronization point dump file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.
- An attempt was made to open a synchronization point dump file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.
| Specify Y for the pd_large_file_use operand, or omit the specification. |
KFPS02123-W L
Error occurred while closing syncpoint dump file group for aa....aa service.file group name: bb....bb,reason code=cccc
- An error occurred while a synchronization point dump file on the aa....aa server was being closed.
- aa....aa: Name of the server on which the error occurred
- bb....bb: File group name of the synchronization point dump file in which the error occurred
- cccc: Reason code
- S: Continues processing.
- Action
- Take appropriate action according to the reason code.
Reason code | Explanation | Action |
---|
66 | Insufficient file system lock segments | Check the memory usage. |
70 | File system I/O error | Check the cause of the I/O error and take appropriate action. |
71 | File system memory shortage | Check the memory usage. |
91 | Error occurred in both the A system and B system. | See the KFPS4321-W message just output and take appropriate action. |
205 | Internal conflict in program | Contact the customer support center. |
KFPS02124-W L
Error occurred while reading from syncpoint dump file for aa....aa service.file name: bb....bb,generation number=cc....cc,reason code=dddd
- An error occurred while reading a synchronization point dump file for server aa....aa.
- aa....aa: Name of the server resulting in the error
- bb....bb: File group name of the synchronization point dump file in which the error occurred
- cc....cc: Generation number resulting in the error
- dddd: Reason code
- S: Continues processing.
- Action
- If the KFPS04323-W message is output immediately before this message, take action according to the KFPS04323-W message. If the KFPS04323-W message is not output immediately before this message, take appropriate action according to the reason code.
Reason code | Explanation | Action |
---|
1 | Record requested for input is outside the file area. | Contact the customer support center. |
70 | I/O error occurred. | Check the cause of the error and take appropriate action. |
71 | Memory is insufficient. | Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center. |
201 203 206 208 | Input error was detected in the synchronization point dump file. | Contact the customer support center. |
KFPS02125-W L
Error occurred while writing to syncpoint dump file for aa....aa service.file group name:bb....bb,generation number=cc....cc.reason code=dddd
- An error occurred when a synchronization point dump file on the aa....aa server was being written to.
- aa....aa: Name of the server resulting in the error
- bb....bb: File group name of the synchronization point dump file in which the error occurred
- cc....cc: Generation number resulting in the error
- dddd: Reason code
- S: Continues processing.
- Action
- If the KFPS04322-W message is output immediately before this message, take action according to the KFPS04322-W message. If the KFPS04322-W message is not output immediately before this message, take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
1 | Record requested for input is outside the file area. | Contact the customer support center. |
70 | I/O error occurred. | Check the cause of the error and take appropriate action. |
71 | Memory is insufficient. | Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center. |
95 | The requested number of records cannot be written into the synchronization point dump file. | Contact the customer support center. |
202 204 207 209 | Output error was detected in the synchronization point dump file. |
KFPS02126-E L
Number of file groups is insufficient for aa....aa service.number of available file groups=bb....bb,number of guaranteed generations=cc....cc
- There is a shortage of synchronization point dump files on the aa....aa server. The number of synchronization point dump files on the aa....aa server did not satisfy the condition guaranteed-generation-count + 1.
- aa....aa: Server name
- bb....bb: Number of available synchronization point dump file groups
- cc....cc: Number of guaranteed generations
- S: Cancels collection of synchronization point dump for server aa....aa.
- Action
- Refer to the following messages that were output before this message to check the cause of the error:
- KFPS02122-W
- KFPS02124-W
- KFPS202127-W
KFPS02127-W L
Unable to use syncpoint dump file for aa....aa service due to insufficient file capacity,file group name=bb....bb,system A/B=c,file capacity=dd....dd,size needed for syncpoint dump=ee....ee
- A synchronization point dump file for server aa....aa cannot be used due to insufficient size.
- aa....aa: Server name
- bb....bb: File group name
- c: System type (a: A system, b: B system)
- dd....dd: Capacity of synchronization point dump files (record count)
- ee....ee: Requested record count of synchronization point dump files
- S: Continues processing.
- Action
- Change the synchronization point dump file capacity for the system displayed in c. See the requested record count indicated in ee....ee.
KFPS02128-E E
Server name aa....aa specified with this command is invalid.
- An invalid server name (aa....aa) was specified in a command.
- aa....aa: Server name
- S: Cancels command execution.
- O: Enter the correct server name and re-execute the command.
KFPS02129-E E
Syncpoint dump file group name aa....aa specified with this command is invalid.
- The synchronization point dump file name specified by the command is invalid.
- aa....aa: File group name
- S: Cancels command execution.
- O: Correctly enter the file group name of the synchronization point dump file, and then re-execute the command.
KFPS02131-E E
-g option specified with this command is invalid.
- The -g option is invalid in a command.
- S: Cancels command execution.
- O: Specify the -g option correctly and re-execute the command.
KFPS02132-E E
Stops command processing due to error. reason code=aa....aa
- Command processing was cancelled due to an error.
aa....aa: Reason code indicating the nature of the error - S: Cancels command execution.
- Action
- Check the error message in the message log file and take appropriate action.
Reason code | Explanation | Action |
---|
2 | Parameter error occurred in a shared memory function. | Contact the customer support center. |
3 | Request segment size is greater than the pool size for the entire shared memory. |
4 | Attempt was made to share a segment allocated by another process, but the segment has not been allocated. | Check the execution status of the log/synchronization point dump service function with a HiRDB command and reenter the command in the online mode. |
5 | Function execution sequence error occurred. |
6 | Size of shared memory pool is insufficient | Contact the customer support center. |
7 | Shared memory pool lock processing failed. |
11 | Argument is invalid. |
12 | Function input sequence error occurred. |
13 | Fatal or unexpected error occurred. | See -303 in 4.1 Detail codes for RPC-related errors. |
14 | Memory shortage occurred. | Check the memory usage. Check the cause of the error using the following procedure and take appropriate action:
- Check the server machine connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
15 | Network error occurred. |
16 | Transfer timeout occurred. |
18 | Length of input parameter exceeds the maximum. |
18 | Returned response is too long to fit in the area at the calling source. |
19 | Specified service function has not been registered. |
20 | Server is being terminated. |
21 | Process that provides the specified service function was not found. | Check the cause of the error using the following procedure and take appropriate action:
- Check the server machine connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
22 25 | Unexpected error occurred. |
23 | RPC environment is not active. |
26 | Name information retrieval error occurred. | Contact the customer support center. |
27 | Specified argument is invalid. |
28 | Process private area cannot be allocated. | Check the memory usage. |
29 | Versions do not match between function and shared memory or between function and server. | Check the cause of the error using the following procedure and take appropriate action:
- Check the node connection status with an OS command.
- Check the execution status of each server with a HiRDB command.
|
31 | Function parameter error occurred. |
32 | Function input sequence error occurred. |
35 | Timeout occurred. |
36 | Network error occurred. |
37 | Name service function cannot be used. |
40 | Specified key value already exists. | Check the server definition or initialization. |
41 | I/O error occurred. | Check the cause of the I/O error and take appropriate action. |
42 | Offset + length is outside the allocated area. | Contact the customer support center. |
43 | Work area cannot be allocated. | Check the memory usage. |
44 | There are not enough buffer sectors. | Check the server definition. |
45 | Requested number of records cannot be allocated (insufficient status file size). |
46 | No record has the corresponding key value. | Contact the customer support center. |
47 | Server for executing the status service function is not active. | Check the server execution status with a HiRDB command. |
48 | Offset is outside the allocated area. | Contact the customer support center. |
49 | Parameter format is invalid. |
50 | Inter-process communication error occurred. | Check the server execution status with a HiRDB command. |
51 | Requested size is invalid. | Contact the customer support center. |
52 | Swapping error occurred. | See -1039 in 4.2 Detail codes for system-related errors, and take appropriate action. Then, start HiRDB. |
53 | Protocol version error occurred. | Contact the customer support center. |
54 | Size is different from an existing key value. |
80 84 86 87 | Specified array size exceeds the defined maximum size. |
81 82 | Area cannot be allocated. | Check the memory usage. |
83 | Error occurred during data conversion. | Contact the customer support center. |
85 | Text received from function is too short to set in arguments. |
96 | Internal conflict was detected in program. |
97 | Invalid file error occurred. | Check the size of the synchronization point dump file. Check the cause of the I/O error and take appropriate action. |
98 | I/O error occurred. |
KFPS02135-E L
File group name aa....aa specified in definition file bb....bb is already defined in definition file cc....cc
- File group name bb....bb specified in definition file aa....aa has already been defined in definition file cc....cc.
- aa....aa: Name of the erroneous definition file
- bb....bb: File group name
- cc....cc: Name of the definition file containing the specified file group name
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Correct the duplicated file group name.
KFPS02137-E L
Physical file name aa....aa specified in definition file bb....bb is already defined in definition file cc....cc.
- File name bb....bb specified in definition file aa....aa has already been defined in definition file cc....cc.
- aa....aa: Name of the erroneous definition file
- bb....bb: Physical file name
- cc....cc: Name of the definition file containing the specified file name
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Correct the duplicated file name.
KFPS02139-E L
Definition file aa....aa contains commands with deleted file group name bb....bb
- File group name bb....bb that was deleted from the definition during normal startup was found in definition file aa....aa at the time of synchronization point dump restart.
- aa....aa: Name of the erroneous definition file
- bb....bb: File group name
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Restore the deleted definition generation so that the same information is used as when the system was started normally.
KFPS02141-E L
File group name aa....aa specified with pdlogadfg is already defined in definition file bb....bb. record number=cc....cc
- File group name bb....bb specified in pdlogadfg in definition file aa....aa has already been specified in the same definition.
- aa....aa: Name of the erroneous definition file
- bb....bb: File group name
- cc....cc: Record number in the erroneous definition file
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Correct the duplicated file group name.
KFPS02143-E L
Physical file name aa....aa specified with pdlogadpf is already defined in definition file bb....bb. record number=cc....cc
- The file name is specified in the pdlogadpf operand more than once.
- aa....aa: File name that is specified more than once
- bb....bb: File name of the server definition in which the error occurred
- cc....cc: Record number in the definition file in which the error occurred
- S: Terminates processing.
- Action
- Correct the file name that is specified more than once.
KFPS02144-E L
pdlogadfg does not specify file group name in definition file aa....aa. record number=bb....bb
- A file group name is missing in pdlogadfg specified in definition file aa....aa.
- aa....aa: Name of the erroneous definition file
- bb....bb: Record number in the erroneous definition file
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Check the information specified in the definition file and correct the error.
KFPS02145-E L
pdlogadpf does not specify file group name in definition file aa....aa.record number=bb....bb
- A file group name is missing in pdlogadpf specified in definition file aa....aa.
- aa....aa: Name of the erroneous definition file
- bb....bb: Record number in the erroneous definition file
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Check the information specified in the definition file and correct the error.
KFPS02147-E L
pdlogadpf does not specify physical file name in definition file aa....aa.record number=bb....bb
- The pdlogadpf operand does not specify a synchronization point dump file name.
- aa....aa: File name of the server definition where the error occurred
- bb....bb: Record number in the definition file where the error occurred
- S: Terminates processing.
- Action
- Take one of the following actions:
- If the synchronization point dump file is not duplicated, determine whether the -a option is specified in the pdlogadpf -d spd or pdlogadpf -d ssp operand.
- If the synchronization point dump file is duplicated, determine whether the -a and -b options are specified in the pdlogadpf -d spd or pdlogadpf -d ssp operand.
KFPS02148-E L
File group name specified with pdlogadpf not defined in definition file aa....aa.record number=bb....bb
- The file group name bb....bb was defined in the pdlogadfg operand but was not defined in the pdlogadpf operand.
- aa....aa: Name of the erroneous definition file
- bb....bb: Record number in the definition file where the error occurred
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Check the following items in the pdlogadfg operand and the pdlogadpf operand for definition file aa....aa.
- Is file group name bb....bb correct?
- After file group name bb....bb was defined in the pdlogadfg operand, was it defined in the pdlogadpf operand?
KFPS02149-E L
Number of pdlogadfg -d bbb commands with ONL is insufficient in definition file aa....aa
- When a synchronization point dump was started, the number of pdlogadfg -d bbb specifications with ONL specified in the system definition was insufficient. (number-of-guaranteed-valid-generations+1).
- aa....aa: Name of the erroneous definition file
- bbb: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.
- Action
- Check the information specified in the definition file and correct the error.
KFPS02153-E E+L
Number of pdlogadfg -d bbb commands exceeds the limit in definition file aa....aa
- The number of pdlogadfg -d bbb specifications exceeds the limit.
- aa....aa: Name of the erroneous definition file
- bbb: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Cancels unit startup processing.
- Action
- Revise the number of pdlogadfg -d bbb specifications to a maximum of 60.
KFPS02154-E L
More than one pdlogadpf -d ccc command is specified for pdlogadfg -g bb....bb in definition file aa....aa
- More than one pdlogadpf -d ccc was specified for pdlogadfg -g bb....bb.
- aa....aa: Name of the erroneous definition file
- bb....bb: File group name for which pdlogadpf was specified more than once
- ccc: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Cancels unit startup processing.
- Action
- Ensure that only one pdlogadpf is specified for each file group indicated in pdlogadfg.
KFPS02155-E E+L
Number of pdlogadpf -d bbb commands exceeds the limit in definition file aa....aa
- The number of pdlogadpf -d bbb specifications exceeds the limit.
- aa....aa: Name of the erroneous definition file
- bbb: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Cancels unit startup processing.
- Action
- Check the information specified in the definition file and correct the error.
KFPS02156-E L
Pdlogadpf -d ccc is not specified for pdlogadfg -g bb....bb in definition file aa....aa
- The pdlogadfg -g bb....bb has no corresponding pdlogadpf -d ccc.
- aa....aa: Name of the erroneous definition file
- bb....bb: File group name specified with pdlogadfg
- ccc: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Cancels unit startup processing.
- Action
- Check the information specified in the definition file and correct the error.
KFPS02157-E L
Shared memory error occurred while starting or terminating syncpoint dump service.reason code=aa....aa, function=bb....bb
- A shared memory error occurred while starting or terminating the synchronization point dump service function.
- aa....aa: Reason code
- bb....bb: Name of the function resulting in the error
- S: Cancels unit startup processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
4 | Shared memory cannot be accessed. | Contact the customer support center. |
6 | Size of shared memory pool is too small to process the request. |
KFPS02158-E L
Error occurred in status file while starting or terminating syncpoint dump service. reason code=aa....aa, function=bb....bb
- A status file error occurred while starting or terminating the synchronization point dump service function.
- aa....aa: Reason code
- bb....bb: Name of the function resulting in the error
- S: Cancels unit startup processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
41 | I/O error occurred. | Check the cause of the I/O error and take appropriate action. |
43 | Work area cannot be allocated. | Check the memory usage. |
44 | There are not enough buffer sectors. | Check the server definition. |
45 | Requested number of records cannot be allocated (insufficient status file). |
47 | Status server is not active. | Check the server execution status with a HiRDB command. |
50 | Inter-process communication error occurred. | Check the cause of the error, take appropriate action, |
52 | Swapping error occurred. | then restart the system. |
KFPS02159-E L
Memory found insufficient while starting or terminating syncpoint dump service.
- A memory shortage occurred while starting or terminating the synchronization point dump service function.
- S: Cancels unit startup processing.
- Action
- Check the memory for any excess resources and release unneeded resources. Or, check the defined shared memory size, take appropriate action, then restart.
KFPS02160-E L
Error occurred in system service call while starting or terminating syncpoint dump service. reason code=aa....aa, function=bb....bb
- An error occurred while starting or terminating the synchronization point dump service function.
- aa....aa: Reason code
- bb....bb: Name of the function resulting in the error
- S: Cancels unit startup processing.
- Action
- Take action appropriate to the reason code, as listed below:
Reason code | Explanation | Action |
---|
72 | Status file write error occurred. | Check the cause of the error and take appropriate action. |
73 | Status file read error occurred. |
74 | Server definition analysis error occurred. | Check the corresponding server definition, correct the error, then restart the system. |
75 | Server terminated abnormally during normal termination or planned shutdown. Or, server is engaged in abnormal termination processing. | Check the cause of the error and take appropriate action. |
77 | Memory shortage occurred. | Check the memory usage. |
78 | Attempt was made to terminate the server forcibly, but the server was on critical status. | Check the cause of the error and take appropriate action. |
79 | Inter-process communication error occurred. |
KFPS02167-W E
File group specified with the command is already open.
- The file group specified in a command is already open.
- S: Cancels command execution.
- O: Enter the pdlogls command to check the file status.
KFPS02168-W E
File group specified with the command is already closed.
- The file group specified in a command is already closed.
- S: Cancels command execution.
- O: Enter the pdlogls command to check the file status.
KFPS02169-E E
Failure to open syncpoint dump file.
- The system failed to open a synchronization point dump file.
- S: Cancels command execution.
- O: Enter the pdlogls command to check the file status. Also, refer to the KFPS02122-W message that was output to the message log file to check the cause of the error.
KFPS02170-E E
Failure to close syncpoint dump file. reason code=aa....aa
- The system failed to close a synchronization point dump file.
- aa....aa: Reason code
- S: Cancels command execution.
- O: Check the reason code and take appropriate action:
Reason code | Explanation | Action |
---|
91 | Error occurred in the file system. | Refer to the KFPS02123-W message output to the log file to check the cause of the error and take appropriate action. |
99 | Close request was issued for a valid file. | Enter the pdlogls command to check the status of the corresponding file. |
100 | Close request was issued for a file being input or output. | Enter the pdlogls command to make sure that the most recent synchronization point dump file points to the current log, then re-execute the command. |
KFPS02171-E E
Unable to perform command processing because there is not enough memory to allocate work area.
- Command cannot be executed, because a work area cannot be allocated.
- S: Cancels command execution.
- Action
- Check for excess memory resources and release any unneeded resource. Or, check the shared memory size specified in the definition, take appropriate action, then reenter the command.
KFPS02172-I E
There is no information to be displayed about syncpoint dump file.
- There is no synchronization point dump file information to be displayed.
There is no synchronization point dump file information to be displayed by the pdlogls command. - S: Terminates command processing.
- O: Check whether the system is in the online mode. Or, check the server execution status and reenter the command.
KFPS02173-E L
Status file error occurred during syncpoint dump processing. reason code=aa....aa
- A status file error occurred during synchronization point dump processing.
- aa....aa: Reason code
- S: Cancels unit startup processing.
- Action
- See the reason code list and take appropriate action. Then re-start HiRDB. If it is necessary to contact the customer support center, obtain data on the error information and then contact the customer support center.
Reason code | Explanation | Action |
---|
40 | Specified key value already exists. | Check the server definition or initialization. |
41 | I/O error occurred. | Check the cause of the I/O error and take appropriate action. |
42 | Offset + length is outside the allocated area. | Contact the customer support center. |
43 | Work area cannot be allocated. | Check the memory usage. |
44 | There are not enough buffer sectors. | Check the server definition. |
45 | Requested number of records cannot be allocated (insufficient status file size). |
46 | No record has the corresponding key value. | Contact the customer support center. |
47 | Status server is inactive. | Check the server execution status with a HiRDB command. |
48 | Offset is outside the allocated area. | Contact the customer support center. |
49 | Parameter format is invalid. |
50 | Inter-process communication error occurred. | Check the server execution status with a HiRDB command. |
51 | Requested size is invalid. | Contact the customer support center. |
52 | Swapping error occurred. | See -1039 in 4.2 Detail codes for system-related errors, and take appropriate action. Then, start HiRDB. |
53 | Protocol version error occurred. | Contact the customer support center. |
54 | Size is different from an existing key value. |
KFPS02174-E L
Contents of syncpoint dump file for aa....aa service are invalid,file group name=bb....bb
- The content of the synchronization point dump file is invalid.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file where the error occurred
- S: Continues processing.
- Action
- Re-create the synchronization point dump file of bb....bb.
KFPS02176-I L
No syncpoint dump file available for next acquisition.
- No file is available for the next synchronization point dump.
- Action
- Open a reserve file to provide the file for the next synchronization point dump.
KFPS02177-I L
Number of syncpoint dump files is not enough for aa....aa service recovery; opens all files.
- There are not enough synchronization point dump files to recover server aa....aa. The system opens all files.
- aa....aa: Server name
KFPS02178-E E+L
Unable to acquire syncpoint dump for assuring syncpoint failure in remote site, server name=aa....aa, group=bb....bb, reason code=cc....cc
- The RDAREA on a remote site for a synchronization point of cannot be acquired.
An inconsistency may have occurred in the data transmitted from server aa....aa that output this message to the remote site due to the Real Time SAN Replication not working correctly. If HiRDB is started on the remote site in this condition, HiRDB cannot start, the data lacks integrity, or the data is corrupt. - aa....aa: Name of the server for which a synchronization point dump could not be acquired
- bb....bb: Name of the pair logical volume group that detected the error
- cc....cc: Reason code
- S: Suspends synchronization point acquisition processing if the protection mode (the value specified in the pd_rise_fence_level operand) is data. Resumes synchronization point acquisition processing if the protection mode is never.
- Action
- Refer to the list of reason codes, and take appropriate action. If HiRDB is running, remove the data inconsistency between the main site and the remote site by taking appropriate action, and then execute the pdlogsync command for server aa....aa and acquire the synchronization point dump.
Reason code | Explanation | Action |
---|
115 116 117 118 119 | During server aa....aa synchronization point dump acquisition processing, the system was waiting for group bb....bb update data copy processing, but the wait failed. | See the KFPS04680-E or KFPS01815-E message displayed immediately before, investigate the cause of the error, and take appropriate action. |
KFPS02179-I L
Syncpoint dump acquisition opportunities for aa....aa service were skipped.number of skip=bb....bb, log generation number=cc....cc factor code=ddd-ee
- There was an opportunity to acquire a synchronization point dump, but because the last synchronization point dump was still processing, the synchronization point dump acquisition opportunity for server aa....aa was ignored.
- aa....aa: Server name
- bb....bb: Total number of synchronization point dump opportunities that were ignored
- Even if synchronization point dumps have been collected, depending on the timing, synchronization point dump collection opportunities might be ignored. In such a case, 0 is displayed.
- cc....cc: Log generation number whose synchronization point dump opportunity was ignored
- ddd: Cause code indicating the reason for ignoring the synchronization point dump opportunity (this code indicates the HiRDB internal status; the user need not know the code)
- ee: Detail code for the ignored synchronization point dump opportunity
- S: Continues processing.
- Action
- This message is output in the following cases:
- The system log file swap interval is short.
- Execution of the UAP transaction is slow relative to the synchronization point dump acquisition interval.
- Due to deferred write processing, synchronization point dump collection is slow.
- If this message is output repeatedly, take the following action on the basis of the factor code:
- factor code = A01-01
Take action as indicated in the section on the tuning of synchronization point dump processing when deferred write processing is applicable in the manual HiRDB Version 9 System Operation Guide.
- factor code = A01-02
Transactions that were not completed when the last synchronization point dump was acquired are still not complete. The cause is the slow execution of the UAP transactions relative to the synchronization point dump acquisition interval. Take corrective action according to message KFPS04374-I, output immediately after this one. If this message is output again, even after taking these actions, take the actions below under Factor code other than the above.
- Factor code other than the above
Increase the value of the pd_log_sdinterval operand. Alternatively, take measures to increase the size of the system log file. If this message continues to be repeatedly output, revise the UAP. Consider shortening the execution time per transaction by splitting the slow transactions into multiple transactions.
- Also, even if this message is output, if there is sufficient system log file space prepared for the swap target, this will not be a hindrance to continuing online or restarting. However, it may take time to restart HiRDB.
KFPS02181-E L
Unable to find syncpoint dump file for aa....aa service recovery.
- There is no synchronization point dump file for recovering server aa....aa.
If Real Time SAN Replication with the log-only synchronous method is used and a log application site HiRDB outputs this message, this indicates that no secondary synchronization point dump files are required for preparation for log application of server aa....aa. Consider the following causes: - There is an error in the path name or file name of the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand.
- The secondary synchronization point dump file specified in the pdlogadpf -d ssp operand does not exist.
- The secondary synchronization point dump file specified in the pdlogadpf -d ssp operand cannot be accessed.
- Preparation for log application was not completed correctly, because there is no pdlogadfg -d spd operand that specifies the same file group name as the pdlogadpf -d ssp operand.
- aa....aa: Server name
- S: Outputs the KFPS02102-E message and terminates HiRDB.
- Action
- Check the error message output before this message, make sure that the same synchronization point dump file is used that was used during the previous online session, then restart HiRDB.
- If Real Time SAN Replication with the log-only synchronous method is used and a log application site HiRDB outputs this message, take the following actions:
- Determine whether there is an error in the path name or file name of the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand, and correct the error.
- Investigate the reason that the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand cannot be accessed, correct the error, perform preparation for log application, and restart HiRDB. For details about preparation for log application, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
- If there is no pdlogadfg -d spd operand that specifies the same file group name as the pdlogadpf -d ssp operand, verify that the file group name specified in the pdlogadpf -d ssp operand is correct.
KFPS02182-E L
Insufficient memory. size=aa....aa, area type:bb....bb
- A memory shortage occurred.
- aa....aa: Size of area that was to be allocated
- bb....bb: Type of area resulting in the memory shortage
- S: Terminates HiRDB.
- Action
- If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, check the system definition, take appropriate action, and then restart HiRDB.
KFPS02183-I S+L+R
Syncpoint dump for aa....aa has been acquired to file group bb....bb. log file information:cc....cc,dd....dd,ee....ee. start time=ff....ff, end time=gg....gg
- Synchronization point dump for server name aa....aa was collected in bb....bb.
- aa....aa: Server name
- bb....bb: File group of destination synchronization point dump file
- cc....cc: Log file group name
- dd....dd: Log file generation number
- ee....ee: Log file block number
- ff....ff: Synchronization point dump collection starting time (hh:mm:ss)
- gg....gg: Synchronization point dump enabling completion time (hh:mm:ss)
- S: Resumes processing.
KFPS02184-E E
Unable to close the file group because number of file groups is insufficient.
- Specified file group cannot be closed, because there are not enough file groups.
If the specified file group is closed, the number of synchronization point dump file groups would be less than the number of guaranteed-valid generations + 1. - S: Cancels command execution.
- O: Enter the pdlogls command to check the file status.
KFPS02185-I L
aa....aa service is recovered with syncpoint dump of file group bb....bb.
- Server aa....aa was recovered from a synchronization point dump in file group bb....bb.
- aa....aa: Server name
- bb....bb: File group name
KFPS02186-W L
aa....aa service could not recovered with effective syncpoint dump.
- Server aa....aa cannot be recovered from a valid synchronization point dump.
- aa....aa: Server name
- S: Attempts to recover the server from previous synchronization point dump generations that can be read.
- Action
- Check the guaranteed-valid generations to determine why they cannot be read and take appropriate action.
KFPS02187-I L
Number of syncpoint dump files is not enough for aa....aa service; continues syncpoint dump processing with file reduced mode
- Operation has switched to the reduced mode, because there are not enough synchronization point dump files for server aa....aa.
- aa....aa: Server name
- Action
- Refer to the message that was output before this message to check the cause.
KFPS02188-I L
Number of syncpoint dump files is enough for aa....aa service; continues syncpoint dump processing with normal mode
- Operation has switched to the normal mode, because the specified number of synchronization point dump files were allocated for server aa....aa.
- aa....aa: Server name
- S: Resumes processing.
KFPS02189-W L
Take measure; syncpoint dump service for aa....aa service is file reduced mode
- The synchronization point dump service function for server aa....aa is in the reduced operation mode; appropriate action should be taken immediately.
- aa....aa: Server name
- S: Resumes processing.
- Action
- Refer to the message that was output before this message to check the cause.
KFPS02190-E L
Number of pdlogadfg -d bbb commands with ONL exceeds the limit in definition file aa....aa
- The number of pdlogadfg -d bbb specifications with ONL specified exceeds the limit.
- aa....aa: File name of the server definition where the error occurred
- bbb: File type
- spd: Synchronization point dump file
- ssp: Secondary synchronization point dump file
- S: Terminates the HiRDB system.
- Action
- Limit the number of operands (pdlogadfg -d spd or ssp) with ONL specified in the server definition files to 30, and restart HiRDB.
KFPS02191-E E
-b option specified with this command is invalid.
- An error was found in the specification of the -b option (B system). The -b option was not specified, even though the synchronization point dump file was duplicated. Or, the -b option was specified, even though the synchronization point dump file was not duplicated.
- S: Terminates processing.
- Action
- Check the specification (whether or not the synchronization point dump file is duplicated) of the pd_spd_dual operand, and then re-execute the command.
KFPS02192-W E
File group specified with the command is already allocate
- A file has already been allocated to the file group specified in a command.
- S: Cancels command execution.
- Action
- Check the file group for which the physical file is to be allocated and re-execute the command.
KFPS02193-E E
Physical file name aa....aa specified with this command is invalid,system A/B=b
- An error was found in the synchronization point dump file name specified by the command.
- aa....aa: File name
- If the file name exceeds 148 characters, the last 148 characters of the file name are output.
- b: System type (a: A system, b: B system)
- S: Terminates processing.
- Action
- Consider the following causes. Check the file name specified in the option, then re-execute the command.
- The file path name exceeds the maximum number of characters.
- The length of the HiRDB file name exceeds the maximum (30 characters).
- The specified file name is in use by the file group of another synchronization point dump file.
KFPS02194-I L
Syncpoint dump file group cc....cc for aa....aa service has been allocated physical file bb....bb
- The synchronization point dump file was allocated to server aa....aa.
- aa....aa: Server name
- bb....bb: File group name
- cc....cc: File name
- If the file name exceeds 122 characters, the last 122 characters of the file name are output.
- S: Terminates processing.
KFPS02195-W E+L
Minor error occured while analyzing definitions for syncpoint dump service, file being analyzed: aa....aa, record number=bb....bb, reason code=cc....cc
- An error occurred while analyzing the definition of synchronization point dump service function.
- aa....aa: Name of definition file being analyzed
- bb....bb: Erroneous record number
- cc....cc: Reason code indicating the nature of the error:
- 408: The pdlogadfg operand is invalid (-d option may be missing)
- 409: The pdlogadpf operand is invalid (-d option may be missing)
- S: Resumes processing.
- Action
- Correct the definition and restart HiRDB, if necessary.
KFPS02196-W L
Server name conflict with status-file. server=aa....aa
- Although one of the following server name operations was performed with the pdstart operand of the system common definition, the server name conflicts with the status file because the status file was not initialized:
- Server name change
- Server name addition
- Server name deletion
- Server name specification sequence change
- aa....aa: Server name
- S: Allocates a new status file area and resumes processing. If sufficient space is not available for the status file, the unit terminates.
- O: The next time the unit terminates normally, initialize the status file as described in the following table:
Change | Status file to be initialized |
---|
Change of pdstart server name | Initialize the status file of the corresponding server. |
Addition, deletion, or server name specification sequence change in pdstart | Initialize all status files in the corresponding unit. |
KFPS02200-E E+L
Unable to provide transaction log service for aa....aa service. reason code=bbbb
- The transaction log service function cannot be provided to server aa....aa.
- aa....aa: Server name
- bbbb: Reason code
- S: Terminates HiRDB abnormally.
- Action
- Take action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action |
---|
0001 | Process private area shortage | Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center. |
0100 | Shared memory shortage | Contact the customer support center. |
1001 | Status file write failure | If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center. |
KFPS02210-E E+L
Insufficient memory. size= aa....aa bytes, area type=bb....bb
- A memory shortage occurred.
- aa....aa: Size of area that was to be allocated
- bb....bb: Type of area resulting in the memory shortage:
- DYNAMIC_SHMPOOL: Dynamic shared memory
- PROCESS: Process private area
- STATIC_SHMPOOL: Static shared memory
- S: Cancels processing.
- Action
- Memory shortage occurred in dynamic shared memory:
- Check the values specified in the definition file, take appropriate action, then re-execute.
- Memory shortage occurred in process private area:
- Check the number of processes, take appropriate action, then re-execute.
- Memory shortage occurred in static shared memory:
- If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit.
- Otherwise, try re-executing at a later time.
- If the same error recurs, contact the customer support center.
KFPS02220-E E+L
Unable to recover transaction due to log error
- A transaction could not be recovered because an invalid log was detected during HiRDB full recovery or log application processing.
Possible reasons are as follows: - The system log file was damaged.
- An invalid system log file was used to execute full recovery of HiRDB.
- The paircreate or pairresync command was executed to perform formatting and copying of the pair volume that stores the system log files.
- S: Terminates processing.
- O: Take the following actions:
- Transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Check the log file and eliminate the cause of the error. To recover the transaction, restart HiRDB.
- Log application site
Confirm that the status of the pair volume is PAIR, and then restart HiRDB. If HiRDB cannot be started, perform preparation for log application, and then restart HiRDB.
- If a site takeover for disasters has occurred, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
KFPS02235-I L
Transaction branch in recovery. server=aa....aa,TRNGID=bb....bb,TRNBID=cc....cc,block number=dd....dd,last block number=ee....ee
- Rollback processing is in progress.
- aa....aa: Name of server
- bb....bb: Global identifier of the transaction
- cc....cc: Branch identifier of the transaction
- dd....dd: Block number (hexadecimal) of the system log being loaded
- ee....ee: System log block number (hexadecimal) that was previously output by message KFPS02235-I (if message KFPS02235-I is first output, the block number of the rollback start point)
- S: Continues processing.
KFPS02240-W L
aa....aa recovery to last commit point bbbb/cc/dd ee:ff:gg, TRNGID=hh....hh, TRNBID=ii....ii, PROGRAM=jj....jj, INFO_FILE=kk....kk
- Server aa....aa recovered the database to the commit point at bbbb/cc/dd ee:ff:gg.
- aa....aa: Name of the server that performed the database recovery
- bbbb: Date of the most recent commit (year)
- cc: Date of the most recent commit (month)
- dd: Date of the most recent commit (day)
- ee: Time of the most recent commit (hour)
- ff: Time of the most recent commit (minute)
- gg: Time of the most recent commit (second)
- hh....hh: Global identifier of the transaction of the most recent commit
- ii....ii: Branch identifier of the transaction of the most recent commit
- jj....jj: Value of PDCLTAPNAME of the transaction of the most recent commit (for a utility, "****" is displayed)
- kk....kk: Path name of the recovered transaction information file (if the path name of the transaction information file is longer than 54 characters, only the last 54 characters are output)
- S: Continues processing.
- Action
- Check the date and time of the commit and whether recovery could be made to the most recent database from the transaction information file. For details about how to check the transaction information file, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. If recovery could not be made to the most recent database, re-execute the update of the non-recovered data.
KFPS02254-E E+L
Unable to start transaction log service. reason code=aaaa
- The error indicated by the reason code occurred while starting the transaction log service function; this function cannot be started.
- aaaa: Reason code
- S: Terminates HiRDB abnormally.
- Action
- Take action appropriate to the reason code, as listed below, and restart HiRDB:
Reason code | Explanation | Action |
---|
0001 | Process private area shortage | Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center. |
0100 | Shared memory shortage | Contact the customer support center. |
0200 | Error during definition analysis startup processing | If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center. |
0201 | Analysis error in system common definition or unit control information definition |
0300 | Communication error | See 4.1 Detail codes for RPC-related errors, and take appropriate action. |
0301 | Timeout |
0600 | Server information failed to be registered in the name service function. | If an error message was output before this message, take the action indicated in the message. If no error message was output, contact the customer support center. |
1000 | Status file read error |
1001 | Status file write error |
1002 | Status file allocation failure |
KFPS02255-E E+L
Error occurred while terminating transaction log service; continues processing. reason code=aaaa
- The error indicated by the reason code occurred while terminating the transaction log service function, but the system is resuming termination processing.
- aaaa: Reason code
- S: Terminates HiRDB abnormally.
- Action
- Take action appropriate to the reason code, as listed below, before the next HiRDB startup:
Reason code | Explanation | Action |
---|
0001 | Process private area shortage | Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center. |
0100 | Shared memory shortage | Contact the customer support center. |
0601 | Service information failed to be deleted from the name service function | If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center. |
1001 | Status file write error |
1003 | Status file release error |
KFPS02256-E E+L
Unable to continue transaction log service.reason code=aaaa
- The system log I/O service for the transaction cannot be continued.
- aaaa: Reason code:
- 2000: Synchronization point dump I/O service cannot be used.
- 2001: Start time for synchronization point dump I/O service is incorrect.
- 2003: I/O processing for synchronization point dump file is disabled.
- S: Terminates HiRDB abnormally.
- O: If the following message related to the synchronization point dump I/O service was output before or is output after this message, take action appropriate to that message, then re-execute the service:
- KFPS021xx-y (where xx is 00 to 99 and y is E, W, or I)
If there is no message related to the synchronization point dump I/O service, contact the HiRDB administrator.
- Action
- Refer to the message log and check whether an error message for an error other than one related to the synchronization point dump I/O service was output. After the cause of the error is identified, take appropriate action, then re-execute the service. If the above does not apply, contact the customer support center.
KFPS03302-E E+L
Unable to start interval service. reason code=aaaa
- The interval service function cannot be started.
- aaaa: Reason code:
- 200: Communication error
- 300: Memory shortage
- 400: Shared memory shortage
- 500: System error
- 600: Status (file) error
- 700: adm error
- S: Terminates processing.
- O: Contact the system administrator, take action appropriate to the reason code, then restart the HiRDB system.
- Action
- Take action appropriate to the reason code.
KFPS03700-E R
Error occurred in XA interface, func=aa....aa, reason=bb....bb, code=cc....cc
- An XA interface error occurred.
- aa....aa: Name of the function resulting in the error
- bb....bb: Character string indicating the type of error
Character string | Error type |
---|
SVR PROC | Error occurred at HiRDB server during transaction settlement processing. |
SQL ERR | Error occurred during SQL processing. |
CLT ENV | Error occurred while setting the environment to use the XA interface. |
RPC INIT | Error occurred during initialization of communication environment. |
RPC CALL | Error occurred during communication. |
TRN OPEN | Error occurred while a communication path was being secured during transaction recovery processing. |
TRN CMIT | Error occurred at HiRDB server during transaction recovery processing (commit). |
TRN ROLB | Error occurred at HiRDB server during transaction recovery processing (rollback). |
TRN WAIT | Error occurred at HiRDB server while monitoring termination of transaction recovery processing. |
TRN RCV | Error occurred at HiRDB server while collecting unsettled transaction information. |
AX FUNC | Error occurred during transaction startup or restart processing. |
AX TRID | Transaction ID was invalid during transaction startup or restart processing. |
TXA OPEN | Error occurred during opening of the resource manager. |
TXA STAT | An error occurred during transaction start/restart (while a multi-thread for support of the XA interface was being used). |
TXA CLOS | Error occurred during closing of the resource manager. |
TXA ENV | Error occurred during linkage with the transaction manager. |
- cc....cc: Code indicating the cause of the error
- S: Resumes processing.
- P or O: Take action appropriate to the code indicating the cause of the error:
Type of error | Code showing the cause of the error | Explanation | Action |
---|
SVR PROC | -902 | Rollback occurred erroneously. | Contact the customer support center. |
SQL CODE | SQLCODE | See the explanation of the corresponding SQL code. | Check the corresponding SQL code and take appropriate action. |
CLT ENV | -1 | A value other than 0 or 1 is specified in the client environment definition PDXAMODE. | Specify 0 or 1 in the client environment definition PDXAMODE. For details on PDXAMODE, see the HiRDB Version 9 UAP Development Guide. |
-10 | The value specified in the client environment definition is incorrect. | See the HiRDB Version 9 UAP Development Guide, and check whether the value specified for the client environment definition is correct. |
TXA CLOS | -6 | The transaction migration settings are different for the transaction manager and the HiRDB client. | Make the settings match for the transaction manager and the HiRDB client. Set the HiRDB client transaction migration in the client environment definition PDXAMODE. For details on transaction migration, see the HiRDB Version 9 Installation and Design Guide. |
RPC INIT | -2403 | Initialization failed. | The server may not be active. Check the server status. |
-2415 | HiRDB server is inactive. |
RPC CALL | -2404 | Memory shortage occurred. | A network error may have occurred; or, the server may not be active. Check the network status or server status. |
-2406 -2418 | Network error occurred. |
-2407 | Transfer timeout occurred. |
-2410 -2411 -2414 -2415 | HiRDB server is inactive. |
-2412 -2413 -2432 | HiRDB server is engaged in termination processing. |
-2416 | System error occurred at HiRDB server. |
-2417 | Memory shortage occurred at HiRDB server. |
-2420 | HiRDB server is being started. |
-2431 | Number of connections to the HiRDB server exceeded the maximum number of concurrent connections. |
TRN OPEN | -99 | HiRDB server is starting. | Possible causes are a network error or the HiRDB server not starting. Check the network status or HiRDB server status. |
100 | Connection established to standby HiRDB system. | Check if a running system host name is specified in the client environment variable HiRDB_PDHOST for the OLTP product. If a running system host name is specified, check to be sure the version of HiRDB Client is not 06-02-/A or earlier. If HiRDB Client is version 06-02-/A or earlier, this error code is sometimes output when a unit is in the primary system and that system is a standby system. In this case, upgrade HiRDB Client to version 06-02-/B or later. If you cannot upgrade right away, switch the primary system unit from a standby system to a running system. |
TRN CMIT TRN ROLB TRN WAIT TRN RCV | -4 | Error occurred during host-to-host communication. | The server may not be active. Check the server status. |
-6 | Rollback occurred erroneously. | Contact the customer support center. |
-7 | Applicable transaction was not found in the HiRDB system. | The applicable transaction was independently determined by the HiRDB system. Check the status of the OLTP transaction. |
100 | Connection established to a standby HiRDB system. | Check if a running system host name is specified in the client environment variable HiRDB_PDHOST for the OLTP product. If a running system host name is specified, check to be sure the version of HiRDB Client is not 06-02-/A or earlier. If HiRDB Client is version 06-02-/A or earlier, this error code is sometimes output when a unit is in the primay system and that system is a standby system. In this case, upgrade HiRDB Client to version 06-02-/B or later. If you cannot upgrade right away, switch the primary system unit from a standby system to a running system. |
AX FUNC | -1 | Error occurred in OLTP. | Check the status of OLTP. |
-3 | Issuance sequence is invalid. | Application program may not be receiving the transaction service. Check the application program. |
AX TRID | -1 | Data is invalid in transaction ID. | Check the status of OLTP. |
-2 | Transaction ID was not specified. |
TXA OPEN | -2 | The number of concurrent connections per process has exceeded the maximum number of concurrent transactions. | Check the maximum number of concurrent transactions. Set the maximum number of concurrent transactions using the client environment definition PDTXACANUM. |
-3 | Connection could not be established with the HiRDB server using a multi-threaded XA interface. | Upgrade the HiRDB version so that connection can be established with the HiRDB server using a multi-threaded XA interface. |
TXA STAT | -2 | The number of transactions that can be processed concurrently in a single process has exceeded the maximum. | Check the maximum number of transactions that can be processed concurrently, which is specified in the PDTXACANUM client environment definition. |
-3 | Cannot connect to HiRDB server using a multi-thread that supports the XA interface. | Upgrade the HiRDB server version so that it can be connected using a multi-thread that supports the XA interface. |
TXA ENV | -1 | When connecting to HiRDB using a data source in standard advanced mode from Cosminexus, the settings are ignored because the XA Open String of the Cosminexus data source is undefined or the format is invalid. Also, the client environment definition PDUSER is not set. | Check the setting of the Cosminexus data source XA Open String and the client environment definition PDUSER. |
-2 | When connecting to HiRDB from OpenTP1/Server Base Enterprise Option, the setting is ignored because the character string used by the xa_open function is not set or the format is invalid. Also, the client environment definition PDUSER is not set. | Check the setting of the OpenTP1/Server Base Enterprise Option xa_open function character string and the client environment definition PDUSER. |
KFPS04128-I E
Usage: pdlogadpf -d spd [-s server_name] -g file_group_name -a physical_file_name
- Displays the format of the pdlogadpf command for a HiRDB/Single Server. This message is output when the specified command format is invalid.
KFPS04128-I E
Usage: pdlogadpf -d spd -s server_name -g file_group_name -a physical_file_name
- Displays the format of the pdlogadpf command for a HiRDB/Parallel Server. This message is output when the specified command format is invalid.
KFPS04160-E E
Specification of aa option required.
- Required option is missing.
- aa: Option name
- S: Terminates processing.
- Action
- Specify the required option and re-execute.
KFPS04161-E E
Argument of aa option is invalid.
- An option argument is missing or its specification is invalid.
- aa: Option name
- S: Terminates processing.
- Action
- Specify the correct option and re-execute.
KFPS04162-W E
Unable to specify aa option. ignored.
- An invalid option was specified (the system ignored the option).
- aa: Option name
- S: Resumes processing.
- Action
- Delete the invalid option.
KFPS04163-E E
Specified hostname conflicts with the server name.
- Specified host name is different from the host name for the specified HiRDB server.
- S: Terminates processing.
- Action
- Either omit the host name or specify the correct host name for the HiRDB server.
KFPS04164-E E
Server name must be equal to SDS's name for single server.
- For HiRDB/Single Servers, the server name must be the same as the single server's name.
- S: Terminates processing.
- Action
- For HiRDB/Single Servers, either omit the server name or specify the correct HiRDB server name.
KFPS04165-E E
Hostname must be equal to SDS hostname for single server.
- For HiRDB/Single Servers, the host name must be the same as the single server's host name.
- S: Terminates processing.
- Action
- For HiRDB/Single Servers, either omit the host name or specify the correct host name.
KFPS04170-E E
Failed to open (unload) log file(aa....aa). reason code=bbbbbb.
- A log file or unload log file failed to open.
- aa....aa: File name
- If the file name exceeds 163 characters, the last 163 characters of the file name are output.
- bbbbbb: Return value of pdi_ofl_open() or p_f_ios_open()
- S: Continues processing.
KFPS04171-E E
Unable to get server name because specfication of 'pdstart' operand is invalid in system definition file.
- The server name cannot be obtained, because the pdstart operand in the system common definition is invalid.
- S: Terminates processing.
- Action
- Correct the pdstart operand specification and re-execute.
KFPS04172-E E
Unable to execute command due to failure of aa....aa system call(command), code=bb....bb
- A command cannot be executed due to an error in system call (command) aa....aa.
This message is output when activation of an internal command called by the log command fails. - aa....aa: System call or command resulting in the error:
- {exec | fork | rsh rcp | tempnam | open}
- bb....bb: Internal code for the system call or the rsh return value
- If tempnam or open is output in aa....aa, the errno value is output.
- S: Terminates processing.
- Action
- In UNIX:
- If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix plcmd in that directory. For typical errno examples, see 4.3 System call return codes.
- If exec, fork, or rsh rcp is output in aa....aa, revise the environment variables or HiRDB system definition, and then retry the operation.
- In Windows:
- If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix plcmd in that directory. For typical errno examples, see 4.3 System call return codes.
- If exec, fork, or rsh rcp is output in aa....aa, revise the environment variables or HiRDB system definition, and then retry the operation.
KFPS04173-E E
Specified hostname invalid in 'pdstart' operand
- The host name specified in the pdstart operand of the system common definition is not valid.
- S: Terminates processing.
- O: Correct the system common definition and re-execute.
- Action
- Correct the host name specification in the pdstart operand of the system common definition.
KFPS04178-E E
Unable to specify aa option
- The aa option cannot be specified.
- aa: Option name
- S: Terminates processing.
- O: Re-execute the command without specifying the aa option.
KFPS04179-E E
Unit ID aaaa is invalid
- The unit identifier specified in the command option is invalid.
- aaaa: Unit identifier
- S: Terminates processing.
- O: Check whether unit aaaa belongs to the standby-less system switchover (effects distributed) HA group. If it does not belong to the HA group, specify the unit identifier of a unit that belongs to the HA group, then re-execute the command.
KFPS04200-E E
(Specification of aa option required.)
- A required option is missing.
- aa: Option name
- S: Terminates processing.
- Action
- Add the required option and re-execute.
KFPS04201-E E
Argument of aa option is invalid.
- An option argument is missing or invalid.
- aa: Option name
- S: Terminates processing.
- Action
- Specify the correct option and re-execute.
KFPS04202-E E
One of aa....aa options must be specified.
- One of the listed options must be specified.
- aa....aa: List of options (separated by the comma)
- S: Terminates processing.
- Action
- Specify one of the options and re-execute.
KFPS04203-E E
Only of aa....aa options can specified.
- Only one of the listed options can be specified.
This message is output when lock options are specified. - aa....aa: List of options (separated by the comma)
- S: Terminates processing.
- Action
- Specify only one of the options and re-execute.
KFPS04204-E E
Specified hostname conflicts with the server name.
- Specified host name does not match the host name for the specified HiRDB server.
- S: Terminates processing.
- Action
- For a HiRDB server, either omit the host name or specify the correct host name for the HiRDB server.
KFPS04205-E E
Server name must be equal to SDS's name for single server.
- For HiRDB/Single Servers, the server name must be the same as the single server's server name.
Because a HiRDB/Single Server consists of only one HiRDB server, specification of a server name can be omitted. This message is output when the specified server name is not the defined single server's server name. - S: Terminates processing.
- Action
- For HiRDB/Single Servers, either omit the server name or specify the correct HiRDB server name.
KFPS04206-E E
Hostname must be equal to SDS hostname for single server.
- For HiRDB/Single Servers, the host name must be the single server host name.
Because a HiRDB/Single Server consists of only one host, specification of a host name can be omitted. This message is output when the specified host name is not the local host name. - S: Terminates processing.
- Action
- For HiRDB/Single Servers, either omit the host name or specify the correct host name.
KFPS04207-E E
Unable to get server name because specfication of 'pdstart' operand is invalid in system definition file.
- The server name cannot be obtained, because the pdstart operand in the system common definition is invalid.
- S: Terminates processing.
- Action
- Correct the pdstart operand specification in the system common definition and re-execute.
KFPS04208-E E
Unable to execute command due to failure of aa....aa system call (command), code=bb....bb
- A command cannot be executed due to an error in system call (command) aa....aa.
This message is output when activation of an internal command called by the status log command fails. - aa....aa: System call or command resulting in the error:
- {exec | fork | rsh | tempnam | open}
- bb....bb: Internal code for the system call or the rsh return value
- If tempnam or open is output in aa....aa, the errno value is output.
- S: Terminates processing.
- Action
- In UNIX:
- If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix pscmd in that directory. For typical errno examples, see 4.3 System call return codes.
- If exec, fork, or rsh is output in aa....aa, revise the environment variables or system definition file and the re-execute.
- In Windows:
- If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix pscmd in that directory. For typical errno examples, see 4.3 System call return codes. If exec, fork, or rsh is output in aa....aa, revise the environment variables or system definition file and the re-execute.
KFPS04209-E E
Specified hostname invalid in 'pdstart' operand.
- The host name specified in the pdstart operand of the system common definition is not valid.
- S: Terminates processing.
- O: Correct the system common definition and re-execute.
- Action
- Correct the host name specification in the pdstart operand of the system common definition.
KFPS04210-E E
Unit ID aaaa is invalid
- The unit identifier specified in the command option is invalid.
- aaaa: Unit identifier specified in the command option
- S: Terminates processing.
- O: Specify the unit identifier of the running system unit of the HiRDB server specified in the command option, and then re-execute the command.
KFPS04211-E E
Unable to specify aa option
- The aa option cannot be specified.
- aa: Name of the option that cannot be specified
- S: Terminates processing.
- O: Re-execute the command without specifying the aa option.
KFPS04320-W L
Failure to open syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd
- An attempt to open a synchronization point dump file failed. The file could not be opened.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- dddd: Reason code
- S: Continues processing.
- Action
- Take action according to the reason code.
Reason code | Description | Action |
---|
59 | File status flag is invalid. | Contact the customer support center. |
61 | The HiRDB file name is invalid. | Check and, if necessary, revise the server definition. |
62 | No synchronization point dump file was created in the HiRDB file system area for system files. | Create a synchronization point dump file in the HiRDB file system area for system files. If Real Time SAN Replication is used, make the path to reference the synchronization point dump file on the remote site the same as on the main site. For a log application site, confirm that the path specified in the pdlogadpf -d ssp operand matches the path of the secondary synchronization point dump file created in the preparation for log application. |
63 | No synchronization point dump file was found. |
64 | File system versions do not match. | Re-evaluate the HiRDB execution environment. |
65 | File system locking error occurred. |
66 | Shortage of file system lock segments. | Re-evaluate the amount of memory used. |
67 107 | The maximum was exceeded when opening the file system. | Close unnecessary files or re-evaluate the open file limit. Re-create the kernel if necessary. |
68 | There is no access privilege for the corresponding HiRDB file system area. | Modify the access privileges for the corresponding HiRDB file system area by using an OS command (chmod, for example). |
70 | File system I/O error. | Check for the cause of the I/O error, and then take appropriate action. |
71 | There is a shortage of file system memory. | Re-evaluate the amount of memory used. |
88 | Memory shortage. | Re-evaluate the usage status of the process private area. |
92 | A file detection error occurred. (Either the file was not initialized as a synchronization point dump file or is a synchronization point dump file in use by another server or HiRDB system.) | To check for the error cause:
- Re-evaluate the pdlogadpf operand of the synchronization point dump file or the system common definition.
- Initialize the HiRDB file system area for use by synchronization point dump files, and then re-execute.
|
97 | Invalid size. | Re-evaluate the size of the synchronization point dump file. |
98 | I/O error. | Check for the cause of the I/O error, and then take appropriate action. |
106 | Invalid file name. | Consider the following causes:
- An invalid character was used in the file name.
- The HiRDB file name length exceeded the maximum (30 characters).
Re-evaluate the file name specified by the server definition or command operand. |
108 | File name is not registered. | Use the pdlogadpf command to register a file name corresponding to the applicable file group. |
121 | The possible causes are as follows:
- An attempt was made to open a synchronization point dump file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.
- An attempt was made to open a synchronization point dump file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.
| Specify Y for the pd_large_file_use operand, or omit the specification. |
KFPS04321-W L
Failure to close syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd
- An attempt to close a synchronization point dump file failed. The file could not be closed.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- dddd: Reason code
- S: Continues processing.
- Action
- Take action according to the reason code.
Reason code | Description | Action |
---|
66 | Shortage of file system lock segments. | Re-evaluate the amount of memory used. |
70 | File system I/O error. | Check for the cause of the I/O error, and then take appropriate action. |
71 | There is a shortage of file system memory. | Re-evaluate the amount of memory used. |
106 | File system path error. | Consider the following causes:
- An invalid character was used in the path name.
- The HiRDB file name length exceeded the maximum (30 characters).
Determine if the file name specification is valid. |
205 | A program internal conflict was detected. | Contact the customer support center. |
KFPS04322-W L
Failure to write to syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd
- An attempt to write a synchronization point dump file failed. The file could not be written.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- dddd: Reason code
- S: Continues processing.
- Action
- Take action according to the reason code.
Reason code | Description | Action |
---|
1 | A record output request that exceeded the file area was issued. | Contact the customer support center. |
70 | File system I/O error. | Check for the cause of the I/O error, and then take appropriate action. |
71 | Memory is insufficient. | Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center. |
95 | A synchronization point dump file for the requested number of records could not be written into a file. | Contact the customer support center. |
202 204 207 209 | An error was detected while a synchronization point dump file was being output. |
KFPS04323-W L
Failure to read from syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd
- An attempt to read a synchronization point dump file failed. The file could not be read.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- dddd: Reason code
- S: Continues processing.
- Action
- Take action according to the reason code.
Reason code | Description | Action |
---|
1 | A record input request that exceeded the file area was issued. | Contact the customer support center. |
70 | An I/O error occurred. | Check for the cause of the error, and then take appropriate action. |
71 | Memory is insufficient. | Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center. |
201 203 206 208 | An error was detected while a synchronization point dump file was being input. | Contact the customer support center. |
KFPS04370-W L
Syncpoint dump file is already closed,system A/B=a
- The synchronization point dump file is already closed.
- a: System type (a: A system, b: B system)
- S: Terminates processing.
- Action
- Execute the pdlogls -d spd -e command and check the status of the synchronization point dump file.
KFPS04371-W L
Syncpoint dump file is already opened,system A/B=a
- The synchronization point dump file is already open.
- a: System type (a: A system, b: B system)
- S: Terminates processing.
- Action
- Execute the pdlogls -d spd -e command and check the status of the synchronization point dump file.
KFPS04372-I L
Syncpoint dump file for aa....aa service has been opened,file group name=bb....bb,system A/B=c
- A synchronization point dump file was opened for the aa....aa server.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- S: Continues processing.
KFPS04373-I L
Syncpoint dump file for aa....aa service has been closed,file group name=bb....bb,system A/B=c
- A synchronization point dump file was closed for the aa....aa server.
- aa....aa: Server name
- bb....bb: File group name of the synchronization point dump file
- c: System type (a: A system, b: B system)
- S: Continues processing.
KFPS04374-I L
Syncpoint skip inf. SERVER=aa....aa,TRNCNT=bb....bb,TGID=cc....ccdd....dd,TBID=cc....ccee....ee,PID=ff....ff,C-PID=gg....gg(hh....hh),TIME=ii....ii,PROGRAM=jj....jj
- This message provides maintenance information when a synchronization point dump acquisition opportunity is ignored or synchronization point dump activation processing is not completed because transactions that were not completed at the time of the last synchronization point dump acquisition are still not complete.
If factor code in the KFPS02179-I that was output immediately before this message is A01-02, this message outputs the following information: - The number of uncompleted transactions
- Information about the first uncompleted database update transaction
- Normally, information about the first uncompleted database update transaction is output in this message, unless the corresponding transaction is completed while its information is being acquired, in which case its transaction information is not output. In this case, **** is output as the transaction information.
If the client connected to the HiRDB server (UAP) is an application complying with X/Open, or the XDS client, message KFPS04375-I is output after this one. - aa....aa: Name of server
- bb....bb: Number of uncompleted transactions
- Outputs the number of uncompleted database update transactions. If the uncompleted database update transactions are all completed while the information is being acquired, 0 is displayed.
- cc....cc: HiRDB system identifier, or unit identifier
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.
- dd....dd: Global transaction number
- Outputs information about the first uncompleted database update transaction. No information is output if the corresponding transaction is completed while the information is being acquired.
- ee....ee: Transaction branch number
- Outputs information about the first uncompleted database update transaction. No information is output if the corresponding transaction is completed while the information is being acquired.
- ff....ff: Process ID of the HiRDB server that was processing the transaction as an extension of the processing of the UAP or utility
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.
- gg....gg: Process ID of the HiRDB client (a UAP or a utility) that was connected to a server process
- If the server process is one of the following, 0 is displayed:
- A server process that is not connected to a client
- A server process that is connected to a client linked to a client library version prior to 04-00
- A server process that is connected to a Type 4 JDBC Driver
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.
- hh....hh: IP address of the HiRDB client (a UAP or a utility) that was connected to a server process
- In the following cases, 0.0.0.0 is displayed:
- A server process that is not connected to a client
- If the client library for linking to the UAP is prior to version 04-00
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.
- ii....ii: Date and time of the first database update transaction (yyyy/mm/dd hh:mm:ss)
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.
- jj....jj: UAP identification information
- Outputs the UAP name specified in PDCLTAPNAME in the client environment definition.
- If PDCLTAPNAME is not set, Unknown is displayed.
- For a utility, the name of the utility command is displayed.
- Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output. However, in the following cases, this information might be left blank:
- The UAP was running as a utility server process.
- The UAP identification information cannot be obtained due to an error.
- S: Continues processing.
- Action
- When the number of uncompleted transactions is 0:
- Because all uncompleted transactions were completed immediately before this message was output, no action is required.
- When the number of uncompleted transactions is 1:
- Based on the transaction information that was output, check whether the transactions have been uncompleted for an extended period, and then execute the commit or cancel as necessary.
- When the number of uncompleted transactions is 2 or more:
- Execute the command pdls -d trn, check whether the transactions have been uncompleted for an extended period, and then execute the commit or cancel as necessary.
KFPS04375-I L
Syncpoint skip inf2. SERVER=aa....aa,TMID=bbbb,XID=cc....cc,dd....dd,ENVGRP=eeee
- If the client connected to the HiRDB server (UAP) is an application complying with X/Open, or an XDS client, this message is output following message KFPS04374-I.
- aa....aa: Name of server
- bbbb: OLTP identifier of the connected OLTP (HiRDB_PDTMID or PDTMID in the client environment definition)
- This information is output if the client connected to the HiRDB server process (UAP) is an application complying with X/Open, or an XDS client. If no OLTP identifier is specified, **** is output. If an XDS client is used, HRDB is output.
- cc....cc,dd....dd:
- One of the following is output:
- The transaction identifier assigned by OLTP
This information is output when the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the OLTP is OpenTP1 or TPBroker for C++.
- The transaction identifier assigned by XDS
This information is output when the client (UAP) connected to the HiRDB server process is an XDS client.
- eeee: Environment variable group identifier assigned by OLTP
- If the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the multi-connection facility is used, this information is output. If the multi-connection facility is not used, **** is output.
- S: Continues processing.
- Action
- See the description of message KFPS04374-I.
KFPS04602-W L
Unable to create pd_tmp_directory directory,unit ID : aaaa, directory : bb....bb
- The specified directory could not be created in the pd_tmp_directory operand.
- aaaa: Unit identifier
- bb....bb: Specified directory name in the pd_tmp_directory operand
- S: Because the directory specified in the pd_tmp_directory operand cannot be created, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.
- O: Contact a HiRDB administrator.
- Action
- To use directories other than those assumed by HiRDB, reset the specifications for the pd_tmp_directory operand. Note that if specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.
KFPS04603-W E+L
Specified pd_tmp_directory directory not exist,unit ID : aaaa, directory : bb....bb
- The directory specified in the pd_tmp_directory operand or environment variable TMP (In UNIX: TMPDIR) cannot be referenced.
- aaaa: Unit identifier
- bb....bb: Specified directory in the operand or environment variable
- S: Because the specified directory cannot be referenced, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.
- O: Contact a HiRDB administrator.
- Action
- To use directories other than those assumed by HiRDB, reset the specifications. Note that if the specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.
KFPS04604-W E+L
Invalid value for variable pd_tmp_directory,reason code=aa....aa
- The value specified in the pd_tmp_directory operand is invalid.
- aa....aa: Reason code
- NOT_ABSOLUTE_PATH: The specified value is not an absolute path.
- INVALID PATH: The specified value is not a valid path name.
- S: Because the directory specified in the pd_tmp_directory operand is invalid, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.
- O: Contact a HiRDB administrator.
- Action
- To use directories other than those assumed by HiRDB, reset the specifications for the pd_tmp_directory operand. Note that if the specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.
- If the reason code is INVALID_PATH, specify the following directory in the pd_tmp_directory operand. Specify a different directory name.
- In UNIX: / (root directory)
- In Windows: Directly under the drive (for example, C:\)
KFPS04605-W L
Unable to specify aa....aa operand, ignored
- A definition that cannot be specified for the platform was specified.
- aa....aa: Ignored definition
- S: Ignores the specified definition and continues processing
- Action
- Delete the corresponding definition from the definition file and start HiRDB.
KFPS04606-W L
Unable to connect to event server of JP1
- The system common definition specifies linkage with Job Management Partner 1 (pd_jp1_use=Y or pd_jp_event_level=2), but connection cannot be established with the Job Management Partner 1 event server.
- S: Continues processing.
- Action
- If it is necessary that events be output to Job Management Partner/Integrated Manager, investigate the cause of the connection failure and eliminate it. Job Management Partner/Integrated Manager or Job Management Partner/Base may not be installed.
- If it is not necessary that events be output to Job Management Partner/Integrated Manager, specify N in the pd_jp1_use operand and restart HiRDB.
KFPS04607-I L
Data replication restart, server ID=aa....aa, reason code=bb....bb
- Linkage with the HiRDB Datareplicator was restarted.
- aa....aa: Server name
- bb....bb: Reason that linkage with the HiRDB Datareplicator was restarted
- FORCE: During the previous session, linkage was established with the HiRDB Datareplicator, but HiRDB was started with the pdstart -i command
- STATUS: One of the following reasons:
- An error occurred in the HiRDB Datareplicator data linkage file, or it was initialized.
- An error occurred in the status file used by the server, or it was initialized.
- S: Stops and then restarts linkage with the HiRDB Datareplicator.
- Action
- If necessary, initialize the HiRDB Datareplicator data linkage file or re-create the target database.
KFPS04608-W L
Unable to continue data replication, server ID=aa....aa, reason code=bb....bb
- Linkage with the HiRDB Datareplicator could not be maintained.
- aa....aa: Server name
- bb....bb: Reason that linkage with the HiRDB Datareplicator could not be maintained
- DEFINITION: During the previous session, linkage was established with the HiRDB Datareplicator, but N was specified in the pd_rpl_init_start operand
- RPL_FILE: An error occurred in the HiRDB Datareplicator data linkage file
- RPL_STATUS: The HiRDB Datareplicator data linkage file was initialized
- S: Stops the linkage with the HiRDB Datareplicator, and continues server activation processing.
- Action
- To re-execute linkage with the HiRDB Datareplicator, eliminate the cause of the error, synchronize with the target HiRDB, and use the pdrplstart command to restart linkage with the HiRDB Datareplicator. Also, if HiRDB is stopped and linkage with the HiRDB Datareplicator is already established, specify Y in the pd_rpl_init_start operand.
KFPS04609-E L
Error occurred in status file while data replication, server ID=aa....aa, reason code=bb....bb
- An error was detected in the status file during linkage with the HiRDB Datareplicator.
- aa....aa: Server name
- bb....bb: Reason code
- COMMUNICATION: Inter-process communication error
- SERVER NOT UP: Status server process has not started
- I/O ERROR: I/O error
- OTHER: Other error
- S: Abnormally terminates.
- Action
- Eliminate the cause of the error on the basis of the message output before this message.
KFPS04611-I E+S
Usage: pdmemsv [{-d | -s}]
- The specification format of the pdmemsv command option is invalid.
- S: Terminates processing.
- O: Reenter correctly the specified command.
KFPS04612-E E
Error occured in execution, reason code=aa....aa
- The pdmemsv command cannot be executed because of error code aa....aa.
- aa....aa:
- ALREADY:
- The attempted operation has already been executed.
- INSTALL_DIR:
- This command cannot be executed in the environment under the installation directory.
- NO_DIR:
- A required directory cannot be found.
- NO_LIBS:
- The environment has been damaged.
- NOT_SINGLE:
- The server is not a HiRDB/Single Server.
- NOT_PARALLEL
- The server is not a HiRDB/Parallel Server.
- PDDIR:
- The PDDIR environment variable cannot be found.
- PERMISSION:
- The person who executed the command is not a superuser.
- SETUP:
- HiRDB is running.
- VERSION:
- The installed HiRDB and the HiRDB in $PDDIR are different versions. Or, the necessary load module was deleted by the pdlodsv command.
- S: Terminates processing.
- O: Take action appropriate to the cause, as described below:
- PDDIR:
- Change the PDDIR environment variable setting to the HiRDB environment to be operated with this command.
- PERMISSION:
- Execute the command as a superuser.
- SETUP:
- Keep the files needed for execution and execute pdsetup -d.
- VERSION:
- Check if the versions of the installed HiRDB and the HiRDB in $PDDIR are the same. When a load module required by the pdlodsv command was deleted, reinstall HiRDB with the same version as the HiRDB in the HiRDB directory.
- Other:
- Check whether the setting for the PDDIR environment variable is correct. If it is correct, contact the HiRDB administrator.
- Action
- Check whether the installed HiRDB and the HiRDB in $PDDIR have the same version. The HiRDB in $PDDIR requires system files; check that the necessary files have not been deleted during pdsetup -d execution.
KFPS04614-I L+S
Usage:aa....aa
- The command option specification format is invalid.
- aa....aa: Command in which option specification is invalid:
- pdopsetup command:
- pdopsetup [-d] -k option HiRDB_home_directory
- pdadmvr command:
- pdadmvr [-s| -c]
- pdlodsv command:
- pdlodsv [-r kind]
- S: Terminates processing.
- Action
- Re-execute the command according to the command usage method.
KFPS04615-E E
Specified HiRDB option already setup, option=aaa, version=bb....bb
- Version bb....bb option program product was already embedded into the HiRDB directory specified by the pdopsetup command.
- aaa: Option program product
- sti: HiRDB Staticizer Option
- aha: HiRDB Advanced High Availability
- nrf: HiRDB Non Recover FES
- drl: HiRDB Disaster Recovery Light Edition
- acl: HiRDB Accelerator
- bb....bb: Version of option program product
- S: Terminates processing.
- Action
- Check the version of the option program product embedded in the specified HiRDB directory and the version of the installed option program product. To embed the version of the installed option program product, execute the pdopsetup -d command, and then execute the pdopsetup command.
KFPS04616-E E
Specified HiRDB option not setup, option=aaa
- An attempt to delete failed because the option program product is not embedded in the HiRDB directory specified by the pdopsetup -d command.
- aaa: Option program product
- sti: HiRDB Staticizer Option
- aha: HiRDB Advanced High Availability
- nrf: HiRDB Non Recover FES
- drl: HiRDB Disaster Recovery Light Edition
- acl: HiRDB Accelerator
- S: Terminates processing.
- Action
- Check if the HiRDB directory specified by the pdopsetup command is correct.
KFPS04617-E E
HiRDB option not installed, PP=aa....aa
- A HiRDB option program product is not yet installed.
- aa....aa: Name of option program product:
- HiRDB Staticizer Option
- HiRDB Advanced High Availability
- HiRDB Non Recover FES
- HiRDB Disaster Recovery Light Edition
- HiRDB Accelerator
- S: Terminates processing.
- Action
- Install the HiRDB option program product and re-execute the command.
KFPS04618-I S
HiRDB option setup complete, func=aa....aa, option=bbb, version=cc....cc
- A HiRDB option program product was either installed or removed.
- aa....aa: Function type:
- add: Install
- delete: Remove
- bbb: Option program product:
- sti: HiRDB Staticizer Option
- aha: HiRDB Advanced High Availability
- nrf: HiRDB Non Recover FES
- drl: HiRDB Disaster Recovery Light Edition
- acl: HiRDB Accelerator
- cc....cc: Version of option program product
- S: Terminates processing.
KFPS04619-E S+R
Unable to execute aa....aa command due to HiRDB unit not offline or not terminate normally
- The HiRDB unit is not stopped; command aa....aa cannot be executed.
aa....aa: Name of the command
S: Terminates processing. - Action
- It is possible that HiRDB was still running (including startup or termination processing) when the command was executed. The command cannot be executed under those conditions.
- If HiRDB is running, use the pdstop command to stop HiRDB and then re-execute the command. Otherwise, activate HiRDB, use the pdstop command to stop HiRDB, and then re-execute the command.
- UNIX edition only
Even if HiRDB is stopped, the pdplgset and pdopsetup commands cannot be entered if HiRDB terminated abnormally or was forcibly terminated by the pdstop -f command.
KFPS04620-I L
Server aa....aa information. Process ID=bb....bb. System event=0xcccccccc dddddddd eeeeeeee. User event=0xffffffff. SYS_CALL=0xgggggggg.
- This is server information.
- aa....aa: Server name
- bb....bb: Process ID
- cccccccc: System event information 1 (internal code)
- dddddddd: System event information 2 (internal code)
- eeeeeeee: System event information 3 (internal code)
- ffffffff: User event information (internal code)
- gggggggg: System call code information (internal code)
- S: Resumes processing.
- Action
- This information is in addition to a KFPS01820-E message that was output before this message. Take a corrective action based on the server name and the KFPS01820-E message that is associated with the process ID.
KFPS04621-E L
Caution: Server aa....aa (process ID=bb....bb) killed by user request
- A HiRDB server process was stopped because of a user request issued from outside HiRDB. User requests issued from outside HiRDB include the following:
- In UNIX:
- OS's kill command was executed. This message is applicable to SIGTERM, SIGKILL, SIGQUIT, and SIGABRT signals only.
- Java Virtual Machine sent a signal when a Java stored procedure or Java stored function was being used. This message is applicable to SIGTERM, SIGKILL, and SIGABRT signals only.
- The facility for parallel output of system logs was applied, even though the aio library was not installed or was not configured correctly.
- In Windows:
- The pdkill command was executed.
- aa....aa: Server name of the stopped process
- bb....bb: Process ID at the server
- S: Continues processing.
- O: If the core file was output in a UNIX edition of HiRDB, contact the HiRDB administrator.
- Action
- In UNIX:
- Take one of the following actions:
- Determine whether the OS's kill command was executed.
- Check if the facility for parallel output of system logs was in use (parallel was specified in the pd_log_dual_write_method operand) while the aio library was not installed or was not enabled. For details about the facility for parallel output of system logs, see the HiRDB Version 9 Installation and Design Guide.
- In Windows:
- Determine whether the pdkill command was executed.
KFPS04622-E E+L
Invalid user name, user=aa....aa; bb....bb processing
- aa....aa is an invalid authorization identifier.
- aa....aa: Authorization identifier
- bb....bb: System action:
- stops: Stops processing.
- continues: Continues processing using the executing user's log-in account (during pdinit execution only).
- S: Performs the bb....bb processing.
- O: Re-execute the utility, as appropriate.
- Action
- If this message was output when pdinit was executing, revise the authorization identifier and then re-execute. The following names cannot be used for the authorization identifier:
- Name more that 8 bytes long
- Name that does not begin with a single-byte character (upper- or lower-case letter)
- Name containing a character string other than single-byte characters (upper- or lower-case letters) and single-byte numbers
- HiRDB, MASTER, ALL, and PUBLIC (reserved words that cannot be used as authorization identifiers)
KFPS04623-E E+L
Invalid password, user=aa....aa; bb....bb processing
- The password for authorization identifier aa....aa is invalid.
- aa....aa: Authorization identifier
- bb....bb: System action:
- stops: Stops processing.
- S: Performs the bb....bb processing.
- O: Re-execute the utility, as appropriate.
- Action
- If this message is output during pdinit execution, check and correct the password if necessary and re-execute. The following names cannot be used as passwords and must be changed:
- Name more that 30 bytes long
- Name that does not begin with a single-byte character (upper- or lower-case letter)
- Name containing a character string other than single-byte characters (upper- or lower-case letters) and single-byte numbers
KFPS04624-I E+L
Data replication already stopped, unit ID=aaaa, server ID=bb....bb
- An error was detected in the data linkage file of the HiRDB Datareplicator or in the server in which a data linkage stoppage occurred. This message is displayed for each server in which an error occurred.
- aaaa: Unit identifier
- bb....bb: Server name
- S: Stops data linkage and continues with HiRDB startup.
- Action
- Take the actions indicated by the KFPS01833-I and KFPS01801-E messages, which follow this message.
KFPS04625-E L
Error found in system configuration, reason code=aa....aa
- An operand specified in the system common definition or unit control information definition is invalid.
- aa....aa: Reason code:
- SPECIFIED pd_spool_cleanup_level:
- An error was found in the specification of the pd_spool_cleanup_level operand.
- SPECIFIED pd_spool_cleanup_interval_level:
- An error was found in the specification of the pd_spool_cleanup_interval_level operand.
- S: Terminates processing.
- Action
- Correct the operand and restart HiRDB.
KFPS04626-E S
Unable to remove aa....aa, reason code=bb....bb
- Load module aa....aa cannot be deleted.
- aa....aa: Load type:
- POSIX: POSIX library version of HiRDB
- bb....bb: Reason code:
- USING: This load module cannot be deleted because it is being used.
- REMOVED: This load module has already been deleted.
- RUNNING: pdsetup command is executing.
- S: Terminates processing.
- Action
- If the reason code is RUNNING, wait for the pdsetup command to terminate and then re-execute.
KFPS04627-E L
HiRDB Datareplicator extraction process not in progress, because error occurred in HiRDB Datareplicator access communication file. unit ID=aaaa, server ID=bb....bb.
- The HiRDB Datareplicator data linkage extraction process did not run because access to the data linkage file failed.
- aaaa: Unit identifier
- bb....bb: Server name
- S: Continues processing.
- Action
- Check the reason why access to the data linkage file failed, and then take appropriate action. You can check the KFPS01889-E message output immediately before this message for the reason access failed.
- When function value of the KFPS01889-E message is SYSTEM CALL(stat) ERROR and errno is 2:
- The data linkage file could not be found. To re-create a data linkage file, you must use HiRDB Datareplicator to initialize the data linkage file.
- To re-create a data linkage file:
- Use the pdrplstop command to terminate data linkage processing.
- For nontarget system logs, use HiRDB Dataextractor or HiRDB Datareplicator data linkage facility to restore consistency between data linkage extraction and target databases.
- Execute the hdestart -i command that HiRDB Datareplicator provides, re-create the data linkage file, and then initialize.
- Use the pdrplstart command to start the data linkage process.
- When errno of the KFPS01889-E message is 13:
- The user has no access privileges to the data linkage file. Request that the HiRDB administrator change access privileges so you can access the data linkage file.
- When function value of the KFPS01889-E message is FILE LOCK ERROR:
- HiRDB Datareplicator may have exclusive ownership of the data linkage file. Check the execution status of HiRDB Datareplicator.
KFPS04628-W E+L
Data replication stopped, please check.
- Data linkage to HiRDB Datareplicator stopped. Check the reason why data linkage stopped.
- S: Continues processing.
- Action
- Check the reason why data linkage to HiRDB Datareplicator stopped. If there is a problem, use the data linkage recovery facility of HiRDB Dataextractor or HiRDB Datareplicator to restore consistency between the data linkage extraction database and the target database.
KFPS04629-I E+L
Command failed on online unit, command=aa....aa, hostname=bb....bb; Retrying on standby unit
- Because execution of command aa....aa on running system unit host bb....bb failed, the command was executed on a standby unit.
- aa....aa: Command name
- bb....bb: Host name
- S: Continues processing.
- Action
- If the command that was re-executed by the standby system unit terminates normally, ignore the error issued by the running system unit. Note that the running system and standby system referred to here are statuses that are determined by the HiRDB system, and may differ from the actual systems. If an error occurs on both the running system and the standby system, check the actual system status, and then take action according to the error message output by the running system unit.
KFPS04643-I L
Assumed aa....aa default value=bb....bb on unit cccc
- Assumed default value bb....bb of definition operand aa....aa in unit cccc.
- aa....aa: Definition operand name
- pd_max_server_process (maximum number of concurrently active server processes)
- pd_tmp_directory (name of work file output directory)
- bb....bb: Default value of the definition operand
- cccc: Unit identifier
- S: Continues processing.
- Action
- When an insufficient maximum number of concurrently active server processes is detected during operation, re-estimate the specified operand value, specify a value greater than the default value, and then restart HiRDB.
- If using the default value of the pd_tmp_directory operand causes problems, change the value specified in the pd_tmp_directory operand.
KFPS04644-I L
Assumed aa....aa default value=bb....bb on server cc....cc
- The default value bb....bb is assumed for operand aa....aa on server cc....cc.
- aa....aa: Operand name
- pd_bes_shmpool_size (shared memory size for back-end server)
- pd_dic_shmpool_size (shared memory size for dictionary server)
- pd_sds_shmpool_size (shared memory size for a single server)
- bb....bb: Default value of the operand (bytes)
- cc....cc: Server name
- S: Continues processing.
- Action
- If a shared memory shortage was detected during operation, re-estimate the value of the specification. Specify a value larger than the default (value of bb....bb) and restart HiRDB.
KFPS04645-I L+S
pdprgcopy ended, return code=aa
- The pdprgcopy command terminated.
- aa: Return code
- 0: The pdprgcopy command terminated normally.
- 8: The pdprgcopy command terminated with an error.
- S: Terminates processing.
- Action
- If the return code is 8, refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), and eliminate the cause of the error. Then, re-execute the command.
KFPS04646-I L+S
pdprgrenew ended, return code=aa
- The pdprgrenew command terminated.
- aa: Return code
- 0: The pdprgrenew command terminated normally.
- 8: The pdprgrenew command terminated with an error. HiRDB is returned to its pre-update version.
- 12: The pdprgrenew command terminated with an error. An error occurred during processing to return HiRDB to its pre-update version. HiRDB stopped.
- S: Terminates processing.
- Action
- Based on the return code, take the following action:
- If the return code is 8:
- Refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), and eliminate the cause of the error. Then, re-execute the command.
- HiRDB operates even after the command termination if HiRDB was running when the command was executed. If HiRDB was inactive when the command was executed, HiRDB remains inactive even after command termination.
- If the return code is 12:
- See the KFPS04647-I message output immediately before this message, check which processing the error occurred, take appropriate action, and then re-execute the pdprgrenew command. Take one of the following actions:
- If SYS_SUSPEND or SYS_RESUME is displayed in the KFPS04647-I message:
If there is a HiRDB process, use the pdstop -f command to forcibly terminate HiRDB, and then execute the pdprgrenew -b command. If there is no HiRDB process, execute the pdprgrenew -b command.
- If RECOVER_REPLACE, RECOVER_BACKUP, or RECOVER_SYS_SUSPEND is displayed in the KFPS04647-I message:
Refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), eliminate the cause of the error, and then execute the pdprgrenew -b command.
KFPS04647-I L+S
pdprgrenew aa....aa started
- The pdprgrenew command started aa....aa processing.
- aa....aa: Processing contents
Processing contents (aa....aa) | Explanation |
---|
SYS_SUSPEND | HiRDB processing is suspended internally. |
BACKUP | A backup of the active HiRDB is being acquired. |
REPLACE | HiRDB is being replaced with an updated version. |
SYS_RESUME | HiRDB has been restarted with an updated version. |
RECOVER_REPLACE | This recovery process is performed when an error occurs. The updated version of HiRDB is returned to the update directory. |
RECOVER_BACKUP | This recovery process is performed when an error occurs. HiRDB is returned to its pre-update version. |
RECOVER_SYS_SUSPEND | This recovery process is performed when an error occurs. The pre-update version of HiRDB is restarted. |
- S: Continues processing.
KFPS04648-E E+L
Error occurred in pdprgrenew command, unit ID=aaaa, reason code=bb....bb
- An error occurred during execution of the pdprgrenew command.
- aaaa: Unit identifier
- If an error occurred before the unit identifier was obtained, **** is displayed.
- bb....bb: Reason code
Reason code (bb....bb) | Explanation |
---|
permission error | The user executing the command is not a HiRDB administrator. |
renew directory not exist | The renew directory was not found in the HiRDB directory. |
renew_bak directory exist | The renew_bak directory was found in the HiRDB directory. |
rename error | An error occurred in the program update process rename() system call. |
transactions exist | The pdprgrenew command waited for transactions to terminate, but execution of the command was suspended because some transactions were still active even 15 minutes later. |
offline units exist | Some inactive units remain in the system. |
offline servers exist | Some inactive servers remain. |
utility be executing | A HiRDB utility is currently running. The pdprgrenew command cannot be executed while a utility is running. |
replication mode unmatch | When using the HiRDB Datareplicator linkage facility, the specification of the pd_rpl_init_start operand and the run status do not match. |
pdprgrenew -b be unnecessary | The pdprgrenew -b command was executed, but no operation was performed because executing the pdprgrenew -b command is not necessary. |
sys_info error | An error occurred during system information (registry, setup information) operations. |
service start error | An error occurred during HiRDB service start processing. |
service stop error | An error occurred during HiRDB service stop processing. |
MSCS-info error | An error occurred during MSCS or MSFC information collection. |
MSCS online error | An error occurred while an MSCS or MSFC resource was online. |
MSCS offline error | An error occurred while an MSCS or MSFC resource was offline. |
resident RDAREA exists | There is an in-memory RDAREA. |
expand unit exists | An expansion unit is specified in the pd_system_expand_unit operand in the system common definition. |
- S: Continues processing.
- Action
- Take action according to the reason code.
- permission error:
- Request that the HiRDB administrator execute the pdprgrenew command.
- renew directory not exist:
- Execute the pdprgcopy command, and then re-execute the pdprgrenew command.
- renew_bak directory exist:
- Either delete the renew_bak directory in the HiRDB directory or change the name of the directory, and then re-execute the pdprgrenew command.
- rename error:
- This error occurs if the renew directory under the HiRDB directory containing the updated HiRDB that was copied with the pdprgcopy command is not in the same file system as the HiRDB directory (bin, lib, etc.) that is currently running under the HiRDB directory. Update so that the required directories exist in the same file system, and then re-execute the pdprgrenew command.
- If the directory is on the same file system, the OS's rename() system call failed. OS messages might be output to the event log (in UNIX, syslogfile). Eliminate the cause of the error, use the pdprgrenew -b command to return HiRDB to its previous state before being updated, and then re-execute the pdprgrenew command.
- transactions exist:
- Check that there are no long-term transactions running, wait for the currently running transactions to terminate, and then re-execute the pdprgrenew command.
- offline units exist or offline servers exist:
- Activate all HiRDB units and servers, and then re-execute the pdprgrenew command.
- utility be executing:
- After the HiRDB utility terminates, re-execute the pdprgrenew command.
- replicator mode unmatch:
- Reconcile the specification of the pd_rpl_init_start operand with that of the operating status, then re-execute the pdprgrenew command.
- pdprgrenew -b be unnecessary:
- Execute the pdprgrenew -b command only after the KFPS04646-I message outputs a return code of 12 and the pdprgrenew command has terminated.
- sys_info error:
- Determine whether regedit.exe or another program is accessing the registry, or whether the HiRDB installation environment file (Setup.ini) is open, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- service start error:
- Check the event log (in UNIX, syslogfile) to determine the reason that the service did not start, and eliminate the cause of the error. If the service is still starting, wait for the service to start or stop, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- service stop error:
- Check the event log (in UNIX, syslogfile) to determine the reason that the service did not stop, and eliminate the cause of the error. If the service is still stopping, wait for the service to start or stop, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- MSCS-info error:
- Check the event log (in UNIX, syslogfile), eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- MSCS online error:
- Check the event log (in UNIX, syslogfile) to determine the reason that the MSCS or MSFC resource did not go online, eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- MSCS offline error:
- Check the event log (in UNIX, syslogfile) to determine the reason that the MSCS or MSFC resource did not go offline, eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
- resident RDAREA exists:
- Release the RDAREA from in-memory allocation, and then re-execute the pdprgrenew command.
- expand unit exists:
- The pdprgrenew command cannot be executed. Terminate HiRDB normally, and then update to HiRDB update version.
KFPS04649-E E+L
Error occurred in pdprgcopy command, unit ID=aaaa, reason code=bb....bb
- An error occurred during execution of the pdprgcopy command.
- aaaa: Unit identifier
- If an error occurred before the unit identifier was obtained, **** is displayed.
- bb....bb: Reason code
- permission error:
- The user executing the command is not the HiRDB administrator.
- invalid version:
- HiRDB could not be updated because the version number and the revision number do not match.
- invalid addressing mode:
- The addressing modes between the running HiRDB and the update replacement version HiRDB do not match.
- invalid version different between units:
- The HiRDB version differs between units.
- no space disk:
- The required disk space is not available.
- renew directory exist:
- The renew directory already exists under the HiRDB directory.
- invalid HiRDB server type:
- The HiRDB server type (HiRDB/Single Server or HiRDB/Parallel Server) of the HiRDB currently running and the update replacement version HiRDB do not match.
- install directory:
- For UNIX, the directory specified as the argument of the pdprgcopy command is the HiRDB installation directory.
- For Windows, the directory specified as an argument of the pdprgcopy command is the directory installed by Program Maintenance Setup.
- copy error:
- An error occurred while copying a file.
- delete error:
- An attempt to delete the renew directory under the HiRDB directory failed because an error occurred during execution of the pdprgcopy command.
- sys_info error:
- An error occurred during system information (registry, setup information) operations.
- S: Terminates processing.
- Action
- Take action according to the reason code.
- permission error:
- Request that the HiRDB administrator execute the pdprgcopy command.
- invalid version:
- The HiRDB system currently running cannot be replaced by the replacement update version HiRDB if the version numbers and revision numbers do not match. Install an update version HiRDB with the same version number and revision number, and then re-execute the pdprgcopy command.
- invalid addressing mode:
- The HiRDB system currently running can only be replaced by the replacement update version if both are in the same addressing mode. Install the update version HiRDB in the same addressing mode as the HiRDB system currently running, and then re-execute the pdprgcopy command.
- invalid version different between units:
- Install the same version of the replacement update HiRDB system for all units.
- no space disk:
- In the HiRDB directory, secure the free disk space that is required for the update version HiRDB, and then re-execute the pdprgcopy command.
- install directory:
- For UNIX, if the HiRDB directory and the installation directory are the same directory, the current version of the HiRDB system cannot be replaced by the update version. If the HiRDB directory and the installation directory are different directories, specify the HiRDB directory in an argument of the pdprgcopy command, and then re-execute.
- For Windows, specify the installation directory of the update version HiRDB, then re-execute the command.
- renew directory exist:
- Either change the name of the renew directory under the HiRDB directory or delete the renew directory, and then re-execute the pdprgcopy command.
- invalid HiRDB server type:
- The HiRDB system currently running can only be replaced by the replacement update version if both have the same HiRDB server type (HiRDB/Single Server or HiRDB/Parallel Server). Install the update version HiRDB system with the same server type as the HiRDB system currently running, and then re-execute the pdprgcopy command.
- communication error occurred:
- Check for the cause of the communication error, take appropriate action, and then re-execute the command.
- copy error:
- OS messages might be output to the event log (in UNIX, syslogfile). Check for the cause of the copy process failure, eliminate the cause, and then re-execute the pdprgcopy command.
- delete error:
- Refer to the error message output before this message, and eliminate the cause of the error. Then, delete the renew directory under the HiRDB directory and re-execute the pdprgcopy command.
- sys_info error:
- Determine whether regedit.exe or another program is accessing the registry, or whether the HiRDB installation environment file (Setup.ini) is open, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.
KFPS04650-I L
Trouble shoot file and temporally file delete aa....aa. system ID=bbbb, unit ID=cccc
- Deletion of the troubleshooting information file under %PDDIR%\spool and the temporary file under %PDDIR%\tmp has started or finished.
- aa....aa: Processing content
- started: Deletion processing has started
- completed: Deletion processing has finished
- bbbb: HiRDB identifier
- cccc: Unit identifier
- S: Continues processing.
KFPS04651-W E+L
Message log server restarted
- This message indicates that the message log server was restarted. From the time the message log server terminates abnormally to the time its restart is complete, HiRDB messages are not output to the message log file (%PDDIR%\spool\pdlog1 or pdlog2). Messages are output to the event log (in UNIX, syslogfile) of the server unit that is the source of the messages. However, in some cases messages might not be output to the event log (in UNIX, syslogfile). For currently active UAPs, commands, and utilities, this does not present a problem.
- S: Continues processing.
KFPS04652-E E+L
Pdstop command failed,reason=aa....aa
- The pdstop command could not be executed because another operation command was currently running.
- aa....aa: Reasons for the command not executing:
- RPL_STARTING: Linkage with HiRDB Datareplicator is currently starting up.
- RPL_STOPPING: Linkage with HiRDB Datareplicator is currently terminating.
- S: Terminates processing.
- Action
- Wait for other operation commands to terminate, and then re-execute the pdstop command.
KFPS04653-E L+S
Unable to stop unit aaaa with alternate servers, reason=bb....bb
- The alternate BES unit or an alternate facility could not be stopped because of the status of the alternate facility in the standby less system switchover facility.
- aaaa: Unit identifier of the unit that could not be stopped.
- If the pdstop -z -c command was executed, **** might be displayed.
- bb....bb: Reason code
- S: Terminates processing.
- Action
- Take action according to the reason code listed in the following table.
Reason code | Description | Action |
---|
STARTING | An alternate facility is currently being prepared. | Re-execute the stop command. |
SBY_STARTING | An alternate facility is currently being prepared as a standby server. | Re-execute the stop command after the KFPS01872-I message is output. |
SBY_TERM | An alternate standby system is currently being stopped. | Re-execute the stop command. |
SBY_RELEASE | Execution of an alternate facility using system switchover is currently being prepared. | Re-execute the stop command after the KFPS05110-I message is output. |
ACT_STARTING | An alternate facility is currently being prepared as a running server. |
STOPPING | An alternate facility is currently being stopped. | Re-execute the stop command after the KFPS01841-I message is output. |
ONLINE | Alternate processing is currently in progress. | Operation cannot be stopped quickly when alternate processing is in progress. When executing the system reconfiguration command or replacing the current HiRDB with an update version, return the system to normal status, and then execute. |
OFFLINE | Already corrected. | The alternate BES unit is already stopped. |
NONALTSVUNIT | The unit is not an alternate BES unit. | Execute the command using the alternate BES unit. |
KFPS04654-W L
Unable to continue alternate service for unit aaaa because of dying alternate server unit bbbb
- The currently running alternate facility stopped because the alternate BES unit terminated.
- aaaa: Unit identifier of a normal BES unit
- bbbb: Unit identifier of an alternate BES unit
- S: Terminates processing.
- Action
- When the alternate BES unit has taken over the server functioning of the normal BES unit, system switchover occurs once the normal BES unit completes standby. If system switchover does not occur, execute the pdstart -q command on the normal BES unit.
KFPS04655-E L
Unable to continue HiRDB server aa....aa processing because serious error occurred
- Processing cannot continue in server aa....aa due to an error.
- aa....aa: Server name
- S: Terminates processing.
- Action
- Check the error message output before this message, and eliminate the cause of the error. If necessary, restart the server.
KFPS04660-I L
Pdchgconf started
- The system reconfiguration command (pdchgconf) has started.
- S: Continues processing.
KFPS04661-I L
Pdchgconf terminated. return code=aa
- The system reconfiguration command (pdchgconf) has terminated.
- aa: Return code
- 0: System reconfiguration processing terminated normally.
- 8: System reconfiguration processing terminated in an error.
- S: Terminates processing.
- Action
- If the return code is 8, see the error message output to standard error or the message log to eliminate the cause of the error. Then, re-execute the command.
KFPS04662-E L
Unable to execute pdchgconf, because aa....aa
- The system reconfiguration command (pdchgconf) could not be executed.
- aa....aa: Reason code
- S: Terminates processing.
- Action
- Take action according to the reason code listed in the following table.
Reason code | Action |
---|
transactions exist | A transaction or utility has been running for 15 minutes. Check if any transactions or utilities require long operation time, and then re-execute the command. |
offline units exist | Some inactive units were found. Start all units, and then re-execute the command. |
offline servers exist | Some inactive servers were found. Start all servers, and then re-execute the command. |
change of configuration invalid (pd_system_id) | The pd_system_id operand could not be changed. Return the specified value of this operand to the original value, and then re-execute the command. |
change of configuration invalid (pd_master_file_name) | The pd_master_file_name operand could not be changed. Return the specified value of this operand to the original value, and then re-execute the command. |
communication error occurred | A communication error occurred. Check for the cause of the communication error, take appropriate action, and then re-execute the command. |
pdrplstop executing | The pdrplstop command is currently running. After the pdrplstop command terminates, re-execute the command. |
only for pdrstr and pdcopy mode | Use the pdstart -r command to start the HiRDB system. Re-execute the command after normal starting or resuming. |
Online DB Reorganization executing | Updatable online reorganization is running. Terminate updatable online reorganization, and then re-execute the command. |
replication mode unmatch | The operating status of linkage with HiRDB Datareplicator does not match the definition. Make the operating status linkage with HiRDB Datareplicator match the definition, and then re-execute the command. |
change of configuration invalid (unit status file:bbbb,cc....cc) | The definition of a status file for a unit that cannot be changed was changed. bbbb is the unit identifier and cc....cc is the name of the status file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command. |
change of configuration invalid (server status file:dd....dd,ee....ee) | The definition of a status file for a server that cannot be changed was changed. dd....dd is the server name and ee....ee is the name of the status file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command. |
change of configuration invalid (log file:ff....ff,gg....gg) | The definition of a system log file that cannot be changed was changed. ff....ff is the server name and gg....gg is the file group name of the system log file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command. |
change of configuration invalid (sync point dump file:hh....hh,ii....ii) | The definition of a synchronization point dump file that cannot be changed was changed. hh....hh is the server name and ii....ii is the file group name of the synchronization point dump file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command. |
configuration change failed | An attempt to change the HiRDB system definition failed. Action:
- Fix the cause of the error. If the disk space under the HiRDB directory is full, secure disk space. If you do not have write privileges to a system shared definition file, request that the HiRDB administrator grant write privilege to this file. If a communication error occurred, eliminate the cause.
- Check the status of the HiRDB system definition for all units. If the status is not the pre-modification status, recover the HiRDB system definition from %PDDIR%\conf\backconf.
- Because HiRDB is inactive, start HiRDB, and then re-execute the command.
|
disk change failed | The disk was disconnected or connection failed. Action:
- Disconnect the disk and check the content of the connection shell. If you do not have shell execution privileges, request execution privileges from the HiRDB administrator.
- Check the status of the HiRDB system definition for all units. If the status is not the pre-modification status, recover the HiRDB system definition from %PDDIR%\conf\backconf.
- Check the disk connection status.
- If the HiRDB system is inactive, start HiRDB, and then re-execute the command.
|
change of configuration directory invalid | The directory is invalid. Check the %PDDIR%\conf\chgconf directory for each unit of the HiRDB system, and then re-execute the command. |
change of configuration directory not exist | The directory does not exist. Check the %PDDIR%\conf\chgconf directory for each unit of the HiRDB system, and then re-execute the command. |
HiRDB Advanced High Availability not setup | HiRDB Advanced High Availability is not set up. When using the system reconfiguration command, set up HiRDB Advanced High Availability. |
unable to skip offline unit | Because the value of the pd_mode_conf operand is AUTO, recovery-unnecessary FES units that have stopped are ignored, and the command cannot be executed. Start the stopped units, and then re-execute the command. |
change of configuration invalid (pdstart -k stls) | For recovery-unnecessary FES units that have stopped, specification of the pdstart operand with the -k stls option cannot be changed. Start the stopped units, and then re-execute the command. |
resident RDAREA exists | Release the RDAREA from in-memory allocation, and then re-execute the command. |
XDS exists | There is a running XDS. Stop all running XDS units, and then re-execute the command. |
expand unit exists | Because an expansion unit is specified in the pd_system_expand_unit operand in the system common definition, the system configuration cannot be changed by the pdchgconf command while HiRDB is running. Terminate HiRDB normally, and then change the system configuration. |
KFPS04663-W L
Now waiting for termination of transaction or utility
- The system manager is currently awaiting termination of a transaction or utility.
This message might be output repeatedly when a transaction or utility does not terminate for a long time. - S: Continues processing.
- Action
- When giving priority to execution of the pdchgconf or pdtrnqing commands, check currently running transactions and utilities using the pdls -d trn or pdls -d prc command, and then cancel them using the pdcancel command. When giving priority to executing transactions and utilities, no action is required.
KFPS04664-I L
Configuration change processing aa....aa. unit:bbbb
- The system reconfiguration command (pdchgconf) was used to change the system definition.
- aa....aa: Processing content
- start: Changing of the system definition has started.
- end: Changing of the system definition has finished.
- recover: Undoing of the changes to the system definition has started.
- bbbb: Unit identifier
- S: Continues processing.
KFPS04665-W E
Changing definition file skipped in pdchgconf, unit ID=aaaa, reason code=bb....bb
- The pdchgconf command did not update the system definition file on unit aaaa.
- aaaa: Unit identifier of the unit for which the system definition file was not updated
- bb....bb: Reason that the system definition file was not updated
- communication error occurred: A communication error occurred. An error may have occurred in the network, each machine, unit, or server.
- S: Continues processing.
- Action
- Before restarting unit aaaa, replace the system definition files under %PDDIR%\conf and %PDCONFPATH% with the system definition file after the update.
- communication error occurred is displayed in bb....bb: This is the reason for the communication error from the system manager unit to unit aaaa. Check that there was no network failure and that the remote shell execution privilege has been granted, and take action appropriate to the cause of the error.
KFPS04666-I J
System configuration changed
- The system definition may have been changed. This message is output when Job Management Partner/Integrated Manager is notified of an event.
- S: Continues processing.
KFPS04667-I L
Transaction and connect pause process start.unit=aa....aa
- Unit aa....aa transaction queuing started.
- aa....aa: Unit identifier
- S: Continues processing.
KFPS04668-I L
Transaction and connect pause process ended.unit=aa....aa
- Unit aa....aa transaction queuing terminated.
- aa....aa: Unit identifier
- S: Continues processing.
KFPS04669-I L
Transaction and connect pause process released.unit=aa....aa
- Unit aa....aa transaction queuing was released.
- aa....aa: Unit identifier
- S: Continues processing.
KFPS04670-E E+L
Error occurred while releasing HiRDB standby state
- An abnormality was detected during standby release processing; or HiRDB normal startup processing was executed on a HiRDB in standby status. In this case, the standby system HiRDB cannot start normally.
- Consider the following causes:
- User server hot standby is applied, and Hitachi HA Toolkit Extension is used:
- Before the Hitachi HA Toolkit Extension service process was activated (using the hateserve command), HiRDB was started using the pdstart command. If HiRDB is started before the Hitachi HA Toolkit Extension service process is activated, HiRDB will start in standby status, and activation of the Hitachi HA Toolkit Extension service process performs standby release processing.
- After starting the standby system HiRDB, start the running system HiRDB normally. At this time, startup of the running system HiRDB will fail, and a system switchover will occur.
- An attempt was made to stop the running system HiRDB:
- After a normal termination or a planned termination was confirmed, a system switchover occurred due to CPU error or service slowdown.
- S: Outputs an abort code (Psadhf0), and terminates the process.
- Action
- User server hot standby is applied, and Hitachi HA Toolkit Extension is used:
- If the pdstart command was executed before activation of the Hitachi HA Toolkit Extension service process, execute pdstart after the Hitachi HA Toolkit Extension service process has been activated; or specify the HiRDB activation command in the Hitachi HA Toolkit Extension server definition statement actcommand operand. If the pdstart command is executed from a shell, make sure that the shell operates in the same way after the Hitachi HA Toolkit Extension service process has activated.
- After taking measures to correct the failed startup of the running system HiRDB, restart the running system HiRDB.
- An attempt was made to stop the running system HiRDB:
- In UNIX
Take measures to correct the failed termination of the running system HiRDB.
When HiRDB is restarted, startup processing might be interrupted in the following circumstance: If the HA monitor is being used as the cluster software, and the HA monitor single system is in shutdown status, the HA monitor might not be able to determine whether a system is the running system or the standby system. In that case, it is necessary to execute the following HA monitor commands to make the system the running system:
Use the monshow command to confirm that the server status is *SBY* (waiting for the running server to start up).
Use the monact command to notify the HA monitor that this is the running server.
- In Windows
Take measures to correct the cause of the failed termination of the running system HiRDB.
KFPS04680-E E+L
Error occurred in Real_Time_SAN_Replication, reason code=aa....aa, command=bb....bb, group=cc....cc
- An error occurred in a RAID Manager command.
- aa....aa: Code
- bb....bb: Name of the RAID Manager command that caused the error
- cc....cc: Name of the pair logical volume group
- S: Continues processing.
- Action
- Take action based on the following codes:
Code (aa....aa) | Explanation | HiRDB administrator action |
---|
SYSTEMCALL | RAID Manager command bb....bb call failed. | See the table SYSTEMCALL actions below, and take the action appropriate to the values of errno and value indicated in the KFPS01815-E message output immediately before this message. |
ERRORRETURN[dd....dd] | RAID Manager command bb....bb caused an error. The error code of the RAID Manager command is dd....dd. The pair logical volume group that corresponds to execution of the command is cc....cc. | See the RAID Manager manual, and take the action appropriate to the error code. Use the code displayed in dd....dd, and see the table ERRORRETURN actions below for typical codes. |
GETRESULTFAILED | Result acquisition of RAID Manager command bb....bb failed. | There may be a shortage of free disk space in the HiRDB directory, or a memory error. Consider the free disk area and free memory area, and increase the amount of free area. |
TIMEOUT | Pair logical volume group update wait processing has exceeded the maximum wait time. | Check the RAID Manager and HORC running status, check the reason that the subvolume reflection of the pair logical volume group displayed in cc....cc was delayed, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager and HORC manuals. |
BROKEN | In pair logical volume group update wait processing, the pair in the volume group was broken. | Check the reason that the pair in the pair volume group was broken, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager manual. |
CHANGED | In pair logical volume group update wait processing, the synchronization status of the volume group was temporarily released and was then resynchronized. | Check the reason that the pair in the pair volume group was broken, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager manual. |
- SYSTEMCALL actions
errno | Value | Explanation | Action |
---|
Ignored | 0 | The process was cancelled during command execution. | Determine the reason for the cancellation (excluding intended cancellation), and take appropriate action. |
126 | There is no command execution privilege. | Request that the HiRDB administrator grant the RAID Manager administrator privilege. |
127 | The command was not installed in the default path. | If the RAID Manager is not installed, install it. Confirm that the RAID Manager commands are located under /usr/bin, and if not, reinstall the RAID Manager. |
11 | Any | The total number of processes being executed by a single user exceeds the maximum for the system. | In UNIX: Increase the value of the following operating system parameters (kernel parameters):
- HP-UX: maxuprc or nproc
- Solaris: maxuprc or max_nprocs
- AIX: maxuproc or the number of fixed licenses
- Linux: MAX_TASKS_PER_USER or NR_TASKS
If these measures do not correct the problem, contact the customer support center. In Windows: Contact the customer support center. |
12 | Any | Consider the following causes:
- Due to a swap area shortage, new processes cannot be generated
- There are too many processes, or some processes are consuming a large amount of memory
| If there is a swap area shortage, extend the area. If the area cannot be extended, stop unneeded processes. If some of the processes are consuming a large amount of memory, consider whether the processes can be stopped temporarily. |
13 | Any | There is an error in the command access privilege. | Check the command access privilege. |
- ERRORRETURN actions
Value of dd....dd | Explanation | Action |
---|
EX_COMERR | Communication with RAID Manager failed. | Check that the RAID Manager instance is running and that the specification of the HORCMINST operand is correct. |
EX_ATTHOR | Unable to connect to the RAID Manager instance. | Take the following actions:
- Check that the RAID Manager instance is running.
- Check that the specification of the HORCMINST operand is correct.
- Check that the pair volume configuration definition is correct.
|
EX_ENOENTEX_ENOGRP | The group specified by cc....cc does not exist. | Take the following actions:
- Check that the specification of the HORCMINST operand is correct.
- Check that the pair volume configuration definition is correct.
|
EX_INVVOL | The status of the group specified by cc....cc is invalid. | Check the attributes and status of each pair volume included in cc....cc, and ensure that the attributes and status of all pair volumes match. Also ensure that the attributes and status of all pair volumes are correct. |
KFPS04681-E E
aa....aa invalid; stops unit startup. server ID=bb....bb, old value= cc....cc, new value= dd....dd
- The unit cannot be restarted because the value specified in aa....aa operand has been changed. The value of aa....aa operand cannot be changed after an abnormal termination, forced termination, or planned termination.
- aa....aa: Operand that does not match the specified value
- pd_rise_use
- pd_rise_pairvolume_combination
- pd_rpl_reflect_mode
- pdstart -k
- pd_system_expand_unit
- bb....bb: Server name
- If aa....aa operand is the system common definition or the unit control information definition, "********" is displayed.
- cc....cc: Value of aa....aa operand before the change
- If an expansion unit was added to the pd_system_expand_unit operand, **** is displayed.
- dd....dd: Value of aa....aa operand after the change
- If the expansion unit specified in the pd_system_expand_unit operand was deleted, **** is displayed.
- S: Terminates processing.
- Action
- If aa....aa is something other than pd_system_expand_unit:
- Return the value of aa....aa operand to its value before the change (cc....cc), and restart the unit.
- If aa....aa is pd_system_expand_unit:
- Because some units might be in the process of starting, execute the command pdls -d ust on each unit to check the status of the unit. If the status of the unit is STARTING, use the pdstop -z command to terminate the unit. Make sure that all the units have terminated, and then change the value specified in the pd_system_expand_unit operand. After that, restart the units.
- Note that the value before the change (the value in cc....cc) and the value after the change (the value in dd....dd) are displayed for each unit.
KFPS04682-E E+L
Unable to specify Real_Time_SAN_Replication, because of using aa....aa
- Some facilities cannot be used when Real Time SAN Replication with the log-only synchronous method is used.
- aa....aa: Facility name
- Staticizer Option: Inner replica facility
- S: Terminates processing.
- Action
- If Real Time SAN Replication with the log-only synchronous method is used, revise the system definition so as not to use the facility indicated in the message.
- If the facility indicated in the message is to be used together with Real Time SAN Replication with the log-only synchronous method, set the pd_rise_pairvolume_combination operand to other than syssync. If the facility is to be used without Real Time SAN Replication, set the pd_rise_use operand to N.
- After revising the system definition, restart HiRDB.
KFPS04683-I L
HiRDB unit aaaa start on standby site
- A log application site unit was started.
- aaaa: Unit identifier
- S: Continues processing.
KFPS04684-E E
Unable to execute aa....aa, because bb....bb
- Due to reason bb....bb, the aa....aa command could not be executed.
- aa....aa: Command name (including options)
- bb....bb: Reason code
- S: Terminates processing.
- Action
- Refer to the reason code, and determine whether the executed command and its options are appropriate. Also, if necessary, take the following actions. Refer to the section on operations when an error has occurred in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
Reason code (bb....bb) | Explanation | HiRDB administrator action |
---|
HiRDB Disaster Recovery Light Edition not set up | HiRDB Disaster Recovery Light Edition is not set up. | If Real Time SAN Replication with the log-only synchronous method is used, also use HiRDB Disaster Recovery Light Edition. |
Real_Time_SAN_Replication mode is not system_log synchronized | Some operands required for Real Time SAN Replication with the log-only synchronous method might not have been specified. | If Real Time SAN Replication with the log-only synchronous method is used, specify Y in the system common definition pd_rise_use operand, and specify syssync in the pd_rise_pairvolume_combination operand. |
necessary to execute pdriseset | The site was not set up using the pdriseset command. | Execute the pdriseset command, and set up the transaction execution site or the log application site. |
this system is Real_Time_SAN_Replication primary site | The command cannot be executed on a transaction execution site. | If it is possible to switch to a log application site, execute the pdriseset -S command. |
this system is Real_Time_SAN_Replication standby site | The command cannot be executed on a log application site. | Execute commands that can be executed on a log application site. To start HiRDB on a log application site, use the pdstart -l command. To stop HiRDB on a log application site, use the pdstop -l command or the pdstop -f command. If it is possible to switch to a transaction execution site, execute the pdriseset -P command. |
this system is not Real_Time_SAN_Replication standby site | The command can only be executed on a log application site. | Ensure that the commands and options to be executed can be executed on a site other than a log application site. |
unit being started | The command cannot be executed because a unit is in startup processing. | The unit that was the cause of the error and its status are displayed in a KFPS05223-I message. Use pdls -d svr to check the unit's status, and, if necessary, restart the stopped unit. |
unit being terminated | The command cannot be executed because a unit is in shutdown processing. |
unit terminated abnormally | The command cannot be executed because a unit terminated abnormally or was terminated using the pdstop -f command. |
execution in process | The command cannot be executed because the pdrisedbto command is executing. | If multiple pdrisedbto commands were executed, wait for any executing pdrisedbto command to terminate. The site inheritance status can be checked using the pdls -d ris command. |
KFPS04685-E E
Status subfiles only initialized, aa....aa
- All status subfiles are in initial status.
Consider the following causes: - In the preparation for log application, the log application site's status subfiles were not created according to the correct procedure.
- The log application site's current status subfiles were deleted.
- aa....aa:
- unit=bbbb
- Unit status file for unit bbbb
- unit=bbbb, server=cc....cc
- Server status file for server cc....cc on unit bbbb
- bbbb: Unit identifier
- cc....cc: Server name
- S: Continues processing.
- Action
- Ensure that there was no error in the procedure for preparation for log application, and then re-execute preparation for log application.
- Execute preparation for log application in order to start the log application site HiRDB.
KFPS04686-I L
HiRDB unit aaaa database take over terminated
- Unit aaaa was terminated, and database inheritance from the transaction execution site terminated.
- aaaa: Unit identifier
- S: Terminates processing.
KFPS04687-I L+S
Real_Time_SAN_Replication information : status=aa....aa
- The site status of Real Time SAN Replication with the log-only synchronous method is displayed.
- aa....aa: Site status
- primary: Execution
- standby: Log application
- ready: Ready
- initial: Initial
- If the site status cannot be determined, **** is displayed.
- S: Continues processing.
- Action
- Site status other than ****
There is no problem.
- Site status is ****
Take one of the following actions:
If using a system switchover configuration, check the system where the command was executed, and execute the pdriseset command from the primary system.
If this message was output when the pdriseset command was executed on the primary system, review the value of the unit control information definition pd_hostname operand.
If the pd_hostname operand contains a specification other than the standard host name of the primary system, specify the standard host name of the primary system.
If this message was output when using a configuration other than a system switchover configuration, contact the customer support center.
KFPS04688-I L+S
Site status set to aa....aa from bb....bb
- The site status was reset.
- aa....aa: Site status that was reset
- primary: Execution
- standby: Log application
- initial: Initial
- bb....bb: Site status before resetting
- ready: Ready
- primary: Execution
- standby: Log application
- initial: Initial
- S: Continues processing.
KFPS04689-W E+L
aa....aa ignored, reason=bb....bb
- Due to reason code bb....bb, specification of the facility indicated by aa....aa was ignored.
- aa....aa: Facility name
- Non_Recover_FES: Recovery-unnecessary front-end server
- System switchover facility: System switchover facility
- Security Audit: Security audit facility
- Statistical information: Statistical information
- HiRDB Datareplicator: HiRDB Datareplicator linkage facility
- bb....bb: Reason code
- standby site: Operates as a log application site
- S: Continues processing.
- Action
- If Real Time SAN Replication with the log-only synchronous method is being used on a log application site, the facility indicated in aa....aa becomes invalid. For details, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
KFPS04690-Q S
The state of site changed to aa....aa. (y/n)
- This is a message inquiring whether to change the site status to aa....aa.
- aa....aa:
- primary: Execution
- standby: Log application
- initial: Initial
- S: Continues processing.
- Action
- To change the site status, enter y or Y; to leave the site status unchanged, enter n or N. If any other letter is entered, or if only the return key is entered, n is assumed.
KFPS04691-I L+S
Pdrisedbto terminated, return code=a
- Database inheritance terminated.
- a: Return code
- 0: Terminated normally.
- 4: Database inheritance has terminated for some of the servers.
- 8: Terminated in an error.
- S: Terminates processing.
- Action
- If the return code is 8, refer to the message output before this message, and take action.
- If the return code is 4, take one of the following actions:
- To perform database inheritance for all servers
Refer to the message output before this message, eliminate the cause of the error from the server for which inheritance failed, use the pdstart -l command to start HiRDB, and then re-execute the pdrisedbto command.
- To invalidate database inheritance for some of the servers, and to perform site switchover
Refer to the section on site switchover in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and continue with site switchover.
KFPS04692-W S
pdrisechk command executed with standby system
- Because the pdrisechk command was executed on a standby system in a system switchover configuration, the site status could not be determined correctly.
- S: Continues processing.
- Action
- If this message was output when the pdrisechk command was executed on the primary system, revise the value specified for the unit control information definition pd_hostname operand. If other than the standard host name of the primary system is specified in the pd_hostname operand, specify the standard host name of the primary system.
- If the pdrisechk command was executed on the standby system, there is no problem. Check the results of the pdrisechk command execution.
KFPS04693-E E+L
Host name specified in pd_security_host_group definition invalid, reason code=aa....aa, hostname=bb....bb
- Invalid host name specified in the pd_security_host_group operand of the system common definition:
- aa....aa:
- INVALID: An invalid host name or a host name that cannot be resolved has been specified.
- DUPLICATE: The host name is a duplicate.
- LENGTH OVER: Exceeds the limit for the length of the host name (256 characters).
- bb....bb: Invalid host name:
- The host name, IP address or FQDN is displayed. If the number of characters exceeds the maximum of 100, only the first 100 characters are displayed.
- S: Terminates system definition analysis processing, and then terminates HiRDB start processing.
- Action
- Take corrective action according to the reason code, and then re-start HiRDB.
- INVALID:
- If the host name is invalid:
Specify the correct host name.
- Other servers:
The host name has not been resolved. If you are not using the DNS server, record the host name in the hosts file. If you are using the DNS server, record the host name in the DNS server file.
- DUPLICATE:
- Specify a unique host name.
- LENGTH OVER:
- Specify a host name that does not exceed 256 characters.
KFPS04694-E E
Unable to create temporary file, dir=aa....aa, func=bb....bb, errno=cc....cc
- Creation of temporary files failed.
- aa....aa: Temporary file creation directory
- If the directory name length is 141 bytes or longer, an ellipsis (...) is output at the front of the name and then the last 137 bytes are output.
- If a directory where temporary files are created cannot be identified, NULL is output.
Directories in which temporary files are created depend on environment variable TMPDIR in UNIX and environment variable TMP or TEMP in Windows. If NULL is output, revise the environment variable.
- bb....bb: OS function in which the error occurred
- tempnam: tempnam function
- open: open function
- cc....cc: errno value of the OS function
- S: Terminates processing.
- Action
- Investigate the errno value, refer to error.h or the OS documentation, and eliminate the cause of the error. For representative errnos, see 4.3 System call return codes.
KFPS04695-I L
Now starting HiRDB expand unit aaaa
- The expansion unit aaaa is starting up.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05001-I E+S
Usage: pdls {[-d {act [-s server_name]
aud [-U user_id]
ha [{-u unit_id | -s server_name}] [-a]|
lck {[-a] [-s server_name]|[-p [-e]]|[-T [-R]]}|
mem|
org [-u unit_id] [-s server_name] [-a]|
prc [-a|-s server_name] [-c] [-C [-H]]|
ris [-u unit_id] [-s server_name] [-a]|
rpc [-a]|
rpl [-j] [-u unit_id] [-s server_name]|
scd [-a|-s server_name]|
stj [-s server_name]|
sts [{-x host_name|-u unit_id}]
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
sts -s server_name
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
svr [-a [-b]]|
trn [-t TRNGID][-{a|c}][-s server_name] [-C [-H]]
ust [-a] [-C [-H]]}]|
[-a [-b]]}
- The specification format of a pdls command option is invalid.
- S: Terminates processing.
- O: Re-executer the command correctly for a HiRDB/Single Server.
KFPS05001-I E+S
Usage: pdls {[{-d act [-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]
aud [-u unit_id] [-U user_id]|
ha [{-u unit_id | -s server_name}] [-a]|
lck {[-a] [-s server_name]|[-p [-e]]|[-T [-R]]} [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
mem [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
org [-s server_name] [-a] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
prc [-a|-s server_name] [-c] [-C [-H]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
ris [-u unit_id] [-s server_name] [-a]|
rpc [-a]|
rpl [-j] [-u unit_id] [-s server_name]|
scd [-a|-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
stj [-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
sts {-x host_name|-u unit_id}
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
sts -s server_name
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
svr [-a [-b]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
trn [-t TRNGID][-{a|c}][-s server_name] [-C [-H]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]
ust [-a] [-C [-H]]}]|
[-a [-b]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]}
- The specification format of a pdls option is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05002-I S
Usage: pdinit -d statement_control_file_name [-u authorization_identifier [-p password]]
- The specification format of a pdinit option is invalid.
- S: Terminates processing.
- Action
- Re-execute the utility correctly.
KFPS05003-I S
Usage: pdmod -a statement_control_file_name
- The specification format of a pdmod option is invalid.
- S: Terminates processing.
- Action
- Re-execute the utility correctly.
KFPS05005-I L+S
Usage: pdstart [{-i|-r [-t]|-l|dbdestroy}]
- The specification format of a pdstart command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05005-I L+S
Usage: pdstart [{-i|-r [-t]|-l|dbdestroy}] | [-x host_name|-u unit_id] [-r [-t]|-l|dbdestroy] | [[-x host_name|-u unit_id] -s server_name] | [-a [-s FES_name]] | [-q [-r [-t]|-l]] | [-q -c] | [-R [-t]]
- The specification format of a pdstart command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05006-I S
Usage: pdstop [-P [-d]|-f [-d|-q]|[-d]|-l [-d]]
- The specification format of the pdstop command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05006-I S
Usage: pdstop [{[-x host_name|-u unit_id][-s server_name][-d]|-P [-d]|-f [-x host_name|-u unit_id][-s server_name][-d]|-z [-d|-q|-c|-s server_name]|-l [-d]}]
- The specification format of a pdstop command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05007-I S
System definition check ended. return code = a
- The pdacunlck command terminated with return code a.
- a: Return code:
- 0: Normal termination
- 8: Error termination (an argument was invalid or an error was output in the execution results of the pdconfchk command)
- S: Terminates processing.
- Action
- If the return code is not 0, check the execution results of the pdconfchk command and correct the error.
KFPS05008-I S
Usage: pdcancel {-U |-u uap_name[-i process_id] |-i process_id -d}
- The specification format of a pdcancel command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05008-I S
Usage: pdcancel {-x host_name| -X unit_id} {-U| -u uap_name [-i process_id]| -i process_id -d}
- The specification format of a pdcancel command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05009-I S
Usage: pdcat {[-a | -b | -ab] [-c importance_code[,importance_code]....] [-y yyyymmdd] [-t hhmmss] [-T hhmmss] [-n record_number] [file_name] | -d sts {[-x host_name|-u unit_id]|-s server_name} -f full_path_name [-v] [-e] }
- The specification format of a pdcat command option is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly for a HiRDB/Single Server.
KFPS05009-I S
Usage: pdcat {[-x host_name|-u unit_id] [-a | -b | -ab ] [-c importance_code[,importance_code]....] [-y yyyymmdd] [-t hhmmss] [-T hhmmss] [-n record_number] [file_name] | -d sts {-x host_name|-u unit_id|-s server_name} -f full_path_name [-v] [-e] }
- The specification format of a pdcat command option is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05011-I S
Usage: pddump [-f rpc_trace_file_name]
- The specification format of a pddump command option is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly for a HiRDB/Single Server.
KFPS05011-I S
Usage: pddump {-x host_name |-u unit_id} [-f rpc_trace_file_name]
- The specification format of a pddump command option is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05012-I E+L+S
Usage: pdconfchk [-d directory_name] [-n][-l]
- The specification format of a pdconfchk command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05012-I E+L+S
Usage: pdconfchk [-d directory_name] [-n] [-l] [-u unit_id]
- The specification format for the pdconfchk command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05015-I E
Usage: pdstjswap [-x host_name| -u unit_id]
- The specification format of a pdstjswap command option is invalid.
- S: Terminates processing.
- P: Re-execute the command correctly for a HiRDB/Single Server.
KFPS05015-I E
Usage: pdstjswap {-x host_name| -u unit_id}
- The specification format of a pdstjswap command option is invalid.
- S: Terminates processing.
- P: Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05016-I S
Usage: pdstbegin [-k statistics_type [, statistics_type]....] [-m time_interval] [-a |-s server_name [, server_name]...][-w]}
- The specification format of a pdstbegin command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05016-I S
Usage: pdststart [-k statistics_type [,statistics_type]....] [-m time_interval] [-x host_name |-u unit_id] [-a |-s server_name [, server_name]...][-w]}
- The specification format of a pdststart command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05017-I S
Usage: pdstend [-k statistics_type[, statistics_type]....] [-a| -s server_name[, server_name]...][-w]
- The specification format of the pdstend command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Single Server.
KFPS05017-I S
Usage: pdstend [-k statistics_type[, statistics_type]....][-x host_name|-u unit_id][-a|-s server_name[, server_name]...][-w]
- The specification format of the pdstend command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05018-I S
Usage: pdchgconf
- The specification format of the pdchgconf command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05019-I E+L
Usage: pdopen {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number]
- The specification format of the pdopen command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05020-I E+L
Usage: pdclose {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number]
- The specification format of a pdclose command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05021-I E+L
Usage: pdhold {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number] {[-c]|[-i]|[-b[-w][-u]]|[-s]}
- The specification format of a pdhold command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05022-I E+L
Usage: pdrels {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number][-o]
- The specification format of the pdrels command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05023-I E+L
Usage: pddbls { { { -r RDAREA[,RDAREA...] | -r ALL | -s server_name[,server_name...] } [ -{ l | a } ] [-{ b | o } ] [ -m ] [-x[-y]] [-M] [-D] [-T] } | { { -q generation_number | -C } [ - { l | a } ] [ -m ] [-x[-y]] [-M] [-D]} }
- The specification format of a pddbls command option is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05024-I S+L
Usage: pdrplstart
- The specification format of the pdrplstart command is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05025-I S+L
Usage: pdrplstop
- The specification format of the pdrplstop command is invalid.
- S: Terminates processing.
- Action
- Re-execute the command correctly.
KFPS05026-I E
Usage: pdndls [-w HiRDB_ID] [-x host_name]
- The specification format of the pdndls command is invalid.
- S: Terminates processing.
- O: Re-execute the command correctly.
KFPS05028-I S
Usage: pdchprc [-p resident_process_count[,max_process_count]]
- The specification format of the pdchprc command is invalid.
- S: Terminates processing.
- P: Re-execute the command correctly for a HiRDB/Single Server.
KFPS05028-I S
Usage: pdchprc {-a |-s server_name} [-p resident_process_count[,max_process_count]]
- The specification format of the pdchprc command is invalid.
- S: Terminates processing.
- P: Re-execute the command correctly for a HiRDB/Parallel Server.
KFPS05029-I S
Usage: dcspool [-i] [-d day_count] [-k { all|dump } ]
- An option is specified in an invalid format in the pdspool command.
- S: Terminates processing.
- O: Re-execute the command correctly.
KFPS05030-I S
Remove following files
- Deletes the following files.
- S: Continues processing. Following this message, HiRDB outputs a list of path names of the files to be deleted, minus the path %PDDIR%\spool.
KFPS05031-E E
An error occurred due to aa....aa
- A command's internal function resulted in an error.
- aa....aa: Cause of the error
- S: Terminates processing.
- Action
- Contact the customer support center.
KFPS05032-E E
RPC error, return code=aa....aa
- An RPC communication error occurred.
- aa....aa: RPC error code
- S: Terminates processing.
- Action
- See 4.1 Detail codes for RPC-related errors to eliminate the cause of the error, and re-execute the command. If the same error recurs, contact the customer support center.
KFPS05033-E E+L
Internal function error, func=aa....aa, return code=bb....bb
- Command's internal processing resulted in an error.
- aa....aa: Name of the function resulting in the error
- bb....bb: Detail code for the system-related error
- S: Terminates processing.
- Action
- See 4.2 Detail codes for system-related errors to eliminate the cause of the error. If the error cannot be corrected by the user, contact the customer support center.
KFPS05034-E E
System call error, func=aa....aa, return code=bb....bb, errno=cc....cc
- A system function error occurred. This message displays the function name resulting in the error, the function's return code, and errno.
- aa....aa: Function name
- bb....bb: Return code
- cc....cc: errno value
- S: Terminates processing.
- O: Check the error indicator value, refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute.
- Action
- Eliminate the cause of the error and execute the command.
KFPS05035-E E+L
Unable to start command; insufficient memory on PROCESS
- A shortage occurred in the process private area.
- S: Terminates processing.
- Action
- Check System call = malloc and Mnemonic = ENOMEM in 4.3 System call return codes to investigate the cause of the error, and take appropriate action.
KFPS05036-E E
aa....aa receive data incorrect
- RPC reception result is invalid for command aa....aa.
- aa....aa: Command name
- S: Terminates processing.
- Action
- There may be a communication error or a memory shortage. If an error message was output before this message, take action as indicated in that message. If this message is output again, even with these actions, contact the customer support center.
KFPS05037-E E
Enter command in manager node
- A command was entered to a host that is not the system manager.
- S: Terminates processing.
- O: Enter the command on the server machine where the system manager is located.
KFPS05038-E E
Remote procedure call error occurred
- A communication error occurred.
- S: Terminates processing.
- Action
- If an error message was output before this message, take action as indicated in that message. If no message was output, contact the customer support center.
KFPS05039-E E+L
Unable to access shared memory
- Shared memory cannot be accessed.
- S: Terminates processing.
- Action
- HiRDB shared memory may have been deleted. If HiRDB shared memory was deleted, contact the customer support center.
- Otherwise, eliminate the cause of the error according to the detail message already output. If no detail message was output, contact the customer support center.
- If you are using the Windows edition of HiRDB/Parallel Server, this message may be output immediately after a value is entered with the pdstart command. In this case, a system definition may be invalid, so re-evaluate the system definitions based on the messages output to the event log.
KFPS05040-E E+L
Unable to start command due to HiRDB status off line
- A command was entered while HiRDB was inactive.
- S: Terminates processing.
- Action
- Activate HiRDB before executing the command.
KFPS05041-E E+L
Incorrect server name specified
- The server name specified in a command option is invalid. The name of a server that was not defined as a HiRDB server was specified, or the name of a server that was not the target of the command was specified.
- S: Terminates processing.
- Action
- Check the server name, and re-execute the command.
KFPS05042-E E
Incorrect hostname or unit id specified
- The host name specified in a command parameter has not been defined as a HiRDB host name.
- S: Terminates processing.
- Action
- Specify a host name that has been defined as a HiRDB host name and execute the command.
KFPS05043-E E
Unable to execute aa....aa command from bb....bb to cc....cc
- A command cannot be executed at a remote host.
- aa....aa: Command name
- bb....bb: Local host name (standard host name of the host that executed the command)
- If no standard host is required, ******** is displayed.
- If the standard host name exceeds 32 characters, only the first 32 characters are displayed.
- cc....cc: Remote host name
- If the remote host name exceeds 32 characters, only the first 32 characters are displayed.
- S: Terminates processing.
- Action
- Take the following action:
- Check if it is permitted to use the same user ID to log in from the local host to the remote host.
- If c-shell is used as the login shell, check PDDIR specified for $HOME/.cshrc for an error (in UNIX).
- If this message is displayed when the pdconfchk command was executed, and if the host name of the reserve system is displayed in cc....cc in the message, the host name specified in the pd_hostname operand or in the -x option of the pdstart operand may be incorrect. Check that the standard host name of the running system is specified in the pd_hostname operand. Also, check that the correct host name is specified in the -x option of the pdstart operand.
KFPS05044-E E
Communication error occurred, function=aa....aa, errno=bb....bb
- Communication error occurred while reporting abnormal termination of a utility.
- aa....aa: Name of the function resulting in the error
- bb....bb: errno
- S: Terminates processing.
- Action
- Check the error indicator value, eliminate the cause of the error, then re-execute the utility, if necessary. If the same error message is reissued, contact the customer support center.
KFPS05045-E E+L
No server in this unit
- No server is defined for the unit from which the command was entered.
- S: Terminates processing.
- Action
- If the command was entered from the wrong unit, execute the command on the correct unit. Otherwise, terminate the unit, add the server definition, then re-execute the command.
KFPS05045-E E
No dictionary server
- No dictionary server is defined.
- S: Terminates processing.
- Action
- Check the system common definition for the dictionary server definition.
- Dictionary server defined:
- Re-execute the processing. If the same message is reissued, contact the customer support center.
- Dictionary server undefined:
- Define the dictionary server.
KFPS05046-E E
Dictionary already initialized
- A dictionary has already been initialized.
- S: Terminates processing.
- Action
- To initialize a dictionary, either use the pdfmkfs command to re-create the HiRDB file area for the master directory RDAREA or enter the pdstart -i command after system startup.
KFPS05047-E L
Command aa....aa failed, process ID=bb....bb
- An operation command or utility command process terminated abnormally.
- aa....aa: Command name
- bb....bb: Process ID
- S: Resumes processing.
- Action
- Refer to the message troubleshooting information (dump, trace, etc.) that was output before this message and to the message for the corresponding server to check the cause of the abnormal termination, then take appropriate action. If the error cannot be corrected, contact the customer support center.
KFPS05048-Q E+L
Fall-back operation will be started, do you really want to proceed? (y/n)
- When the HiRDB system performs reduced activation by specifying the pd_start_skip_unit operand, the system waits for operator confirmation.
- S: Resumes processing.
- O: Preceding this message, the system displays a KFPS01837-I message indicating the unit identifier on which the reduced activation operation is to be skipped. Check the message and reply y to perform the reduced activation operation, and n to skip it. If n is indicated, the system cancels the HiRDB startup processing.
KFPS05049-Q S
DB recovery from backup required when restarting with "pdstart -dbdestroy", (n/3), do you really want to proceed ?(y/n)
- When pdstart dbdestroy is used to restart HiRDB, database recovery with the database recovery utility becomes necessary, and the system asks whether forced startup should actually be executed. This message is output three times; if the y response is entered all three times, the system executes forced restart. If any other response is entered, the system cancels forced restart and terminates. pdstart dbdestroy should be entered only when HiRDB cannot be started with pdstart; pdstart should always be used first to restart HiRDB. If HiRDB cannot be restarted, take appropriate action, as described below:
- Enter pdstart -r to restart HiRDB.
- Recover the master directory RDAREA, make a backup, then terminate the HiRDB system.
- Enter pdstart dbdestroy to start HiRDB forcibly.
- Recover RDAREAs that were updated since the previous HiRDB startup or since the pdclose command was entered, make a backup, then release the shutdown status.
- S: Waits for a response.
- Action
- To execute forced startup:
- Enter y as the response to all messages that are output.
- To cancel forced startup:
- Enter any character other than y as the response.
KFPS05050-Q S
DB will be initialized when restarting with "pdstart -i", do you really want to proceed ?(y/n)
- When HiRDB is started with the pdstart -i command, all databases must be re-created; the system therefore asks whether HiRDB should actually be started in the initialization mode.
If y is entered as the response, the system resumes startup in the initialization mode; if any character other than y is entered as the response, the system cancels startup and terminates.
To start HiRDB without initializing the database, enter the pdstart command. - S: Waits for a response.
- Action
- To reinitialize the database, enter y as the response.
- To cancel database reinitialization, enter any character other than y as the response.
KFPS05051-E E+L
Unable to cancel process due to status critical
- The process cannot be cancelled because the process status is critical.
- S: Terminates the command.
- O: Re-execute the command if necessary.
KFPS05052-E E
Unable to cancel process due to HiRDB status busy
- Cancellation of the process failed because the HiRDB workload is high.
- S: Terminates the command.
- O: Re-execute the command, if necessary.
KFPS05053-E S
Unable to specify manager node
- The system manager server machine (host) cannot be specified in a command parameter.
- S: Terminates processing.
- Action
- Enter the command to the system manager server machine.
KFPS05054-E E
Same UAP name process exists, Specify server process id
- There is more than one UAP process with the UAP name specified in the pdcancel command.
- S: Terminates processing.
- Action
- Re-execute the command specifying the process ID.
KFPS05055-E E
No such process
- One of the following occurred:
- The process specified in the pdcancel command was not found.
- The specified process terminated immediately before the pdcancel command was entered.
- An attempt was made to cancel a HiRDB system control process by entering the pdcancel command with the -d option specified. (in UNIX)
- S: Terminates processing.
- O:
- If the intended process is still active, re-execute the command with its process ID specified or the correct UAP name specified.
- To execute a pdcancel command that specifies the -d option, specify the process ID of the front-end server, back-end server, dictionary server, single server, or utility server (in UNIX).
KFPS05056-E E
Unable to stop MGR unit with "-z" option
- The pdstop command with the -z option specified cannot be executed at the system manager (MGR).
- S: Terminates processing.
- O: To terminate the system manager, specify the pdstop command without any option specified or with the -f option specified, and terminate the HiRDB system.
KFPS05057-W E
Unable to find server process
- The HiRDB/Single Server process specified in the pdcancel command was not found.
- S: Terminates processing.
- Action
- Check if the process specified in the option for cancellation exists, and re-execute the command specifying the correct option, if necessary.
KFPS05057-W E
Unable to find front end server process
- The front-end server process for a HiRDB/Parallel Server whose cancellation was requested by the pdcancel command was not found.
- S: Terminates processing.
- Action
- Check if the process specified in the option for cancellation exists, and re-execute the command specifying the correct option, if necessary.
KPS05058-E S
Dictionary being initialized
- pdinit is already executing.
- S: Terminates processing.
KFPS05059-E S
Usage: aa....aa
- The command option specification format is invalid.
- aa....aa: Command format
- S: Terminates processing.
- Action
- Check the command usage in the manual HiRDB Version 9 Command Reference, and re-execute.
KFPS05060-E S
Unable to execute aa....aa because bb....bb
- The aa....aa command cannot be executed.
- aa....aa: Command name
- bb....bb: Reason code
- file not found: The setup file does not exist.
- setup file is invalid: The setup file is invalid.
- S: Terminates processing.
- Action
- file not found
Check that the path name of the setup file specified in the aa....aa command is correct.
- setup file is invalid
There is an error in the contents of the setup file specified in the aa....aa command. Revise the contents of the setup file and re-execute the command.
KFPS05061-E E
Too long path name with aa....aa and directory_name
- The pathname of the HiRDB system definition file in the directory specified by the -d option of the pdconfchk command is too long.
- aa....aa:
- PDDIR: Storage location of the unit control information definition file
- PDCONFPATH: Storage location of HiRDB system definition files other than the unit control information definition file
- S: Terminates processing.
- Action
- Take one of the following actions:
- If aa....aa is PDDIR:
Re-evaluate the length of the path name of the %PDDIR%\conf\ subdirectory so that it is no more than 220 bytes.
- If aa....aa is PDCONFPATH (in UNIX):
If the PDCONFPATH operand is specified in the unit control information definition, re-evaluate so that the total length of the shared directory and the subdirectory path name is no more than 220 bytes. If the PDCONFPATH operand is not specified in the unit control information definition, re-evaluate so that the length of the $PDDIR/conf/ subdirectory is no more than 220 bytes.
- If aa....aa is PDCONFPATH (in Windows):
Revise the path name of the %PDDIR%\conf\subdirectory to 220 bytes or less.
KFPS05062-W E
Unmatched PDCONFPATH between system definition file and environment variable
- The value of the PDCONFPATH operand (%PDDIR%\conf is assumed if no value is specified) in the unit control information definition file and the value of the PDCONFPATH environment variable when executing pdconfchk do not match. The pdconfchk command uses the value of the PDCONFPATH operand in the unit control information definition file.
- S: Continues processing.
- Action
- Re-evaluate the value of the PDCONFPATH environment variable.
KFPS05063-E S
Unable to stop normally because unit terminated abnormally
- HiRDB cannot be terminated normally, because a unit was terminated abnormally or forcibly by the pdstop -f command.
- S: Resumes processing.
- Action
- Use the pdls command to determine which unit terminated abnormally or was stopped by the pdstop -f command, start the unit, then terminate it normally with the pdstop command. Or, terminate the unit forcibly with the pdstop -f command.
- If Real Time SAN Replication with the log-only synchronous method is used:
- Transaction execution site
Use the pdls command to determine which units terminated abnormally or were terminated using the pdstop -f command, restart the units, and then use the pdstop command to perform normal termination. Alternatively, use the pdstop -f command to terminate them forcibly.
- Log application site
Use the pdls command to determine which units terminated abnormally or were terminated using the pdstop -f command, start the units, and then use the pdstop -l command to perform normal termination. Alternatively, use the pdstop -f command to terminate them forcibly.
KFPS05064-E S
Unable to stop HiRDB normally because unit being started
- HiRDB cannot be terminated normally, because a unit is engaged in startup processing.
- S: Resumes processing.
- Action
- Re-execute the pdstop command after HiRDB system startup is completed. Or, terminate HiRDB forcibly with the pdstop -f command.
KFPS05065-E S
Unable to stop HiRDB normally because unit being terminated
- HiRDB cannot be terminated normally, because a unit is engaged in termination processing.
- S: Resumes processing.
- Action
- Re-execute the pdstop command after unit termination is completed. Or, terminate HiRDB forcibly with the pdstop -f command.
KFPS05066-E E+L
Error found while analyzing system common definition file
- An error was detected while analyzing the operands in the system common definition.
- S: Terminates processing.
- Action
- Correct the information specified in the system common definition and re-execute.
KFPS05067-E E
Unable to start server due to dictionary server is inactive
- Front-end server or back-end server cannot be started because the dictionary server is inactive.
- S: Terminates processing.
- Action
- If the dictionary server can be used, start the dictionary server and re-execute.
KFPS05068-E S
Unable to stop aa....aa normally due to existence of half status unit
- aa....aa cannot be terminated normally, because a unit has been shut down.
- aa....aa: Termination type:
- HiRDB: System
- unit: Unit
- server: Server
- S: Resumes processing.
- Action
- To terminate, enter the pdstop -f command.
KFPS05069-W S
Unable to stop unit due to error occurred while terminating
- A unit cannot be terminated because an error occurred during termination processing.
Or, the unit has already terminated. - S: Resumes processing.
- Action
- If a KFPS05222-E message was output immediately before, take action as indicated in that message. If the pdstop -f command was used, the unit may already be stopped, so check the message that was output immediately before.
- If other than the above, check the unit that cannot be terminated from the message immediately before, and stop the unit using the pdstop -f or pdstop -z command.
- If it cannot be terminated forcibly, contact the customer support center.
KFPS05070-E S
Unable to stop unit normally due to error occurred while terminating
- A unit cannot be terminated normally, because an error occurred during termination processing.
- S: Resumes processing.
- Action
- Terminate the unit forcibly with the pdstop -f command. If it cannot be terminated forcibly, contact the customer support center.
KFPS05071-E S
Unable to stop server due to error occurred while terminating
- A server cannot be terminated normally, because an error occurred during termination processing. Or, the server is already stopped.
- S: Resumes processing.
- Action
- Terminate the server forcibly with the pdstop -f command. If it cannot be terminated forcibly, contact the customer support center.
- If a stop command is issued for a server that has already stopped, this message may be output. In this case, ignore this message.
- If a message indicating the reason that the server to be stopped could not be stopped was output to the event log (in UNIX, syslogfile) of the unit on which the server is running, refer to that message.
KFPS05072-W E+L
HiRDB system termination process (mode=aa....aa) execution exceeds bb minutes
- The shutdown processing of HiRDB has not terminated after bb minutes.
- aa....aa: Termination mode
- "PLAN": Planned termination
- "NORMAL": Log application site termination
- bb: Elapsed time (in minutes)
- S: Terminates the pdstop command, and continues termination processing.
- Action
- Take one of the following actions:
- Take no action if the planned shutdown process is to be held until the current utility or transaction terminates.
- Use the pdcancel command to cancel the current utility or transaction if the planned shutdown process is to proceed by cancelling the current utility or transaction. When the utility or transaction is cancelled, HiRDB proceeds with the planned shutdown process.
- (In UNIX:) If the pdcancel command cannot cancel the transaction, remove the relevant process using the OS's kill command with the -6 option specified, terminate the unit forcibly, save the data under $PDDIR/spool, and contact the customer support center.
- (In Windows:) If the pdcancel command cannot cancel the transaction, remove the relevant process using the pdkill command, terminate the unit forcibly, save the data under %PDDIR%\spool, and contact the customer support center.
- If this message was output during termination of a log application site, the termination processing probably caused the error. Use the pdstop -f command to terminate HiRDB forcibly, investigate the cause of the error by reviewing messages output before this message, and eliminate the cause of the error. For the primary causes of errors and recovery procedures, see the section on operations when an error occurs with the log-only synchronous method in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. After removing the cause of the error, perform preparation for log application, and restart the log application.
KFPS05073-E E
Environmental variable aa....aa nothing
- Environment variable aa....aa has not been set up.
- aa....aa: Environment variable
- S: Continues or terminates processing, depending on how the HiRDB environment variables have been set up.
- Action
- Check whether or not all environment variables required by HiRDB have been set up. Set up any needed environment variables and re-execute the command.
KFPS05074-E S
Unable to stop normally, use pdstop command with "-f" option
- The system cannot be terminated normally because an error occurred during termination processing.
- S: Terminates processing.
- O: If a process is engaged in UAP or utility execution, re-execute the pdstop command after the process terminates. In other cases, terminate the system forcibly with the pdstop -f command.
- Action
- If the system cannot be terminated, contact the customer support center.
KFPS05075-E E
Unable to execute command, command=aa....aa, return code=bb....bb, errno=cc....cc
- A shell command to be executed within a command failed.
- aa....aa: Command to be executed
- bb....bb: Command's return code
- cc....cc: Error number
- S: Terminates processing.
- Action
- Eliminate the cause of the command failure and re-execute the command, if necessary. If this error message is output repeatedly, contact the customer support center.
KFPS05076-E L
Unable to start this unit with "-i" option
- A utility special unit could not be started with the pdstart -i command.
For HiRDB/Parallel Servers, the -i option cannot be specified when starting at the unit level. - S: Terminates processing.
- Action
- Start HiRDB/Single Servers using the pdstart command. Alternatively, specify the -r or dbdestroy option with the pdstart command to activate HiRDB/Single Servers.
- When reinitializing using a HiRDB/Parallel Server, stop the system, and then start the system using the pdstart -i command. To start a unit, either specify the pdstart -x option alone, specify it with the -r option (pdstart -x -r), or specify it with the -dbdestroy option (pdstart -x -dbdestroy).
KFPS05077-E E
Unable to execute remote shell command, hostname=aa....aa
- The command cannot be executed for a remote host (in UNIX, remote shell).
- aa....aa: Remote host name (in UNIX, host name)
- S: Terminates processing.
- Action
- Take one of the following actions:
- In UNIX
Check if the remote shell execution privilege has been granted for the corresponding remote host and re-execute, if necessary.
- In Windows
Determine whether the same user ID has privilege to log on to the remote host from the local host, and, if necessary, re-execute. If using HiRDB/Parallel Server or if using HiRDB/Single Server with a system switchover facility, a connection with the remote shell is required. Check if the settings are still valid. For details, see the section on OS environment file settings in the HiRDB Version 9 Installation and Design Guide.
KFPS05078-I L
Unable to recognize HiRDB system initialization completion
- The pdstart command could not confirm completion of system initialization processing.
- S: Continues processing.
- Action
- Database Initialization Utility not running:
- Check whether a KFPS05201-Q message has been output. If it has been output, the system is waiting for the input of the pdinit command, in which case the pdinit command should be executed. System initialization processing is resumed after the processing of the utility has terminated. After a while, enter the pdls command to check the system status. The pdls command can also be used to determine whether or not the system is waiting for the input of the pdinit command.
- A HiRDB version upgrade command not running:
- Check whether a KFPS05203-Q message has been output. If it has been output, the system is waiting for the input of the pdvrup command, in which case the pdvrup command should be executed. System initialization processing is resumed after the processing of the pdvrup command has terminated. After a while, enter the pdls command to check the system status.
- When there is no request for the input of an HiRDB version upgrading command in the Database Initialization Utility:
- Because the server startup is taking time, wait a while and enter the pdls command to check the system status.
- If the system initialization processing has not terminated, check the message for other causes of the problem. If the cause of the problem cannot be determined, contact the customer support center.
- The pdstart command is failing to terminate normally:
- Specify the pdstart command completion wait time in the pd_system_complete_wait_time operand. If the completion wait time is increased, the pdstart command terminates normally.
- When the system switchover facility is used and the standby system is activated:
The standby system unit may be waiting for the running unit to initialize because the running system unit has not yet initialized. Use the pdls command and the HA monitor or Hitachi HA Toolkit Extension commands to check the status of the running system unit. If the running system unit was not initialized, eliminate the cause of the initialization error and reinitialize the running system unit.
- When the system switchover facility is used and the running system is activated:
The system may be waiting for activation of the running system unit or it may be activated as the standby system unit. Check the system status using the pdls command and the HA monitor or the Hitachi HA Toolkit Extension commands. If it is not activated as the running system unit, activate it as the running system unit using the HA monitor (Hitachi HA Toolkit Extension) commands or cluster software.
KFPS05079-E E
Dictionary not initialized, unable to start server
- A dictionary has not been initialized by the pdinit command, but an attempt was made to start the server with the pdstart command.
- S: Terminates processing.
- Action
- Initialize the dictionary and re-execute, if necessary.
KFPS05080-Q S
Uap name=aa....aa, uap start time=bb....bb, server process id=cc....cc,cancel process? (y/n)
- If a UAP name is specified in the pdcancel command and the command is executed, this message outputs the UAP name, the UAP start time, and the server process ID, and then awaits user response to determine whether to cancel the process.
If the -d option is specified in the pdcancel command and the command is executed, this message outputs the server process ID, and then awaits user response to determine whether to cancel the process. - aa....aa: UAP name (if the pdcancel command was executed with the -d option specified, ******** is displayed)
- bb....bb: UAP startup time (if the pdcancel command was executed with the -d option specified, 999999 is displayed)
- cc....cc: ID of the process subject to cancellation processing
- S: Resumes processing.
- O: To continue cancellation processing, enter y; to cancel the processing, enter n.
KFPS05081-Q S
Cancel all server process? (y/n)
- Asks the operator whether or not all single server processes on a HiRDB/Single Server are to be canceled.
- S: Resumes processing.
- Action
- To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).
KFPS05081-Q S
Hostname=aa....aa, cancel all front end server processes? (y/n)
- Asks the operator whether or not all front-end server processes being executed on the specified host are to be canceled.
- aa....aa: Host name
- S: Resumes processing.
- Action
- To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).
KFPS05082-Q S
Utility server name=aa....aa, process id=bb....bb, cancel process? (y/n)
- When a utility is cancelled by the pdcancel command, the system displays the utility server name and process ID and asks the operator whether or not cancellation processing is to be continued.
- aa....aa: Utility server name
- bb....bb: Utility server process ID
- S: Resumes processing.
- Action
- To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).
KFPS05083-E E
aa....aa terminated, due to server process abnormal end
- A remote server process terminated abnormally during execution of a utility or operation command.
- aa....aa: Command name
- S: Terminates processing.
- Action
- If a server process was terminated by pdstop or pdcancel, contact the customer support center.
KFPS05084-E E
Invalid option argument specified, option argument=aa....aa
- An invalid option argument was specified in a command.
- aa....aa: Option argument
- S: Terminates processing.
- Action
- Correct the option argument and re-execute, if necessary.
KFPS05087-E E
Unable to execute aa....aa command because bb....bb
- The aa.....aa command could not be executed because the system did not have a system switchover configuration.
- aa....aa: Command name
- pdls -d ha
- pdstop -f -q (HiRDB/Single Server)
- pdstop -z -q (HiRDB/Parallel Server)
- bb....bb: Reasons the command cannot be executed:
- pd_ha is not 'use': This system does not have a system switchover configuration.
- pd_ha is not 'use' or pd_ha_unit is 'nouse': This system or unit does not have a system switchover configuration.
- S: Terminates processing.
- Action
- Check that use is specified in the pd_ha operand. Or, check that nouse is specified in the pd_ha_unit operand.
KFPS05090-E L
Unable to execute pdndls command
- The pdndls command cannot be executed.
- S: Terminates processing.
- O: Re-execute the command after creating a multi-node-configuration definition file.
KFPS05091-E L
Incorrect HiRDB ID specified
- Undefined HiRDB identifier was specified in a command parameter.
- S: Terminates processing.
- O: Check the multi-node-configuration definition file or option definitions for the correct HiRDB.
KFPS05092-E E
Error occurred
- Error was detected during execution of pdndls command.
- S: Resumes processing.
- O: Check the detail information that is displayed after this message, then take appropriate action.
KFPS05093-E E
Error found while analyzing pdmnd definition file
- The pdndls command cannot be executed.
- S: Terminates processing.
- O: Check the contents of the multi-node-configuration definition file.
KFPS05094-E E
System error, func= aa....aa, code= bb....bb, detail=cc....cc, call func=dd....dd, line=ee....ee
- An error was detected in the internal processing of a HiRDB-embedded support function.
- aa....aa: Name of the function in which the error occurred
- bb....bb: Error code
- cc....cc: Error detail code
- dd....dd: Call-originating file name (internal information)
- ee....ee: Call-originating line number (internal information)
- S: Terminates processing.
- O: Take one of the following actions:
- When HiRDB-embedded support function is not used
This command can be executed only when a HiRDB-embedded support function is used.
- When HiRDB-embedded support function is used
Referencing the operation model setup file failed. Check the status of this file. Or, check that the PDEMBDIR environment variable has been set up correctly.
- Action
- See 4. Error Detail Codes and take appropriate action. If the cause is unknown, save the contents of this message, the files under %PDDIR%\spool, and a backup of the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05095-E E
Unable to execute command, user=aa....aa
- The command that user aa....aa entered could not be executed.
- aa....aa: Log in user name of the user entering the command
- S: Terminates processing.
- O:
- Re-evaluate the log in the user environment of the user who entered the command. For command details or the error cause, see the KFPS05043-E or KFPS05077-E message output immediately before this message.
KFPS05096-I S+L
Usage: pdpfresh [-s server_name] [-{f | c} ]
- The option specification format of the pdpfresh command is invalid.
- S: Terminates processing.
- Action
- Correct the option specification, and then re-execute.
KFPS05097-E S
Unable to stop normally during Online DB Reorganization
- An attempt to terminate normally failed because updatable online reorganization is not complete.
- S: Terminates processing.
- Action
- Correct the option specification, and then re-execute.
- O:
- Execute the pdls -d org command to check if discrepancies application processing of online reorganization is complete. If it is complete, re-execute the pdstop command to terminate normally. If the HiRDB system is terminated before discrepancies application processing of online reorganization is complete, execute either a planned stop (pdstop -P) or forced termination (pdstop -f).
KFPS05098-I S
Usage: pdprgrenew [-b] HiRDB_home_directory
- The specification format of the pdprgrenew command option is invalid.
- S: Terminates processing.
- Action
- Correct the option specification and re-execute.
KFPS05099-I S
Usage: pdprgcopy HiRDB_home_directory
- The specification format of the pdprgcopy command option is invalid.
- S: Terminates processing.
- Action
- Correct the option specification and re-execute.
KFPS05100-E L
Error occurred in HiRDB unit starting process,reason code=aa
- The unit cannot be started due to an error during unit startup processing.
- aa: Reason code:
- 10: Definition analysis error
- 20: Communication error
- 30: Area shortage
- 40: Shared memory shortage
- S: Terminates abnormally.
- Action
- Take an appropriate action according to the reason code. If the error cannot be corrected, contact the customer support center.
Reason code | Explanation | Action |
---|
10 | Definition analysis error. | See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error. |
20 | A communication error occurred. | See the message output immediately before, check the cause of the communication error, and eliminate it. |
30 | An area (memory) shortage occurred. | Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute. |
40 | A common memory shortage occurred. | Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center. |
KFPS05101-E L
HiRDB unit definition parameter analysis error
- An error occurred while analyzing the HiRDB unit definition parameters.
- S: Terminates abnormally.
- Action
- Contact the customer support center.
KFPS05102-E L
Insufficient memory on STATIC_SHMPOOL, size=aa....aa
- A shared memory allocation error occurred.
- aa....aa: Size (in bytes) of the area that was to be allocated
- S: Terminates processing.
- Action
- Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05110-I S+L
HiRDB unit aaaa initialization process complete
- Initialization of HiRDB unit aaaa has been completed.
- aaaa: Unit identifier
- S: Resumes processing.
KFPS05111-E L
Error occurred in HiRDB unit aaaa termination process. mode=bb....bb, reason code=cc....cc
- Error occurred during termination processing at HiRDB unit aaaa.
If the termination mode is PLAN, or if Real Time SAN Replication is used for a log application site that is terminating with a termination mode of NORMAL, all units other than unit aaaa are terminated forcibly. - aaaa: Unit identifier
- bb....bb: Termination mode:
- NORMAL: Normal termination
- PLAN: Planned termination
- FORCE: Forced termination
- cc....cc: Reason code:
- COMMUNICATION: System manager communication error
- INTERNAL ERROR: Internal processing error
- S: Terminates abnormally.
- Action
- Check the messages that were output before this message, correct the error, then restart the system.
- (Planned termination or normal termination of a log application site when Real Time SAN Replication is used)
- Check that all units have terminated, then restart the system.
- If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit or by logging directly into the unit and entering the pdstop -z command, and then restart the system.
- The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:
- KFPS01821-E message
- System manager unit: KFPS01850-I message (termination mode = FORCE)
- For a unit that is not the system manager: KFPS01841-I message (termination mode = FORCE)
- If the cause is unknown, save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05112-I L
Some servers did not startup,please check
- Some HiRDB servers may not be active (although they are on startup completed status as a HiRDB unit).
- S: Resumes processing.
- Action
- Check the server status with the pdls command. If a server is on HELD status, the database must be recovered. If a server is on STOP status, eliminate the cause of the startup error and restart the server.
KFPS05113-E L
Error occurred in HiRDB unit aaaa starting process, reason code=bb....bb
- An error occurred while starting Unit aaaa.
If the error code is 7, the unit cannot be restarted because planned termination processing is underway. The system forcibly terminates all units.
If the error code is 11, the unit cannot be restarted because there are units in termination processing on the log application site. All units are terminated forcibly.
If the error code is 12, the unit cannot be restarted because there are units performing database inheritance. All units are terminated forcibly. - aaaa: Unit identifier
- bb....bb: Error code:
- S: If the error code is 1-6, 8, 9, or 10, the unit is terminated abnormally.
- If the error code is 7, 11, or 12, all units are terminated forcibly.
- Action
- The following shows the error codes and their appropriate actions:
Error code | Error contents | Action |
---|
1 | Internal processing error | Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center. |
2 | Communication error | Check whether the system manager unit is stopped. If the system manager unit is stopped, check the cause of the system manager unit being stopped, and eliminate the error. Then, restart HiRDB. If the error occurred even when the system manager unit was active, there may be a network failure. See 4.1 Detail codes for RPC-related errors to investigate the error. If the cause is unknown, save the files under %PDDIR%\spool on the system manager unit and the unit that output the abort code, save the event log (in UNIX, syslogfile), and contact the customer support center. |
3 | Definition parameter error | A definition parameter specified for the unit may contradict the system manager unit definition or another unit definition. Check the server configuration and unit identifier for errors, correct any errors, then re-execute. For details, see the KFPS05215-W message. |
4 | Memory shortage | Execute after other processes terminate, or revise the size of the swap area, then re-execute. |
5 | Version mismatch | Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center. |
6 | Internal processing error |
7 | Status mismatch error with another unit | A unit in planned termination was detected. Check that all units have terminated, then restart the system. If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit, or by logging directly onto the unit and entering the pdstop -z command, and then restart the system. The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:
- KFPS01821-E message
- System manager unit: KFPS01850-I message (termination-mode=FORCE)
- For a unit that is not the system manager: KFPS01841-I message (termination-mode=FORCE)
|
8 | An activation waiting timeout occurred on a server to be used with standby-less system switchover (effects distributed) | Check the activation status of the server indicated in the KFPS05251-W message that was output immediately before using the HA monitor or the Hitachi HA Toolkit Extension, and then re-activate the units that abnormally terminated. |
9 | The contents of the system definition do not match between units | Check the KFPS05247-E message that was output immediately before, make the value of the pd_rpl_hdepath operand the same for each unit, and restart the units that abnormally terminated. |
10 | The activation mode does not match between units | Refer to the KFPS05247-E message output immediately before this message, read each unit's activation options, and then re-activate the abnormally terminated units. |
11 | Status mismatch error with another unit (during log application site termination processing) | A unit on the log application site in termination processing was detected. Confirm that all units have terminated, and then restart HiRDB. If there are still units that have not terminated, execute the pdstop -f command from the system manager unit, wait until they have terminated, and then restart HiRDB. The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If a KFPS01821-E message is output (for HiRDB/Parallel Server, system manager unit, a KFPS01850-I message (termination-mode=FORCE); for a unit other than the system manager unit, a KFPS01841-I message (termination-mode=FORCE)), the unit is terminated. |
12 | Status mismatch error with another unit (during database inheritance) | A unit performing database inheritance was detected. Confirm that all units have terminated, and then restart HiRDB. If there are still units that have not terminated, execute the pdstop -f command from the system manager unit, wait until they have terminated, and then restart HiRDB. The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If a KFPS01821-E message is output (for HiRDB/Parallel Server, system manager unit, a KFPS01850-I message (termination-mode=FORCE); for a unit other than the system manager unit, a KFPS01841-I message (termination-mode=FORCE)), the unit is terminated. |
KFPS05114-E L
SDS server did not startup
- The activation of the single server cannot be confirmed.
- S: Terminates abnormally.
- Action
- Contact the customer support center.
KFPS05120-W L
Waiting for UAP and/or utility disconnect in HiRDB unit aaaa, current connect user count = bbb
- The system is waiting for termination of a UAP or utility.
- aaaa: Unit identifier of the unit waiting for termination
- bbb: Number of connected users who are waiting for the termination of the UAP or utility
- S:
- Resumes processing while not allowing new users to connect to HiRDB. Holds the termination processing of HiRDB until the processing of the UAP or utility ends (15 minutes). Starts HiRDB termination processing upon termination of the UAP or utility.
- Outputs detained information about the users connected to HiRDB to a connection user information file (%PDDIR%\spool\cnctusrinf). In addition, outputs the execution results of the following commands to a connection user detail file (cnctusrdtl under %PDDIR%\spool):
- pdls -d act
- pdls -d prc
- pdls -d trn
- For a HiRDB/Parallel Server, these files are output to the server machine in which the System Manager is located.
- Alternatively, if a currently running UAP or utility stopped near the time this message is output, this information may not be included in the detail information for the servers connected to the HiRDB system.
- O: Referring to the information output to the connection user information file (%PDDIR%\spool\cnctusrinf), determine which users are connected, and take corrective action. If you are still unsure which users are connected, refer to the connected user detail file (%PDDIR%\spool\cnctusrdtl) to determine this information, and take corrective action. For details on corrective actions, see the HiRDB Version 9 System Operation Guide.
- Following is an example of output from the connection user information file:
- Output example:
UNIT ID : M350(173420)
UID PID GID SVID TIME PROGRAM
C-GRP C-PID C-IP
334 22118 300 fes1 173330 uap00
WS 22205 172.17.32.37 |
- Explanation:
- UNIT ID:
- Displays the unit identifier and the time of creation of the cnctusrinf file (hhmmss).
- UID:
- Displays the user IDs of the users who are connected to HiRDB.
- PID:
- Displays the process IDs of the users who are connected to HiRDB.
- GID:
- Displays the group IDs of the users who are connected to HiRDB.
- SVID:
- Displays the server name of the server to which users are connected.
- A space may be displayed after a HiRDB server process is started.
- TIME:
- Displays the time (hhmmss) when HiRDB accepted a service request. Displays the number 999999 for the server to which users are not connected.
- PROGRAM:
- Displays the value specified in the PDCLTAPNAME operand of the client environment definition. The default for the PDCLTAPNAME operand is Unknown.
- For details on the PDCLTAPNAME operand, see the HiRDB Version 9 UAP Development Guide.
- Displays ****** for a utility.
- The symbol ****** may be displayed after a HiRDB server process is started.
- C-GRP:
- Displays the types (client group types) of users who are connected to HiRDB.
- If a client group connection frame guarantee facility is used and a user-defined client group is defined, displays the name of the user-defined client group.
Displayed character string | User type |
---|
XA | Users who are connected to HiRDB using the X/Open XA interface |
PC | Users who are connected to HiRDB from a PC client |
WS | Users who are connected to HiRDB from a WS client |
MF | Users who are connected to HiRDB from a mainframe-based client (including a VOS3 client) |
- C-PID:
- Displays the process ID of the client.
- C-IP:
- Displays the IP address of the client.
- Note
- C-GRP, C-PID, or C-IP is not displayed in the following cases:
- The UAP or utility is not executed on the client side (the UAP or utility is executed on the HiRDB system).
- The version of the client that linked the UAP is earlier than HiRDB Version 4.0 04-00.
KFPS05121-E L
Unable to stop normally, UAP and/or utility remaining in HiRDB unit aaaa, current connect user count = bbb
- The HiRDB system cannot be stopped because a UAP or utility is being executed.
- aaaa: Unit identifier of unit executing the UAP or utility
- bbb: Number of connected users who are executing the UAP or utility
- S: Terminates termination processing.
- O: Re-execute the pdstop command after UAP or utility processing ends. Use the pdls -d trn or pdls -d prc command to determine the users who are executing the UAP or utility.
KFPS05123-W L
Using resource for "aa....aa" operand reached bb....bb% [, cc....cc]
- The resources for the system definition operand "aa....aa" have reached a warning value bb....bb.
- aa....aa: Name of the system definition operand
- bb....bb: Warning value (in percentage)
- cc....cc: Additional information
- S: Resumes processing.
- Action
- The additional information that is output and the corrective action to be taken vary with the name of the operand. Take action by referring to the following table. Some operand names do not output additional information.
System definition operand name aa....aa | Additional information cc....cc | Action |
---|
pd_max_users: Maximum number of concurrent connections | dd....dd/ee....ee, server = ff....ff
- dd....dd: Number of connected users
- ee....ee: Defined value
- ff....ff: Front-end server name or single server name. The symbol '**....**' is output if a warning value is reached during the execution of one of the following utilities:
- pdload
- pdrorg
- pddbst
- pdgetcst
- pdmod
| Re-evaluate whether the value for pd_max_users is appropriate. If the value is not appropriate, change the value of the operand. |
pd_max_access_tables: Maximum value for the sum of the number of tables and the number of sequence generators that one user can access concurrently in one transaction | dd....dd/ee....ee, server=ff....ff
- dd....dd: Usage count
- ee....ee: Definition count
- ff....ff: Server name
- ff....ff: Server name
| Re-evaluate whether the value for pd_max_access_tables is appropriate. If the value is not appropriate, change the value of the operand. |
pd_max_rdarea_no: Maximum number of RDAREAs pd_max_file_no: Maximum number of HiRDB files comprising an RDAREA | dd....dd/ee....ee, server = ff....ff
- dd....dd: Number of RDAREAs used
- ee....ee: Number of definitions
- ff....ff: Server name
| Re-evaluate whether the value for pd_max_rdarea_no or pd_max_file_no is appropriate. If the value is not appropriate, change the value of the operand. |
pdwork: Work table HiRDB file system area | dd....dd=ee....ee / ff....ff, file system = gg....gg (hh....hh)
- dd....dd: Detail category#
capacity file count expand count
- ee....ee: Size of area used
- ff....ff: Assigned amount
- gg....gg: HiRDB file system area name
- hh....hh: Server name
| Re-evaluate whether the option specified by the pdfmkfs command is appropriate for the applicable work table HiRDB file system area. If the option is not appropriate, re-estimate the value of the operand, and then initialize the work table HiRDB file system area using the pdfmkfs command. Terminate the HiRDB system normally before executing the pdfmkfs command. |
client-group connect users: Number of users in the free utilization frame at the time of client group specification | dd....dd/ee....ee, server = ff....ff
- dd....dd: Number of users connected within the free utilization frame
- ee....ee: Number of definitions
- ff....ff: Front-end server or back-end server. A symbol **....** is output if a warning value is reached during the execution of any of the following utilities:
pdload
pdrorg
pddbst
pdgetcst
pdmod
| Check whether the value of the minimum connection guarantee number for each client group, specified in the pdcltgrp operand, is appropriate.
- When executing a large number of utilities or UAPs that do not belong to a client group, reduce the minimum connection guarantee number for each client group specified in the pdcltgrp operand, and increase the free utilization frame.
- If the minimum connection guarantee number assigned to a client group is sufficient, reduce the minimum connection guarantee number for that client group specified in the pdcltgrp operand, and increase the free utilization frame.
|
pd_max_list_users: Maximum number of users who can create lists | dd....dd/ee....ee, server = ff....ff
- dd....dd: Number used
- ee....ee: Number defined
- ff....ff: Server name
| Check if the value specified in pd_max_list_users is appropriate. If not, re-estimate the appropriate value and specify it. |
pd_max_list_count: Maximum number of lists one user can create | dd....dd/ee....ee, server = ff....ff
- dd....dd: Number used
- ee....ee: Number defined
- ff....ff: Server name
| Check if the value specified in pd_max_list_count is appropriate. If not, re-estimate the appropriate value and specify it. Before modifying system definitions, terminate HiRDB normally. |
pd_aud_max_generation_num: Maximum number of audit trail tables | dd....dd/ee....ee/unit=ffff
- dd....dd: Number of audit trail tables that cannot become the swap destination
- ee....ee: Operand value
- ffff: Unit identifier
| - Request that the auditor load the data in the audit trail files that are waiting for data loading.
- Re-evaluate whether the value of the pd_aud_max_generation_num operand is appropriate. If the value is not appropriate, change the value of the operand.
|
- #: If the detail category is capacity, the size of an area used or allocated is indicated in megabytes.
KFPS05124-W L
Number of connect users exceeded max users, server=aa....aa
- The number of connections to HiRDB exceeded the maximum number of concurrent connections (value of the pd_max_users operand).
- aa....aa: Name of the server on which the number of concurrently connected users was detected
- S: Resumes processing.
- O: Re-execute the command after other users have terminated.
- P: Re-execute the command after other users have terminated.
- Action
- Check whether the value specified in the pd_max_users operand is appropriate. If not, re-estimate the specification value and change the value.
KFPS05125-E L
Unable to execute receiving RPC service, send unit=aaaa, reason code =bb....bb
- Request from unit aaaa cannot be executed.
- aaaa: Unit ID of the unit that sent the request
- bb....bb: Reason code
- STOPPED NRFUNIT: A message was received from a recovery-unnecessary FES unit that has stopped.
- S: The SQL statement executed in response to the recovery-unnecessary FES that sent the request terminates with an error. This transaction will be invalidated.
- Action
- After checking the status of unit aaaa, recover from the error according to the reason code. If the reason code is STOPPED NRFUNIT, use the command pdls -d svr to check whether the status information of unit aaaa is STOP(A).
- If the status information is STOP(A), there might be a network error between unit aaaa and the system manager. In that case, use the pdstop -z command to terminate unit aaaa, and then take action to investigate the cause of the network error. After taking corrective action, restart unit aaaa.
- If the status information is something other than STOP(A), check other messages to eliminate to cause of the error.
KFPS05130-E L
Unable to execute command. except pdvrup
- No commands can be executed while pdvrup is executing.
- S: Terminates processing.
- Action
- Re-execute the command after system startup is completed.
KFPS05131-E L
Unable to execute aa....aa command. reason code=bbbb
- Execution of command aa....aa failed.
- aa....aa: Name of the command being executed
- bbbb: Detail code (see 4.2 Detail codes for system-related errors)
- S: Terminates processing.
- O: Correct the cause of the error and re-execute the command as necessary. If this error message is output repeatedly, contact the customer support center.
KFPS05140-I E+L
Data replication started. unit=aaaa
- HiRDB Datareplicator linkage has started.
- aaaa: Unit identifier
- S: Resumes processing.
KFPS05141-I E+L
Data replication stopped. unit=aaaa
- HiRDB Datareplicator has stopped.
- aaaa: Unit identifier
- S: Resumes processing.
KFPS05142-W E+L
Unable to stop data replication, server=aa....aa, reason=bb....bb
- Data linkage with HiRDB Datareplicator could not be stopped.
- aa....aa: Server name
- bb....bb: Reason code
- S: Continues processing.
- Action
- Take appropriate action according to the reason code.
Reason code | Cause | Action |
---|
FILE LOCK ERROR | A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator. | HiRDB Datareplicator has exclusive ownership of the data linkage file. Investigate the cause, and then take appropriate action. |
FILE OPEN ERROR | A data linkage file used by HiRDB Datareplicator could not be opened. | Either the data linkage file has been deleted or it could not be opened due to a disk error. Synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB. |
KFPS05160-I L+S
HiRDB unit aaaa initialization process complete on standby site
- Unit start processing on the log application site has finished.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05162-E L
Error occurred in HiRDB unit aaaa database take over process, reason code=bb....bb
- An error occurred during database inheritance. All units are terminated forcibly.
- aaaa: Unit identifier
- bb....bb: Error code
- COMMUNICATION: Error in communication with another unit
- INTERNAL ERROR: Internal processing error
- S: Terminates abnormally.
- Action
- Check the messages output before this message, eliminate the error, and start the log application site HiRDB. Ensure that all units have terminated, and then restart HiRDB.
- If there are still units that have not terminated, either execute the pdstop -f command from the system manager unit or execute the pdstop -z command from the units that have not terminated, wait until they have terminated, and then restart the log application site HiRDB.
- The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If any of the following messages is output, the unit is terminated:
- KFPS01821-E message
- System manager unit: KFPS01850-I (termination-mode=FORCE)
- Unit other than the system manager unit: KFPS01841-I (termination-mode=FORCE)
- If the cause cannot be determined, collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05170-E L
Server aa....aa recovery failed, abnormally terminated unit=bbbb
- Server recovery processing failed due to abnormal termination of the indicated unit.
- aa....aa: Name of the server whose recovery failed
- bbbb: Identifier of the unit that terminated abnormally
- S: Resumes processing.
- Action
- Collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05171-E L
Process recovery failed,abnormally terminated process=aa....aa
- Recovery processing failed due to abnormal termination of the indicated process.
- aa....aa: ID of the process that terminated abnormally
- S: Terminates abnormally.
- Action
- For the abnormally terminated process ID, 0 might be output.
- If other than 0 is output, use the pdls -d prc command to determine whether the relevant process is still running. If it is not running, there is no problem. If it is running, collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05172-E L
Unable to inform unit aaaa that process is abnormal, abnormal process=bb....bb
- Indicated process terminated abnormally, but the indicated unit cannot be recovered.
- aaaa: Unit identifier of the unit for which recovery processing could not be executed
- bb....bb: ID of the process that terminated abnormally
- S: Resumes processing.
- Action
- For the abnormally terminated process ID, 0 might be output.
- Check the unit status because no error has occurred if the unit output in the message has not been started.
- If the unit has been started, contact the customer support center.
KFPS05173-E L
Recovery failure because server aa....aa abnormally terminated, utility=bb....bb cc....cc
- Unit recovery processing failed with abnormal termination of the server.
- aa....aa: Name of the server that abnormally terminated (maximum 8 characters)
- bb....bb: Process ID (maximum 10 characters) of the utility that failed in recovery that is related to the server that abnormally terminated
- cc....cc: Internal service name used by HiRDB (maximum 16 characters)
- S: Continues processing.
- Action
- Use the pdls -d prc -a command to check whether the process ID output by the message was retained. If it was not retained, there is no problem. If it was retained, use the pdls -d trn -a command to check the name of the executed utility, and check whether the execution time of the utility is long. For actions to take if the execution time is long, see the HiRDB Version 9 System Operation Guide.
KFPS05180-E L
System call/function error, call=aa....aa, code=bbb
- A system call or function error occurred.
- aa....aa: Name of the system call or function resulting in the error
- bbb: Error code
- S: If this message is output during system startup, when pdstop -x is executed, or when pdstop -u is executed, the command is terminated abnormally. If this message is issued as an extension of the pdstop command, the system terminates the command's processing.
- Action
- If the system call or function cannot be identified by the displayed error code, contact the customer support center.
Name of system call or function resulting in the error | Error code | Cause | Action |
---|
System | -1 | Total number of processes being executed exceeded the limit applicable to the system (in UNIX). | Increase the nproc parameter value of the OS. |
Maximum number of processes that can be used by a user was exceeded (in UNIX). | Increase the maxuprc parameter value of the OS. |
Physical memory shortage occurred. | Check that at least the necessary amount of memory has been allocated. If sufficient memory has been allocated, release unneeded resources. |
Other | Other | -- | Contact the customer support center. |
- --: Not applicable
KFPS05190-E L
Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc
- An error occurred during communication from host aa....aa to host bb....bb.
- aa....aa: Host name
- bb....bb: Host name
- ccc: Code being processed (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the system status.
- Action
- If the host defined as the system manager (MGR) is not active, start it and then restart the HiRDB unit.
- If a utility special unit is defined, the bb....bb host may not be active. If the host is not active, no error has occurred. Check whether the bb....bb host was active.
- If this message is output in the following cases, confirm that the host indicated by bb....bb is operating.
A unit on which the standby-less system switchover (effects distributed) facility is being used terminates normally
A server on which the standby-less system switchover (effects distributed) facility is being used terminates normally
A unit on which the standby-less system switchover (effects distributed) facility is being used terminates forcibly
If the host indicated by bb....bb is not operating, this message can be ignored. If the host indicated by bb....bb is operating, check the server standby status of the unit indicated by bb....bb. If a running server that terminated under the above conditions is the unit indicated by bb....bb and is not in standby status, this message can be ignored. Otherwise, contact the customer support center.
- Otherwise, contact the customer support center.
KFPS05191-E L
Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc, reason code=dddd
- An error occurred during communication from host aa....aa to host bb....bb.
- aa....aa: Host name
- bb....bb: Host name
- ccc: Code being processed (HiRDB internal code)
- dddd: Reason code (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the system status.
- Action
- If the host defined as the system manager (MGR) is not active, start it and then restart the HiRDB unit.
- If a network error has occurred, eliminate the cause of the error and restart the HiRDB unit.
- Otherwise, contact the customer support center.
KFPS05192-E L
Communication error occurred, from utility to MGR/SDS unit, processing code=aaa
- An error occurred during communication from the unit that executed the utility to either the system manager (MGR) or the unit defined as the single server (SDS).
- aaa: Code being processed (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the system status.
- Action
- Save the files under %PDDIR%\spool on the system manager unit and the unit that executed the utility, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05193-E E+L
Communication error occurred, to host aa....aa, processing code=bbb, reason code=cccc
- An error occurred during communication to host aa....aa.
If the host name is ********, the error occurred during communication to either the system manager or the host defined as the single server. - aa....aa: Host name
- bbb: Code being processed (HiRDB internal code)
- cc: Reason code (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the system status.
- Action
- Check whether a unit of host aa....aa is inactive. If this is the case, start the corresponding unit. If the corresponding unit is not running in reduced mode, ignore this message.
- If this message is output even though the corresponding unit is running, a communication error has occurred. Take corrective action according to 4.1 Detail codes for RPC-related errors.
- In cases other than the above, contact the customer support center.
KFPS05194-E L
Communication error occurred, to node MGR, processing code=aaa
- Communication in a HiRDB unit failed (the displayed processing code is an HiRDB internal code).
- aaa: Code being processed
- S: Terminates abnormally.
- Action
- Save the files under %PDDIR%\spool on the system manager unit and this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05195-E L
Communication error occurred, to node MGR,processing code=aaa, reason code=bbbb
- An error occurred during communication to the server machine (MGR) at the HiRDB unit (the displayed reason code and processing code are HiRDB internal codes).
- aaa: Code being processed
- bbbb: Reason code
- S: Terminates abnormally.
- Action
- Save the files under %PDDIR%\spool on the system manager unit and this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05200-E L
Error occurred in HiRDB system starting process, reason code=aa
- HiRDB cannot be started due to an error during HiRDB startup processing.
- aa: Reason code:
- 10: Definition analysis error
- 20: Communication error
- 30: Memory shortage
- 40: Shared memory shortage
- S: Terminates abnormally.
- Action
- Take action appropriate to the reason code. If the error cannot be resolved, save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
Reason code | Explanation | Action |
---|
10 | Definition analysis error. | See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error. |
20 | A communication error occurred. | See the message output immediately before, check the cause of the communication error, and eliminate it. |
30 | An area (memory) shortage occurred. | Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute. |
40 | A common memory shortage occurred. | Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center. |
KFPS05201-Q S+L
Dictionary not initialized; enter pdinit command
- A dictionary has not been initialized in the HiRDB system. Initialize the dictionary by entering the pdinit command.
- S: Waits until initialization of the dictionary by the pdinit -d command is completed.
- Action
- Enter the pdinit command. When the Windows edition is being used, execute the pdinit command with the Administrator privilege. In this case, root is the executor.
KFPS05202-E L
Insufficient memory on STATIC_SHMPOOL, size=aa....aa
- A shared memory allocation error occurred.
- aa....aa: Size (in bytes) of the area that was to be allocated
- S: Terminates processing.
- Action
- Save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05203-Q S+L
HiRDB version upped: enter pdvrup command
- The system is waiting for the pdvrup command to be entered. Enter the command.
- S: Waits for the pdvrup command to be entered.
- Action
- Enter the pdvrup command.
KFPS05205-E L
Error occurred while starting HiRDB control process, reason code=aa
- Because an error occurred while starting the process server process, the system cannot be started.
- aa: Reason code:
- 10: Definition analysis error
- 20: Communication error
- 30: Memory shortage
- 40: Shared memory shortage
- S: Terminates abnormally.
- Action
- Take action appropriate to the reason code. If the error cannot be resolved, save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
Reason code | Explanation | Action |
---|
10 | Definition analysis error. | See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error. |
20 | A communication error occurred. | The port number specified in the -a option of the pd_alv_port or pdunit operand might be the same as the port number of another definition or program. If they are the same, change the values in the port number settings so that they are unique, and then restart. Otherwise, determine the cause of the communication error and eliminate it by referring to the message that was output immediately before this one. |
30 | An area (memory) shortage occurred. | Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute. |
40 | A common memory shortage occurred. | Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center. |
KFPS05206-E L
Incompatible character code set for HiRDB unit aaaa, character code set=bb....bb, MGR unit character code set=cc....cc
- bb....bb character codes at unit aaaa are incompatible with cc....cc character codes at the MGR unit. Therefore, the HiRDB system cannot be activated.
- aaaa: Unit identifier
- bb....bb: Character codes used at unit aaaa:
- CHINESE: EUC Chinese kanji codes
- CHINESE-GB18030: Chinese GB18030 codes
- LANG-C: One-byte character codes
- SJIS: Shift JIS codes
- UJIS: EUC Japanese kanji codes
- UTF-8: Unicode(UTF-8)
- cc....cc: Character codes used at the MGR unit
- S: Terminates abnormally.
- Action
- Take the following actions:
- In UNIX
To unify the character code classifications, execute the pdsetup -d command, respond y at the prompt, and then specify the correct character code classification again using the pdsetup -c command.
- In Windows
Unify the character code classifications. To unify the character code classifications, execute the pdntenv -c command.
KFPS05207-E L
Unable to start HiRDB system, some units exist whose version are not equal to that of MGR unit
- The HiRDB system cannot be started because some units differ from the unit containing the system manager (MGR) in terms of one or more of the items listed below:
- Version
- Addressing mode (32-bit mode vs. 64-bit mode)
- Load type (whether or not POSIX library version is being used)
- S: Abnormally terminates.
- P:
- Take the following actions:
- In UNIX
Based on message KFPS05209-I, set the same version, addressing mode, and load type for all units, and then start HiRDB.
- In Windows
Based on message KFPS05209-I, set the same version and addressing mode for all units, and then start HiRDB.
KFPS05208-E L
Unable to start HiRDB system, abnormally terminated units exist
- There is a unit that previously terminated abnormally, underwent a planned shutdown, or was terminated forcibly. Therefore, HiRDB cannot be started.
- S: Abnormally terminates.
- Action
- Take the following actions:
- In UNIX
Based on message KFPS05209-I, revert the version, addressing mode, and load type of all units (whether or not a POSIX library is used) to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to revert HiRDB to a previous version and how to upgrade HiRDB to a later version, see the HiRDB Version 9 Installation and Design Guide.
- In Windows
Based on message KFPS05209-I, revert the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to revert HiRDB to a previous version and how to upgrade HiRDB to a later version, see the HiRDB Version 9 Installation and Design Guide.
KFPS05209-I L
HiRDB version information, unit_id=aaaa, bb....bb, cc....cc
- Displays information for HiRDB unit aaaa.
- aaaa: Unit identifier
- bb....bb: HiRDB version information:
- version: HiRDB version
- addressing mode: HiRDB addressing mode:
- 32: 32-bit mode
- 64: 64-bit mode
- load: Displays the HiRDB load type. This information is displayed when using the HP-UX version (32-bit mode), the Solaris version, or the AIX version of HiRDB.
- POSIX: POSIX library version
- NO-POSIX: Non-POSIX library version
- cc....cc: HiRDB version information at the previous termination:
- stop status: Previous HiRDB termination mode:
- A: Planned termination, forced termination, or unit abnormal termination
- N: Normal termination
- previous operation stop version: HiRDB version at the previous termination (if the status file is being initialized, ******** is displayed)
- addressing mode: HiRDB addressing mode at the previous termination:
- 32: 32-bit mode
- 64: 64-bit mode
- load: Displays the load type from the previous time HiRDB terminated. This information is displayed when using the HP-UX version (32-bit mode), the Solaris version, or the AIX version of HiRDB.
- POSIX: POSIX library version
- NO-POSIX: Non-POSIX library version
- S: Terminates abnormally.
- Action
- Take corrective action by referring to message KFPS05207-E or KFPS05208-E that was output prior to this message.
- In UNIX:
- If message KFPS05207-E is output:
Based on message KFPS05207-E, set the version, addressing mode, and load type of all units to be the same, and then start HiRDB.
- If message KFPS05208-E is output:
Based on message KFPS05208-E, return the version, addressing mode, and load type of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.
- In Windows:
- If message KFPS05207-E is output
Based on message KFPS05207-E, set the version and addressing mode of all units to be the same, and then start HiRDB.
- If message KFPS05208-E is output
Based on message KFPS05208-E, return the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.
KFPS05210-I S+L
HiRDB system initialization process complete
- Initialization of the HiRDB system has been completed.
- S: Resumes processing.
KFPS05211-I L
Server aa....aa is ready to connect
- The front-end server (FES) of a HiRDB/Parallel Server was terminated and then was started again. It is now ready to execute connect.
- aa....aa: Server name
- S: Resumes processing.
KFPS05212-E L
HiRDB aa....aa option information, unit_id=bbbb, version=cc....cc, previous operation stop version=dd....dd
- Displays the version information of option program product aa....aa for HiRDB unit bbbb.
- aa....aa: Option program product
- Staticizer Option: HiRDB Staticizer Option
- Advanced High Availability: HiRDB Advanced High Availability
- Non Recover FES: HiRDB Non Recover FES
- Disaster Recovery Light Edition: HiRDB Disaster Recovery Light Edition
- Accelerator: HiRDB Accelerator
- bbbb: Unit identifier
- cc....cc: Additional program product version information:
- The information is displayed in vv-rr format.
- vv: Additional program product version
- rr: Additional program product revision
- If the version information displayed is 00-00, the additional program product is not included.
- dd....dd: Additional program product version information from the previous time the unit terminated:
- The information is displayed in vv-rr format.
- vv: Additional program product version
- rr: Additional program product revision
- If the version is displayed as 00-00, it indicates that the option program product was not embedded.
- S: Terminates abnormally.
- Action
- Take corrective action by referring to the message KFPS05207-E or KFPS05208-E that was output prior to this message.
- In UNIX:
- If the KFPS05207-E message is output:
Based on this message and the KFPS05212-E message, set the version, addressing mode, and load type for all units to be the same, and then start HiRDB.
- If the KFPS05208-E message is output:
Based on this message and the KFPS05212-E message, restore the version, addressing mode, and load type for all units to the previous version. After terminating normally in the previous version, upgrade HiRDB.
For details on how to return the version to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.
- In Windows:
- If message KFPS05207-E is output
Refer to that message and to the KFPS05209-I message, set the same version and addressing mode for all units, then start HiRDB.
- If message KFPS05208-E is output
Refer to that message and to the KFPS05209-I message, and return the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return values to the previous version and how to upgrade, see the manual HiRDB Version 9 Installation and Design Guide.
KFPS05213-E E+L
Unit aa....aa did not startup
- When the system manager unit was starting, the start status of unit aa....aa could not be determined. For this reason, the system manager unit cannot start.
- aa....aa: Unit identifier
- S: Terminates abnormally.
- Action
- Take corrective action in the following order:
- Check the status of unit aa....aa. The operating status of a unit can be checked with the command pdls -d ust.
- Use the pdstop -z command to forcibly terminate the unit, unless the operating status of unit aa....aa is not one of the following:
In addition, make sure that the operating status of all units is either ONLINE or STOP.
- Check for errors in unit aa....aa and take corrective action if an error occurred.
- Refer to the syslog or pdlog of unit aa....aa and the system manager unit, investigate the cause of the error from the error messages, and then take corrective action.
- If no error messages were output, investigate whether a network error occurred between the system manager unit and unit aa....aa, and if so take corrective action.
- After taking corrective action, make sure that the operating status of all units is ONLINE or STOP, and then restart the system with the pdstart command.
Note that when unit aa....aa is one of the following units, it is not necessary to start the unit:
- A unit for which reduced activation is specified
- A recovery-unnecessary FES unit
- A unit using standby-less system switchover (effects distributed)
KFPS05214-W E+L
Fall-back operation ignored, because of aa....aa
- The HiRDB system cannot perform reduced activation. Ignores the reduced activation mode.
- aa....aa: Reason code
- HiRDB version upped: HiRDB has been upgraded.
- dictionary not initialized: The dictionary is not yet initialized.
- S: Resumes processing.
- Action
- If there are no units that cannot be started, no processing is required.
- When upgrading HiRDB or initializing the dictionary, start all the units that make up the system.
KFPS05215-W L
HiRDB unit aaaa definition error, reason code=b
- An error was detected in the unit definition.
- aaaa: Unit identifier
- b: Error code:
- 1: System ID is invalid.
- 2: Host name is invalid.
- 3: Unit identifier is invalid.
- 4: Required server is not defined.
- 5: Unnecessary server is defined.
- 9: Other error
- S: Resumes processing.
- Action
- If the error code is 1 to 5, check the unit definition according to the displayed code and re-execute the unit. If the error code is 9, contact the customer support center.
KFPS05216-I E+L
Valid option for HiRDB system fall-back operation
- The option for the reduced activation of the HiRDB system is specified.
- S: Resumes processing.
KFPS05217-I E+L
Unit aa....aa did not startup; switches to fall-back operation
- Because a unit was not started during HiRDB system activation, HiRDB is in reduced-startup mode.
- aa....aa: Unit identifier
- S: Resumes processing.
- Action
- Check the reason that the HiRDB unit did not start. After taking corrective action, clear the reduced status by starting the HiRDB unit.
KFPS05218-I E+L
All unit initialization completed; switches to normal operation
- All HiRDB units have been started. The reduced status is cleared and normal operation resumes.
- S: Resumes processing.
KFPS05219-I L
HiRDB initialization process complete; only for pdrstr and pdcopy
- HiRDB startup by pdstart -r has been completed. Only pdrstr can be executed in this mode.
- S: Resumes processing.
KFPS05220-I L
HiRDB system termination process started. mode=aa....aa
- HiRDB system termination processing has begun.
- aa....aa: Termination mode:
- FORCE: Forced termination
- NORMAL: Normal termination
- PLAN: Planned termination
- S: Resumes processing.
KFPS05221-E L
Error occurred in HiRDB system termination process. mode=aa....aa
- An error occurred during HiRDB system termination processing.
If the termination mode is PLAN, or if Real Time SAN Replication is used for a log application site that is terminating with a termination mode of NORMAL, all units other than the system manager are terminated forcibly. - aa....aa: Termination mode:
- NORMAL: Normal termination
- PLAN: Planned termination
- FORCE: Forced termination
- S: Terminates abnormally.
- Action
- A termination error or communication error may have occurred at a unit other than the system manager unit. Check the messages output before this message, correct the error, then restart the system.
- (Planned termination or normal termination of a log application site when Real Time SAN Replication is used)
- Check that all units have terminated, then restart the system.
- If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit or by logging directly into the unit and entering the pdstop -z command, then restart the system.
- The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:
- KFPS01821-E message
- System manager unit: KFPS01850-I message (termination-mode=FORCE)
- For a unit that is not a system manager: KFPS01841-I message (termination-mode=FORCE)
- If the cause is unknown, collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05222-E L
Unable to terminate HiRDB unit aaaa due to communication error
- Unit aaaa cannot be terminated due to a communication error.
- aaaa: Unit identifier
- S: Resumes processing.
- Action
- Use one of the following methods to terminate the unit:
- From the unit containing the system manager, use the pdstop -x command to specify the appropriate host name
- From the unit containing the system manager, use the pdstop -u command to specify the appropriate unit identifier
- Log on directly to the appropriate unit and execute the pdstop -z command
- If the HiRDB unit cannot be terminated by this command, contact the customer support center.
KFPS05223-I L
HiRDB unit aaaa inactive,status=bb
- The status of HiRDB unit aaaa is bb.
- aaaa: Unit identifier
- bb: Status code:
- 10: Being started
- 15: Being started
- 16: Ready for database to be initialized with pdinit command
- 20: Unit startup completed
- 21: Front-end server startup completed
- 25: Being terminated
- 30: Terminated normally
- 31: Terminated forcibly
- 32: Terminated abnormally
- 33: Planned termination
- 40: Database is being shut down
- S: Resumes processing.
- Action
- If the HiRDB unit cannot be terminated normally by the pdstop command, the system displays the cause and the unit status. To terminate the HiRDB unit when it cannot be terminated normally, enter the pdstop -f command.
- If the pdrisedbto command terminates with an error or a warning, the status of the unit that caused the error is displayed. If there is an error, and if the pdrisedbto command is to be re-executed, use pdls -d svr to check the status of the unit, and then restart the stopped unit.
KFPS05224-E L
Error occurred while terminating MGR unit
- An error occurred while terminating the unit where the system manager (MGR) is located.
- S: Terminates abnormally.
- Action
- Collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05225-E L
Error occurred while terminate HiRDB control process
- An error occurred during termination processing of the process server process.
S: Terminates abnormally. - Action
- Collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05226-E L
Unable to terminate HiRDB server aa....aa
- Server with server name aa....aa cannot be terminated.
- aa....aa: Server name
- S: Terminates processing.
- Action
- See the KFPS05180-E message and take appropriate action.
KFPS05227-W L
Now waiting for termination of HiRDB unit aaaa
- The system is waiting for completion of termination processing at HiRDB unit aaaa.
- aaaa: Unit identifier
- S: Resumes processing.
- Action
- If the same message has been issued more than once with the same unit identifier, it may be taking a long time to terminate the unit for some reason or the unit may have terminated abnormally. Check the messages output before this message to determine the status of the HiRDB system.
- Unit terminated abnormally:
Enter the pdstop -f command to forcibly terminate the HiRDB system.
- Unit is taking a long time to terminate:
The following are possible reasons:
Transaction recovery processing is under way.
Communication error occurred.
KFPS05230-E S
Unable to stop aaaa normally because bbbb being cccc
- Normal, planned, or forced termination could not be executed for aaaa because bbbb is engaged in cccc processing.
- aaaa: Type of entity
- { HiRDB|unit|server }
- bbbb: Type of entity
- { HiRDB|unit|server }
- cccc: Processing:
- started: Startup
- terminated: Termination
- S: Resumes processing.
- O: Re-execute the pdstop command after bbbb startup or termination processing is completed. Or, terminate aaaa forcibly with the pdstop -f command. For HiRDB/Parallel Servers, forced termination cannot be executed using the pdstop -f -x host-name command or the pdstop -f -u unit-identifier command.
KFPS05231-E S
Unable to stop server due to server is inactive
- The server cannot be stopped because it is inactive.
- S: Resumes processing.
KFPS05232-E S
Unable to stop unit due to unit is inactive
- The unit cannot be stopped because it is inactive or is already stopped.
- S: Resumes processing.
KFPS05233-E S
Unable to stop HiRDB system normally due to user identifier remained
- The HiRDB system cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.
- S: Terminates processing.
- O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.
- To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.
KFPS05234-E S
Unable to stop unit due to user identifier remained
- The HiRDB unit cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.
- S: Terminates processing.
- O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.
- To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.
KFPS05235-E S
Unable to stop server due to user identifier remained
- The HiRDB server cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.
- S: Terminates processing.
- O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.
- To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.
KFPS05236-E L+S
Unable to stop HiRDB system normally, because unit aaaa stop failed
- The system was unable to perform a normal termination or a planned termination of HiRDB because termination processing of unit aaaa failed.
- aaaa: Identifier of unit for which termination processing failed
- S: Continues processing.
- Action
- Determine why termination processing of unit aaaa failed. Unit aaaa may be running. Execute the ps command to determine whether any HiRDB processes are executing, and if necessary use the pdstop -z command to forcibly terminate unit aaaa.
KFPS05237-E L
Unable to stop unit aaaa by force, reason code=bb....bb
- The aa....aa unit cannot be forcibly terminated because of bb....bb.
- aaaa: Unit identifier of the unit that could not be forcibly terminated.
- bb....bb: Reason why termination was not possible
- NOT RECOVERY:
- The unit was not the HiRDB that was started by executing the pdstart -r command.
- S: Continues processing.
- Action
- When you forcibly terminate non-MGR units that were started using the pdstart command without the -r option specified, execute the pdstop -z command in the unit to be forcibly terminated.
KFPS05240-E E+L
Pdrplstart command failed. reason=aa....aa
- Error occurred while executing the pdrplstart command.
- aa....aa: Character string indicating the type of error
- SYSTEM INCOMPLETE:
- System startup is not complete.
- ANY UNIT INACTIVE:
- The status of one or more units is inactive.
- ANY BES INACTIVE:
- The status of one or more back-end servers is inactive.
- UTL UNIT: The system is unable to run on the UTL unit.
- STARTED:
- HiRDB Datareplicator linkage is already running.
- PD_RPL_HDEPATH:
- HiRDB Datareplicator linkage cannot run in the current environment.
- TIMEOUT:
- An execution time-out occurred.
- STATUS WRITE ERROR:
- Writing of the status file failed.
- STOPPING NOW:
- HiRDB Datareplicator linkage is being stopped.
- EXTRACT STOPPED:
- HiRDB Datareplicator extraction processing was interrupted.
- S: Terminates processing.
- Action
- Take action appropriate to the type of error. If the displayed information is none of the character strings shown above, contact the customer support center.
Error indicator character string | Explanation | Action |
---|
SYSTEM INCOMPLETE | System startup was not completed. | Re-execute the command after system startup has been completed. |
ANY UNIT INACTIVE | Some units were not on ACTIVE status. | Restart all inactive units and re-execute the command. |
ANY BES INACTIVE | Some back-end servers were not on ACTIVE status. | Restart all inactive back-end servers and re-execute the command. |
UTL UNIT | Requested processing cannot be executed at the UTL unit. | -- |
STARTED | HiRDB Datareplicator linkage was already executing. | -- |
PD_RPL_HDEPATH | HiRDB Datareplicator linkage cannot be executed in this environment. | Specify the pd_rpl_hdepath operand in the unit control information definition, restart HiRDB, then re-execute the command. |
TIMEOUT | Execution timeout occurred. | Re-execute the command. |
STATUS WRITE ERROR | Write error occurred in the status file. | Check that the pd_rpl_hdepath operand is specified correctly in the system common definition. Or, check that there is a file for data linkage. |
STOPPING NOW | HiRDB Datareplicator linkage was terminating. | Re-execute the command after HiRDB Datareplicator linkage has terminated at all units. |
EXTRACT STOPPED | Data extraction processing by HiRDB Datareplicator was cancelled. | Initialize the file for data linkage and re-execute the command. |
- --: Not applicable
KFPS05241-E E+L
Pdrplstop command failed, reason=aa....aa
- An error occurred while the pdrplstop command was executing.
- aa....aa: Error type
- S: Terminates processing.
- Action
- Re-execute the pdrplstop command after taking one of the following actions. Contact the customer support center if an error type not described in the manual is output.
Error type | Error description | Action |
---|
UTL UNIT | Cannot be executed by a utility special unit. | The pdrplstop command cannot be executed on a utility special unit. |
STOPPED | Replication with HiRDB Datareplicator already stopped. | The pdrplstop command cannot be executed because replication with HiRDB Datareplicator already stopped. |
PD_RPL_HDEPATH | The pd_rpl_hdepath operand was not specified. | Specify the pd_rpl_hdepath operand. After starting the HiRDB system, re-execute the pdrplstop command. |
TIMEOUT | Execution time was exceeded. | Re-execute the pdrplstop command. |
STATUS WRITE ERROR | An attempt to write the status file failed. | Check if the specification of the pd_rpl_hdepath operand is correct, and then re-execute the pdrplstop command. Alternatively, after checking that data linkage files exist, re-execute the pdrplstop command. |
ANY UNIT INACTIVE | There are inactive units. | Start inactive units, and then re-execute the pdrplstop command. |
ANY BES INACTIVE | There are inactive back-end servers. | Start inactive back-end servers, and then re-execute the pdrplstop command. |
EXTRACTING STATUS | Extraction processing of HiRDB Datareplicator is not complete. | See the KFPS05243-W message output before this message, and then take appropriate action. |
FILE LOCK ERROR | A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator. |
FILE OPEN ERROR | A data linkage file used by HiRDB Datareplicator could not be opened. |
COMMUNICATION | An inter-process communication error occurred. | Check for the cause of the network error on the unit where the communication error occurred. |
BUSY | The command could not be executed because the service request destination server was processing. | See the KFPS05244-W message output immediately before this message, and then take appropriate action. |
KFPS05242-I E+L
Accepted data replication stop request
- HiRDB Datareplicator linkage termination request has been accepted.
- S: Resumes processing.
KFPS05243-W E+L
Unable to stop data replication,server=aa....aa,reason=bb....bb
- Data replication with HiRDB Datareplicator could not be stopped.
- aa....aa: Server name
- bb....bb: Reason code
- S: Continues processing.
- Action
- Re-execute the pdrplstop command after taking the appropriate actions.
Reason code | Error description | Action |
---|
EXTRACTING STATUS | Extraction processing by HiRDB Datareplicator is not complete. | Check all of the following items, and then re-execute the pdrplstop command:
- Check if the hdestate command of HiRDB Datareplicator started the extraction process. If the extraction process is not running, start the extraction process, and then check item 2.
- Check if extraction processing by HiRDB Datareplicator is complete. Extraction processing is complete if the following conditions are all met:
- No transactions are active
Execute the pdls -d trn command to check for active transactions.
- The system block number being extracted is the last block number of the current file
Execute the pdls -d rpl -j command to check the system log block number being extracted. Also, execute the pdlogls -d sys command to check the last block number of the current file.
|
BES INACTIVE | Inactive back-end server(s) found. | Start the inactive back-end server(s), and then re-execute the pdrplstop command. |
FILE LOCK ERROR | A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator. | HiRDB Datareplicator has exclusive ownership of the data linkage file. Investigate the cause, and then re-execute the pdrplstop command. |
FILE OPEN ERROR | A data linkage file used by HiRDB Datareplicator. | Either the data linkage file has been deleted or it could not be opened due to a disk error. Synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB. |
KFPS05244-W E+L
Unable to stop data replication,unit=aaaa,reason=bb....bb
- Data replication with HiRDB Datareplicator could not be stopped.
- aaaa: Unit identifier
- bb....bb: Reason code
- S: Terminates processing.
- Action
- Take action according to the following table, and then re-execute the pdrplstop command.
Reason code | Error description | Action |
---|
UNIT INACTIVE | There are inactive units. | Start inactive units, and then re-execute the pdrplstop command. |
COMMUNICATION | An inter-process communication error occurred. | Check for the cause of the network error on the unit where the communication error occurred. |
PD_RPL_HDEPATH | The pd_rpl_hdepath operand was not specified. | Specify the pd_rpl_hdepath operand. |
BUSY | The command could not be executed because the service request destination server is processing. | Re-execute the pdrplstop command. |
KFPS05245-W E+L
Unit stopped for fall-back operation exists. Do not create target database from stopped unit,unit=aaaa
- Some units were not started because of reduced activation. Do not re-create the target database based on the database of a unit that was not started because of reduced activation.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05246-E L
Unable to start HiRDB system, because pd_rpl_hdepath not matched between units
- HiRDB cannot be started, because aa....aa does not match between units.
- aa....aa: Information that does not match between units
- pd_rpl_hdepath: HiRDB Datareplicator working directory
- start option: HiRDB startup mode
- S: Terminates abnormally.
- Action
- aa....aa is pd_rpl_hdepath
Refer to the KFPS05247-E message, and match the value of the pd_rpl_hdepath operand of the unit using the standby-less system switchover (effects distributed) facility. Then, start HiRDB.
- aa....aa is start option
If Real Time SAN Replication with the log-only synchronous method is used, depending on the site status of each site, match either the pdstart command or the pdstart -l command.
KFPS05247-E L
HiRDB unit information, unit_id = aaaa, bb....bb
- Information on unit aaaa is displayed.
- aaaa: Unit identifier
- bb....bb: Unit information
- pd_rpl_hdepath:
- Value of the pd_rpl_hdepath operand (name of the HiRDB Datareplicator directory where data is extracted)
- If this operand is omitted, (null) is displayed.
- start option:dd....dd
- dd....dd: Unit start status
- "primary": Execution
- "standby": Log application
- S: Abnormally terminates.
- Action
- "pd_rpl_hdepath" is displayed
- Set the value of the pd_rpl_hdepath operand to the same value for the units using the standby-less system switchover (effects distributed) facility. Then, start HiRDB.
- "start option" is displayed
- Make sure that the startup mode is the same for all units where Real Time SAN Replication with the log-only synchronous method is used.
KFPS05248-E L
Unable to start unit aaaa due to pd_ha_agent operand invalid
- HiRDB cannot be started because the pd_ha_agent operand of unit aaaa is invalid. The value of the pd_ha_agent operand of unit aaaa may have been changed from the standby-less system switchover (effects distributed) facility to another system switchover facility.
- aaaa: Unit identifier
- S: Terminates processing.
- Action
- Check the value of the pd_ha_agent operand of unit aaaa. If the unit is using the standby-less system switchover (effects distributed) facility and the server abnormally terminated, the value of the pd_ha_agent operand cannot be changed. Specify activeunits in the pd_ha_agent operand, and start HiRDB.
KFPS05249-E L
aa....aa invalid; stops unit startup, unit_id = bbbb
- During restart processing of unit bbbb, the contents of aa....aa did not match that for normal startup.
- aa....aa: Error cause
- pdhagroup: pdhagroup operand
- bbbb: Unit identifier
- S: Abnormally terminates.
- Action
- Check the value of the pdhagroup operand. If the system manager unit did not terminate normally, the pdhagroup operand cannot be changed. Return it to normal startup status, and start HiRDB.
KFPS05250-I L
Pdvrup command will be executed automatically
- The pdvrup command will be activated automatically.
- S: Continues processing.
KFPS05251-W L
Waiting for server start, server = aa....aa
- The system is waiting for the server to start.
- aa....aa: Name of the server that is waiting to start
- S: Continues processing.
- Action
- On the standby-less system switchover (effects distributed) target unit, use the cluster software commands#1 to check the status of the server indicated in the message.
- If the server is not displayed for any unit:
- Select the unit to start the running system server, and activate#2 the server as the running system server.
- If the server is waiting to be activated as the running server:
- Activate#2 the server as the running system server.
- If there is a unit activating the running system server:
- The wait is released as the server is activated. Nothing in particular is required.
- If none of this is applicable, contact the customer support center.
- #1: If the cluster software is HA monitor, enter the monshow command; if it is Hitachi HA Toolkit Extension, enter the hateshow command.
- #2: If the cluster software is HA monitor, enter the monact command; if it is Hitachi HA Toolkit Extension, enter the command to activate the upper-level cluster software package (such as MC/ServiceGuard).
KFPS05260-I L+S
HiRDB system initialization process complete on standby site
- Startup processing on the log application site HiRDB has finished.
- S: Continues processing.
KFPS05261-W L
Database take over skipped, unit_id=aaaa, server=bb....bb
- Database inheritance was skipped.
- aaaa: Unit identifier
- bb....bb: Server name
- S: Continues processing.
- Action
- If switchover to a transaction execution site occurs when database inheritance was skipped, the data cannot be guaranteed on the server that output the message. Refer to the section on site switchover in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take the actions necessary to perform site switchover.
KFPS05262-E L
Error occurred in HiRDB unit aaaa database take over process, reason code=bb....bb
- An error occurred during database inheritance. All units were terminated forcibly.
- aaaa: Unit identifier
- bb....bb: Error code
- COMMUNICATION: Error in communication with another unit
- STOP(A): STOP(A) Notification
- INTERNAL ERROR: Internal processing error
- S: Terminates abnormally.
- Action
- Ensure that all units have terminated, and then check the message that was output before this message. Eliminate the cause of the error, and then start the log application site HiRDB.
- If there are still units that have not terminated, either execute the pdstop -f command from the system manager unit or execute the pdstop -z command from the units that have not terminated. After all units have terminated, start the log application site HiRDB.
- The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If any of the following messages is output, the unit is terminated:
- KFPS01821-E message
- System manager unit: KFPS01850-I (termination-mode="FORCE") message
- Other than the system manager unit: KFPS01841-I (termination-mode="FORCE") message
- If the cause cannot be determined, save the files under $PDDIR/spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.
KFPS05263-W L
Necessary to prepare for applying system log, reason=aa....aa
- On the transaction execution site, aa....aa was executed. When aa....aa is executed, the following results might occur on the log application site:
- The log application site fails to respond.
- The log application site units shut down.
- When a site switchover to the log application site is performed, data may be lost.
- aa....aa: Operation performed on the transaction execution site
- pdinit: Database initialization utility
- pdstart dbdestroy: HiRDB forcible startup
- pdvrup: HiRDB version upgrade
- S: Continues processing.
- Action
- Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and perform preparation for log application.
KFPS05270-I L
Pd_system_expand_unit specified in system configuration
- The pd_system_expand_unit operand is specified in the HiRDB system definition.
This is the system that has the expansion unit. - S: Continues processing.
KFPS05273-I L
HiRDB expand unit aaaa initialization process complete
- Start processing for expansion unit aaaa is finished.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05274-I L
HiRDB expand unit aaaa termination process complete
- Termination processing for expansion unit aaaa is finished.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05275-W L
Error occurred in status file while bb....bb expand unit status, unit_id=aaaa
- An error was detected while the status of expansion unit aaaa was being read from the status file or written to the status file.
- aaaa: Unit identifier
- bb....bb: Processing classification (content of processing to the status file)
- reading: Reading of the status file
- writing: Writing of the status file
- S: Continues processing.
- Action
- Follow the error message that was output before this error message to eliminate the cause of the error.
KFPS05276-E L
Error occurred in status file while aa....aa expand unit status
- An error was detected while the status of the expansion unit was being read from the status file or written to the status file.
- aa....aa: Processing classification (content of processing to the status file)
- reading: Reading of the status file
- writing: Writing of the status file
- S: Terminates abnormally.
- Action
- Follow the error message that was output before this error message to eliminate the cause of the error.
KFPS05288-I L
HiRDB unit aaaa status change to ACTIVE
- Because the running status of STOP(A) unit aaaa has been confirmed, the status of the unit is changed to ACTIVE.
- aaaa: Unit name
- S: Resumes processing.
KFPS05289-E L
HiRDB unit aaaa status change to STOP(A)
- Communication with unit aaaa or data reception from unit aaaa failed. Or, a status in which the client cannot connect to unit aaaa was detected. The status of unit aaaa is changed to STOP(A).
- aaaa: Unit name
- S: Resumes processing.
- Action
- Execute the ps command on unit aaaa to determine whether the process is active.
- If the HiRDB process is active, a communication error or a service slowdown in unit aaaa may have occurred. Check the cause of the error based on the message output before this message, stop the unit by entering pdstop -z, then restart the unit.
- While the HiRDB process is inactive, either a system switchover or abnormal termination could have occurred. If abnormal termination occurred, take action according to the message that was output. To restart the HiRDB process, execute either the pdstart -x or pdstart -u command.
KFPS05290-E L
Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc
- An error occurred during communication from host aa....aa to host bb....bb.
- aa....aa: Host name
- bb....bb: Host name
- ccc: Code being processed (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the status.
- Action
- If this message is issued during HiRDB startup, a HiRDB unit other than the system manager (MGR) may not be active. Start the applicable HiRDB unit.
- If action 1 does not apply, take corrective action according to the description in Table 4-1 Frequently occurring causes and required action for RPC-related errors.
- Otherwise, contact the customer support center.
KFPS05291-E L
Communication error occurred,to host=aa....aa processing code=bbb reason code=ccc
- An error occurred during communication to host aa....aa.
- aa....aa: Host name
- bbb: Code being processed (HiRDB internal code)
- cccc: Reason code (HiRDB internal code)
- S: Resumes processing or terminates abnormally, depending on the status.
- Action
- Check whether a unit of host aa....aa is inactive. If so, start the corresponding unit. If the corresponding unit is not running in reduced mode, ignore this message.
- If this message is output even though the corresponding unit is running, a communication error has occurred. Take corrective action according to 4.1 Detail codes for RPC-related errors.
- In cases other than the above, contact the customer support center.
KFPS05292-I L
Unit aaaa inactive
- Unit aaaa is not on normal active status.
- aaaa: Unit identifier
- S: Terminates processing.
- Action
- Take action appropriate to the unit status.
KFPS05293-E E
Unable to access shared memory
- Shared memory cannot be accessed during execution of the pdls command.
- S: Terminates processing.
- Action
- Start the corresponding host and enter the pdls command.
KFPS05294-E L
Unable to stop normally HiRDB system due to auto audit trail loading service is operating
- The facility for automatically loading audit trail table data was enabled when the pdaudatld -b command was executed during termination processing. As a result, the HiRDB system cannot terminate normally.
- S: Terminates processing.
- O: Re-execute the pdstop command.
- Action
- Do not execute the pdaudatld command during termination processing.
KFPS05300-I E+L
Now preparing for statistics log service. run ID=aaaaaaaa
- Preparation is underway for the statistics log service function.
- aaaaaaaa: Run ID
- S: Resumes processing.
KFPS05303-E E+L
Unable to start statistics log service. reason code=aaaa
- The statistics log service function cannot be started for the displayed reason (aaaa).
- aaaa: Reason code:
- 101: Memory shortage
- 103: Communication error
- 401: Undefined error
- 405: Definition error
- 514: til start failure
- S: Terminates processing.
- O: Contact the HiRDB administrator, take action appropriate to the reason code, then restart the HiRDB system.
- Action
- Take action appropriate to the reason code.
KFPS05304-I L
Specified pd_stj_file_size is too small; sets pd_stj_file_size at 1024 and continues processing
- The value of the pd_stj_file_size operand was too small, so it was rounded up to 1024 KB and processing continues.
The value of the pd_stj_file_size operand must satisfy the following condition:
pd_stj_file_size
pd_stj_buff_size
2 - S: Continues processing.
- Action
- Once HiRDB has terminated, change the pd_stj_file_size operand value.
KFPS05308-W E+L
Error occurred while terminating statistics log service; continues processing. reason code=aaaa
- An error occurred while terminating the statistics log service function, but processing continues.
- aaaa: Reason code:
- 103: Communication error
- S: Resumes processing.
KFPS05321-E E+L
Insufficient memory. required memory size=aa....aa, area type=bb....bb
- A memory shortage occurred. The message displays the size and type of the memory that was to be allocated.
- aa....aa: Size of memory that was to be allocated
- bb....bb: Type of memory:
- STATIC_SHMPOOL: Static shared memory
- S: Terminates processing.
- O: Contact the HiRDB administrator, take appropriate action, then restart the HiRDB system.
- Action
- Increase the shared memory available to the system.
KFPS05350-E E+L
Failure to open statistics log file. file name=aa....aa, reason code=bbbb-cc
- Statistics log file open processing failed.
- aa....aa: Name of the statistics log file
- bbbb: Reason code:
- 303: Open system call error
- cc: HiRDB internal code
- S: Terminates processing.
- O: Contact the HiRDB administrator, eliminate the cause of the error, then re-execute.
- Action
- Determine the cause of the error from the preceding KFPO00107-E message and take appropriate action.
KFPS05351-W E+L
Failure to close statistics log file. file name=aa....aa, reason code=bbbb-cc
- Statistics log file close processing failed.
aa....aa: Name of the statistics log file - bbbb: Reason code:
- 304: Close system call error
- cc: HiRDB internal code
- S: Resumes processing.
- O: Contact the HiRDB administrator and eliminate the cause of the error.
- Action
- Eliminate the cause of the error indicated by the reason code.
KFPS05352-W E+L
Failure to write statistics log file. fime name=aa....aa, reason code=bbbb-cc
- Output to a statistics log file failed.
- aa....aa: Name of the statistics log file
- bbbb: Reason code:
- 305: Write system call error
- cc: HiRDB internal code
- S: Resumes processing.
- O: Contact the HiRDB administrator and eliminate the cause of the error.
- Action
- Determine the cause of the error from the preceding KFPO00107-E message and take appropriate action.
KFPS05353-E E+L
Error occurred while handling statistics log file. file name=aa....aa, reason code=bbbb-cc
- An error occurred while handling a statistics log file.
- aa....aa: Name of the statistics log file
- bbbb: Reason code:
- 103: Communication error
- cc: HiRDB internal code
- S: Terminates processing.
- Action
- Eliminate the cause of the error indicated by the reason code.
KFPS05354-E E+L
Error occurred while handling statistics log file. reason code= aa....aa - bb....bb
- An error occurred while handling a statistics log file.
- aa....aa: Reason code:
- 101: Memory shortage
- 103: Communication error
- 105: Timeout (communication)
- If the reason code is 101 or 103, information in the statistics log buffer is not output to the statistics log file. If the reason code is 105, the information might be output.
- bb....bb: HiRDB internal code
- S: Continues processing.
- If this message is output during execution of the pdstjsync command, the pdstjsync command outputs message KFPS05840-I and terminates normally.
- O: Contact the HiRDB administrator to eliminate the cause of the error.
- Note that when this message is output, statistics from around the time the message was output will not be included in the statistics to be edited by the statistics analysis utility (pdstedit).
- Action
- Eliminate the cause of the error indicated by the reason code.
KFPS05355-I E+L
Statistics log file swapped. from=aa....aa, to=bb....bb, unit ID=cccc
- Statistics log files were swapped.
- aa....aa: Name of the old file (before swapping)
- bb....bb: Name of the new file (after swapping)
- cccc: Unit identifier
- S: Resumes processing.
KFPS05360-W L
Cancels statistics output. unit ID=aaaa
- Unit aa....aa has stopped collecting statistical information.
An error message concerning the statistics log file has been output immediately before this message; see that message for the cause of the error. - aaaa: Unit identifier
- S: Terminates processing.
- Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.
- Action
- If the statistical information is not needed for the unit displayed in the message, operation can be continued. If the statistical information is needed, terminate the applicable unit, eliminate the immediate cause of the error indicated by the message output immediately before this message. Then, execute the pdstjswap command for the unit or restart the unit and resume collection of statistical information.
KFPS05361-W L
Already canceled statistics output. unit ID=aaaa
- Output of statistical information for unit aaaa has already been terminated due to a previous error.
- aaaa: Unit identifier
- S: Resumes processing.
- Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.
- Action
- If the statistical information is not needed for the displayed unit, operation can be continued. If the statistical information is needed, terminate the corresponding unit, eliminate the cause of the error indicated by the message output immediately before this message, restart the unit, then restart collection of statistical information.
KFPS05362-W L
Unable to cancel statistics output. unit ID=aaaa
- Statistical information collection cannot be stopped for unit aaaa.
An error message concerning the statistics log file has been output immediately before this message; see that message for the cause of the error. - aaaa: Unit identifier
- S: Resumes processing.
- Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.
- Action
- Enter the pdstend command to terminate collection of statistical information. If the statistical information is not needed for the displayed unit, operation can be continued. If the statistical information is needed, terminate the corresponding unit, eliminate the cause of the error indicated by the message that was output immediately before this message, restart the unit, then restart collection of statistical information.
KFPS05370-I E
Usage:pdstjswap [-x host_name| -u unit_id]
- Displays the format of the pdstjswap command.
- S: Continues processing.
KFPS05372-E E
One of aa....aa option must be specified.
- One of the indicated options must be specified.
- aa....aa: Options
- S: Terminates processing.
- O: Specify an option and re-execute the command.
KFPS05373-E E
Unable to execute command due to failure of aa....aa system call (command), code= bb....bb
- Command cannot be executed because of an error in system call (or command) aa....aa.
- aa....aa: System call or command in which the error occurred
- {exec|fork|rsh|tempnam|open}
- bb....bb: Internal code for the return value of the system call or rsh
- If tempnam or open is output in aa....aa, the errno value is output.
- S: Terminates processing.
- O: Contact the administrator, take corrective action, and then re-execute the command.
- Action
- In UNIX:
- If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix psjcm in that directory. For typical errno examples, see 4.3 System call return codes.
- If exec, fork, or rsh is output in aa....aa, determine the cause of the error and take corrective action based on message KFPO00107-E, which was output immediately before this one.
- In Windows:
- If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix psjcm in that directory. For typical errno examples, see 4.3 System call return codes.
- If exec, fork, or rsh is output in aa....aa, determine the cause of the error and take corrective action based on message KFPO00107-E, which was output immediately before this one.
KFPS05374-E E
Specified hostname invalid in "pdstart" operand
- The host name specified in the pdstart operand in the system definition is invalid.
- S: Terminates processing.
- O: Correct the host name specified in the pdstart operand in the system definition.
KFPS05375-E E
Hostname must be equal to SDS hostname for single server.
- For a HiRDB/Single Server, the host name that is specified must be the host name of the single server. Because there is only one single server host for a HiRDB/Single Server, the specification may be omitted. This message is output when a host name is specified but that name is invalid.
- S: Terminates processing.
- O: Omit the host name or specify the correct host name, and then re-execute the command.
KFPS05381-E E
Insufficient memory
- A memory shortage occurred.
- S: Terminates processing.
- O: Re-examine the number of processes, take appropriate action, and re-execute.
KFPS05393-E E
Communication error occurred. info=aa....aa
- A communication error occurred during command execution.
- aa....aa: Maintenance information
- S: Terminates processing.
- O: Eliminate the cause of the communication error, then re-execute the command.
- Action
- If a message that shows the cause of the communication error was output immediately before this message, take the action indicated in the message to eliminate the cause of the communication error. If no message that displays the cause of the communication error was output, save the maintenance information and contact the customer support center.
KFPS05394-E E
Unit state not online. info=aa....aa
- The unit is not online.
- aa....aa: Maintenance information
- S: Terminates processing.
- O: If the unit is not running, start the unit and re-execute the command.
- Action
- If this message is output, even though the unit is running, save the maintenance information and contact the customer support center.
KFPS05395-E E
Statistics log service is inactive. info=aa....aa
- The statistics log is not being acquired for this unit.
- aa....aa: Maintenance information
- S: Terminates processing.
- O: Start acquisition of the statistics log and re-execute the command.
- Action
- If this message is output, even though the statistics log is being acquired for this unit, save the maintenance information and contact the customer support center.
KFPS05396-W E
Statistics log file not deleted.
- Swap processing of the statistics log file has terminated, but the statistics log file could not be deleted. Consider the following causes:
- There was an attempt to delete the statistics log file that is currently being output
- The statistics log file to be deleted is being used by another program or command
- S: Continues processing.
- O:
- If the statistics log file was deleted, subsequent swapping of the statistics log file may not perform normally. If statistical information is being acquired, stop the acquisition of statistical information before swapping the statistics log file. If statistical information is not to be acquired, suppress the acquisition of statistical information. To acquire statistical information, stop and then restart HiRDB.
- If the statistics log file is in use by another program or command, inherited statistical information can be acquired. However, because the statistics log file to be deleted is not deleted, be careful when unloading or editing it.
- Action
- If the reason indicated in the message explanation is not appropriate, contact the customer support center when this message is output.
KFPS05397-E E
Unexpected error occurred. info:(aa....aa:bbbb)cc....cc
- An unexpected error occurred.
- aa....aa: Maintenance information
- bbbb: Maintenance information
- cc....cc: Maintenance information
- S: Abnormally terminates.
- Action
- Save the maintenance information and contact the customer support center.
KFPS05398-E E
Statistics log file can not open
- The statistics log file could not be opened during command execution. Consider the following causes:
- There is a shortage in the file system area.
- The swap target statistics log file cannot be overwritten (there is no write privilege for the statistics log file or the directory that stores the statistics log file).
- S: Terminates processing.
- O:
- If this message is output, statistical information cannot be acquired. If statistical information is being acquired, immediately stop the acquisition of statistical information. If statistical information is not being acquired, suppress statistical information acquisition.
- If the cause is a file system area shortage, delete any unnecessary files in the file system. If the swap target statistics log file cannot be overwritten, enable the overwriting attribute of the statistics log file.
- After taking appropriate measures, execute the pdstjswap command to restart acquisition of statistical information.
- Action
- If the reason indicated in the message explanation is not appropriate, contact the customer support center when this message is output.
KFPS05600-I L
HiRDB unit aaaa prepare for starting. status=bb....bb
- Preparations are underway to start unit aaaa.
aaaa: Unit identifier - bb....bb: Unit status:
- ACCEPT pdstart
- The pdstart command has been accepted.
- FIX SHARED MEMORY
- Fixing of shared memory page has started.
- CREATE PIPE FILE
- Creation of a pipe file has started.
- S: Continues processing.
KFPS05601-I L
This program is HiRDB/Workgroup Server
- This program is HiRDB/Workgroup Server.
S: Continues processing.
KFPS05602-I L
HiRDB Option = aa....aa, unit_id = bbbb, version = cc....cc
- Displays the embedded option program product names. This message is output during normal starting or restarting of a unit. During restart, this message shows the previous environment.
- aa....aa: Option program product names
- Staticizer Option: HiRDB Staticizer Option
- Advanced High Availability: HiRDB Advanced High Availability
- Non Recover FES: HiRDB Non Recover FES
- Disaster Recovery Light Edition: HiRDB Disaster Recovery Light Edition
- Accelerator: HiRDB Accelerator
- bbbb: Unit identifier
- cc....cc: Option program product names (vv-rr)
- Displays the version (vv) and revision (rr) of the option program product.
- S: Continues processing.
- Action
- Check the execution environment.
KFPS05603-I L
Server aa....aa starting on unit bbbb
- On unit bbbb, server aa....aa was started as the running system.
- aa....aa: Name of the server started as the running system
- bbbb: Identifier of the server start target unit
- S: Continues processing.
KFPS05604-I L
Allocated shared memory for aa....aa.owner=bb....bb,size=cc....cc
- Allocated shared memory.
- aa....aa: Type of shared memory that was allocated
- UNIT_CONTROLLER: Unit controller
- bb....bb: Attribute of the process using the shared memory (same as the value of SHM-OWNER displayed by the pdls -d mem command)
- MANAGER: Manager
- cc....cc: Size of the shared memory that was allocated (bytes)
- S: Continues processing.
KFPS05605-W L
No more guest servers activatable on unit aaaa, number of active guest servers reached pd_ha_max_act_guest_servers
- Because there is no free guest area, unit aaaa cannot receive any more guest BES's.
- aaaa: Identifier of the unit for which there is no free guest area
- S: Continues processing.
KFPS05606-W L
Unable to activate server aa....aa on unit bbbb,number of act guest servers over pd_ha_max_act_guest_servers
- Because there is no free guest area on unit bbbb, server aa....aa could not become the running system on unit bbbb.
- aa....aa: Name of the server that cannot become the running system
- bbbb: Identifier of the unit with no free guest area
- S: Continues processing.
- Action
- Use one of the following methods to check whether the corresponding server is operating as the running system on another unit in the HA group:
- Check whether this message is followed by a KFPS01813-I message output to another unit in the HA group.
- Execute the pdls -d ha command.
- Execute the pdls -d svr command.
- If the corresponding server is not operating as the running system, see the message output to the system manager unit or to each unit. Take the indicated action as necessary, and then start the server.
KFPS05607-I L
HiRDB server aa....aa stop request issued from HA monitor;stops HiRDB server aa....aa, reason=bb....bb
- Server aa....aa was stopped because a stop request was issued from the HA monitor or the Hitachi HA Toolkit Extension.
- aa....aa: Name of the server to be stopped
- bb....bb: HiRDB internal stop reason code
- S: Abnormally terminates.
- O: See the HA monitor or Hitachi HA Toolkit Extension message.
KFPS05608-I L
HiRDB server aa....aa restart request issued from HA monitor;stop HiRDB server aa....aa temporarily, reason=bb....bb
- Server aa....aa stopped because a restart request was issued from the HA monitor or Hitachi HA Toolkit Extension.
- aa....aa: Name of the stopped server
- bb....bb: HiRDB internal stop reason code
- S: Stops and restarts the server.
- O: After this message is output, check the server running status using the pdls -d ha (or pdls -d ha -a) command from the system manager unit. If the server has not restarted, depending on the error cause it may not be able to start. See any messages output after this message, and take any indicated action.
KFPS05609-I L
HiRDB server aa....aa start mode determined, start mode:bb....bb
- The server start mode has been determined.
- aa....aa: Server name
- bb....bb: Start mode
- R: Restart
- R(P): Restart after planned termination
- S: Normal start
- S: Continues processing.
KFPS05610-I E+L
Server aa....aa is placed in the starting wait state
- Server aa....aa is in running system server starting wait state.
- aa....aa: Server name
- S: Continues processing.
- O: The running system server is not activated. Either start the running system server, or use the HA monitor or Hitachi HA Toolkit Extension command to activate it as the running system server.
KFPS05611-I E+L
Server aa....aa is placed in the standby state
- Server aa....aa is placed in standby state.
- aa....aa: Server name
- S: Continues processing.
KFPS05612-I E+L
Unable to recognize HiRDB server aa....aa initialization completion
- Completion of server aa....aa initialization processing cannot be recognized using the pdstart command.
Or, for whatever reason, the server cannot be activated. - S: Continues processing.
- O:
- Server activation took too much time or failed. Enter the pdls command to check the server running state.
- If the server is activating
Wait a period of time, and then re-enter the pdls command to check the system status. If server initialization processing has not completed, check the messages to determine if there may be another cause.
- If the server is stopping
An error may occur during server activation, preventing the server from activating. Check the messages in the message log file and the event log (in UNIX, syslogfile), and investigate the cause of the server activation failure. If there are no messages, the reason that the server could not be activated may be that there are no unused guest areas in the unit. Use the pdls -d ha command to check the number of unused guest areas in the unit from the number of guest back-end servers running in the unit and the value of the pd_ha_max_act_guest_servers operand. If the number of guest back-end servers running in the unit reaches the value of the pd_ha_max_act_guest_servers operand, start the back-end server on another unit.
- If the reason cannot be determined, contact the customer support center.
- If server activation processing always takes a lot of time, specify the time required for system activation in the pd_system_complete_wait_time operand, and terminate it normally with the pdstart command.
KFPS05613-W E+L
Too big "pd_ha_max_act_guest_servers". Max value assumed, reason code = aa....aa, unit = bbbb, original value = cc....cc, assumed value = dd....dd
- A value greater than the maximum was specified in the pd_ha_max_act_guest_servers operand. The maximum value is assumed.
- aa....aa: Reason code
- SERVER LIMIT:
- The total of the value specified in the unit control information definition pd_ha_max_act_guest_servers operand and the number of host BES's exceeds the maximum number of servers in a unit. Specify a value in the pd_ha_max_act_guest_servers operand that does not exceed the maximum number of servers in a unit.
- GUEST BES COUNT:
- The value set in the unit control information definition pd_ha_max_act_guest_servers operand exceeds the maximum number of guest BES's. Set the number of BES's in the pd_ha_max_act_guest_servers operand.
- bbbb: Unit identifier
- cc....cc: Value specified in the unit control information definition pd_ha_max_act_guest_servers operand
- dd....dd: The value set in the pd_ha_max_act_guest_servers operand based on internal calculation
- S: Continues processing.
- Action
- Consider the following explanations on the basis of the reason code, and consider whether the specification of the unit control information definition pd_ha_max_act_guest_servers operand is correct.
- SERVER LIMIT: The total of the value specified in the pd_ha_max_act_guest_servers operand and the number of host BES's inside the unit exceeds the maximum. Specify a value in the pd_ha_max_act_guest_servers operand that does not exceed the maximum number of servers in the unit. The number of guest servers that can run concurrently becomes less than the value specified in the pd_ha_max_act_guest_servers operand.
- GUEST BES COUNT: The pd_ha_max_act_guest_servers operand specifies a value greater than the number of guest BES's running in the unit. To allocate the appropriate resources, set the number of guest BES's running in the unit in the pd_ha_max_act_guest_servers operand.
KFPS05614-W E+L
Too small "pd_ha_max_server_process". Total of host BES "pd_max_bes_process" assumed, unit = aaaa, original value = bb....bb, assumed value = cc....cc
- The value specified in the unit control information definition pd_ha_max_server_process operand is less than the total of the pd_max_bes_process operands for the host BES in the corresponding unit. Set the total of the pd_max_bes_process operands for the host BES in the corresponding unit.
- aaaa: Unit identifier
- bb....bb: Value specified in the unit control information definition pd_ha_max_server_process operand
- cc....cc: Value set in the pd_ha_max_server_process operand based on internal calculation
- S: Continues processing.
- Action
- Reconsider the specification of the unit control information definition pd_ha_max_server_process operand.
KFPS05615-W E+L
Too small "pd_ha_process_count". Total of host BES "pd_process_count" assumed, unit = aaaa, orginal value = bb....bb, assumed value = cc....cc
- The value specified in the unit control information definition pd_ha_process_count operand is less than the total specified in the pd_process_count operands of the host BES in the corresponding unit. Set the total specified in the pd_process_count operands of the host BES in the corresponding unit.
- aaaa: Unit identifier
- bb....bb: Value specified in the unit control information definition pd_ha_process_count operand
- cc....cc: Value set in the pd_ha_process_count operand based on internal calculation
- S: Continues processing.
- Action
- Reconsider the specification of the unit control information definition pd_ha_process_count operand.
KFPS05616-I L
Guest servers became activatable on unit aaaa
- Because there is a free guest area, unit aaaa can receive the guest BES.
- aaaa: Unit identifier
- S: Continues processing.
KFPS05617-I L
Server aa....aa stop request accept from HA monitor; stops server reason=bb....bb
- Because a server stop request was issued from the HA monitor or Hitachi HA Toolkit Extension, server aa....aa is stopped.
- aa....aa: Server name
- bb....bb: HiRDB internal stop reason code (maintenance information)
- S: Terminates processing.
- O: See the HA monitor message that was output immediately before.
KFPS05618-E E+L
Unable to specify definition in HAgroup unit, unit ID=aaaa, definition file=bb....bb, record number=cc....cc
- In the unit control information definition of units for which standby-less system switchover (effects distributed) is applied, an operand was specified that cannot be specified for units for which standby-less system switchover (effects distributed) is applied.
- aaaa: Unit identifier
- bb....bb: Name of the definition file being analyzed
- cc....cc: Number of the record with the error
- S: Abnormally terminates.
- Action
- Revise the unit control information definition. On units where the standby-less system switchover (effects distributed) facility is being used, the operands that can be specified in the unit control information definition are restricted. Remove the operands that cannot be specified in the unit control information definition. Because the operands that were specified in error can be specified in the system common definition, specify them there as necessary, and then restart HiRDB.
KFPS05619-E E+L
Unable to execute aa....aa command,server bb....bb state not cc....cc
- The status of server bb....bb is not cc....cc. Therefore, the command cannot be executed.
- aa....aa: Name of the command that was input {pdstart | pdstop | pdxdsstart | pdxdsstop }
- bb....bb: Name of the server that could not execute the command
- cc....cc: Status that can enter the command
- OFFLINE: Offline
- ONLINE: Online
- S: Terminates processing.
- Action
- Wait for the status of server bb....bb to become cc....cc, then re-execute the command. However, the pdstart command cannot be executed in start status (including during start processing), and the pdstop command cannot be executed in stop status (including during stop processing). In this case, check that the system has stopped or started and then execute the command.
- If the pdxdsstart command is executed and this message is output, even though the XDS specified in the argument is offline, a previously-executed pdxdsstart command might have terminated abnormally or been terminated with the kill command. In that case, take corrective action by following these steps:
- Determine the status of the XDS from the XDS log or syslogfile. If message KFPQ80001-I was output, the XDS began starting without a problem.
- If you can verify that XDS is offline, execute pdxdsstop -s XDS-server-name -f.
- After execution of the pdxdsstop command, execute the pdxdsstart command.
- If the pdxdsstop command is executed and this message is output, even though the XDS specified in the argument is online, a previously-executed pdxdsstop command might have terminated abnormally or been terminated with the kill command. In that case, take corrective action by following these steps:
- Determine the status of the XDS from the XDS log or syslogfile. If message KFPQ80021-I was output, the XDS began stopping without a problem.
- If you can verify that XDS is online, execute pdxdsstop -s XDS-server-name -f.
- After execution of the pdxdsstop command, recover the database. For details about how to recover the database, see Using the memory database recovery facility to recover the database in the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPS05620-I L
Invalid version of HiRDB option, option=aaa, invalid version=bb....bb, required version=cc....cc
- The version of the additional PP aaa that has been set up is invalid. The version of the additional PP aaa that has been set up is bb....bb, and valid versions are cc....cc or later.
- aaa: Additional PP
- aha: Advanced High Availability
- bb....bb: Version of the additional PP that has been set up
- cc....cc: Correct version of additional PP
- S: Interrupts HiRDB start processing.
- O: This message provides additional information to the KFPS01801-E message that was output before this message. Check the additional PP name and the correct version of the additional PP, and follow the directions of the KFPS01801-E message.
KFPS05621-I L+S
Server aa....aa standby state released, status=bb....bb
- The standby state of server aa....aa has been released.
- aa....aa: Server name
- bb....bb: Server status code (maintenance information)
- S: Continues processing.
KFPS05622-E E
pdtrnqing command failed, reason=aa....aa, inf=bb....bb
- An error occurred during execution of the pdtrnqing command.
- aa....aa: Reason code
- bb....bb: Internal code
- S: Terminates processing.
- Action
- Take action on the basis of the reason code. If an error occurred during transaction queuing release, the transaction queuing status might remain unchanged. In that case, use the pdtrnqing -f command to release the transactions forcibly.
aa....aa (Reason code) | Action |
---|
NOT_HAGROUP | A server that is specified is not a target of the standby-less system switchover (effects distributed) facility. In the -s option, specify a back-end server that is a target of the standby-less system switchover (effects distributed) facility. |
NOT_ACTIVE | The server is not running on the command execution unit. Execute the command on the unit where the back-end server specified in the -s option is running. If performing a transaction queuing release specification, specify the -f option. |
TIMEOUT_S | When transaction queuing started, the system waited for transactions running on the back-end server or unit specified in the -s option to finish, but the transactions did not finish before the expiration of the wait time specified in the pd_ha_trn_queuing_wait_time operand in the system definition or the -t option of the pdtrnqing command. Terminate the transactions running on the back-end server or unit specified in the -s option, or use the pdcancel command to cancel them. In addition, revise the wait time specified in the pd_ha_trn_queuing_wait_time operand in the system definition or the -t option of the pdtrnqing command. |
TIMEOUT_E | During transaction queuing release, the system waited for server startup processing to finish, but the server startup processing did not finish before the time specified in the system definition pd_ha_trn_queuing_wait_time operand. Ensure that the server startup did not fail. If it failed, eliminate the cause of the error, and then start the server. Also, review the value of the system definition pd_ha_trn_queuing_wait_time operand. |
PROCESS_MEMORY | There is insufficient process native memory. Terminate unnecessary processes, reduce the memory in use in the server machine, and then re-execute the command. |
INVALID_UNIT | The pdtrnqing command cannot be executed in this system configuration. |
CANCEL | During transaction queuing start processing, the wait for the end of the transactions was canceled by one of the following commands:
- pdstop
- pdprgrenew
- pdchgconf
- pdtrnqing -d
If the cancellation was done with the pdstop, pdprgrenew, or pdchgconf commands, check and, if necessary, revise the operating procedures, including those for the pdtrnqing command. If cancellation was done with the pdtrnqing -d command, re-execute the pdtrnqing command if necessary. |
STOPPING | HiRDB is stopping. The pdtrnqing command cannot be executed while HiRDB is stopping. |
EXECUTING_UTILITY | A utility is executing. Terminate or cancel the utility, and then re-execute the pdtrnqing command. |
EXECUTING_ORG | Updatable online reorganization is executing. Re-execute the pdtrnqing command after updatable online reorganization has completed. |
EXECUTING_PDTRNQING | The pdtrnqing command cannot be executed because transaction queuing is starting. |
KFPS05623-I L
Online server not exist, unit=aa....aa
- There is no running system server in the unit. Unit start processing continued.
This message might be output when the standby-less system switchover (effects distributed) facility is used. - aa....aa: Unit name
- S: Continues processing.
- Action
- Use the cluster software commands to check the status of the servers in unit aa....aa. If the cluster software is HA monitor, use the monshow command; if it is Hitachi HA Toolkit Extension, use the hateshow command. Based on the result, take one of the following actions:
- If all servers on the unit are started as standby systems
No action is required.
- If a server is waiting to be activated as the running system server
Activate the running system server from any unit in the HA group. If using HA monitor, use the monact command; if using Hitachi HA Toolkit Extension, execute the command to activate the package from the upper level cluster software.
- If a server is activated as the running system server
The processing of commands specified in the usrcommand operand in the sysdef file of HA Monitor might take a long time. Consider increasing the value of the pd_ha_resource_act_wait_time operand.
KFPS05700-I L
HiRDB unit aaaa Security Audit bb....bb
- Indicates the status of the security audit facility when HiRDB (or unit, for a HiRDB/Parallel Server) starts.
- aaaa: Unit identifier
- bb....bb: Status of the security audit facility
- inactive: Does not start audit tracing from when the HiRDB system starts.
- S: Continues processing.
- Action
- Because HiRDB was forcibly started, the security audit facility is stopped. To enable the security audit facility, execute the pdaudbegin command. If it is acceptable that it is stopped, no action is necessary.
KFPS05701-E L
Unable to start Security Audit, unit=aaaa, reason code=bb....bb
- Audit tracing could not be started because an error occurred in unit aaaa.
- aaaa: Unit identifier
- bb....bb: Reason code
- S: Abnormally terminates the HiRDB system.
- Action
- Take appropriate action according to the reason code, and then restart the HiRDB system.
Reason code | Action |
---|
PROCESS_MEMORY | There is a shortage of process private memory. Re-estimate the process private memory. |
COMMUNICATION | A network error occurred. Recover from the network error. |
CONFIGURATION | An error occurred during analysis processing in the HiRDB system definition. See the definition analysis error message output before or after this message and re-evaluate the operand in the system definition. |
NO_FILE_NAME | The pd_aud_file_name operand is not specified. Specify the pd_aud_file_name operand. |
FILE_ACCESS | An error occurred when accessing the audit trace file. See the KFPS05704-E message output before or after this message, and then take appropriate action. |
KFPS05702-I L+S
aa....aa assigned as current audit trail generation file, unit=bbbb
- Audit trail file aa....aa is assigned to unit bbbb as the current file.
- aa....aa: Audit trail file name
- bbbb: Unit identifier
- S: Continues processing.
KFPS05703-I L+S
Audit trail generation file aa....aa released, unit=bbbb
- Audit trail file aa....aa for unit bbbb is no longer the current file.
- aa....aa: Audit trail file name
- bbbb: Unit identifier
- S: Continues processing.
KFPS05704-E E+L
aa....aa error occurred in audit trail generation file bb....bb, unit=cccc, reason code=dd....dd
- An error occurred when accessing audit trail file bb....bb for unit cccc.
- aa....aa: Processing when an error occurs:
- Open: Open the file.
- Close: Close the file.
- Read: Read the file.
- Write: Write the file.
- Create: Create the file.
- Delete: Delete the file.
- bb....bb: Audit trail file name
- Displays **************** when an access error of the HiRDB file system area for audit trace files occurs.
- cccc: Unit identifier
- dd....dd: Reason code
- S: Terminates processing.
- Action
- Take appropriate action according to the reason code, and then restart the HiRDB system.
Reason code | Action |
---|
PROCESS_MEMORY | There is a process private memory shortage. Re-estimate the process private memory. |
OPEN_MAX | The number of files opened by an open process for audit trace files exceeded the maximum number of files that can be opened. Re-evaluate the maximum number of files that can be opened by a single process. If necessary, re-create the kernel. |
FILE_PERMISSION | The user does not have access privileges for the HiRDB file system area for audit trace files. Check your access privileges using the operating system ls command or other command. If you do not have access privileges, ask the HiRDB administrator to grant you access privileges. |
IO_ERROR | An I/O error occurred. Action:
- Check for the cause of the I/O error, and then take appropriate action.
- Execute the pdaudrm command to delete the audit trace files that the I/O error generated. If some files cannot be deleted, continue working on the remaining files.
If this procedure does not solve the problem, replace the disk and re-create the HiRDB file system area for audit trail files. |
VERSION | The version of the HiRDB file system area for audit trail files does not match. To re-create the HiRDB file system area for audit trail files, execute the pdfmkfs command. To restore the previous version after upgrading HiRDB and restarting, return the HiRDB file system area for audit trail files to the previous version. To restore the pre-upgrade version, use the pdfrstr command on the HiRDB file system area for audit trail files that was backed up using the pdfbkup backup command before the upgrade. |
GEN_FILE_PERMISSION | You do not have access privileges to the audit trail file. To check your access privileges to audit trail files, execute the pdfls command. If you do not have access privileges, request that the HiRDB administrator grants you access privileges. |
FILE_NOT_FOUND | The audit trail file does not exist. When the error process is not Delete:
- Check if the HiRDB file system area for audit trail files was created. If the area was not created, execute the pdfmkfs command to create the HiRDB file system area for audit trail files.
- Check if the created HiRDB file system area for audit trail files and the HiRDB file system area name specified in the pd_aud_file_name operand match.
- Check if the audit trail file name specified in the control statement file when the pdload command was executed is correct.
When the error process is Delete:
- Check if the HiRDB file system area for audit trail files was created.
- Check if the created HiRDB file system area for audit trail files and the HiRDB file system area name specified in the pd_aud_file_name operand match.
|
GEN_FILE_NOT_FOUND | - The audit trail file does not exist. To check if the audit trail file exists, execute the pdls -d aud command.
- To check if the audit trail file name specified in the control statement file during command execution is correct, execute the pdload command.
|
LOCKSEGMENT | There is a lock segment shortage. Re-evaluate the number of record lock segments specified when performing a system build of the OS. |
NO_SPACE | The free space required to create audit trail files could not be secured. Re-estimate the size of the HiRDB file system area for audit trail files. |
FILE_TYPE | The HiRDB file system area for audit trail files was not created in character special files. To create HiRDB file system areas in character special files, execute the pdfmkfs file. |
FILE_OBJECT | The usage objective (-k option of the pdfmkfs command) of the HiRDB file system area for audit trail files is not SYS or SVR. Specify SYS or SVR in the -k option of the pdfmkfs command, and then re-create the HiRDB file system area. |
FILE_AREA | The area for audit trail files was not created as a HiRDB file system area. Create a HiRDB file system area for audit trail files by executing the pdfmkfs command. |
LARGE_FILE | The possible causes are as follows:
- The HiRDB file system area for audit trail files was created as a large file (if the HiRDB server is the Windows edition, a HiRDB file system area of 2,048 MB or greater), but N is specified in the pd_large_file_use operand.
- The HiRDB file system area for audit trail files was created by the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.
Specify Y for the pd_large_file_use operand, or omit the specification. |
FILE_NUM | The maximum number of audit trail files that can be created was exceeded. Action:
- Re-evaluate the value of the pd_aud_max_generation_num operand.
- Re-create the HiRDB file system area for audit trail files by executing the pdfmkfs command. Re-estimate the maximum file count in the HiRDB file system and the area size. To change the maximum file count or the area size, re-evaluate the value of the pd_aud_max_generation_num and pd_aud_max_generation_size operands.
|
INTERNAL_ERROR | An internal error occurred. Save all files under C:\PDDIR\spool, save the event log (in UNIX, syslogfile), and contact the customer support center. |
INVALID_SYSTEM_ID | The HiRDB identifier of the audit trail file is invalid. Specify an audit trail file whose HiRDB identifier is valid. |
KFPS05705-E L
Available audit trail generation file number=a. HiRDB unit bbbb force terminate
- The number of audit trail files available for use as the swap destination is 0 or 1. unit bbbb was forcibly terminated because down is specified in the pd_aud_no_standby_file_opr operand.
- a: Number of audit trail files that are available for use as the swap destination
- bbbb: Unit identifier
- S: Abnormally terminates HiRDB.
- Action
- For details about how to work with audit trail files, see the HiRDB Version 9 System Operation Guide.
KFPS05706-W L
No standby audit trail generation file available, unit=aaaa. Force overwrite audit trail generation file
- There are no audit trail files in unit aaaa that are available for use as the swap destination. The data load standby file (excluding files in shutdown status) with the earliest update date/time is made available as the swap destination because forcewrite (default value) is specified in the pd_aud_no_standby_file_opr operand.
- aaaa: Unit identifier
- S: Continues processing.
- Action
- Request that the auditor load the data of data load standby audit trail files. For details about how to work with audit trail files, see the HiRDB Version 9 System Operation Guide.
KFPS05707-E L
Error occurred in all audit trail generation files, unit=aaaa. Security Audit stopped
- forcewrite (default value) is specified in the pd_aud_no_standby_file_opr operand, but output of the audit trail was stopped because all audit trail files in the HiRDB file system area were shut down.
- aaaa: Unit identifier
- S: Continues processing.
- Action
- For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.
KFPS05708-W E+L
Unable to use Security Audit, unit=aaaa, reason code=bb....bb
- The security audit facility could not be used because the system configuration does not meet the preconditions of the security audit facility.
- If there is a unit (including units with just a system manager) on the HiRDB/Parallel Server with no server, the security audit facility cannot be used.
- Cannot use the security audit facility in the utility special unit.
- aaaa: Unit identifier
- bb....bb: Reason code
- ONLY_SYSTEM_MANAGER: Cannot use the security audit facility because only the system manager is defined in the unit.
- NO_SERVER: Cannot use the security audit facility because no server is defined in the unit.
- UTILITY: Cannot use the security audit facility because the current unit is not a utility special unit.
- S: Continues processing.
- Action
- When using the security audit facility, change the system configuration.
KFPS05709-E E+L
Internal function error occurred, unit=aaaa, function=bb....bb, return code=cc....cc
- An internal processing error occurred in unit aaaa.
- aaaa: Unit identifier
- bb....bb: Name of function where the error occurred
- cc....cc: Detail code of a system-related error.
- S: Terminates processing.
- Action
- Take action according to the detail code of an output system-related error. For detail codes of system-related errors, see 4.2 Detail codes for system-related errors. Contact the customer support center for errors that cannot be solved.
KFPS05710-I L
Auto audit trail loading service status=aa....aa
- The execution status of the facility for automatically loading the audit trail table data is aa....aa.
- aa....aa: The execution status of the facility for automatically loading the audit trail table data
- ENABLE: Operating
- DISABLE: Stopped
- Note that if it was started using pdstart -r, DISABLE is normally displayed.
- S: Continues processing.
KFPS05711-I L+S
Auto audit trail loading service restart
- The facility for automatically loading audit trail table data is restarting.
- S: Continues processing.
KFPS05712-I L+S
Auto audit trail loading service stopped
- The facility for automatically loading audit trail table data stopped.
- S: Continues processing.
KFPS05713-E L
Auto audit trail loading service stopped, because of loading error occurred
- An error occurred during loading, so the facility for automatically loading audit trail table data stopped.
- S: Continues processing.
- Action
- Refer to the message that was output directly prior to this message, investigate the reason why an error occurred while data was being loaded to the audit trail table, and take corrective action. After taking action, if you want to restart the automatic data load facility, execute the pdaudatld -b command.
KFPS05714-I L
Audit trail generation file loading started, unit=aaaa
- Loads the audit trail file of unit aaaa to the audit trail table.
- aa....aa: Unit identifier of the unit with the audit trail file
- S: Continues processing.
KFPS05715-I L
Audit trail generation file loading ended, unit=aaaa
- The audit trail file of unit aaaa was loadedto the audit trail table.
- aa....aa: Unit identifier of the unit with the audit trail file
- S: Continues processing.
KFPS05716-W L
Audit trail generation file loading failed, unit=aaaa; continue processing
- Loading of the audit trail file of unit aaaa to the audit trail table failed. Re-execute load processing.
- aa....aa: Unit identifier of the unit with the audit trail file
- S: Continues processing.
KFPS05717-W L
Error occurred while starting pdload command, reason code=aa....aa
- The pdload command failed to start.
- aa....aa: Reason code
- FORK FAILED: A process fork failed.
- MEMORY: A memory shortage occurred.
- PARAMETER ERROR: Parameter generation failed.
- S: Use a set time interval (pd_aud_auto_loading_retry_intvl specification) at which to retry starting pdload.
- Action
- Take appropriate action according to the reason code.
aa....aa (reason code) | Action |
---|
FORK FAILED | Re-examine the quantity of memory used and the number of processes. |
MEMORY | Re-examine the quantity of memory used. |
PARAMETER ERROR | An internal conflict was detected, so contact the customer support center. |
KFPS05718-W L
Audit trail generation file loading skipped, unit=aaaa, status=bb....bb
- Skips the loading of the audit trail file of unit aaaa into the audit trail table.
- aaaa: Unit identifier of the unit with the audit trail file
- bb....bb: Operational status of the unit with the audit trail file
- STARTING: In the process of starting
- STOPPING: In the process of stopping
- STOP: Stopped (for all cases of normal termination, forced termination, and abnormal termination)
- NO_SERVER: No operating server (Servers in the unit have all stopped, or running system servers do not exist in units to undergo standby-less system switchover (effects distributed).)
- S: Continues processing.
- Action
- If bb....bb is STARTING, STOPPING, or STOP:
- Use the pdls -d svr command to check the status of the corresponding unit, and if it has stopped, restart the unit. If it is operating, there is a chance that a network error occurred between the MGR unit and the corresponding unit. Therefore, resolve the network error.
- If the corresponding unit was changed during operation (ACTIVE shown in pdls -d svr command), loading of the audit trail file that was skipped is re-scheduled.
- If bb....bb is NO_SERVER:
- Restart the server by executing the pdstart -s command for one or more servers from among the servers that have stopped on unit aaaa. If unit aaaa is the object of standby-less system switchover (effects distributed), execute the system switchover or the pdstart -s command to start up one or more running systems in unit aaaa. Once the server starts up, loading of the audit trail file that was skipped is re-scheduled.
KFPS05719-W L+S
Now waiting for termination of audit trail generation file loading process
- Waiting for audit trail table load processing to finish.
- S: Continues processing.
- Once the process of loading to the audit trail table is finished, the KFPS05720-I message is displayed and command processing continues.
KFPS05720-I L+S
Audit trail generation file loading process complete
- Audit trail table load processing is finished.
- S: Continues processing.
KFPS05721-W L+S
Audit trail generation file loading process error occurred
- An error occurred during audit trail table load processing.
- S: Continues processing.
- Action
- Refer to the message that was output directly prior to this message to determine which error occurred during audit trail table load processing. Take corrective action if necessary.
KFPS05722-E L
Audit trail buffer full occurred. HiRDB unit aaaa force terminate
- Output processing of the audit trail is centralized, and all segments of the asynchronous output buffer of the audit trail are in a flush waiting state. Because down is specified in the pd_aud_no_standby_file_opr operand in the system common definition, forcibly terminate HiRDB (for HiRDB/Parallel Servers: the unit).
- aaaa: Forced termination unit identifier
- S: Terminates abnormally.
- Action
- Re-examine the size and segment count of the asynchronous output buffer of the audit trail.
If the size and segment count of the asynchronous output buffer is smaller than the output count of the audit trail per unit of time, increase the specification value of the pd_aud_async_buff_size and pd_aud_async_buff_count operands in the HiRDB system definition.
- If there is a heavy load on the machine or network, decrease the load.
- If a network error occurred, resolve the network error.
- For details, see When all sectors of the asynchronous output buffer are placed in flush-wait status in the HiRDB Version 9 System Operation Guide.
KFPS05723-W L
Audit trail buffer full occurred, unit=aaaa. Force overwrite audit trail buffer
- Output processing of the audit trail is centralized, and all segments of the asynchronous output buffer of the audit trail are in a flush waiting state. Because forcewrite is specified in the pd_aud_no_standby_file_opr operand in the system common definition, the audit trail of the asynchronous output buffer that was initially waiting for flush is discarded.
- aaaa: Forced termination unit identifier
- S: Continues processing.
- Action
- HiRDB processing continues, but because the audit trail was discarded and lost, take the following corrective actions.
- Re-examine the size and segment count of the asynchronous output buffer of the audit trail.
If the size and segment count of the asynchronous output buffer is smaller than the output count of the audit trail per unit of time, increase the specification value of the pd_aud_async_buff_size and pd_aud_async_buff_count operands in the HiRDB system definition.
- If there is a heavy load on the machine or network, decrease the load.
- If a network error occurred, resolve the network error.
- For details, see When all sectors of the asynchronous output buffer are placed in flush-wait status in the HiRDB Version 9 System Operation Guide.
KFPS05724-E L
No standby audit trail generation file available, unit=aaaa
- No audit trail generation files available in unit aaaa.
- aaaa: Unit identifier
- S: Continues processing.
- Action
- Take corrective action based on the KFPS05725-W message that was output after this message.
KFPS05725-W L
Security Audit stopped, unit=aaaa. Continues HiRDB unit start processing
- The security audit facility stopped, but start processing of the HiRDB unit continues.
- aaaa: Unit identifier
- S: Continues processing.
- Action
- Unit start processing is completing, but the audit trail cannot be acquired because the security audit facility has stopped. Contact the auditor to load the data from the pending audit trail file into the audit trail table. After the data has been loaded, use the pdaudbegin command to restart the security audit facility.
- Because an audit trail cannot be acquired, until the security audit facility resumes, do not execute any transactions or commands other than loading data into the audit trail table.
- For details, see When an error occurs in an audit trail file in the HiRDB Version 9 System Operation Guide.
KFPS05750-I S
Security Audit aaaaaaa, unit=bbbb
- Acquisition of audit trails of unit bbbb started or stopped.
- aaaaaaa: Status of audit trails
- started: Acquisition of audit trails has started.
- stopped: Acquisition of audit trails has stopped.
- bbbb: Unit identifier
- S: Continues processing.
KFPS05751-I E+S
Usage: aa....aa
- Indicates the usage of the aa....aa command at the HiRDB/Single Server. This message is output when an error is found in the command format.
- aa....aa: Usage of the command
- pdaudbegin
- pdaudend
- pdaudrm -g audit_generation_file_name [-f]
- pdaudswap [-U user_id]
- pdaudatld [-b|-t|-i] [-U user_id]
- S: Terminates processing.
- Action
- Re-execute the command.
KFPS05751-I E+L
Usage: aa....aa
- Indicates the usage of the aa....aa command at the HiRDB/Parallel Server. This message is output when an error is found in the command format.
- aa....aa: Usage of the command
- pdaudbegin [-u unit_id]
- pdaudend [-u unit_id]
- pdaudrm -u unit_id -g audit_generation_file_name [-f]
- pdaudswap -u unit_id [-U user_id]
- pdaudatld [-b|-t|-i] [-U user_id]
- S: Terminates processing.
- Action
- Re-execute the command.
KFPS05752-E E+L
Error occurred during aa....aa command execution, unit=bbbb, reason code=cc....cc
- An error occurred when executing the aa....aa command.
- aa....aa: Command name
- pdaudbegin
- pdaudend
- pdaudrm
- pdaudswap
- pdls -d aud
- pdaudatld
- bbbb: Unit identifier when an error occurred
- cc....cc: Reason code indicating the type of failure
- S: Terminates processing.
- Action
- Take action according to the reason code.
Reason code | Action |
---|
ALREADY_STARTED | Acquisition of audit trails has already started. |
COMMUNICATION | A network error occurred. Recover from the network error. |
CONFIGURATION | An error occurred during analysis processing in the HiRDB system definition. See the definition analysis error message output before or after this message and re-evaluate the operand in the system definition. |
PROCESS_MEMORY | There is a process private memory shortage. Re-estimate the process private memory. |
ALREADY_STOPPED | Already stopped acquiring audit trails. |
DELETE_ERROR | The audit trail file could not be deleted because it is in one of the following statuses:
- It is not locked
- It is waiting for data loading
- It has not been generated yet
To check the status of the audit trail files, execute the pdls -d aud command. Files that are not locked or generated cannot be deleted. To delete files waiting for data loading, execute the pdaudrm command with the -f option specified. |
NOT_AUDITOR | Check the auditor's authorization identifier and password. If the command pdls -d aud was executed, check the status of HiRDB. If HiRDB is running, only the auditor can execute the command pdls -d aud, unless HiRDB was started by the pdstart -r command, in which case the command pdls -d aud cannot be executed at all. If HiRDB is not running, only the HiRDB administrator can execute the command pdls -d aud. |
UNABLE_SWAP | One remaining file cannot be made the swap destination because pd_aud_no_standby_file_opr=down is specified. Action:
- Request that the auditor load data for the audit trail files that are waiting for data loading.
- For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.
|
NO_STANDBY_FILE | An attempt to swap failed because no files can be made into the swap destination. Action:
- Request that the auditor load data for the audit trail files that are waiting for data loading.
- For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.
|
NO_GEN_FILE | Swap processing could not be performed on the audit trail files because no audit trail files were created. |
OTHER_COMMAND | The command could not be executed because another command (pdaudbegin, pdaudend, pdaudrm, pdaudswap, or pdaudatld) is executing. Re-execute the command after the other command terminates. |
SECURITY_AUDIT_NOT_UP | An audit trail was not acquired. Execute the command when acquiring audit trails. |
FILE_ACCESS | An error occurred when accessing an audit trail file. See the KFPS05704-E message output before or after this message, and then take appropriate action. An attempt was made to delete an audit trail file, but it was a file that failed to be created due to a shortage of space. If an attempt was made to use the pdaudrm command to delete an audit trail file that failed to be created due to a shortage of space, this message is output but no action is required. When HiRDB starts normally, this file will not be displayed by the command pdls -d aud. If necessary, revise the space for audit trail files and the system definition values related to the space for audit trail files to prevent a shortage of space from occurring. |
UNIT_NOT_ONLINE | The target unit for the command is inactive. Execute the command after starting the unit. |
NO_FILE_NAME | The pd_aud_file_name operand is not specified. Specify the pd_aud_file_name operand. |
UTILITY | The security audit facility could not be used because the unit is a utility special unit. |
ONLY_SYSTEM_MANAGER | The security audit facility could not be used because only the system manager is defined in the unit. When using the security audit facility, change the system configuration. |
NO_SERVER | The security audit facility could not be used because the server is not defined in the unit. When using the security audit function, change the system configuration. |
LOCK | A lock error occurred when executing the command. Wait for a short time, and then re-execute the command. |
NO_AVAILABLE_GEN_FILE | An audit trail file available for use as the swap destination could not be found. Take the following action to secure an audit trail file that can be available for use as the swap destination. Then, restart HiRDB.
- Request that the auditor load the data for files waiting for data loading into the audit trail table.
- For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.
|
RESTORE_MODE | The following commands cannot be executed because HiRDB was started with the pdstart -r command:
- pdaudswap
- pdls -d aud
- pdaudatld
|
AUTO_LOADING_NOT_SETUP | The facility for automatically loading audit trail table data cannot be used. To use the facility for automatically loading audit trail table data, the pd_aud_auto_loading operand must be set to Y. Set the pd_aud_auto_loading operand to Y, and then restart HiRDB. |
AUTO_LOADING_ALREADY_RUNNING | The facility for automatically loading audit trail table data is already running. If you want to terminate the facility for automatically loading audit trail table data, execute the pdaudatld -t command. |
AUTO_LOADING_STOPPING | The facility for automatically loading audit trail table data is in the process of stopping. If you want to start the facility for automatically loading audit trail table data, wait until stop processing has completed, and then execute the pdaudatld -b command. |
AUTO_LOADING_ALREADY_STOPPED | The facility for automatically loading audit trail table data is already stopped. If you want to start the facility for automatically loading audit trail table data, execute the pdaudatld -b command. |
TIME_OUT | There was a timeout while the facility for automatically loading audit trail table data was restarting. Because the facility for automatically loading audit trail table data cannot be restarted, execute the pdaudatld -i command and make sure that there are no units performing automatic data loading. After that, use the pdaudatld -b command to restart the facility for automatically loading audit trail table data. If there is a unit performing automatic data loading, wait for the automatic data loading to finish, and then restart the facility for automatically loading audit trail table data. |
KFPS05753-W L
Unable to read audit trail generation file=aa....aa, unit=bbbb
- The version of the audit trail file does not match the version of HiRDB being used. Therefore, part or all of the information in the audit trail file is not reflected in the audit trail table.
- aa....aa: Audit trail file name
- bbbb: Unit identifier
- S: Continues processing.
- Action
- If, after a HiRDB version upgrade, there is a return to the previous version, part or all of the information collected to the audit trail file after the upgrade is not reflected in the audit trail table. To make sure all of the information is reflected, contact the customer support center.
KFPS05801-I S
Usage: pdvrchk -x host_name -d directory_name
- The specification format of the pdvrchk command option is invalid.
- S: Terminates processing.
- Action
- Correct the option specification, and then re-execute the command.
KFPS05802-E S
Error occurred in execute pdvrchk command, reason_code = aa(bb....bb,cc....cc,dd....dd)
- An error occurred during execution of the pdvrchk command.
- aa: Error code
- bb....bb: Internal information of the HiRDB system
- cc....cc: Internal information of the HiRDB system
- dd....dd: Internal information of the HiRDB system
- S: Terminates processing.
- Action
- Take action according to the error cause.
Error code | Error cause | Action |
---|
01 | The environment variable PDDIR was not found. | Set environment variable PDDIR in the environment of the person executing this command, and then re-execute the command. |
02 | An error occurred in the remote shell regarding the host name specified in the -x option. Possible causes:
- The HiRDB directory specified in the -d option was not found.
- The network of the host specified in the -x option was not found.
- The host name specified in the -x option is invalid.
| Use the execution results of ping or other similar utility to determine if the network for the specified host is active. Alternatively, check if the HiRDB directory specified in the -d option or the host name specified in the -x option is correct. |
03 | Internal processing error | Take action according to the message output before this message, and then re-execute the command. |
KFPS05803-I S
pdvrchk ended, return code = aa....aa
- The pdvrchk command terminated with return code aa....aa.
- aa....aa: Return code of the command
- S: Terminates processing.
- Action
- Take appropriate action according to the return code.
Return code | Description | Action |
---|
0 | Version information and additional options between the command execution source server machine and the target server machine match. | Not necessary. |
8 | Version information and additional options between the command execution source server machine and target server machine do not match. | Unify the versions of the HiRDB and installed option program product. With HiRDB Advanced High Availability, some version information, additional option comparison source, and configurations of the target unit are displayed as a mismatch (comparing units of the system manager and units of the back-end server). |
12 | An error occurred during execution of the command (including command argument errors). | Take action according to the KFPS05801-I, KFPS05802-E or other message output before this message. |
KFPS05809-I S
Usage: pdriseset [{-P|-S|-D} [-f]]
- The option specification format of the pdriseset command is invalid.
- S: Terminates processing.
- Action
- Specify valid options, and then re-execute the command.
KFPS05810-I E+L+S
Usage: pdrisechk [-d {all|db|sys}] [{-u unit_id|-s server_name}] [-l [-n]] [-r]
- The specification format of the pdrisechk command options is incorrect.
- S: Terminates processing.
- Action
- Specify valid options and re-execute the command.
KFPS05813-E E
Unable to execute aa....aa command, reason bb....bb
- Execution of aa....aa command failed.
- aa....aa: Name of the command that could not be executed
- bb....bb: Reason that it could not be executed
- pd_rise_use is not 'Y': Y is not specified in the pd_rise_use operand.
- NEED TO SPECIFY pd_rise_pairvolume_combination: The pd_rise_pairvolume_combination operand was not specified, or the specified value is invalid.
- NEED TO SPECIFY pd_rise_fence_level: The pd_rise_fence_level operand was not specified, or the specified value is invalid.
- UNABLE TO SPECIFY pd_inner_replica_control: The pd_inner_replica_control operand cannot be specified.
- secondary system: Operands that cannot be specified for a secondary system were specified.
- ONE_UNIT: HiRDB/Parallel Server cannot execute in a single-unit system configuration.
- S: Terminates processing.
- Action
- If bb....bb is not secondary system or ONE_UNIT:
- Check the system common definition, revise the system common definition, and then re-execute the command.
- If bb....bb is a secondary system:
- If a system switchover facility is being used, check the system where the command was executed, and execute the command on the primary system. If this message was output when the command was executed on the primary system, revise the specification of the pd_hostname operand. If the pd_hostname operand specifies other than the standard host name of the primary system, specify the standard host name of the primary system.
- If bb....bb is ONE_UNIT:
- To forcibly terminate the single-unit configuration HiRDB system on the HiRDB/Parallel Server, execute the pdstop -f command.
KFPS05814-I S
Usage: pdrisedbto [-f]
- The option specification format of the pdrisedbto command is invalid.
- S: Terminates processing.
- Action
- Specify valid options, and then re-execute the command.
KFPS05815-I S
"pdrisechk" ended, end code=aa....aa
- The pdrisechk command terminated with termination code aa....aa.
- aa....aa: Command termination code
- S: Terminates processing.
- O: Follow the action appropriate to the termination code.
- Action
- Follow the action appropriate to the termination code.
Command termination code | Explanation | Operator action | HiRDB administrator action |
---|
OK | The pdrisechk command terminated normally. The pair volume setting is invalid. | -- | -- |
INVALID_PAIR_SETUP | The pair volume setting used by HiRDB is invalid. | Contact the HiRDB administrator. | See the KFPS05816-E message, and correct the invalid pair volume setting. |
ERROR_SOME_UNIT | During execution of the pdrisechk command, an error occurred during a unit's configuration check. | See the message output before this message and take action, then re-execute the command. If necessary, contact the HiRDB administrator. | See the message output before this message and take action, then re-execute the command. |
- Legend:
- --: Not applicable.
KFPS05816-E E
Invalid volume setup. aa....aa, file type=bb....bb, group=cc....cc, code=dd....dd
- The pair setting of pair logical volume group cc....cc is invalid.
- aa....aa: Depending on the HiRDB file type allocated to the pair logical volume group where there is a problem with the pair setting, the output is in the following format:
- bb....bb is DB, LOG, SPD, or SSTS:
- server=ee....ee
- ee....ee: HiRDB server name
- bb....bb is USTS:
- unit=ffff
- ffff: Unit identifier
- bb....bb is ALL:
- system=gggg
- gggg: HiRDB identifier
- bb....bb: File type created in pair logical volume group cc....cc
- DB: Database file (file that comprises the RDAREA)
- LOG: System log file
- SPD: Synchronization point dump file
- SSTS: User status file
- USTS: Unit status file
- ALL: Database file and system files
- cc....cc: Name of the pair logical volume group
- dd....dd: Reason code
- S: Terminates processing.
- O: Take action appropriate to the reason code.
- Action
- Take action appropriate to the reason code.
Reason code | Explanation | HiRDB administrator action |
---|
INVALID_VOLUME_ATTRIBUTE | The pair attribute of the corresponding pair logical volume group is invalid. | Confirm that the site where the command was executed is correct. Confirm that the pair attribute of the corresponding pair logical volume is valid. Also, if no pair logical volume group has been created, create a pair logical volume group. |
INVALID_FENCE_LEVEL | The fence level setting of the corresponding pair logical volume group is invalid. | Take one of the following actions:
- If the value of the pd_rise_pairvolume_combination operand is sync, set the value of the pair volume group fence level to data or never, to match the value of the pd_rise_fence_level operand.
- If the value of the pd_rise_pairvolume_combination operand is hybrid and DB is displayed in bb....bb, set the value of the pair volume group fence level to async.
If other than DB is displayed in bb....bb, set the value of the pair volume group fence level to data or never, to match the value of the pd_rise_fence_level operand.
- If the value of the pd_rise_pairvolume_combination operand is async, set the value of the pair volume group fence level to async.
- If the value of the pd_rise_pairvolume_combination operand is syssync, set the fence level of the pair logical volume to data or never to match the specification of the pd_rise_fence_level operand.
|
INVALID_STATUS | A pair with a pair status of other than PAIR or PFUL exists in the corresponding pair logical volume group. | Check the pair status of the corresponding pair logical volume group, check the reason that it became that pair status, and take appropriate action. For details on the how to check the reason and take action, see the RAID Manager documentation. |
KFPS05821-E E+L
Unable to specify hostname or server name outside HAGROUP
- The error is one of the following:
- The specified host name (unit identifier) or server name is not a host (unit) or server that is applicable to the standby-less system switchover (effects distributed) facility.
- The specified host (unit) and the server belong to different HA groups.
- S: Terminates processing.
- Action
- Make sure that the specified host name (unit identifier) and server name belong the same HA group, and then re-execute the command.
KFPS05822-E E
aa....aa invalid; stops server restart.server ID=bb....bb, old value=cc....cc,new value=dd....dd
- Because the value specified for the aa....aa operand has changed, the server cannot be restarted. The value of the aa....aa operand cannot be changed after abnormal termination, forced termination, or planned termination.
- aa....aa: Definition items that do not match
- "pd_utl_exec_mode": Utility execution mode
- "pd_max_list_users": Number of users that can own the list concurrently
- "pd_max_list_count": Number of lists created per user
- "pd_max_reflect_process_count": Number of processes to be allocated for reflection processing
- "pd_max_users": Maximum number of concurrent connections (SDS, FES)
- "pd_max_bes_process" or "pd_max_users": Maximum number of startup processes (BES)
- "pd_max_dic_process" or "pd_max_users": Maximum number of startup processes (DS)
- bb....bb: Server name (if the aa....aa operand is the system common definition or the unit control information definition, ******** is displayed)
- cc....cc: Value before the aa....aa operand was changed
- dd....dd: Value after the aa....aa operand was changed
- S: Terminates processing.
- Action
- Return the value of the aa....aa operand to the value before the change (cc....cc) and restart the server. However, if any of the following operands was output in the aa....aa operand, make it as follows:
- If "pd_max_bes_process", "pd_max_dic_process", or "pd_max_users" was output, and the pd_max_bes_process or pd_max_dic_process operand is not specified, change the value of pd_max_users.
- If "pd_max_bes_process", "pd_max_dic_process", or "pd_max_users" was output, and the pd_max_bes_process or pd_max_dic_process operand is specified, make it as follows:
- cc....cc > value specified for pd_max_users:
- Change the value of the pd_max_bes_process or pd_max_dic_process operand.
- cc....cc
value specified for pd_max_users: - If cc....cc > value of pd_max_bes_process or pd_max_dic_process, change the value of pd_max_users.
- If cc....cc
value of pd_max_bes_process or pd_max_dic_process, change the value of the pd_max_users, pd_max_bes_process, or pd_max_dic_process operand.
KFPS05827-E E+L
Unable to stop server outside HAGROUP with "aa....aa" option
- The "aa....aa" option cannot be specified in the pdstop -s server_name command for servers that are not used with the standby-less system switchover (effects distributed) facility.
- aa....aa: Specified option {-x host_name | -u unit_id} -z
- S: Terminates processing.
- Action
- If the specified option is -x host_name or -u unit_id:
- Reconsider the specification of the command options. If stopping a server that is not used with the standby-less system switchover (effects distributed) facility, execute the command without specifying the -x host_name or -u unit_id option.
- If the specified option is -z:
- Reconsider the specification of the command options. Servers other than those that use the standby-less system switchover (effects distributed) facility cannot be forcibly terminated. To terminate them, use normal termination (execute the pdstop -s server_name command from the unit that contains the system manager).
KFPS05828-E S
Unable to stop normally because server terminated abnormally
- HiRDB cannot be normally terminated because there are servers that were abnormally terminated or that were forcibly terminated with the pdstop -f or pdstop -z command.
- S: Terminates processing.
- Action
- Use one of the following methods to terminate HiRDB:
- Use the pdls command to check servers that were abnormally terminated or that were forcibly terminated using the pdstop -f or pdstop -z command, start the servers, and then normally terminate them using the pdstop command.
- Use the pdstop -f command to forcibly terminate HiRDB.
KFPS05829-E E
Unable to stop, reason code=aa....aa
- Normal termination or planned termination of HiRDB cannot be performed.
- aa....aa: Reason termination cannot be executed
- resident RDAREA exists: There is an in-memory RDAREA.
- XDS exists: XDS is operating.
- S: Terminates processing.
- Action
- When aa....aa is resident RDAREA exists:
- Release in-memory allocation and then re-execute the pdstop command. If you want to terminate HiRDB before releasing in-memory allocation, use the pdstop -f command to forcibly terminate HiRDB.
- If aa....aa is XDS exists:
- Stop XDS and then re-execute the pdstop command. If you want to terminate HiRDB before stopping XDS, use the pdstop -f command to forcibly terminate HiRDB. In this case, data in the XDS memory cannot be recovered.
KFPS05837-I E
Usage: pdtrnqing {[-d|-t wait_time]|[-d [-f]][-t wait_time]-s server_name}
- Displays how to use the pdtrnqing command. This message is displayed in the following circumstances:
- The pdtrnqing command was specified with the -h option.
- An option or argument to the command was specified incorrectly.
- S: Terminates the pdtrnqing command.
- O: If there is an error in the usage of the command, re-enter the command correctly.
KFPS05839-I E
Usage: pdstjsync [-m]
- The specification format of the pdstjsync command options is invalid.
- S: Terminates processing.
- O: Re-execute on the basis of the command usage method.
KFPS05840-I S
Statistics log written, from statistics log buffer to statistics log file
- Information in the statistics log buffer was output to the log file.
- S: Continues processing.
KFPS05841-E S
pdstjsync command failed, readson=a....a
- Information in the statistics log buffer could not be output to the log file.
- aa....aa: Reason code that indicates the contents of the error
- ALREADY_STOPPED: Statistical information is already stopped.
- S: Terminates processing.
- Action
- ALREADY_STOPPED:
- Execute this command during statistical information acquisition.
KFPS05842-I E
Usage: pdsvhostname -s server_name [-b]
- The specification format of the pdsvhostname command options is invalid.
- S: Terminates the pdsvhostname command.
- Action
- If there is an error in the command usage method, re-execute using a correct usage method.
KFPS05843-E E
Invalid environment variable aa....aa, reason code=bb....bb
- The value of an environment variable is incorrect.
- aa....aa: Environment variable name {PDDIR|PDCONFPATH}
- bb....bb: Reason code
- NOTHING: No environment variable is set.
- INVALID_LENGTH: The value set for the environment variable exceeds the limit.
- S: Terminates processing.
- Action
- Refer to the reason code, and confirm that the environment variable is set appropriately.
KFPS05844-E L
Unable to recognize stop HiRDB units by force
- Completion of forced termination processing of the HiRDB unit cannot be confirmed.
- S: Terminates processing.
- Action
- Re-execute the pdstart -R command or the pdstart -R -t command.
- If the situation does not change, use the following procedure to terminate all non-MGR units.
- Execute the pdls -d ust command.
- If the status of the unit (UNIT_STAT) is STARTING, ONLINE, or STOPPING, run the pdstop -z command, and forcibly terminate non-MGR units.
If the status of the unit is other than any of those mentioned above, terminate the non-MGR units.
KFPS05901-W L
pdprfd service failed. pid=aa....aa
- The troubleshooting information collection process (pdprfd) terminated abnormally. As a result, collection of performance trace information was terminated.
- aa....aa: Process ID
- S: Terminates processing.
- Action
- Check whether any error messages were output before this message. In addition, make sure no disk I/O errors have occurred. To restart collection of performance trace information, terminate HiRDB and then restart it.
KFPS05902-W L
Unable to start pdprfd service. detail code=aa....aa
- The troubleshooting information collection process (pdprfd) could not be started. As a result, collection of performance trace information was terminated.
- aa....aa: Maintenance information
- S: Terminates processing.
- Action
- Check whether any error messages were output before this message. In addition, make sure that no disk I/O errors have occurred. To restart collection of performance trace information, terminate HiRDB, and then restart it.
KFPS05903-I L
PRF trace started. level=aaaaaaaa
- Collection of performance trace information started.
- aaaaaaaa: Performance trace collection level
- S: Continues processing.
KFPS05904-I S+L
PRF level changed. before=aaaaaaaa, after=bbbbbbbb
- The performance trace collection level changed from aaaaaaaa to bbbbbbbb.
- aaaaaaaa: Performance trace collection level before the change
- bbbbbbbb: Performance trace collection level after the change
- S: Continues processing.
KFPS05905-I E+S
Usage: aa....aa
- Indicates how to use the aa....aa command.
- aa....aa: How to use the command (displays one of the following)
- pdprflevel [-l prf_level]
- pdprfed [-T begin_time,end_time] [-p pid[,pid]...] [-e event_id[,event_id]...] [-H] prf_file_name
- S: Continues processing.
- O: Specify the correct options and re-execute the command.
KFPS05906-E E
pdprfd service has been stopped. command=aa....aa, detail code=bb....bb
- The troubleshooting information collection process (pdprfd) has stopped.
- aa....aa: Command name
- pdprflevel
- bb....bb: Maintenance information
- S: Terminates processing.
- Action
- Take the corrective action indicated in the following, and then execute the command:
- If message KFPS05901-W is output and the pdprfd process has stopped, terminate and restart HiRDB to restart collection of performance trace information.
- If the performance trace facility was disabled by specifying N in the pd_prf_trace operand in the system definition, enable the performance trace facility by specifying Y in the pd_prf_trace operand, or by omitting the pd_prf_trace operand.
KFPS05907-E E
Unable to read file. command=aa....aa, rc=bb....bb, errno=cc....cc
- The performance trace information file was specified incorrectly, or there is a problem with access privileges.
- aa....aa: Command name
- pdprfed
- bb....bb: Maintenance information
- cc....cc: Maintenance information
- S: Terminates processing.
- O: Change the specification of the performance trace information file, and then re-execute the command.
KFPS05908-E E
Insufficient memory. command=aa....aa, rc=bb....bb, errno=cc....cc
- A memory shortage occurred in the execution of the aa....aa command.
- aa....aa: Command name
- pdprfed
- bb....bb: Maintenance information
- cc....cc: Maintenance information
- S: Terminates processing.
- O: Resolve the memory shortage, and then re-execute the command.
KFPS06001-E L
Error occurred in system call aa....aa. errno= bbb
- An error occurred in a system call issued during initialization at processing activation.
The KFPS04621-E message may be output following this message; however, it may be ignored. - aa....aa: Name of the system call that was issued
- bbb: System call return code (errno)
- S: Terminates this processing by issuing abort code Popt001.
- O: To determine the cause, refer to the OS documentation based on the system call name and return code.
- Action
- Determine the cause of the error from the system call name and the system call return code. If the error was caused by a memory shortage, increase the available memory by stopping unneeded processes or increasing the system swap area. If the error was not caused by a memory shortage, contact the customer support center.