KFPK00001-E E+L
aaaaaaaa: file not found, file_kind:bb....bb file_name:cc....cc
- Specified file or temporary file created by a utility was not found. Or, specified directory does not contain an analyzable file.
- aaaaaaaa: Utility:
- Pdstedit: Statistics analysis utility
- bb....bb: File type
- control file: Control statements file
- sort data file: Work file for sorting
- unload log file: Unload log file
- cc....cc: File name or directory name
- S: Terminates processing.
- O: Take one of the following actions, depending on the file type:
- unload log file or control file:
- Check the command name and reenter the command. If file_name is a directory name, check the files under the directory and reenter the command.
- sort data file:
- Check if the temporary file automatically created by the utility was deleted by mistake.
KFPK00002-E D+E+L
aa....aa: file open failed, file_kind:bb....bb, file_name:cc....cc, errno=dd....dd
- Specified file or temporary file created by a utility cannot be opened.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: File:
- control file: Control statements file
- edit work file: Work file
- sort data file: Work file for sorting
- unload log file: Unload log file
- DAT file: DAT-format file
- predict csv file: CSV output file
- cc....cc: File name
- dd....dd: errno returned from the open system call
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Statistics analysis utility:
- Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
- If *** is indicated in errno, check the cause of the error based on the preceding error message.
- Database condition analysis utility:
- Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
KFPK00003-E D+E+L
aa....aa: file close failed, file_kind:bb....bb, file_name:cc....cc, errno=dd....dd
- A file cannot be closed.
- aa....aa: Utility
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: File
- control file: Control statements file
- edit work file: Work file
- sort data file: Work file for sorting
- unload log file: Unload log file
- predict csv file: CSV output file
- cc....cc: File name
- dd....dd: errno returned from the close system call
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Statistics analysis utility:
- Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
- If *** is indicated in errno, check the cause of the error based on the preceding error message.
- Database condition analysis utility:
- Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
KFPK00004-E D+E+L
aa....aa: I/O error, cause:bb....bb, file_name:cc....cc, errno=dd....dd
- An I/O error occurred.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: Type of system call that caused the error
- LSEEK: lseek system call
- READ: read system call
- WRITE: write system call
- cc....cc: File name
- dd....dd: errno returned from the system call
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O:
- Statistics analysis utility:
Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
If *** is indicated in errno, check the cause of the error based on the preceding error message.
- Database condition analysis utility:
Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
KFPK00005-E D+E+L
aa....aa: system call error, func=bb....bb, errno=cc....cc
- A system call (function) error occurred.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: Name of system call resulting in the error
- cc....cc: errno returned from the system call
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and the applicable OS manual to eliminate the cause of the error, then re-execute the command.
KFPK00006-E D+E+L
aa....aa: unrecovable error, func=bb....bb, errno=ccc
- An unrecoverable error occurred.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: Type of system call that caused the error
- CLOSEDIR: closedir system call
- CREATE: create or open system call
- DELETE: unlink system call
- OPENDIR: opendir system call
- READDIR: readdir system call
- ccc: errno returned from the system call
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and the manual describing the applicable function to eliminate the cause of the error, and then re-execute the command. When the error number is ***, check for the cause based on the error message previously output. If a control statement file is specified and bb....bb is CREATE, review the path name specified in the control statement.
KFPK00007-W E
aa....aa error occurred in log element file, server_name:bb....bb file_name:cc....cc system A/B:d reason=(eee,fffff)
- An error occurred in the system log file.
- aa....aa: Processing resulting in the error:
- Close: Close processing
- Open: Open processing
- Read: Read processing
- bb....bb: Server name corresponding to the file group
- cc....cc: File group name
- d: System in which the error occurred
- eee: Reason code
- fffff: Detail code
- S: If the error was not in a log file of the other system, the HiRDB system resumes processing by using the log file in the other system.
- O: Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
-40 -41 -42 -43 | I/O error occurred. | Find the detail code corresponding to the error code in Section 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error. |
-50 -51 -52 -53 | File contents are invalid. | Determine which of the following caused the message to be output, eliminate the cause of the error, and re-execute the command:
- The current group was specified.
- An unused file group was specified after initialization.
- Non-system log file group was specified.
- The log file has been damaged (check whether the log file definition was changed or initialized or whether the status was changed erroneously).
The detail code consists of system maintenance information. |
KFPK00008-E E
aa....aa error occurred in log element file, server_name:bb....bb file_name:cc....cc system A/B:d reason=(eee,fffff)
- An error occurred in the system log file.
- aa....aa: Processing resulting in the error:
- Close: Close processing
- Open: Open processing
- Read: Read processing
- bb....bb: Server name corresponding to the file group
- cc....cc: File group name
- d: System in which the error occurred
- eee: Reason code
- fffff: Detail code
- S: Terminates processing.
- O: Take action appropriate to the reason code:
Reason code | Explanation | Action |
---|
-40 -41 -42 -43 | I/O error occurred. | Find the detail code corresponding to the error code in Section 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error. |
-50 -51 -52 -53 | File contents are invalid. | The log file may have been damaged (check whether the log file definition was changed or initialized or whether the status was changed erroneously). The detail code consists of system maintenance information. |
KFPK00009-E E
aaaaa error occurred, file=bb....bb
- A file I/O error occurred.
- aaaaa: Process that caused the error:
- Open: An error occurred on an open process
- Read: An error occurred on a read process
- Close: An error occurred on a close process
- bb....bb: File name
- S: Terminates processing.
- O: Refer to the error message output immediately after this message to eliminate the error cause, and then re-execute the command.
KFPK00010-E E
File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)
- An error occurred when inputting or outputting a file.
- aa....aa: Error cause
- Invalid-parameter: The combination of specified parameters is invalid.
- Invalid-permission: The user does not have access permission for the file.
- Invalid-device: The file entry type (attribute) is invalid. A directory name might be specified where a file name must be specified (or the converse). In UNIX, a character special file might be assigned to a file on which a character special file cannot be used.
- File-format: The file formats are different. It is possible that the specified file name is incorrect, or the file format specified on the command line or in the control statement does not match the file contents.
- Invalid-file: The specified file was not created correctly.
- File-lock: The file is being used by another user. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.
- No-file: Cannot find the file.
- For Invalid-device, when the entry type of the specified file can be identified, the device type is displayed with the entry type in parentheses. In UNIX, the content is the same as the entry for the mode displayed by the operating system's ls -l command.
- bb....bb: Name of the system function where an error occurred
- If the operating system detected the error, the system function name
- If the HiRDB file system detected the error, the HiRDB file system function name beginning with p_f_ios
- If other than the above, ***
- cc....cc: Error code
- If the operating system detected the error, the error number (errno: foreign reference variable that shows the error status) returned by the system function name
- If the error was detected by the HiRDB file system, the HiRDB file system error code (for details on HiRDB file system error codes, see 5.1 Error codes returned from HiRDB file system access requests)
- If an error cause other than the above, 0
- dd....dd: Troubleshooting information (source file name and row number that detected the error). This information is used by the customer support center.
- S: Terminates processing.
- O: From the error cause, function name, and error code, check errno.h, the manual for the operating system in use, and 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error, and re-execute.
KFPK00011-E E
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc
- An error occurred when accessing a HiRDB file.
- aa....aa: Process where the access error occurred
- open: An open process of a HiRDB file
- read: A read process from a HiRDB file
- close: A close process of a HiRDB file
- bb....bb: Error code of the HiRDB file system
- cc....cc: HiRDB file name
- S: Terminates processing.
- O:
- When bb....bb is error code -1562, the applicable HiRDB file system area may not be the UTL type. Check if the HiRDB file system area specified in the input is the correct type.
- When bb....bb is an error code other than -1562, see 5.1 Error codes returned from HiRDB file system access requests to eliminate the error cause, and then re-execute.
KFPK00012-E E+L
aa....aa: file already exist, file_kind=bb....bb, file_name=cc....cc
- Temporary work file created by the utility already exists.
- aa....aa: Utility type
- Pdstedit: Statistics analysis utility
- bb....bb: File type
- sort data file: Temporary work file
- cc....cc: File name
- S: Terminates processing.
- O: Make sure that the same command is not executing concurrently, delete file cc....cc, and then re-execute the command.
KFPK00013-E D+E+L
aa....aa: system call error, func=bb....bb, file_name=cc....cc, errno=dd....dd
- Error occurred with the system call (function) That accesses the file.
- aa....aa: Utility type
- Pdstedit: Statistics analysis utility
- Pddbst: Database condition analysis utility
- bb....bb: Name of system call causing the error
- cc....cc: File name
- dd....dd: Error number set in errno
- S: When output to standard error, this message terminates processing. When output to a message dialog, the display returns to the screen displayed before the error occurred.
- O: Check the error number (errno: external integer variable expressing the error status), see the documentation that describes errno.h and the applicable functions to eliminate the cause of the error, and then re-execute the command.
KFPK00050-E D+E+L
aa....aa: insufficient memory, size=bb....bb
- A memory shortage occurred.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: Size (in bytes) of area that was to be allocated
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Check for a process that uses a large amount of memory:
- When there is a process using a large amount of memory:
- Wait for the process to terminate, and then re-execute the command.
- When there is no process using a large amount of memory:
- Use one of the following methods to prepare sufficient memory:
- Reduce the number of simultaneously executing processes.
- Increase the size of the swap area.
- Increase the memory.
KFPK00100-E D+E+L
aa....aa: interface error, func:bb....bb, return code=cccc
- An interface error occurred between program functions.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- bb....bb: Name of function that returned an invalid code
- cccc: Detail code
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPK00200-I E
Usage: pdstedit [-k edit_item[,edit_item]...]
[-m interval][-t [start_time][,end_time]]
[-u uap_name[,uap_name]...]
[-x host_name[,host_name]...]
[-s server_name[,server_name]...]
[-o dat_dir[-e ext_fmt[,ext_fmt]]][-i unload_log][-w work_dir]
[-d control_file][-b]
- Following is a description of how to use the Statistics analysis utility (pdstedit):
- -b: Specifies that the title bar is to be displayed for a DAT-format file.
- -d: Specifies the name of the control statements file.
- -e: Specifies the value of the extended format specification.
- -i: Specifies the unload file or unload file storage directory.
- -k: Specifies the types of statistical analysis information (more than one information type can be specified).
- -m: Specifies the editing interval in minutes (up to 1440 can be specified).
- -o: Specifies the name of the DAT-format file output destination directory.
- -s: Specifies the server names (a maximum of 32 server names can be specified).
- -t: Specifies the editing startup time and end time (the start time and end time cannot both be omitted).
- -u: Specifies the UAP names (a maximum of 16 UAP names can be specified).
- -x: Specifies the host names (a maximum of 32 host names can be specified).
- -w: Specifies the name of the directory under which work files are to be created.
- S: Terminates processing.
- O: Check the pdstedit parameters for any errors.
KFPK00201-E E+L
aa....aa: invalid parameter
- An invalid parameter was specified in the utility activation command. This message is displayed because an invalid option was specified:
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- S: Terminates processing.
- O: Check for errors in each utility's runtime input parameters.
KFPK00202-E E+L
aa....aa: invalid combination of options
- A combination of utility activation command options is invalid. Or, the combination of the options and the control statement is invalid.
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- S: Terminates processing.
- O: Check for errors in the specification of each utility's runtime parameters (command line and control statements).
KFPK00203-E E+L
aa....aa: invalid bb option
- Option bb is invalid in a utility activation command.
This message is displayed in one of the following cases: - No key is specified in the option.
- Specified key format is invalid in the option.
- The key specified in the option exceeds the repetitions limit.
- The key specified in the option exceeds the limit.
- The -G option was specified in an environment where the HiRDB Staticizer Option cannot be used.
- Although not using the facility for predicting reorganization time (Y specified in the system definition pd_rorg_predict operand), the -e, -k pred, -m, -R, -c, or -v option was specified.
- The pattern character string of the RDAREA batch specification includes a percent sign (%).
- The pattern character string specified in the option consists of only asterisks (*).
- aa....aa: Utility:
- Pddbst: Database condition analysis utility
- Pdstedit: Statistics analysis utility
- b: Name of invalid option
- S: Terminates processing.
- O: Check each utility activation command for parameters that were entered incorrectly. If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.
KFPK00204-E L+E
Invalid attribute exists in Control file, line=aa....aa
- An invalid value was detected in line aa....aa of the control statement file specified in the -v option.
- aa....aa: Control statement line number
- S: Throws an SQLException.
- O:
- pddbst execution:
- When executing the facility for predicting reorganization time (when -k pred is specified), check the control statement specification and correct the error. Then, re-execute pddbst.
- If other than the above and the -v option is specified, delete the -v option and re-execute.
- HiRDB CM execution:
- Contact the HiRDB administrator.
- Action
- If this message is output during the execution of HiRDB CM, contact the customer support center.
KFPK00205-E E+L
Length of unload log file name exceeds bytes
- Invalid file name was specified for the statistics analysis utility (pdstedit).
- S: Terminates processing.
- O: Check the parameters of the utility activation commands for errors.
KFPK00206-E E+L
aaaaaaaa: invalid directory name, kind=bb....bb
- The name of a file creation directory specified in a utility activation command is invalid for one of the following reasons:
- Specified directory was not found.
- The command executor does not have write privilege for the specified directory.
- The directory with the specified name does not have the directory attribute.
- Specified directory name exceeds 128 bytes.
- aaaaaaaa: Utility:
- Pdstedit: Statistics analysis utility
- bb....bb: Directory:
- DAT data file: DAT format file creation
- sort data file: Work file for sorting
- S: Terminates processing.
- O: Check for errors in the specification of each utility's runtime input parameters.
KFPK00207-E E
aaaaaa: unable to assume user id
- For the reasons indicated below, the default for the authorization identifier cannot be assumed:
- The PDUSER environment variable is undefined.
- The authorization identifier or password defined in the PDUSER environment variable exceeds the maximum length.
- In the authorization identifier or password defined in the PDUSER environment variable, double quotation marks (") are not paired.
- An authorization identifier is not specified in the PDUSER environment variable.
- aaaaaa: Utility:
- Pddbst: Database condition analysis utility
- S: Terminates processing.
- O:
- If the -u option is omitted when the command is executed, make sure the correct authorization identifier or password is specified in the PDUSER environment variable, and then re-execute the command.
- When the Windows edition is being used and the -u option is omitted, check that the authorization identifier and password specified at the command prompt are not enclosed in single quotation marks (').
- Example of correct specification:
- PDUSER="root"/"root"
- When specifying an authorization identifier or password in the client environment definition (hirdb.ini), enclose it in single quotation marks (').
- Example of correct specification: PDUSER='"root"/"root"'
KFPK00208-E E
Invalid attribute exists in Base value file, line=aa....aa
- One of the following errors occurred in line aa....aa of the standard value definition file specified in the -c option.
- Invalid standard value item name
- Invalid analysis specification
- Invalid specification value descriptor or invalid range
- aa....aa: Control statement line number
- S: Terminates processing.
- O: Check the contents of the standard value definition file, correct the specification error, and re-execute.
KFPK00210-E E
Number of RDAREA exceeded aaaa
- The number of RDAREAs specified in flag arguments (excluding duplicates) exceeds the maximum value (aaaa).
- aaaa: Maximum value
- S: Terminates processing.
- Action
- Make sure that the number of RDAREAs specified in flag arguments (excluding duplicates) is at or below the maximum value. For the maximum number of RDAREAs that can be specified, see Specification of RDAREAs in operation commands and utilities in the manual HiRDB Version 9 Command Reference.
KFPK00250-W E
Invalid unload log file, file_name:aa....aa
- An error was detected in the input file for the statistics analysis utility (pdstedit command).
- When the input of the statistics input unload file specified for the statistics analysis utility is a file name:
- A file of the specified file's type is not subject to analysis.
- The specified file is not an unload statistics log file or unload log file
- A pipe file was specified, but the file contained data other than an unload statistics log file. (UNIX edition only.)
- The name of an unload statistics log file obtained in 64-bit mode HiRDB is specified in a 32-bit mode HiRDB.
- When the input of the statistics input unload file specified for the statistics analysis utility is a directory name:
- A file of file aa....aa's type in the specified directory is not subject to analysis.
- The specified file is not an unload statistics log file or unload log file of file aa....aa under the specified directory.
- The HiRDB file (aa....aa) in the HiRDB file system area in the specified directory is not an unload log file.
- File aa....aa located in the specified directory is an unload statistics log file obtained in a 64-bit mode HiRDB; it cannot be input in a 32-bit mode HiRDB.
- When the specified input of the statistics input unload file in the statistics analysis utility is a HiRDB file system area name
- No HiRDB file was found in HiRDB file system area aa....aa.
- HiRDB file aa....aa in the specified HiRDB file system area is not an unload log file.
- HiRDB file aa....aa in the specified HiRDB file system area is being unloaded.
- The user does not have read or write privileges to the specified HiRDB file system area.
- aa....aa: File name
- S: Resumes processing, ignoring the invalid file (does not edit the file).
- O: Check the pdstedit command parameters for an error. Alternatively, if the user does not have the necessary privileges to the specified HiRDB file system area, grant the user read or write privileges.
KFPK00251-E E
Invalid log record, record_number:aa....aa
- A log record is invalid.
- aa....aa: Serial number of log record
- S: Terminates processing.
- O: Contact the HiRDB administrator.
- Action
- Check the data in the unload log file or unload statistics log file for any damage.
KFPK00252-E E
Invalid sort data file, cause:aa....aa file_name:bb....bb
- A work file for sorting is invalid.
- aa....aa: Reason:
- corrupt record: Records are corrupted
- invalid type: Not a work file for sorting
- bb....bb: Invalid work file for sorting
- S: Terminates processing.
- O: Check that no change was made to the sort work file created internally by the pdstedit.
KFPK00253-E E
Invalid log block, block_number:aa....aa
- A log block is invalid.
- aa....aa: Serial number of log block
- S: Terminates processing.
- O: Contact the HiRDB administrator.
- Action
- Check the data in the unload log file for any damage.
KFPK00254-E E+L
aa....aa : Invalid contents in file, file_kind : bb....bb file_name : cc....cc record_length=dd....dd read_length=ee....ee
- The contents of the input file are invalid. The file's contents may have been damaged.
- aa....aa: Utility type:
- Pdstedit: Statistics analysis utility
- bb....bb: File type:
- unload log file: Unload log file
- unload stj log file: Unload statistics log file
- sort data file: I/O file for sorting
- cc....cc: File name
- dd....dd: Record length that was to be loaded (maintenance information)
- ee....ee: Length of the data that was loaded successfully (maintenance information)
- S: Terminates processing.
- O: Contact the HiRDB administrator.
- Action
- When the file type is unload log file or unload stj log file:
- Check as follows for whether or not the data in the unload file has been damaged:
- For data transfer using FTP, check if the data in the unload file has been damaged.
- Check if the unload file has been updated illegally.
If the file type is unload log file:
In UNIX:
If the statistics log file (statistics log file named pdstj1 or pdstj2 that was output under $PDDIR/spool before unloading was performed using the OS's cp command or the pdstjacm shell script) before cc....cc was unloaded is available, use a command such as cmp to compare the contents of cc....cc with the contents of the file before unloading to make sure they are identical.
In Windows:
If the statistics log file output before cc....cc was unloaded is available, use the fc command to compare cc....cc and the contents of the file before it was unloaded, and make sure they are identical.
If the file type is unload stj log file:
If cc....cc is an unload log file that was backed up using the pdlogunld command and if there is a subsequent unload file acquired using the pdlogunld command and associated with that file, use the cmp command (in UNIX) or the fc command (in Windows) to compare the contents of the two files, and make sure they are identical.
- When the file type is sort data file:
- Check as follows for whether or not the I/O file for sorting that is created internally by the statistics analysis utility has been modified inadvertently:
- In UNIX:
- Check whether or not the files under $PDDIR/tmp or /usr/tmp were deleted or updated illegally during execution of the statistical analysis utility.
- In Windows:
- Determine whether a file under %PDDIR%\tmp was deleted or improperly updated during execution of the statistical analysis utility.
- If none of the above is applicable, contact the customer support center.
KFPK00255-W E
aaaaaaaa:Invalid contents in file, file_kind:bb....bb file_name: cc....cc record_length=dd....dd read_length=ee....ee
- The contents of the input file are invalid. The file's contents may have been damaged. Perform editing using the records that had been input before the invalid record was detected.
- aaaaaaaa: Utility:
- Pdstedit: Statistics analysis utility
- bb....bb: File type:
- unload log file: Unload log file
- unload stj log file: Unload statistics log file
- cc....cc: File name
- dd....dd: Record length that was to be loaded (maintenance information)
- ee....ee: Length of the data that was loaded successfully (maintenance information)
- S: Continues processing.
- O: Contact the HiRDB administrator. For the acquisition time for the log record that was input successfully, refer to FIRST and LAST in the input log file summary information.
- Action
- When the file type is unload log file or unload stj log file:
- Check as follows for whether or not the data in the unload file has been damaged:
- For data transfer using FTP, check if the data was transferred in the binary mode.
- Check if the unload file has been updated illegally.
- When the file type is unload stj log file:
- Check that the disk at the statistics log file's output destination (%PDDIR%\spool) did not become full during acquisition of the statistics log file before unloading of cc....cc.
- In UNIX, if the statistics log file (statistics log file named pdstj1 or pdstj2 that was output under $PDDIR/spool before unloading was performed using the OS's cp command or the pdstjacm shell script) before cc....cc was unloaded is available, use the cmp command to compare the contents of cc....cc and the file before it was unloaded, and make sure they are identical.
In Windows, if the statistics log file output before cc....cc was unloaded is available, use the fc command to compare cc....cc and the contents of the file before it was unloaded, and make sure they are identical.
- When the file type is unload log file:
- If cc....cc is an unload log file that was backed up using the pdlogunld command and if there is a subsequent unload file acquired using the pdlogunld command and associated with that file, use the cmp command (in UNIX) or the fc command (in Windows) to compare the contents of the two files, and make sure they are identical.
- If none of the above is applicable, contact the customer support center.
KFPK00300-I E
Pdstedit terminated, return code=aa....aa
- Execution of the statistics analysis utility is completed.
- aa....aa: Return code:
- 0: Terminated normally
- 4: Terminated normally, but a warning message was issued
- 8: Processing was cancelled due to an error
- 12: Processing was cancelled due to an interrupt (signal generated)
- S: Terminates processing.
- O:
- 4 set as the return code:
- Check the cause on the basis of the message with type W that was issued during processing.
- 8 set as the return code:
- Check the cause on the basis of the message with type E that was issued during processing.
KFPK00301-I E
Stdin assumed as input
- Processing was performed using the standard input, because the -i option was omitted, or processing was placed on input wait status, because the -i option was omitted. Therefore, the standard input was assumed.
- S: Resumes processing.
- O: Determine whether or not the processing should be resumed using the standard input. To cancel the processing, terminate the utility with the following methods:
- Processing placed on input wait status:
Press the return key again.
- Other:
In UNIX, specify a process ID, and enter the kill command.
In Windows, specify a process ID, and enter the pdkill command.
KFPK00400-E E
Sort program error
- An error occurred during sort processing.
- S: Terminates processing.
- O: Refer to the preceding sort processing error message, and investigate the cause of the error. If the cause of the error cannot be identified, contact the HiRDB administrator.
- Action
- Correct the error and re-execute.
KFPK00901-E E
Unable to make an entry SQL_DB_STATE_ANALYZED
- Because the result of condition analysis could not be registered in the database management table, the reorganizing time cannot be predicted for the most recent database condition.
- S: Terminates processing.
- O: Refer to the message# output before this message and eliminate the cause of the error. Then, re-execute pddbst, and register the result of condition analysis in the database management table.
- #: For KFPA11204-E, pdmod must be used to create the RDAREA used by the data dictionary to store the database state analyzed table and the database management table.
KFPK00911-W E
Unable to make an entry SQL_DB_STATE_ANALYZED, RDID=aa....aa, OBJID=bb....bb, code=ccc
- The facility for accumulating condition analysis results was executed in a merge analysis; the results could not be merged with the database state analysis table.
- aa....aa: RDAREA ID
- bb....bb: Table or index ID
- ccc: Reason code for merge failure
- -10: Table or index deleted during execution of pddbst
- Other than above: Multiple pddbst commands executed simultaneously
- S: Continues processing.
- O: Do not execute multiple pddbst commands simultaneously on the same RDAREA. Also, do not delete a table or index during execution of pddbst.
KFPK00999-E L+E
HiRDB Control Manager interface file I/O error occurred, reason=aa....aa
- An error occurred in the file that interfaces with HiRDB CM.
- aa....aa: Error cause
- PATH_NAME: The file path name is too long.
- FILE_OPEN: File open failed.
- FILE_WRITE: File write failed.
- FILE_CLOSE: File close failed.
- S: Terminates processing.
- O:
- If aa....aa is PATH_NAME, see the HiRDB CM manual, and change the file output destination.
- If aa....aa is FILE_OPEN, FILE_WRITE, or FILE_CLOSE, refer to pdlog, the event log, or the KFPK00005-E or KFPK00010-E error message that was output to the event log (in UNIX, syslogfile) to resolve the error.
KFPK05200-E E+L
Invalid format exists in control file, line=aa....aa
- The format of line aa....aa in the control statements file specified with the -d option of the statistics analysis utility is incorrect.
- aa....aa: Line number resulting in the error during analysis
- S: Terminates processing.
- P: Correct the indicated line in the control statements file and re-execute the command.
KFPK05201-E E+L
Invalid attribute exists in control file, line=aa....aa
- The value of line aa....aa in the control statements file specified with the -d option of the statistics analysis utility is incorrect.
- aa....aa: Line number resulting in the error during analysis
- S: Terminates processing.
- P: Correct the indicated line in the control statements file and re-execute the command.
KFPK05202-E E+L
Line of file_group sentence in control file exceeds the limit
- The number of file_group statements in the control statements file specified with the -d option of the statistics analysis utility exceeds the maximum.
- S: Terminates processing.
- P: Correct the control statements file so that the number of file_group statements specified does not exceed 34 and re-execute the command.
KFPK05203-E E+L
server name specified twice in control file, server_name: aa....aa
- The same server name was specified more than once in the control statements file with the -d option of the statistics analysis utility.
- aa....aa: Duplicated server name
- S: Terminates processing.
- P: Correct the control statements file so that the same server name is specified only once and re-execute the command.
KFPK05204-E E+L
Error occurred in log file group, server_name:aa....aa, file_name:bb....bb, reason=(cc....cc, dd....dd)
- An error was detected in a log file group specified with a control statement of the statistics analysis utility.
- aa....aa: Server name corresponding to the file group
- bb....bb: File group name
- cc....cc: Reason code
- dd....dd: Detail code
- S: Terminates processing.
- Action
- Following are the reason codes and actions:
Reason code | Explanation | Action |
---|
-1 | Argument is invalid. | Contact the customer support center. |
-2 | Fatal error or unexpected error occurred. |
-30 | Error in log file definition analysis function | Refer to the error message output before this message to eliminate the cause of the error. The detail code consists of system maintenance information. |
-31 | Error in log file definition analysis | Log file definition has been changed incorrectly. Refer to the detail code to return to the original definition. |
- Following are the detail codes:
Detail code | Explanation |
---|
-1 | File group name in definition is incorrect. |
-2 | System A file name in definition is incorrect. |
-3 | System B file name in definition is incorrect. |
Other | Maintenance information |
KFPK05300-I E
No data in log file, record_kind=aaa, reason=bb....bb
- The log file that was to be subject to the analyses contained no records.
- aaa: Record type:
- sop: SQL static optimization information log records
- dop: SQL dynamic optimization information log records
- pcd: SQL object execution information log records
- obj: SQL object transfer information log records
- cnc: connect/disconnect information log records
- sqh: SQL statement information log records
- plg: Plug-in statistical information log records
- bb....bb: Reason:
- NOOPT:
- -d option not specified:
- The indicated edit item record was not found in the total analysis log file.
- -d option specified:
- The indicated edit item record was not found in the total analysis log file.
- The server specified in the -s option was not defined in the control statements file specified in the -d option.
- HOST:
- There was no statistics log record that was output from the host specified in the -x option.
- SERVER:
- The statistical record output from the server specified in the -s option cannot be found.
- UAP:
- There was no statistics log record that was output from the UAP specified in the -u option.
- TIME:
- There was no statistics log record that was output within the edit interval specified in the -t option.
- S: Resumes processing.
- Action
- Check the HiRDB Version 9 Command Reference for the message that is output when there is no edit data for the statistics analysis utility, and take appropriate action.
KFPK10012-E D+E
Transaction start error on aa....aa, func=bb....bb return code=cc....cc
- An error occurred during transaction startup processing.
- aa....aa: Name of server where the error occurred
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Contact the HiRDB administrator.
- Action
- See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the command. If the error cannot be corrected, contact the customer support center.
KFPK10013-E D+E
Transaction termination error on aa....aa, func=bb....bb return code=cc....cc
- An error occurred during transaction termination processing.
- aa....aa: Name of server where the error occurred
- bb....bb: Name of processing resulting in the error
- cc....cc: Error code
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Contact the HiRDB administrator.
- Action
- See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the command. If the error cannot be corrected, contact the customer support center.
KFPK10014-E D+E
aa....aa lock request failed, name=[bb....bb] "cc....cc"
- Locking of a resource failed.
- aa....aa: Resource type:
- Index: Index
- RDAREA: RDAREA
- Table: Table
- bb....bb: Authorization identifier (displayed only when aa....aa is Index or Table)
- cc....cc: Name of resource
- S: If the facility for accumulating condition analysis results is being executed and there is another process making exclusive use of the target resource, skips the analysis of the target resource, and continues processing. Information on the RDAREA whose processing is skipped is not accumulated.
- Terminates processing in the following cases:
- A locking error occurred due to other causes
- The database condition analysis facility and the facility for predicting reorganization time are being executed
- O: Refer to the message that is output to the message log file, resolve the error, and re-execute the command. If the output message is KFPA11770-I, wait until the other process making exclusive use of the target resource terminates, and then re-execute the command.
KFPK10015-E D+E
Directory access error, server=aa....aa
- An error occurred while a directory was being accessed.
- aa....aa: Server name
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Eliminate the cause of the error on the basis of the message that was output to the log file, then re-execute the command. If the output message is KFPA11815-E, the table definition was modified during execution of the command. If that is the case, re-execute the command when the table definition is not being modified.
KFPK10016-E D+E
Insufficient memory in message buffer pool due to concurrent execution of "pddbst"
- A temporary memory shortage occurred in the message storage buffer pool during process allocation when the database condition analysis utility (pddbst) was being executed concurrently.
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: Re-execute the command after execution of the current command is completed.
- Action
- 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 utilities are being executed concurrently, review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.
KFPK10017-E D+E
Unable to send message from aa....aa to bb....bb
- Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.
- aa....aa: Send source host name#
- bb....bb: Send destination host name#
- #: If the system switching facility is being used, the host name of the primary system is indicated.
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- Action
- Take action appropriate to the KFPK10100-E message output before this message. If the error was not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.
KFPK10018-E E
Dynamic load error occurred, shared library=aa....aa
- An error occurred in dynamic loading of a shared library required for processing.
- aa....aa: Full path name of the shared library
- S: Terminates processing.
- O: Refer to the preceding KFPK00005-E message.
- In UNIX:
- Check the following, resolve the error, and re-execute the command:
- GUI function used
Check whether X Window System and Hitachi Motif have been installed correctly
- GUI function not used
Check whether processing is being executed with output of analysis results to standard output specified
- In Windows:
- Determine whether processing is being executed with output of analysis results to standard output specified, resolve the error, and re-execute the command.
KFPK10019-E E+D
HiRDB file error, func=aa....aa return code=bb....bb filename=cc....cc
- An error that produces error code bb....bb occurred in file access function aa....aa for file cc....cc.
- aa....aa: Function name
- bb....bb: Error code
- cc....cc: HiRDB file name
- S: Terminates processing.
- Action
- Correct the error by referring to 5.1 Error codes returned from HiRDB file system access requests, and then re-execute.
KFPK10020-E D+E
RDAREA "aa....aa" not found
- RDAREA "aa....aa" could not be found.
Possible cause: - RDAREA to be processed was deleted while a utility was running.
- aa....aa: RDAREA name
- S: Terminates processing.
- O: When the RDAREA to be processed is deleted while a utility is running, reconstruct the environment so that the utility can be executed, and then re-execute the utility. If the RDAREA cannot be deleted, contact the customer support center.
KFPK10100-E D+E
RPC(system) error, func=aa....aa, return code=bbbbb
- An RPC-related error or system-related error occurred.
- aa....aa: Name of function resulting in the error
- bbbbb: Error detail code
- S: Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O: See 4. Error Detail Codes to eliminate the cause of the error and re-execute the command. If the HiRDB administrator cannot handle the error, contact the customer support center.
KFPK10101-E E
Unable to start pddbst
- The database condition analysis utility cannot be started for one of the following reasons:
- The maximum number of concurrently executable utilities has been reached.
- HiRDB is engaged in termination processing.
- S: Terminates processing.
- O: Eliminate the cause of the error and restart.
KFPK10102-W D+E
Specified value not found in system aa....aa="bb....bb"
- One of the following errors occurred:
- The specified RDAREA name, table identifier, or index identifier was not found.
- No replica RDAREA was found in the generation specified by the -q option.
- ALL was specified in the second, or subsequent, position.
- A pattern character string of only asterisks (*) was specified.
- aa....aa: Identifier:
- index: Index
- RDAREA: RDAREA
- table: Table
- bb....bb: Specified identifier
- S: Resumes processing.
- O: Take one of the following actions:
- Check whether the specified name exists in the system, specify the correct name, and then restart.
- If multiple RDAREA names are specified and ALL is specified as the second, or subsequent, RDAREA name, specify ALL by itself and re-execute the command.
- Specify the correct RDAREA name, not a pattern character string that consists of only asterisks (*), and then re-execute the command.
KFPK10103-W D+E
Unable to get status information
aa....aa="bb....bb" [server=ee....ee]
cc....cc="dd....dd" [server=ff....ff]
- Information cannot be collected for the specified RDAREA or table identifier for one of the following reasons:
- The server subject to analysis is not active.
- The RDAREA subject to analysis is on the following status:
- When the RDAREA attribute is INITIAL
The RDAREA is not on one of the following statuses:
Open without shutdown
Open with reference-possible backup hold
Referencing-possible backup-hold
Updatable backup-hold
- When the RDAREA attribute is DEFER or SCHEDULE
The RDAREA is not on one of the following statuses:
Open without shutdown
Closed without shutdown
Open with reference-possible backup hold
Closed with reference-possible backup hold
Reference-possible backup hold
Updatable backup-hold
- aa....aa: Identifier:
- index: Index
- RDAREA: RDAREA
- table: Table
- bb....bb: Specified identifier
- cc....cc: Identifier:
- index: Index
- RDAREA: RDAREA
- table: Table
- dd....dd: Specified identifier
- ee....ee: Server name
- ff....ff: Server name
- S: Resumes processing.
- O: Address the reason that information could not be obtained and restart.
KFPK10104-W D+E
No select privilege for authorization id
aa....aa="bb....bb" [server=ee....ee]
cc....cc="dd....dd" [server=ff....ff]
- The user does not have the SELECT privilege for the specified table or index authorization identifier.
- aa....aa: Identifier:
- index: Index
- RDAREA: RDAREA
- table: Table
- bb....bb: Specified identifier
- cc....cc: Identifier:
- index: Index
- RDAREA: RDAREA
- table: Table
- dd....dd: Specified identifier
- ee....ee: Server name
- ff....ff: Server name
- S: Resumes processing.
- O: Check if the user has the SELECT privilege for the table or index authorization identifier subject to analysis, specify a table or index permitted by the SELECT privilege, then re-execute the command.
KFPK10105-E D+E
Unable to connect to HIRDB, user=aa....aa
- Connection with HiRDB cannot be established.
- aa....aa: authorization identifier
- S:
- Message is output to standard error:
- Terminates processing.
- Message is output to the error message dialog:
- Redisplays the screen immediately before the error occurred.
- O:
- SQL statement-related message issued before this message:
- Eliminate the cause of the error indicated by the message and re-execute the command.
- No SQL statement-related message issued before this message:
- Check if the user has the DBA privilege for the HiRDB system and re-execute the command.
KFPK10106-W D+E
Unable to analyze aa....aa="bb....bb", kind=cc....cc
- Cannot analyze the specified RDAREA, table identifier, or index identifier.
- aa....aa: Analysis target:
- RDAREA: RDAREA name
- table: Table identifier
- index: Index identifier
- bb....bb: Name
- cc....cc: Type:
- When RDAREA is displayed in aa....aa:
- master directory: Master directory RDAREA
- data directory: Data directory RDAREA
- list: List RDAREA
- RDAREA for temporary table: Temporary table RDAREA
- other: Others
- When table is displayed in aa....aa:
- view table: Viewed table
- cluster: Table without a cluster key definition
- temporary table: Temporary table
- other: Other
- When index is displayed in aa....aa:
- temporary index: Temporary table index
- other: Index
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Check if the specified resource is subject to analysis. If it is not subject to analysis, correct the specification and re-execute.
KFPK10107-W D+E
No data
RDAREA="aa....aa" server=bb....bb
- Specified RDAREA contains no table or index, so the status cannot be displayed.
- aa....aa: RDAREA name
- bb....bb: Server name
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
KFPK10108-W D+E
No original RDAREA
RDAREA="aa....aa"
- The specified RDAREA is not the original RDAREA. If the facility for predicting reorganization time is used, the target is the original RDAREA.
- aa....aa: RDAREA name
- S: Continues processing.
- O: Check to determine if the specified RDAREA is the original RDAREA. If it is not the original RDAREA, specify the original RDAREA and re-execute. Also, to perform condition analysis of the specified replica RDAREA, delete the -q option and re-execute.
KFPK10200-I E
Usage: pddbst -r rdarea_name [-k logi] [-d [-z]] [-a [-h]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] -r rdarea_name[,rdarea_name]... -k phys [-f] [-a [-h]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -t [auth_id.]table_name [-s] [-d] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -t [auth_id.]table_name -k clus [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -i [auth_id.]index_name [-d [-z]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -r {rdarea_name | ALL} [-k logi] -e predict_level [-I] [-n divided_number] [-w sleep_time,segment_number] [-u user_id[-p password]] [-v control_file_name] | [-r ALL] -k pred [-m] -e predict_level [-R watch_time[,maintenance_extension_time]] [-c base_value_define_file_name] [-v control_file_name] [-u user_id[-p password]]
- Displays the format of the pddbst utility.
- -u: Specifies an authorization identifier.
- -p: Specifies a password. This option must be specified together with the -u option.
- -b: Specified to avoid online performance degradation of the application due to execution of pddbst.
- -r: Specifies the name of an RDAREA. Specify this to perform analysis in units of RDAREAs. If -k phys is specified, multiple RDAREA names can be specified. If -k pred or -k logi -e is specified, -r all can be specified.
- -k: Specifies the analysis type in units of RDAREAs. Specify either logi, phys, clus, or pred. Specify logi and phys in pairs with the -r option. Similarly, specify clus in pairs with the -t option. Specify pred when the facility for predicting reorganization time is used.
- -d: Specifies the display of detailed information on a page.
- -z: Specifies the display of detailed information about index entries. Specify together with -d.
- -q: When a replica RDAREA is found, specifies the generation to be analyzed.
- -f: Specifies that HiRDB file information is to be displayed.
- -a: Specifies the display in DAT format.
- -h: When displaying in DAT format, specifies to output the title bar. Specify together with -a.
- -t: Specifies [authorization-identifier.] table-identifier. Specify this to perform analysis in units of tables.
- -s: Specifies that the number of stored lines is to be analyzed in units of tables. This option can be specified when the -t option is specified. However, it cannot be specified when the -k option is specified.
- -i: Specifies the index identifier. This option is specified to perform analysis in units of indexes. The -r option, the -t option, and the -i option cannot be specified together.
- -e: When executing the condition analysis results depository facility or the facility for predicting reorganization time, this specifies the prediction level. Specify together with -k logi or pred.
- -m: When -k pred -e 1 is specified, specifies performance of a detail analysis.
- -R: Specifies the monitoring time and the maintenance delay time. Specify together with -k pred.
- -c: Specifies the name of the standard value definition file. Specify together with -k pred.
- -v: If the results of the facility for predicting reorganization time are to be output in CSV format or if the work file used by pddbst is to be output to a file other than %PDDIR%\tmp, specifies a control statement specifying an output destination file.
- -I: When accumulating analysis information, specify this option when accumulated information on the RDAREA being analyzed is to be reset.
- -n: Specify this option when analysis information is to be accumulated multiple times. For the accumulation of analysis information, this option can be specified if 2 is specified in the -e option.
- -w: Specify this option when the accumulation of analysis information is to be executed in the background to transactions. For the accumulation of analysis information, this option can be specified if 2 is specified in the -e option.
- S: Terminates processing.
- O: Check the database condition analysis utility (pddbst) parameters for any errors.
KFPK10201-W D
No parameter in input area
- Nothing is specified in the screen input area.
- S: Redisplays the input screen on which the error occurred.
- P: Set the appropriate value in the input area and re-execute.
KFPK10202-W D
Length of parameter is too long
- The specification in the screen input area exceeds the maximum length.
- S: Redisplays the input screen on which the error occurred.
- P: Specify the correct value in the input area and re-execute.
KFPK10203-W D
Value of aa....aa is not specified
- The specification on the screen is invalid. This message is output in either of the following cases:
- Authorization identifier cannot be identified because a period is specified at the beginning of the table or index identifier
- Table name or index name cannot be identified because a period is specified at the end of the table or index identifier.
- An error was found in the specified generation number.
- aa....aa: Item specified incorrectly:
- authid: Authorization identifier
- table name: Table name
- index name: Index name
- generation number: Generation number
- S: Redisplays the input screen on which the error occurred.
- O: Specify the correct value in the input area and re-execute.
KFPK10204-W D
Number of RDAREA names exceeds 128
- More than 128 RDAREA names are specified.
- S: Redisplays the input screen on which the error occurred.
- O: Specify the correct values in the input area and re-execute.
KFPK10250-E D+E
User RDAREA inconsistent with dictionary, aaaaa-bb....bb."cc....cc"
- Table or index subject to analysis was found in the dictionary but not in the user RDAREA. An inconsistency was found between the dictionary table and a user RDAREA or a user LOB RDAREA.
- aaaaa: Identifier:
- table: Table
- index: Index
- bb....bb: Authorization identifier
- cc....cc: Specified identifier
- S: Skips processing of the table or index resulting in the error and resumes processing.
- O: Make sure the problem is not one of the types indicated below. If none of these potential causes applies, contact the customer support center.
- If synchronization was ensured when a master directory RDAREA, a data directory RDAREA, and a data dictionary RDAREA were restored from their backups
In this case, perform restoration by ensuring synchronization. If synchronization was not achieved at the time of backup, unload all databases by using the database reorganization utility, re-initialize the databases, and re-create them.
- If the status file was initialized and HiRDB was restarted without terminating HiRDB normally, or if HiRDB was started using the pdstart -dbdestroy command
In this case, re-create the database by re-initializing the database.
- If tables and indexes were deleted during execution of the command
In this case, re-execute the command when table or index definitions are not being modified.
KFPK10251-W E
Unable to get status information, cause cluster index incomplete RDAREA="aa....aa"
- The system was unable to obtain the correct information because the cluster index specified for analysis has not been created.
- aa....aa: RDAREA name
- S: Resumes processing.
- O: Re-execute the command after creating the cluster index.
KFPK10300-I E
Pddbst started
- Execution of the database condition analysis utility has started.
- S: Resumes processing.
KFPK10301-I E
Pddbst terminated, return code=aa....aa
- Execution of the database condition analysis utility is completed.
- aa....aa: Return code:
- 0: Terminated normally
- 4: Terminated normally, but a warning message was issued. Or, part of the processing might have been skipped.
- 8: Processing was cancelled due to an error
- S: Terminates processing.
- O: If the return code is 4 or 8, refer to the warning or error message that is output to standard error or to the message log file, and resolve the error.
KFPK10311-I E
Applied objects nothing
- The result of executing the facility for predicting reorganization time is that no resources require maintenance in the specified day range.
- S: Continues processing.
KFPK10312-I E
Number of saved data a few, RDAREA aa....aa
- Due to insufficient data for predicting with the facility for predicting reorganization time, prediction processing was skipped. For details on the amount of data required for predicting, see the section on the facility for predicting reorganization time in the manual HiRDB Version 9 Command Reference.
- aa....aa: Name of the RDAREA
- S: Continues processing.
- Action
- Execute the condition analysis results depository facility on the RDAREA to be analyzed, and after at least four results have been registered, re-execute.
KFPK10313-I E
No data in SQL_DB_STATE_ANALYZED
- None of the data required for predicting using the facility for predicting reorganization time is in the condition analysis table (SQL_DB_STATE_ANALYZED).
- S: Continues processing.
- Action
- Execute pddbst for the RDAREA to be analyzed, and register at least four condition analysis results in the condition analysis table. Then, re-execute.
KFPK10314-I E
aaaaa bb....bb."cc....cc" not found, in dd....dd
- During execution of the facility for predicting reorganization time, resources in the RDAREA were deleted.
- aaaaa: Resource type in the RDAREA
- TABLE: Table
- INDEX: Index
- bb....bb: Authorization identifier
- cc....cc: Table identifier or index identifier
- dd....dd: Name of the RDAREA
- S: Continues processing.
- Action
- Register the condition analysis result of the condition analysis results depository facility, and re-execute the facility for predicting reorganization time.
KFPK10315-I E
Unable to predict due to data on same time, RDAREA aa....aa
- For the following reason, prediction cannot be made from the analysis information table, and so processing of the prediction target RDAREA was skipped.
- Data of the prediction target RDAREA was all collected at the same time (within 1 second).
- aa....aa: Name of the RDAREA to be analyzed
- S: Continues processing.
- Action
- Execute the condition analysis results depository facility on the prediction target RDAREA at an appropriate interval (in units of 1 day is recommended), and re-execute the facility for predicting reorganization time.
KFPK10316-I E
Number of saved data a few, RDAREA aa....aa, bb....bb=cc....cc.dd....dd
- Prediction processing on a table or index in an RDAREA was skipped, because the amount of data necessary for prediction by the facility for predicting reorganization time was insufficient.
- aa....aa: RDAREA name
- bb....bb: Analysis type
- table: Table
- index: Index
- cc....cc: Authorization identifier
- Displays "(Data dictionary)" in the case of a dictionary table or an index in a dictionary table.
- dd....dd: Table identifier or index identifier
- S: Continues processing.
- Action
- Execute the facility for accumulating condition analysis results on the RDAREA storing the table or index that is the object of prediction, register four or more pieces of analysis information, and then re-execute the command.
KFPK10400-E D+E
Sort program error -aa....aa
- An error occurred during sorting.
- aa....aa: Cause of the error:
- destroyed file,file_name: Name of the damaged file
- incorrect version: Invalid version
- insufficient memory: Insufficient memory
- I/O error,file_name: Name of file resulting in the I/O error
- logical error (maintenance-code): Logical error
- S:
- Message is output to standard error:
Terminates processing.
- Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.
- O: Check the cause of the error on the basis of the displayed cause, correct the error, then re-execute. In the case of a logical error, contact the customer support center.
KFPK10450-E E
Pddbst must be executed at unit defined as manager
- The database condition analysis utility must be executed on the unit where the system manager (MGR) is defined.
- S: Terminates processing.
- O: Re-execute the utility on the unit where the system manager (MGR) is defined.
KFPK10451-E E
Unable to analyze with -e option, aa....aa
- For one of the following reasons, condition analysis result processing with the -e option specification could not be executed:
- The system definition pd_rorg_predict operand is not Y.
- The data dictionary RDAREA that stores the analysis information table and the database management table does not exist.
- The replica RDAREA is specified by the -q option.
- aa....aa: {not predict mode 'Y' | not found datadictionary of dbmanagement | on replica RDAREA}
- S: Terminates processing.
- Action
- When using the facility for predicting reorganization time, take the following actions:
- Specify Y in the system definition pd_rorg_predict operand, and restart HiRDB. Then, execute the facility for predicting reorganization time.
- Use pdmod to create the data dictionary RDAREA to store the analysis information table and the database management table, and then execute the facility for predicting reorganization time.
- Remove the specification of the -q option, and execute the facility for predicting reorganization time.
KFPK10999-E D+E
Directory kind=aa....aa, file=bb....bb, line=cc....cc
- Outputs information about the directory where an access error occurred.
- aa....aa: Directory type
- SGMB: Segment-managing directory
- bb....bb: Internal information 1 (name of the analyzed file)
- cc....cc: Internal information 2 (analyzed row)
- S: Terminates processing.
- O: Refer to the preceding message, resolve the error, and then re-execute the command.