KFPL00607-I L+S
aa....aa load started
- Index or LOB data loading started.
- aa....aa: Data that started loading
- Index: Index
- LOB: LOB data
- S: Continues processing.
KFPL00608-I L+S
aa....aa load ended
- Index or LOB data loading terminated.
- aa....aa: Data that finished loading
- Index: Index
- LOB: LOB data
- S: Continues processing.
KFPL00615-I L+S
aa....aa load started, server=bb....bb
- Server bb....bb index data loading started.
- aa....aa: Data that has started loading
- Index: Index
- bb....bb: Server name
- S: Continues processing.
KFPL00616-I L+S
aa....aa load ended, server=bb....bb
- Server bb....bb index data loading terminated.
- aa....aa: Data that finished loading
- Index: Index
- bb....bb: Server name
- S: Continues processing.
KFPL00621-I L+S
aa....aa in table bb....bb. cc....cc deleted
- Row or LOB data was deleted from table bb....bb.cc....cc.
- aa....aa: Type of data that was deleted
- Data: Row data
- LOB data: LOB data
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Continues processing.
KFPL00622-I L+S
aa....aa in table bb....bb. cc....cc deleted, server=dd....dd
- Server dd....dd row or LOB data was deleted from table bb....bb.cc....cc.
- aa....aa: Type of data that was deleted
- Data: Row data
- LOB data: LOB data
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Server name
- S: Continues processing.
KFPL00700-I L+S
Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff
- Multivolume reopen processing will be performed cc minutes from now. The maximum retries count is bb, and the next retry is number aa. The name of the file is ee....ee, and its host name is dd....dd.
- aa: Next retry number
- bb: Maximum retries count
- cc: Retry interval
- dd....dd: Host name
- ee....ee: File name
- If the length of the file name exceeds 104 characters, the last 104 characters of the file name are output.
- ff....ff: Reason for retry:
- No-file: File is not set.
- Same-file: The same file as before is set
- S: Resumes processing.
- O: Set the next file during retry processing.
KFPL00701-I L+S
File swapping started, file=aa....aa, reason=bb....bb
- Processing has begun on file aa....aa on the second or subsequent volume of a multivolume file.
- aa....aa: File name
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- bb....bb: Reason code:
- ENOSPC: There is no more space on the device
- EOV: End-of-volume was detected
- S: Resumes processing.
KFPL00702-I L+S
Pdload started, table=aa....aa.bb....bb, cc....cc, dd....dd
- Data loading or file partitioning (creation of the partitioning input data file) has started.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Double-byte space conversion level (spacelvl=space-conversion-level)
- If the space conversion level is specified in the system common definition pd_space_level operand or the database load utility option statement's spacelvl operand, this displays spacelvl=space-conversion-level. Further, if space conversion processing is not performed, spacelvl=space-conversion-level is not displayed.
- dd....dd:
- For data loading:
- generation=generation-number is displayed. However, this is only valid when the HiRDB Staticizer Option is included.
- For file partitioning:
- mode=split is displayed.
- S: Resumes processing.
KFPL00703-I L+S
aa....aa rows loaded
- aa....aa rows were stored.
When data is loaded into a FIX table in which a reserved column is defined, make sure that the number of rows being stored matches the number of rows in the input data file. If they do not match, some data from the input file might be loaded into the reserved column. - aa....aa: Number of rows stored
- S: Resumes processing.
KFPL00704-I L+S
Pdload terminated, return code=aa
- pdload utility processing is completed.
- aa: Return code:
- For data loading:
- 0: Data loading terminated normally.
- 4: Data loading terminated normally; however, a processing-unrelated warning error occurred or an input data error was detected, and some of the data was not stored.
- 8: Data loading terminated abnormally. Further, this return code is output even with an input data error, when there is a duplicate key error with the dataerr=rollback operand specified or the -i c option (index batch creation mode) is specified.
- For file partitioning (creation of the partitioning input data file):
- 0: All data in the input data file is output to the partitioning input data file.
- 4: Normal data in the input data file was output to the partitioning input data file. However, error data was not output to the partitioning input data file.
- 8: Creation of the partitioning input data file terminated abnormally.
- S: Terminates processing.
- O:
- 8 set as the return code:
Refer to the error message that was output to standard error or message log file to eliminate the cause of the error, then re-execute the command. Further, if data loading was executed in no-log mode, and the RDAREA performs a logless shutdown or a duplicate key error is detected during batch index creation, which leads to incompatibility between the tables and the indexes, return the database to its status before the database load utility (pdload) was executed, and then re-execute.
- 4 set as the return code:
Check for erroneous data by referring to the error information file. If there is any erroneous data, for data loading, re-execute data loading with the corrected data only. For file partitioning, correct the data, and then re-execute the database load utility.
KFPL00705-I L+S
aa....aa rows processing
- Row aa....aa is being processed.
- aa....aa: Number of rows
- S: Resumes processing.
KFPL00706-I L+S
Partial input data file split started, part=a/b
- Out of b total execution iterations required to create a partitioning input data file, processing of iteration a has started (in units of 1,024 RDAREAs).
- a: Current execution iteration count
- b: Total number of iterations to be executed
- S: Continues processing.
KFPL00707-I L+S
LOB load started, RDAREA=aa....aa
- Data loading of LOB data to the LOB RDAREA aa....aa has started.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: RDAREA name
- S: Continues processing.
KFPL00708-I L+S
LOB load ended, RDAREA=aa....aa, return code=bb
- Data loading of LOB data to the LOB RDAREA aa....aa has ended with return code bb.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: RDAREA name
- bb: Return code
- 0: Data loading of LOB data terminated normally.
- 8: Data loading of LOB data terminated abnormally.
- S: Continues processing if the return code is 0. Terminates processing if the return code is 8.
- O: If the return code is 8, refer to the error message output to standard error output, the message log file, or the error information file, and eliminate the cause of the error. Then, use a LOB intermediate file to re-execute data loading for the LOB RDAREA that had the error or the LOB RDAREA that was not processed.
KFPL00709-I L+S
aa....aa file was created, file=bb....bb
- Because specification of an error information file or a LOB intermediate file was omitted, file bb....bb was created.
SQL definition file bb....bb was created. - aa....aa: File type
- Error information: Error information file
- Lobmid: LOB intermediate file
- SQLDef: SQL definition file
- bb....bb: Unique file name generated by the system
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- S: Resumes processing.
KFPL00710-I L+S
Index information file assigned, index=aa....aa.bb....bb, RDAREA=cc....cc. file=dd....dd
- Index information for RDAREA cc....cc of index aa....aa.bb....bb was output to dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- cc....cc: RDAREA name
- dd....dd: File name
- If the length of the file name exceeds the value obtained from the following formula, the last number of characters obtained from the formula are output.
- 150 - authorization-identifier-length - index-name-length - RDAREA-name-length
- S: Resumes processing.
KFPL00711-I L
aa....aa started. table=bb....bb."cc....cc", RDAREA="dd....dd"
- The aa....aa process started.
RDAREA dd....dd of table bb....bb."cc....cc" is to be processed. - aa....aa:
- pdloadm: pdload control process
- pdsds: Single server process
- pdbes: Back-end server process
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: RDAREA name
- For loading of table unit data, an asterisk (*) is displayed.
- S: Continues processing.
KFPL00712-I L+S
aa....aa started, table=bb....bb.cc....cc, server=dd....dd,spacelvl=e, generation=ff
- Unload or reload processing has started for table bb....bb.cc....cc at server dd....dd.
spacelvl=e is displayed when a space conversion level is specified in the spacelvl operand of the option statement of the database reorganization utility. spacelvl=e is not displayed if no space conversion is performed by the utility.
When the inner replica facility is being used, generation=ff is displayed. - aa....aa: Executed processing:
- { LOB reload|LOB unload|Reload|Unload }
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Server name
- e: Space conversion level
- ff: Generation number
- S: Resumes processing.
KFPL00713-I L+S
aa....aa rows bbbbbb, table=cc....cc.dd....dd, server=ee....ee
- aa....aa rows of table cc....cc.dd....dd on server ee....ee were unloaded or reloaded.
- aa....aa: Number of rows processed
- bbbbbb: Executed processing:
- { unloaded|reloaded }
- cc....cc: Authorization identifier
- dd....dd: Table identifier
- ee....ee: Server name
- If the -g option is specified with respect to a row-partitioned table, displays the name of the server storing the RDAREA that matches the last partitioning condition in the table definition.
- S: Resumes processing.
KFPL00714-I L+S
aa....aa ended, table=bb....bb.cc....cc, server=dd....dd, return code=ee
- Unload processing, reload processing, used free page release processing, or used page read processing has terminated for table bb....bb.cc....cc at server dd....dd.
- aa....aa: Executed processing:
- { Unload|Reload|LOB unload|LOB reload|Reclaim|Page read }
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Server name
- ee: Return code
- S: If the return code is 0 or 4, resumes processing; otherwise, terminates processing.
- O: If the return code is neither 0 nor 4, refer to the error message that was output to the message log file to eliminate the cause of the error, then re-execute the command.
KFPL00715-I L+S
Index load started at aa....aa, index=bb....bb."cc....cc", RDAREA=dd....dd, generation=ee
- Index loading has started.
When the inner replica facility is being used, generation=ee is displayed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Server name
- bb....bb: Authorization identifier
- cc....cc: Index identifier
- dd....dd: RDAREA name
- ee: Generation number
- S: Resumes processing.
KFPL00716-I L+S
Index load ended at aa....aa, index=bb....bb, RDAREA=cc....cc, return code=dd
- Index loading terminated with return code dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Server name
- bb....bb: Index identifier
- cc....cc: RDAREA name
- dd: Return code:
- 0: Normal termination
- 8: Abnormal termination
- S: Resumes processing.
- O: If the processing terminated abnormally, refer to the error message that was displayed before this message to eliminate the cause of the error.
KFPL00717-I L+S
Pdrorg started, func=aaaa
- Database reorganization utility processing aaaa has started.
- aaaa: Processing:
- rorg: Table reorganization
- unld: Table unloading
- reld: Table reloading
- ixmk: Batch index creation
- ixrc: Index re-creation
- ixor: Index reorganization
- rclm: Used free page release processing
- bfon: Page read processing
- S: Resumes processing.
KFPL00719-I L+S
Pdrorg terminated, return code=aa
- Database reorganization utility (pdrorg) processing has terminated.
- aa: Return code:
- 0: Terminated normally.
- 4: Terminated normally, but a processing-unrelated warning error occurred.
- 8: Terminated abnormally.
- S: Terminates processing.
- O: If the return code is neither 0 nor 4, refer to the error message that was output to standard output or message log file to eliminate the cause of the error, then re-execute the command.
KFPL00720-I L+S
aaaaa file bb....bb, server=cc....cc, file=dd....dd
- An index information file was deleted.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aaaaa: Index
- bb....bb: deleted
- cc....cc: Server name
- dd....dd: File name
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- S: Resumes processing.
KFPL00721-I L+S
aa....aa in table bb....bb.cc....cc deleted, RDAREA=dd....dd
- Row data or LOB data was deleted from table bb....bb.cc....cc in RDAREA dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Type of data that was deleted:
- Data: Row data
- LOB data: LOB data
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: RDAREA name
- S: Resumes processing.
KFPL00722-I L+S
Unload file output completely, server=aa....aa, file=bb....bb
- Output to an unload data file has been completed at server aa....aa.
- aa....aa: Server name
- bb....bb: Name of unload data file
- If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Resumes processing.
KFPL00723-I L+S
aa....aa rows bb....bb, table=cc....cc.dd....dd, RDAREA=ee....ee
- bb....bb processing for aa....aa rows was executed for RDAREA ee....ee in table cc....cc.dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Number of rows processed
- bb....bb: Processing type
- { loaded|unloaded|reloaded }
- cc....cc: Authorization identifier
- dd....dd: Table identifier
- ee....ee: RDAREA name
- S: Resumes processing.
KFPL00724-I L+S
Index not created, index=aa....aa.bb....bb, RDAREA=cc....cc
- Because index aa....aa.bb....bb in RDAREA cc....cc is only part of a non-partitioned index, the index is left on uncompleted status.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- cc....cc: RDAREA name
- S: Resumes processing.
- O: Create the index using the index information file for the entire index.
KFPL00725-I L+S
Index aa....aa started at bb....bb, index=cc....cc."dd....dd", RDAREA="ee....ee", source=ff....ff, generation=gg
- Index information unload processing has started.
When the inner replica facility is being used, generation=gg is displayed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: unload
- bb....bb: Server name
- cc....cc: Authorization identifier
- dd....dd: Index identifier
- ee....ee: RDAREA name
- ****** is displayed for the RDAREA name in the case of index re-creation by index (idxname statement specified) or in the case of index reorganization.
- ff....ff: Data to be unloaded:
- row: Table data
- key: Index key
- gg: Generation number
- S: Resumes processing.
KFPL00726-I L+S
Index aa....aa ended at bb....bb, index=cc....cc."dd....dd", RDAREA="ee....ee", return code=ff....ff
- Index information unload processing is completed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: unload
- bb....bb: Server name
- cc....cc: Authorization identifier
- dd....dd: Index identifier
- ee....ee: RDAREA name
- ****** is displayed for the RDAREA name in the case of index re-creation by index (idxname statement specified) or in the case of index reorganization.
- ff....ff: Return code (0: normal termination; 8: abnormal termination)
- S: Resumes processing.
- O: In the case of abnormal termination, check the message that was output before this message, eliminate the cause of the error, then re-execute the command.
KFPL00727-I L+S
aa....aa keys processed, index=bb....bb."cc....cc", RDAREA="dd....dd"
- aa....aa plug-in indexes were batch-created.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Number of records
- bb....bb: Authorization identifier
- cc....cc: Index identifier
- dd....dd: RDAREA name
- S: Continues processing.
KFPL00728-I L+S
Index not reorganized, PLUGIN index aa....aa."bb....bb"
- Plug-in index aa....aa."bb....bb" is included in the indexes to be reorganized. Because plug-in indexes cannot be reorganized, reorganization processing for the plug-in index was skipped.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Continues processing.
- O: If the plug-in index needs to be re-created, take one of the following actions:
- Reorganize the table for which the plug-in index is defined
- Re-create the plug-in index
KFPL00732-I L+S
aa....aa started, table=bb....bb.cc....cc, spacelvl=d, generation=ee
- Unload or reload processing for table bb....bb.cc....cc has started.
spacelvl=d is displayed when a space conversion level is specified by the spacelvl operand of the option statement of the database reorganization utility. spacelvl=d is not displayed if no space conversion is performed by the utility.
When the inner replica facility is being used, generation=ee is displayed. - aa....aa: Processing that was executed:
- { LOB reload | LOB unload | Reload | Unload }
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- d: Space conversion level
- ee: Generation number
- S: Resumes processing.
KFPL00733-I L+S
aa....aa rows bb....bb, table=cc....cc.dd....dd
- Unload or reload processing for aa....aa rows has started for table cc....cc.dd....dd.
- aa....aa: Number of processed rows
- bb....bb: Processing type:
- unload: Unloading
- reload: Reloading
- cc....cc: Authorization identifier
- dd....dd: Table identifier
- S: Resumes processing.
KFPL00734-I L+S
aa....aa ended, table=bb....bb.cc....cc, return code=dd
- Unload or reload processing for table bb....bb.cc....cc has terminated.
- aa....aa: Processing type:
- Unload: Unloading
- Reload: Reloading
- LOB unload: LOB data unloading
- LOB reload: LOB data reloading
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd: Return code
- S: Return code 0 or 4: Resumes processing.
- Return code other than 0 or 4: Terminates processing.
- O: Return code other than 0 or 4:
- Refer to the error message that was output to the log file to eliminate the cause of the error, then re-execute the command.
KFPL00735-I L+S
Unload file output completed, file=aa....aa
- Output processing of an unload data file terminated.
- aa....aa: Unload data file name
- If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Resumes processing.
KFPL00736-I L+S
Pdrorg restarted, at aa....aa,table=bb....bb."cc....cc"dd....dd
- The table reorganization process was restarted from aa....aa.
- aa....aa: Process type
- unload: Unload process
- delete: Data deletion process
- reload: Reload process
- ixrc: Index re-create process
- status clear: Status clear process
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: ", server=server-name" is displayed when the -g option is not specified.
- S: Continues processing.
KFPL00738-I L+S
Pdpgbfon terminated, return code=aa
- Processing of the global buffer residence utility (pdpgbfon) Terminated with return code aa.
- aa: Return code
- 0: Terminated normally (reading into the global buffer completed).
- 4: A buffer flush occurred (not all pages were read into the global buffer).
- 8: Terminated abnormally (reading into the global buffer failed).
- 12: Terminated abnormally (pdrorg could not start, or it terminated abnormally).
- S: Terminates processing.
- O:
- If the return code is 4:
- If all table and index pages must be read into the global buffer, consider extending the global buffer. If there is an increase in dummy pages due to reduced data storage efficiency, resulting in an increased volume of used pages, consider releasing free pages or reorganizing the database.
- If the return code is 8:
- Refer to the message that was output before this message, and eliminate the cause of the error. Then, re-execute.
- If the return code is 12:
- Execution of pdrorg operating as an extension of pdpgbfon failed. Refer to the message that is output to standard error, the message log file, or the event log (in UNIX, syslogfile), resolve the error that caused abnormal termination of pdrorg, and then re-execute the command. For the system function return values to determine the reason for the execution of pdrorg failing, see the KFPL22000-E message output immediately before this message.
KFPL00739-I L+S
Pdreclaim terminated, return code=aaa
- The free page release utility (pdreclaim) process terminated with return code aaa.
- aaa: Return code:
- 0: Normal termination (releasing of used free page is complete)
- 4: A time-out occurred (now releasing a used free page)
- 8: Abnormal termination (releasing of used free page failed)
- Other values: Abnormal termination (pdrorg cannot be started or pdrorg terminated abnormally).
- S: Terminates processing.
- O:
- When the return code is 4:
Increase the wait time specified with the -w option. Alternatively, wait for the UAP accessing the table in which used free pages are to be released to terminate, and then re-execute.
- When the return code is 8:
See the message output before this message to eliminate the cause of the error, and then re-execute.
- When the return code is not 0, 4, or 8:
Failed to execute pdrorg when extending pdreclaim. The value returns to the return value of the system function. Refer to the message that is output to standard error, the message log file, or the event log (in UNIX, syslogfile), resolve the error that caused abnormal termination of pdrorg, and then re-execute the pdreclaim command.
KFPL00740-I L+S
Error exists in command line, usage is as follows
- An error was detected in the specified command. The command's format is output after this message.
- S: Terminates processing.
- O: Correct the error in the command and re-execute.
KFPL00750-I L+S
Audit trail aa....aa file load started(b,c,d), file=ee....ee
- Data began loading into the audit trail table.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Generation
- b: c (current) or s (other than current)
- c: d (waiting for data loading) or - (data loading is complete)
- d: h (currently holding) or - (not currently holding)
- ee....ee: Absolute path name of the audit trail file
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- S: Continues processing.
KFPL00751-I L+S
Audit trail aa....aa file loaded, file=bb....bb
- Data has been loaded into the audit trail table.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: Generation
- bb....bb: Absolute path name of the audit trail file
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- S: Continues processing.
KFPL00791-I L+S
Pdparaload started, table=aa....aa."bb....bb"
- Parallel loading of table aa....aa."bb....bb" was started.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Continues processing.
KFPL00792-I L+S
Pdload execution started, table=aa....aa."bb....bb"
- RDAREA unit data loading (pdload) of table aa....aa."bb....bb" was started by means of parallel loading.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Continues processing.
KFPL00793-I L+S
Pdload execution abnormal terminated, table=aa....aa."bb....bb", RDAREA="cc....cc", return code=dd, pdload process id=ee....ee
- RDAREA unit data loading (pdload), which was executed by parallel processing, terminated abnormally in the return code dd.
For details about pdload return codes, refer to message KFPL00704-I. - aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: RDAREA name
- dd: pdload return codes
- ee....ee: pdload process ID
- S: Continues processing.
- O: Take corrective action by following the procedure in the Operation when a command error occurs section under When loading data to a row partitioned table (parallel loading facility) in the HiRDB Version 9 Installation and Design Guide.
KFPL00794-I L+S
Pdparaload terminated, return code=aa
- Parallel loading terminated.
- aa: Return code
- 0: Parallel loading terminated normally.
- 4: Parallel loading terminated normally. However, one or more of the executed RDAREA unit data loads (pdload) terminated with return code 4.
- 8: Parallel loading terminated abnormally. However, one or more of the executed RDAREA unit data loads (pdload) terminated with return code 8.
- S: Terminates processing.
- O: When the return code is not 0, take corrective action according to the previously output error message KFPL00793-I. If the KFPL00793-I message was not output, take corrective action according to the previously output error message.
KFPL00800-I L+S
Loading until aa....aath row committed
- The loading transaction was completed up to the aa....aath row.
- aa....aa: Number of rows from the beginning of the input data file or unload file (number of rows from the beginning is also displayed in the case of re-execution)
- S: Continues processing.
KFPL00810-I L+S
aa....aa restart at bb....bbth row
- The utility's processing was restarted at the bb....bbth row.
- aa....aa: Utility:
- Pdload: Database load utility
- Pdrorg: Database reorganization utility
- bb....bb: Number of rows from the beginning of the input data file or unload file
- S: Continues processing.
KFPL00900-I E+L
Error detail, aa....aa
- This is error detail information.
- aa....aa: Internal error information
- S: The higher system that received the message handles it.
KFPL10000-E E+L
Command option '-i s' cannot be specified in this case
- For processing tables defined with non-partitioned key indexes processed in units of RDAREAs, -i s (index update mode) cannot be specified as the index creation method.
- S: Continues processing.
- O: Change the index creation method to -i n (index information output mode) and re-execute the command.
KFPL10001-E E+L
Command option '-r' cannot be used when partitioning condition altered
- Processing in units of RDAREAs cannot be specified for unload data file consolidation (-g option specified) because the partitioning condition for a table in the unload data file differs from the partitioning condition of the table to be reloaded.
- S: Terminates processing.
- Action
- To change the table partitioning condition, restore the previous partitioning condition and make a backup of the table. Specify the -g option and unload the file in table units.
- After changing the table partitioning condition, specify the -g option and reload the file in table units.
KFPL10002-E E+L
Command option "aa....aa" cannot be specified in this case
- If aa....aa is -W:
- When the lobunld statement (for unloading LOB data) is specified in the control information file, the -W option cannot be specified.
- When the unload statement (uoc) is specified in the control information file, the -W option cannot be specified.
- The -W option cannot be specified for a table containing abstract data type columns.
- If aa....aa is -k unld:
- Unload processing cannot be executed for a table for which a LOB column has been defined, except in the following cases:
For unloading data by specifying the -W option
Both the LOB column structure base table and the LOB data are unloaded at the same time with the -j option specified
- The falsification prevented table cannot perform unload processes for which the -W option is not specified.
- If aa....aa is -g:
- The -g option cannot be specified for the processing of a LOB column structure base table relative to a hash-partitioned table in which a LOB column is defined.
- If aa....aa is -j:
- When the -j option is specified, the -W option cannot also be specified.
- If aa....aa is -kc, -f:
- These options cannot be specified for a table that includes an abstract data type.
- If aa....aa is -b:
- If -k f (default) or -k c is specified, a binary-format input data file cannot be used for a table containing a column of abstract data type for which BLOB is an input parameter.
- If aa....aa is -in, -ix:
- These options cannot be specified for a table for which a plug-in index is defined.
- If aa....aa is -c:
- The -c and -W options cannot both be specified for a FIX table.
- If aa....aa is -t:
- Reloading by schema cannot be executed for an unload data file created by means of unloading by table. Also, if a tblname statement is specified by table, reloading by schema cannot be executed.
- If aa....aa is -k:
- When using UOC, only rorg or unld can be specified with the -k option.
- If aa....aa is -c dic:
- When using UOC, -c dic (specified for a dictionary table) cannot be specified.
- If aa....aa is -U:
- The -U option cannot be specified when data is loaded into one of the following tables:
- A table with an abstract data type column
- A table with a BINARY type column
- A table with a repetition column
- A FIX table
- aa....aa: {-W|-k unld|-g|-j|-kc|-f|-b|-in|-ix|-c|-t|-k|-c dic|-U}
- S: Terminates processing.
- O: Take one of the following actions:
- If aa....aa is -W:
- For the unloading operation, either specify the unload statement or delete the lobunld statement.
- To create an unload data file with pdrorg while using a UOC, specify the unload data file in the unload statement. To create an unload data file using a UOC, delete the -W option.
- If data loading is being performed, delete the -W option.
- If aa....aa is -k unld:
- When reorganizing a table, specify -k rorg. For unloading, specify the -W option.
- If aa....aa is -g:
- Delete the -g option.
- If aa....aa is -j:
- When unloading both LOB column structure base table data and LOB data simultaneously, delete the -W option. When unloading row data only, delete the -j option.
- If aa....aa is -kc, -f:
- When specifying a table containing an abstract data type, delete the -kc, -f option.
- aa....aa is -b:
- Specify the -k v option.
- If aa....aa is -in, -ix:
- When specifying a table for which a plug-in index is defined, delete the -in, -ix option.
- If aa....aa is -c:
- Correct the contents of the column structure information file by specifying the -a and -W options for a FIX table.
- If aa....aa is -t:
- Correct the -t option specification.
- If aa....aa is -k:
- When using a UOC, specify rorg or unld with the -k option. Also, when not using UOC, delete the unlduoc statement.
- If aa....aa is -c dic:
- When using a UOC, no process can be performed on the dictionary table. To process the table the user defined, specify -c user. Also, when not using UOC, delete the unlduoc statement.
- If aa....aa is -U:
- Load data from a pdload unload file. To create the pdload unload file, specify the -W option when you execute the pdrorg, and then unload the data.
KFPL10003-E E+L
Unable to specified command option 'aa....aa' when bb....bb
- If bb....bb is ADT column defined:
- The aa....aa option cannot be specified because the abstract data type is defined.
- If bb....bb is unload_row(uoc):
- The aa....aa option cannot be specified because (uoc) is specified in the unload statement.
- If bb....bb is INSERT ONLY table:
- The aa....aa option cannot be specified in the falsification prevented table.
- If bb....bb is ORG status:
- The aa....aa option cannot be specified because the RDAREA that stores the table is in online reorganization hold.
- aa....aa: {-W|-j|-k rorg|-f|-d}
- bb....bb: {ADT column defined|unload_row(uoc)|INSERT ONLY table|ORG status}
- S: Terminates processing.
- O:
- If bb....bb is ADT column defined:
- With the -W option, the data to be input from the indicated table to the Database Load Utility (pdload) cannot be created by the Database Reorganization Utility (pdrorg). Therefore, use a UAP to create the data.
- With the -j option, delete the -j option and re-execute.
- If bb....bb is unload_row(uoc):
- -W: Delete the -W option and execute.
- -k rorg: Change to -k unld and execute.
- -f: Delete the -f option and execute.
- If bb....bb is INSERT ONLY table:
- Delete the aa....aa option and execute.
- If bb....bb is ORG status:
- Execute after releasing online reorganization hold or after deleting the aa....aa option.
KFPL10004-E E+L
Unable to specified aa....aa in Control file when bb....bb
- If bb....bb is ADT column defined:
- aa....aa cannot be specified because an abstract data type is defined.
- If bb....bb is INSERT ONLY table:
- aa....aa cannot be specified because the table is a falsification prevented table.
- If bb....bb is invalid condition:
- aa....aa cannot be specified because the specification conditions are different.
- If bb....bb is Not divided table:
- For non-partitioned tables, the src_work control statement cannot be specified.
- If bb....bb is current character code set:
- For the current HiRDB default character encoding, the charset operand cannot be specified in the option control statement.
- If aa....aa: Control statement information
- {tblname | unlduoc |option job | option_row (diverskip) | src_work |option_row(charset)}
- If bb....bb: Reason information
- {ADT column defined | INSERT ONLY table | invalid condition | Not divided table |current character code set }
- S: Terminates processing.
- O:
- If bb....bb is ADT column defined:
- Data cannot be transferred to the indicated table. To transfer data to the indicated table, use a UAP to create data from the source table and then move it to the indicated table.
- If bb....bb is INSERT ONLY table:
- To port a falsification prevented table, specify the -W option, unload the table, and then use the database load utility (pdload) To port the table. Alternatively, if the aa....aa option cannot be specified for a falsification prevented table, delete the aa....aa option and re-execute.
- If bb....bb is invalid condition:
- option diverskip=on cannot be specified in the control statement. Remove it, and re-execute, or ensure a condition that can be specified.
- If bb....bb is Not divided table:
- Creation of the partitioning input data file can be executed for a partitioning table. Check whether the table specified on the command line is a partitioning table.
- If bb....bb is current character code set:
- The charset operand cannot be specified in the option control statement. Remove it, and then retry the operation, or ensure a condition that can be specified.
KFPL10005-E E+L
Unable to execute aa....aa command by each RDAREA, RDAREA="bb....bb"
- Data reloading by RDAREA or reorganization by RDAREA cannot be executed for the following reason:
- Although an added RDAREA is the processing target, the rebalancing utility has not been executed on that RDAREA.
- aa....aa: Utility:
- pdload: Database load utility
- pdrorg: Database reorganization utility
- bb....bb: RDAREA name
- S: Terminates processing.
- O: Take one of the following actions:
- After execution of the rebalancing utility, execute data reloading by RDAREA or reorganization by RDAREA
- Execute data loading by table or reorganization by table
KFPL10006-E E+L
Unable to execute aa....aa command, Table status=bb....bb, RDAREA=cc....cc, table=dd....dd."ee....ee"
- When bb....bb is DATA_UNFINISH:
- The following utilities cannot be executed because the table is in reload-not-completed data status:
- pdload
- pdrorg -k {rorg|ixmk|ixrc|ixor}
- pdrbal
- When bb....bb is completed:
- The following utility cannot be executed because table reloading is complete (the table is not in reload-not-completed data status):
- When bb....bb is memory_db:
- The following utilities cannot be executed because the table is in an in-memory database:
- pdrorg -k {rorg|reld}
- pdload
- aa....aa: Utility name
- pdload: Database load utility
- pdrorg: Database reorganization utility
- pdrbal: Rebalancing utility
- bb....bb: Table status
- DATA_UNFINISH: Reload-not-completed data status
- completed: Reload is complete
- memory_db: In an in-memory database
- cc....cc: RDAREA name
- dd....dd: Authorization identifier
- ee....ee: Table identifier
- S: Terminates processing.
- Action
- When bb....bb is DATA_UNFINISH:
- Use the database reorganization utility to reorganize the table, and then re-execute.
- bb....bb is completed:
- You cannot reregister a row in the applicable table or RDAREA.
- When bb....bb is memory_db:
- You cannot update the applicable table.
KFPL10007-E E+L
Unable to execute aa....aa command on ORG status, RDAREA="bb....bb", reason=cc....cc
- When the RDAREA is in online reorganization hold status, aa....aa could not be executed for reason cc....cc.
- aa....aa: Utility name
- pdload: Database load utility
- pdrorg: Database reorganization utility
- pdreclaim: Free page release utility
- bb....bb: RDAREA name
- cc....cc: Reason
- BLOB COLUMN defined: A BLOB column was defined.
- INSERT ONLY table: A falsification prevented table.
- replica RDAREA: The RDAREA is a replica RDAREA.
- current RDAREA: The RDAREA is the current RDAREA.
- S: Terminates processing.
- Action
- After releasing online reorganization shutdown, re-execute.
KFPL11111-E E+L
Time over, no response from utility server, time=(aa....aa, bb....bb)
- Because the process did not terminate within the utility run monitoring time specified in the pd_utl_exec_time operand of the system definition or the option statement in the utility, a no-response failure was judged to have occurred.
- aa....aa: The value set as the utility run monitoring time (in seconds)
- bb....bb: The response wait time for a time-out to occur (in seconds)
- S: Abnormally terminates.
- O: If the value aa....aa set as the processing time for the utility is not appropriate, change the specified value of the exectime operand in the option statement in the utility (after recovering from an error such as logless shutdown), and then re-execute. If the specified value is appropriate, after recovering from an error such as logless shutdown, re-execute the utility. If a similar error recurs even after re-executing the utility, contact the HiRDB administrator.
- Action
- If a timeout occurred even though value aa....aa set as the processing time for the utility is appropriate, a no-response error may have occurred. Back up the files in the %PDDIR%\spool\save directory and the %PDDIR%\tmp\command-name YYYYMMDDHHMMSS process-ID.txt file as investigation data and contact the customer support center.
KFPL11724-E E+L
PLUGIN environment definition error, code=aaa
- The environment variable is incorrectly specified.
- aaa: Error reason code
- -30: The storage area for the environment variable is invalid.
- -90: The specification value for the environment variable is greater than the maximum length that can be specified.
- S: Terminates processing.
- O: If the reason code is -90, correct the environment variable specification and re-execute the command.
- Action
- If the reason code is -30, contact the customer support center.
KFPL13002-E E+L
Row length too long
- A value specified in the table definition exceeds the row length that can be processed by a utility.
- S: Terminates processing.
- O: Consider revising the table definition as follows:
- Reduce the number of elements in a repetition column
- Reduce the column definition length
KFPL15007-E E+L
Dynamic load error occurred, shared library=aa....aa
- An error occurred during dynamic loading of a shared library required for processing.
- aa....aa: Absolute pathname of shared library
- S: Terminates processing.
- O: Refer to the preceding KFPL22000-E message.
- In UNIX:
- Resolve the error as follows, and then re-execute the command:
- If using EasyMT, check its installation for an error.
- If not using EasyMT, check the control information file and delete the information about the usage of EasyMT.
- In Windows:
- Review the control information file.
KFPL15010-E E+L
Invalid environment for aa....aa, reason=bb....bb
- The environment required to execute utility aa....aa is invalid.
- aa....aa: Name of utility
- bb....bb: Reason code:
- No-tty: There is no terminal in the execution environment.
- S: Terminates processing.
- O: Eliminate the cause of the error on the basis of the displayed reason code and re-execute:
- No-tty: Specify the identifier and password in the PDUSER environment variable and re-execute without specifying -u in the command line.
KFPL15011-E E+L
No specified Environment variable aa....aa
- The aa....aa environment variable has not been set.
- aa....aa:
- PDDIR: PDDIR environment variable
- PDUSER: PDUSER environment variable
- S: Terminates processing.
- O: Set the PDDIR environment variable or the PDUSER environment variable, and then re-execute.
KFPL15027-E E+L
Unable to execute pdload command without aa....aa privilege
- Because the user does not have privilege aa....aa for the table that was to be subject to data loading, the pdload utility could not be executed.
- aa....aa: Privilege:
- insert: INSERT privilege
- delete: DELETE privilege
- audit: Audit privilege
- S: Terminates processing.
- O: After being granted the privilege required during data loading, re-execute the command. When the target table for data loading is the audit trail table, the auditor must execute the command.
KFPL15029-E E+L
Table aa....aa.bb....bb not found in system
- The table specified on the command line was not found.
When *all* is displayed for bb....bb, the specified schema has no tables. Or, the tables in the schema were deleted during execution of the utility.
aa....aa: Authorization identifier - bb....bb: Table identifier
- S: Terminates processing.
- O: Correct the authorization identifier or table identifier specified on the command line and re-execute the command. Also, do not delete the tables during execution of the utility.
KFPL15030-E E+L
Table definition altered (aa....aa/bb....bb)
- Definition of a table subject to processing was modified during utility execution.
- aa....aa: Internal information
- bb....bb: Internal information
- S: Terminates processing.
- O: Do not modify the tables during execution of the utility; check the table definition and re-execute.
KFPL15031-E E+L
Unable to specify aa....aa table
- The following tables cannot be processed by the utility:
- Viewed tables
- Temporary tables
- Tables for which flexible hash partitioning is defined
- Matrix-partitioned tables for which flexible hash partitioning is defined on a second dimension partitioning column
- aa....aa: Table type
- viewed: Viewed table
- temporary: Temporary table
- flexiblehash: Table for which flexible hash partitioning is defined, or matrix-partitioned table for which flexible hash partitioning is defined on a second dimension partitioning column
- S: Terminates processing.
- O:
- For a viewed table or temporary table specified on the command line:
- Change the specified table name to the name of the base table, and then re-execute the command.
- For the following tables specified on the command line:
- Tables for which flexible hash partitioning is defined
- Matrix-partitioned tables for which flexible hash partitioning is defined on a second dimension partitioning column
- Because the pdparaload command cannot be executed, load the data another way, such as on a per-table basis.
- If the table name is incorrect, specify the correct table name, and then re-execute the command.
KFPL15032-E E+L
Specified constraint aa....aa."bb....bb" not found
- The specified constraint name is not defined in HiRDB.
- aa....aa: Authorization identifier
- bb....bb: Constraint name
- S: Terminates processing.
- P: Revise the constraint name, and then re-execute the command.
KFPL15034-E E+L
Specified RDAREA aa....aa not found
- Specified RDAREA does not contain a table or index to be processed.
- aa....aa: RDAREA name
- S: Terminates processing.
- O: Correct the RDAREA name and re-execute the command.
KFPL15035-E E+L
Only one RDAREA name can be specified
- An attempt was made to execute the database load utility (pdload) by specifying multiple RDAREA names, but the corresponding table was not partitioned by values.
- S: Terminates processing.
- O: Delete the incorrect information from the control information file and re-execute the command.
KFPL15036-E E+L
Specified RDAREA ID not found, ID=aa....aa
- The applicable utility (the RDAREA may have been deleted by mistake) cannot be executed because the RDAREA with the RDAREA ID aa....aa was not found.
- aa....aa: RDAREA ID (real RDAREA ID)
- S: Terminates processing.
- O: If the user inadvertently deleted the RDAREA while the utility was executing, create the deleted RDAREA and re-execute the utility. Alternatively, specify the generation number of the RDAREA to be processed and re-execute the utility.
KFPL15037-E E+L
Changed aa....aa, RDAREA "bb....bb"
- When aa....aa is current generation:
If the utility was executing without the generation (-q option) specified, the generation of RDAREA "bb....bb" was changed from the current generation.
When aa....aa is inner replica status:
If the utility was executing with the generation (-q option) specified, the replica status of RDAREA "bb....bb" was changed. - aa....aa:
- current generation: Current generation
- inner replica status: Replica status
- bb....bb RDAREA name
- S: Terminates processing.
- O:
- When aa....aa is current generation:
When executing the utility without specifying the generation, do not change the current generation of the RDAREA storing the table that is being executed.
When re-executing the utility without specifying the generation, return the generation of RDAREA aa....aa to the generation from when the utility was executed previously.
- When aa....aa is inner replica status:
When executing the utility while specifying the generation, do not change the inner replica status of the RDAREA being executed.
KFPL15040-E E+L
Insufficient memory on PROCESS
- A work area shortage occurred.
- S: Terminates processing.
- O: Check whether there are other processes that use a large amount of memory.
- There are processes that use a large amount of memory:
- Wait for the associated processes to terminate, then re-execute the command.
- There are no processes that use a large amount of memory:
- Use one of the following methods to ensure that there is sufficient memory:
- Reduce the number of simultaneously executing processes.
- Increase the size of the swap area.
- Increase the amount of memory.
- Note
- If this message is displayed during the execution of a plug-in-provided command, the message is output only to the indicated output device type (L).
KFPL15046-E E+L
aaaaaa error occurred, file=bb....bb
- A file I/O error occurred.
- aaaaaa: Processing resulting in the error:
- { Open|Read|Write|Close|Reopen }
- bb....bb: File name
- S: Terminates processing (in the case of the Close error, the system may resume processing).
- O: Refer to the message that is output after this message to eliminate the cause of the error, then re-execute the command.
KFPL15047-E E+L
File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)
- A file I/O error occurred.
- aa....aa: Reason for the error:
- Date-check:
- The creation date of the mounted tape is earlier than the date specified in the validate operand.
- Empty-file:
- The specified file is empty (0 bytes).
- File-format:
- The specified format and the actual file format are different. It is possible that the specified file name is invalid, or the file format specified on the command line or in the control statement does not match the contents. Further, for a DAT format input file, if the length of a single row of data exceeds 32 KB, the maxreclen operand must be specified in the source control statement.
- 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.
- File-sequence:
- The multi-volume file sequence was incorrect.
- Invalid-device:
- The entry type (attribute) of the specified file is invalid. Or, when MTguide is being used, MTguide has not been started. If the system can identify the entry type, it displays one alphabetic character enclosed in parentheses; this character is the same as the entry in the mode output by the OS's ls -l command. It is possible that a directory name was specified in a location that requires a file name (or vice versa), or that a character special file was assigned to a file where a character special file cannot be used.
- Invalid-environment:
- Because the set value 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 satisfies the prerequisite conditions of the HiRDB system or related program products.
- Invalid-parameter:
- The combination of specified parameters is invalid.
- Invalid-path:
- The path name is invalid.
- Invalid-permission:
- The specified file version is invalid (access privilege error). It is possible that a file is being used for which an access privilege has not been granted by an HiRDB administrator, or for MT, the write protect may be enabled.
- No-data:
- The data for the number of data items stored at the synchronization point was not found in the specified file.
- No-file:
- File to be read was not found or file into which data was to be written has been deleted.
- No-space:
- There is not enough space in the file to which data is to be written.
- In UNIX:
If this error occurs even when there is sufficient disk space, you might not have defined the HiRDB file system area for a large file, or the case falls under OS kernel parameter restrictions. For details about OS kernel parameter restrictions, see Checking and modifying OS parameters in the HiRDB Version 9 Installation and Design Guide.
- In Windows:
If this error occurs when there is sufficient disk space, it is possible that the HiRDB file system area is not defined as a large file (2048 MB or greater) in the pd_large_file_use operand.
- No swap-file:
- There is no unload data file for multivolume (check the file size or specify a multivolume file). If this error occurs during read processing, it is possible that a file is used for which write processing (unloading processing, etc.) did not terminate normally.
- Rorg:
- When pdrorg was executed, a file was unloaded by specifying -k unld.
- Same-file:
- The file processed immediately before was specified as a multivolume file. Or, an attempt was made to overwrite a previous volume during multivolume write processing.
- Schema-file:
- An unload file was used that was created on a per-table rather than a per-schema basis.
- Suppress:
- The -S option was not specified when unloading.
- Unmatch-entry:
- An entry in the file header does not match the information in the control information file (the system displays the inconsistent entry name in parentheses).
- bb....bb: Name of the system function in which the error occurred
- If the operating system detected the error: The system function name
- If the HiRDB file system detected the error: The name of the HiRDB system function name beginning with p_f_ios
- If other than the above: ***
- cc....cc: Error code
- If the operating system detected the error, this is the error number (errno: the foreign reference variable that displays the error status) returned by the system function.
- If the error is detected by the HiRDB file system, this is the HiRDB file system error code. For details on error codes, see 5.1 Error codes returned from HiRDB file system access requests. The primary error causes and measures to consider are listed below:
-1511: It is possible that the specified file path name violates the file name rules of the HiRDB file system. Area names have a maximum of 117 characters, and file names have a maximum of 30 characters.
-1532: It is possible that the specified file path name is invalid. Correct the file path name. Further, specify only the HiRDB file system name; if it is not specified up to the file name, specify it up to the file name.
-1534: It is possible that the specified file name is the same as a file name in use by another job. Change the file name.
-1535: There is insufficient volume. Further, if the insufficient volume appears immediately after the beginning of processing, consider that the value specified for the file size on the command line or in a control statement may exceed the HiRDB file system restriction. Use the pdfmkfs command to create a large HiRDB file system, or revise the initial volume and incremental volume specified on the command line or in the control statement.
-1538: The pdfmkfs command specifies a file that has not been initialized. Have the pdfmkfs command use an initialized file.
-1540: There is no access privilege to the HiRDB file system name. Have the HiRDB administrator grant an access privilege.
-1562: There is no HiRDB file system initialized by the pdfmkfs -k UTL command. Use the pdfmkfs command with UTL specified in the -k option to specify an initialized file.
- If an error cause other than the above: 0.
- dd....dd: Troubleshooting information (source file name and number that detected the error). This information is used by the customer support center.
- S: Terminates processing.
- O: From the error reason, function name, and error code, refer to 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.
KFPL15048-E E+L
File operation was canceled by aa....aa
- Multi-volume file exchange was cancelled.
- aa....aa: Cause of cancellation:
- system: Cancelled by the system.
- user: Cancelled by the user.
- S: Terminates processing.
- O: Re-execute the processing, if necessary.
KFPL15049-I L+S
MT was created at aa....aa
- The MT creation date specified in the input data file is YYYY-MM-DD.
- aa....aa: Creation date specified in the mounted MT label (in the format YYYY-MM-DD)
- Format: YYYY-MM-DD
- YYYY: Year
- MM: Month
- DD: Date
- S: Cancels processing if the file was created prior to the date or number of days specified in the validate operand of the control information file; continues processing if the file was created after the date or number of days specified in the operand.
- O: If processing is cancelled, mount the MT with the correct creation date and re-execute.
KFPL15050-E E+L
EasyMT error occurred, func=aa....aa, reason=bb....bb
- File I/O processing using EasyMT resulted in an error.
- aa....aa: Name of function resulting in the error
- bb....bb: Error detail information
- S: Terminates processing.
- O: Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.
KFPL15052-E E+L
Invalid aa....aa statement bb....bb entry in Control file, value=cc....cc, reason=dd....dd
- Value cc....cc specified for entry bb....bb of control statement aa....aa in the control information file is invalid.
- aa....aa: Control statement type
- bb....bb: Entry name
- cc....cc: Specified value
- dd....dd: Reason code:
- Invalid-device: File format is invalid.
- Invalid-permission: File permission is invalid.
- No-directory: There is no directory.
- Pathname-length: The length of the file path name is invalid.
- For items omitted from the control information file, the default values are displayed.
- S: Terminates processing.
- O: Check the corresponding item in the control information file, eliminate the cause of the error, then re-execute.
KFPL15053-E E+L
Length of statement in Control file is over,line=aa....aa
- If the control statement specified in the control statement file of the pdparaload command is added to the RDAREA name, the maximum length (1,023 bytes) is exceeded.
- aa....aa: Row number error (row number of the control statement in which the error occurred)
- S: Terminates processing.
- O: Change the file path name so that the maximum file length (1,023 bytes) will not be exceeded even if the control statement that specified the pdparaload control statement file is added to the RDAREA name. Then, re-execute the command. For details about how to specify control statements, see pdparaload in the manual HiRDB Version 9 Command Reference.
KFPL15059-E E+L
aa....aa directory not found
- The name specified for an index information file is not a directory.
- aa....aa: Directory name specified in the control information file
- S: Terminates processing.
- O: Correct the directory name in the control information file and re-execute the command.
KFPL15060-E E+L
Invalid file for index information file, file=aa....aa, reason=bb....bb
- File aa....aa specified as an index information file is invalid.
- aa....aa: Specified file name
- If the length of the file name exceeds 134 characters, the last 134 characters of the file name are output.
- bb....bb: Reason code:
- Duplicated-entry:
- When multiple files were specified, the same file was specified more than once.
- Invalid-device:
- File format is invalid.
- Invalid-header:
- Header ID is missing.
- Invalid-permission:
- Specified file permission is invalid.
- Invalid-record-length:
- When multiple files were specified, some of the files have different record lengths.
- No-file:
- Specified file was not found.
- No-header:
- Header is missing.
- S: Terminates processing.
- O: Refer to the specified index information file and the reason code to eliminate the cause of the error, then re-execute.
KFPL15061-E E+L
Imcomplete record found in index information file, file=aa....aa, reason=bb....bb
- Index information file aa....aa contains an invalid record.
- aa....aa: Specified file name
- If the length of the file name exceeds 118 characters, the last 118 characters of the file name are output.
- bb....bb: Reason code:
- Tally-length:
- Total length of fixed-length records is not a multiple of the record length.
- Variable-record:
- The length of the data part of a variable-length record is invalid.
- S: Terminates processing.
- O: Because the index information file is damaged, re-create the index and re-execute.
KFPL15062-E E+L
aa....aa error occurred, func=bb....bb, rc=cc....cc
- An error occurred in one of the following processing operations:
- Sort processing
- Magnetic tape I/O processing
- aa....aa: Processing that generated the error
- SORT: Sort processing
- EasyMT: Magnetic tape I/O processing
- bb....bb: Name of function resulting in the error
- cc....cc: Return code set by the function resulting in the error
- S: Terminates processing.
- O: Take the following action:
- If aa....aa is SORT:
Refer to 7. Messages Related to Sort Processing, and take corrective action.
Messages related to sort processing are output in the format KBLSnnn-E, where nnn denotes the absolute value of the return code that is output to cc....cc.
The table below summarizes frequently output return codes and the required corrective action:
Return code | Action |
---|
-202 | Memory shortage. Reduce the work buffer size specified in the sort operand. |
-290 | Work buffer shortage. Increase the work buffer size specified in the sort operand. |
-210, -230 | An I/O error occurred. It is possible that the disk space for sort processing is insufficient. If insufficient disk space is the cause of the error, specify a disk with sufficient space in the sort operand, and then re-execute the processing. |
If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact the customer support center.
- If aa....aa is EasyMT:
Contact the customer support center.
KFPL15063-E E+L
aa....aa failed, index=bb....bb, authid=cc....cc, file=dd....dd, RDAREA=ee....ee
- An error occurred during processing aa....aa.
- aa....aa: Processing:
- Check-status: Checking the index status
- Commit: Terminating index creation
- Load-index: Creating an index
- Preparation: Preparing for processing
- Purge-index: Deleting an index
- Unfinish-index: Processing the incomplete index status
- bb....bb: Index identifier
- cc....cc: Authorization identifier
- dd....dd: File name
- If the length of the file name exceeds 52 characters, the last 52 characters of the file name are output.
- ee....ee: RDAREA name (if the RDAREA name cannot be identified, **....** is displayed)
- S: Terminates processing.
- O: Refer to the message that was output before this message to eliminate the cause of the error, and re-execute.
KFPL15064-E E+L
Specified index record file=aa....aa conflicted with command line specification, reason=bb....bb
- Specification on command line is in conflict with index information file aa....aa due to bb....bb reason.
- aa....aa: File name
- If the length of the file name exceeds 95 characters, the last 95 characters of the file name are output.
- bb....bb: Reason code:
- Invalid-table: Authorization identifier or table identifier is invalid.
- S: Terminates processing.
- O: Check the specification of the authorization identifier or table identifier on the command line and in the index information file to eliminate the cause of the error, then re-execute.
KFPL15065-E E+L
Index aa....aa on table bb....bb.cc....cc not found in server=dd....dd
- Index aa....aa of table bb....bb.cc....cc was not found on server dd....dd.
- aa....aa: Index name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Server name
- S: Terminates processing
- O: Correct the server name specified in the control statement or command line, and then re-execute.
KFPL15066-E E+L
Index record in aa....aa not available for bb....bb.cc....cc, reason=dd....dd (system=ee....ee, file=ff....ff)
- Index information file aa....aa is not the most recent file for index bb....bb.cc....cc.
- aa....aa: File name
- If the length of the file name exceeds the value obtained from the following formula, the last number of characters obtained from the formula are output.
- Where the reason code is Table-division:
- 100 - authorization-identifier-length - index-identifier-length
- Where the reason code is Unload-time:
- 97 - authorization-identifier-length - index-identifier-length
- bb....bb: Authorization identifier
- cc....cc: Index identifier
- dd....dd: Reason code:
- Table-division:
- The number of partitions does not match the actual table partitions.
- Unload-time:
- The date the index information file was created does not match. ee....ee displays the date the most recent index information file was created (when -i c or n was specified) or the date the index was invalidated (when -i x was specified). ff....ff displays the date the specified index information file was created. Both dates are displayed in the format %Y-%m-%d %H:%M:%S. If reload processing has already been completed, loaded is displayed.
- ee....ee: Value in the HiRDB system
- ff....ff: Value in index information file
- S: Terminates processing.
- O: Re-execute specifying the most recent information file, or re-create the index.
KFPL15067-E E+L
Unmatched number of index record file(s)=aa....aa, table division=bb....bb at server=cc....cc, index=dd....dd
- The number of index information files specified in the index statements of the control information file does not match the number of table partitions in the server.
- aa....aa: Number of index statements specified in the control information file
- bb....bb: Number of table partitions in the server
- cc....cc: Server identifier
- dd....dd: Index name
- S: Terminates processing.
- O: Specify as many index statements in the control information file as there are table partitions in the server, then re-execute.
KFPL15068-E E+L
Specified index record file=aa....aa conflicted with Control file specification, reason=bb....bb
- Information in the control information file contradicts the information in index information file aa....aa in terms of bb....bb.
- aa....aa: File name
- If the length of the file name exceeds 113 characters, the last 113 characters of the file name are output.
- bb....bb: Reason code:
- Unload-condition:
- The user specified the file into which the non-partitioning index of a partitioned table was unloaded in units of RDAREAs using the control information file, but the file contains the index information file unloaded in units of tables
- Invalid-index:
- Index name is different.
- Invalid-RDAREA:
- RDAREA name is different.
- Invalid-RDAREA-id:
- RDAREA identification number is different.
- S: Terminates processing.
- O: Check the index information file specified in the index statement of the control information file, eliminate the cause of the error, then re-execute.
KFPL15069-E E+L
Unmatched index records, files=aa....aa,bb....bb
- Index information in index information file aa....aa is different from that in index information file bb....bb.
- aa....aa: Name of index information file
- bb....bb: Name of index information file
- If the length of the file name exceeds 85 characters, the last 85 characters of the file name are output.
- S: Terminates processing.
- O: Correct the control information file and re-execute.
KFPL15070-E E+L
aa....aa failed, status=bb
- An error occurred during the aa....aa processing.
- aa....aa: Processing:
- Check-Status: Index status checking
- bb: Status:
- 1: After the index information file had been created, the table was modified by one of the following means, so the index information file's contents no longer match the table's contents, making the index information file unusable:
- By execution of pdload or pdrorg by RDAREA
- By reinitialization of an RDAREA storing the index's table (execution of pdmod)
- 3 or 4: An index has been created.
- S: Terminates processing.
- O:
- When the status is 1:
Create an index based on the index information file created with pdload or pdrorg; or, use pdrorg (-k ixrc) To re-create the index.
- When the status is 3 or 4:
Check that the correct index was created.
KFPL15071-E E+L
Unmatched generation number between number "aa" of bb....bb "cc....cc" and number "dd" of command line
- Generation number "aa" of bb....bb and generation number "dd" of the -q option (the current generation number when the -q option is not specified) do not match.
- aa: Generation number of bb....bb
- bb....bb: File type
- index-record-file: Index information file
- Lobmid-file: LOB middle file
- unload-file: Unload data file
- cc....cc: The file name of bb....bb
- dd: The generation number specified by the -q option (the current generation number if the -q option is not specified)
- S: Terminates processing.
- O:
- If "dd" is correct:
Specify bb....bb created by the generation number specified by the -q option in the control statement, and then re-execute.
- If "dd" is incorrect:
Specify in the -q option the generation number that created bb....bb, and then re-execute.
KFPL15101-E E+L
Specified column aa....aa not found
- Column name specified in the column structure information file is not found in the names of columns comprising the table.
- aa....aa: Column name
- S: Terminates processing.
- O: Correct the column name in the column structure information file and re-execute the command. Note that neither unneeded tabs nor spaces can be specified in the column structure information file. Accordingly, do not use any unneeded tabs or spaces when specifying the column name.
KFPL15102-E E+L
Column aa....aa is duplicated
- A duplicated column name was specified in the column structure information file.
- aa....aa: Column name
- S: Terminates processing.
- O: Delete the duplicate column name from the column structure information file and re-execute the command.
KFPL15199-E E+L
Logical inconsistency occurred in aa....aa, data=bb....bb
- Logical inconsistency was detected in a program.
- aa....aa: Name of function
- bb....bb: Invalid data
- S: Terminates processing.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPL15224-E E+L
Insert error occurred at aa....aaTH row, table=bb....bb.cc....cc
- An error occurred during reloading of row aa....aa.
- aa....aa: Row number
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Refer to the message output to the log file before this message to check the cause of the error, and re-execute the command.
KFPL15225-E E+L
Rollback called
- Processing was rolled back for the reason indicated in the message log file before this message.
- S:
- n specified in the -l option:
Terminates abnormally (the database remains on error status)
- a or p specified in the -l option:
Terminates processing
- O: Eliminate the cause of the rollback by checking the message log file that was output before this message. If n was specified in the -l option, use the backup copy to recover the database to the status it was in before the utility executed.
KFPL15226-E E+L
aa....aa request failed, table=bb....bb.cc....cc, server=dd....dd
- An error occurred in a table during processing aa....aa.
- aa....aa: Processing:
- Scan: Row retrieval
- Delete: Row deletion
- Insert: Row insertion
- LOB delete: LOB data deletion
- LOB insert: LOB data insertion
- LOB scan: LOB data retrieval
- Map purge: Deletion of LOB data definition information
- LOB length: Acquisition of LOB data length
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Server name
- S: Terminates processing.
- O: Refer to the message that was output to the message log file before this message to eliminate the cause of the error.
KFPL15227-E E+L
Unable to aa....aa without bbbbbb privilege
- The aa....aa command cannot be executed because the user does not have table access privilege.
- aa....aa: Command
- pdrorg: Database reorganization utility
- pdreclaim: Free page release utility
- pdpgbfon: Global buffer residence utility
- bbbbbb: Required access privilege
- DBA: DBA privilege
- audit: Audit privilege
- delete: DELETE privilege
- insert: INSERT privilege
- select: SELECT privilege
- S: Terminates processing.
- O: After being granted table access privileges, re-execute the command. When the audit trail table is being processed, the auditor must execute this command.
KFPL15229-E E+L
Unable to get aa....aa information, table=bb....bb."cc....cc"
- Definition information aa....aa cannot be obtained due to the message that was output before this message.
- aa....aa: Type of definition information:
- ADT: Abstract data type information
- AUDIT: Audit definition information
- cluster: Cluster key information
- column: Column information
- divide: Partitioning information
- gen: Generation number
- index: Index information
- LOB: LOB information
- multidim: Matrix partitioning information
- privilege: Access privilege information
- rdarea: RDAREA information
- schema: Schema information
- server: Server information
- table: Table information
- constraint: Constraint information
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- If a name cannot be determined, HiRDB displays the symbol **....**.
- For schema units, HiRDB displays the symbol *all*.
- S: Terminates processing.
- O: Refer to the message in the log file that was output before this message to eliminate the cause of the error, and re-execute the command.
- Note
- If this message is displayed during the execution of a plug-in-provided command, the message is output to the indicated output device type (E+L).
KFPL15231-E E+L
cc....cc table aa....aa.bb....bb cannot be specified for table name
- The specified table cannot be processed because it is not a permanent base table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Table type
- Viewed: Viewed table
- Temporary: Temporary table
- S: Terminates processing.
- O: Review the specified table name, and then re-execute the command after specifying the name of the correct permanent base table.
- Note
- If this message is displayed during the execution of a plug-in-provided command, the message is output to the indicated output device type (E+L).
KFPL15232-E E+L
Unable to use sequence aa....aa."bb....bb"
- You do not have privileges to use the sequence generator aa....aa."bb....bb", so you cannot use it.
- aa....aa: Sequence generator authorization identifier
- bb....bb: Sequence generator identifier
- S: Terminates processing.
- O: Use a sequence generator for which you have use privileges.
KFPL15233-E E+L
Unable to get sequence information, sequence=aa....aa."bb....bb"
- Definition information about aa....aa."bb....bb" cannot be obtained due to the details described in the message that was output prior to this message.
- aa....aa: Sequence generator authorization identifier
- bb....bb: Sequence generator identifier
- S: Terminates processing.
- O: Refer to the preceding message, resolve the error, and then re-execute the command.
KFPL15234-E E+L
Specified RDAREA aa....aa not found, table=bb....bb.cc....cc
- RDAREA aa....aa specified in the -r option does not contain table bb....bb.cc....cc.
- aa....aa: RDAREA name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Correct the RDAREA name and re-execute the command.
KFPL15235-E E+L
Specified sequence aa....aa."bb....bb" not found
- There is no sequence generator specified in the column structure information file, the null value information file, o rthe function information file.
- aa....aa: Sequence generator authorization identifier
- bb....bb: Sequence generator identifier
- S: Terminates processing.
- O: Re-examine the sequence generator specified in the structure information file, null value information file, or the function information file, and if the name is invalid, specify a correct name and re-execute data loading. In addition, if a sequence generator has not been defined, define the corresponding sequence generator, and then re-execute data loading.
KFPL15240-E E+L
Insufficient memory on PROCESS, size=aa....aa, part=bb....bb, code=cc....cc
- A memory shortage occurred.
- aa....aa: Size (in bytes) of memory resulting in shortage
- However, a negative value is displayed because the size of the target memory exceeds 2 GB.
- bb....bb: Part number
- cc....cc: Part code
- S: Terminates processing.
- O: Check whether there are other processes that use a large amount of memory.
- There are processes that use a large amount of memory:
- Wait for the associated processes to terminate, then re-execute the command.
- There are no processes that use a large amount of memory:
- Use one of the following methods to ensure that there is sufficient memory:
- Reduce the number of simultaneously executing processes.
- Increase the size of the swap area.
- Increase the amount of memory.
KFPL15246-E E+L
aa....aa error occurred, file=bb....bb
- File deletion failed.
- aa....aa: Unlink
- bb....bb: File name
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- S: Resumes processing.
- O: The file is not deleted. Delete the file if it is not needed.
KFPL15281-E E+L
No index on table aa....aa.bb....bb
- An index is not defined on the specified table aa....aa.bb....bb; therefore, the following operations cannot be performed: index creation, used free page release processing, or reading data into the global buffer.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Check the specified table name, specify the name of a table for which an index has been defined, then re-execute the command.
KFPL15282-E E+L
No LOB column on table aa....aa.bb....bb
- LOB processing is disabled because no LOB column is defined in the specified table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Check the specified table name. To process LOB data, specify the name of a table for which a LOB column has been defined, then re-execute the command.
KFPL15283-E E+L
Unable to execute pdrorg command, aa....aa does not support
- aa....aa, which is not supported by the current version of the Database Reorganization Utility (pdrorg), cannot be executed. Similarly, pdreclaim and pdpgbfon, which also use pdrorg, cannot be executed.
- aa....aa:
- ADT column: Abstract data type column
- ADT return: Constructor parameter reverse generation function for returning the abstract data type
- S: Terminates processing.
- O: When ADT return is displayed for aa....aa, unloading with -W specified cannot be executed. To reorganize a table or transfer data to another table, check if unloading without the -W specification might be possible. To reference the unload data from a UAP, use another facility to unload the data or use a UAP to extract the data.
- Action
- Cancel the execution of the database reorganization utility (pdrorg), the free page release utility (pdreclaim), and the global buffer residence utility (pdpgbfon).
KFPL15284-E E+L
Unable to execute aa....aa, PLUGIN does not support bb....bb function
- The function bb....bb is not supplied by the plug-in; the function aa....aa cannot be executed. Or, the function aa....aa cannot be executed because the function bb....bb of the plug-in used by the LOB RDAREA is not supported.
- aa....aa: Function for which execution was attempted
- ixmk: Batch creation of an index
- pdreclaim: Free page release utility
- pdpgbfon: Global buffer residence utility
- bb....bb: Plug-in-provided function
- INDEX_LOAD: Plug-in index batch-created section recovery function
- PAGE_FREE: Release used free pages
- PAGE_READ: Data read facility to the global buffer
- S: Terminates processing.
- O: To create a plug-in index, execute the index creation function (-k ixrc). Also, pdpgbfon cannot be processed for a LOB RDAREA. Terminate the command.
KFPL15285-E E+L
Unable to specified aa....aa option, PLUGIN does not support bb....bb function
- The function bb....bb is not supplied by the plug-in; the option aa....aa cannot be executed.
- aa....aa: Option {-i n: index information output mode}
- bb....bb: Implementation function {INDEX_LOAD: Plug-in index batch-created section recovery function}
- S: Terminates processing.
- O: If aa....aa is -i n, set index creation mode to either -i c (batch index creation mode) or -i s (index update mode).
KFPL15286-E E+L
Column "aa....aa" cannot be specified in bb....bb
- Because column "aa....aa" does not support the constructor parameter reverse generation function for returning the BLOB attribute, it cannot be specified for bb....bb.
- aa....aa: Column name
- bb....bb: Type:
- blobtovarchar_row: Row in the blobtovarchar statement
- S: Terminates processing.
- O: When blobtovarchar_row is displayed for the type, specify an abstract data type whose return value from the constructor parameter reverse generation function is the BLOB type, and re-execute the command.
KFPL15287-E E+L
Unable to convert data, column= aa....aa, line=bb....bb
- Data in the bb....bbth row of column aa....aa cannot be converted.
Consider the following causes: - There is more than 32 KB of data in the BLOB-type data that was returned by the constructor reverse generation function, and it has the abstract data type specified by the blobtovarchar statement.
- An invalid string was stored in the relevant column.
- aa....aa: Column name
- bb....bb: Row number
- S: Terminates processing.
- P: If there is more than 32 KB of data in the BLOB-type data that has the abstract data type specified by the blobtovarchar statement, reduce the data size to no more than 32 KB. Alternatively, check whether any invalid character strings are stored in the relevant column, and if so, correct them.
KFPL15288-E E+L
Unable to data copy, data size=aa....aa, limit=bb....bb, line= cc....cc
- BLOB data in the cc....ccth line with data size aa....aa cannot be copied because it is larger than the allocated memory size of bb....bb.
- aa....aa: Data size
- bb....bb: Allocated memory size
- cc....cc: Line number
- S: Terminates processing.
- O:
- If the loblimit operand is specified in the option statement, change the specified value so that it is greater than the data size and re-execute.
- If the loblimit operand is not specified in the option statement, specify a value greater than the data size in the loblimit operand in the option statement and re-execute.
KFPL15300-E E+L
Invalid unload file, file=aa....aa
- Specified unload data file was not created correctly.
- aa....aa: Name of unload data file
- If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Terminates processing.
- O: Specify an unload data file that was created correctly during unload processing and re-execute the command.
KFPL15301-E E+L
Unable to reload file by aa....aa, file=bb....bb
- Because the specified unload data file was not created in units of tables in a user RDAREA or dictionary RDAREA, data cannot be reloaded in the units specified in the -c option.
- aa....aa: Reload unit:
- { user table|dictionary }
- bb....bb: Name of unload data file
- If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Terminates processing.
- O: If the unload data file was created for each table in a user RDAREA, reload the data in units of tables. If the unload data file was created for tables in a dictionary RDAREA, reload the data in units of dictionary tables.
KFPL15302-E E+L
Invalid aa....aa file, kind=bb....bb, file=cc....cc
- The file specified for aa....aa processing contains bb....bb. The file cannot be used because the processing to be executed does not match the file contents.
- aa....aa: Processing to be executed
- { lobunld|unload }
- bb....bb: Specified file contents:
- table: Base table
- LOB: LOB data
- table (LOB): Base table and LOB data
- cc....cc: Name of the unload data file
- If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Terminates processing.
- O: Match the processing to be executed with the file contents and re-execute.
- lobunld statement executed:
Specify a file to which LOB data was unloaded.
- unload statement executed:
Specify a file to which a base table was unloaded. To use a file to which base table and LOB data were unloaded simultaneously, specify the command's -j option.
KFPL15305-E E+L
Table aa....aa.bb....bb not found in unload file, file=cc....cc
- Specified table aa....aa.bb....bb was not found in the unload data file.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 169 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Specify the unload data file containing the table and re-execute the command. Or, if the specified table name is invalid, correct it and re-execute the command.
KFPL15308-E E+L
Number of aa....aa.bb....bb columns not equal to unload file, file=cc....cc
- The number of columns in table aa....aa.bb....bb in the unload data file does not match the number of columns in the reload destination table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 157 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Create an unload data file for the specified table and re-execute the command.
KFPL15310-E E+L
aa....aa information of bb....bb.cc....cc not equal to unload file, file=dd....dd
- Reloading cannot be executed because the definition (partitioning definition or LOB column definition) for table bb....bb.cc....cc in the unload data file does not match the definition of the reload table. LOB cannot be processed if the partitioning definition for the unload data file differs from the reload table definition.
- aa....aa: Definition description of the specified table:
- Divided: Partitioning definition
- LOB: LOB column definition
- Divided (LOB): Partitioning definition (LOB process)
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Name of the unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 147 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Create the unload data file for the specified table and reload.
KFPL15311-E E+L
Table aa....aa.bb....bb definition altered RDAREA information not equal to unload file, file=cc....cc
- Table aa....aa.bb....bb cannot be reloaded because the definition of table storage RDAREAs used during reloading does not match the definition used during unloading.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of the unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 131 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Specify the RDAREAs used during unloading and re-execute the command.
KFPL15312-E L+E
Unable to reload divided method altered
- Loading cannot be executed without the -g option specified because the table partitioning method specified for reloading does not match the partitioning method used for unloading. Reloading fails in the following cases when there is a mismatch in the partitioning method specifications:
- Reloading from an unpartitioned table or a table partitioned by flexible hash partitioning or FIX hash partitioning to a table with key range partitioning
- Reloading from an unpartitioned table or a table partitioned by key range partitioning or flexible hash partitioning to a table with FIX hash partitioning
- Reloading from a table partitioned by FIX hash partitioning to a table with FIX hash partitioning when the partitioning conditions have been changed
- Reloading from a table partitioned by key range partitioning to a table with key range partitioning when the partitioning conditions have been changed
- Data cannot be reloaded between tables partitioned with different partitioning methods during reorganization by RDAREA.
- S: Terminates processing.
- O: Change the partitioning method; use the following procedure, as applicable:
- When the data can be placed in one unload file:
Unload with the -g option specified, modify the table definition, then reload with the -g option specified.
- When the data cannot be placed in one unload file:
Unload with the -W option specified, modify the table definition, then use the database load utility to load the data.
KFPL15313-E E+L
Abstract data type definition altered, table=aa....aa."bb....bb", COLUMN="cc....cc", TYPE="dd....dd", attribute=ee....ee
- Reloading cannot be executed because the abstract data type definition during unloading differs from the abstract data type definition during reloading. For details, see the KFPL15314-E message.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Column name
- dd....dd: Abstract data type name
- ee....ee: Attribute that is different from the one used during unloading:
- TYPE_NAME: Data type name
- PLUGIN_ID: Plug-in ID
- DEF_ATTR_NUM: Abstract data type attributes count
- DEF_ATTR_DTYPE: Attribute data type
- DEF_ATTR_DLEN: Attribute definition length
- DEF_ATTR: Abstract data type attribute definition
- LOB_RDAREA_NUM: Number of LOB column storage RDAREAs
- LOB_RDAREA: RDAREA for storing LOB attribute data
- LOB_RDAREA_ID1, -2, -3: Attributes 1 to 3 of the LOB column storage RDAREAs
- LOB_RDAREA_ID: LOB column storage RDAREA ID
- LOB_RDAREA_SERV: Server name where LOB column storage RDAREAs are located
- ADT_NUMBER: Abstract data type column definitions count
- UNLOAD_TYPE: Abstract data type unload method
- FUNC_PARAM_NUM: Function parameters count
- FUNC_PARAM_TYPE: Function parameter data type
- FUNC_PARAM_LEN: Function parameter data length
- S: Terminates processing.
- Action
- A table whose abstract data type definition has been modified cannot be reloaded. Use a UAP, etc., to transfer the data. Or, set the abstract data type definition to that used during unloading and then reload.
- If the plug-in that provides the applicable abstract data type supports the constructor parameter reverse generation function, recover the table from the backup or set the abstract data type definition to that used during unloading and then reload. Then specify the constructor parameter reverse generation function (unld_func statement) in the control information file and unload the table, modify the abstract data type attribute, and then reload the table by specifying the constructor function facility (unld_func statement).
KFPL15314-E L
Unload=aa....aa, Reload=bb....bb, position=cc....cc
- Displays detailed information (definition contents during unloading and reloading) for the preceding KFPL15313-E message.
- aa....aa: Definition contents during unloading
- bb....bb: Definition contents during reloading
- cc....cc: Definition position (0 if the position cannot be identified)
- The relationships between ee....ee in the KFPL15313-E message and aa....aa, bb....bb, and cc....cc in this message are shown below:
ee....ee in KFPL15313-E | Output aa....aa and bb....bb | Output format | cc....cc |
---|
TYPE_NAME | authorization-identifier.abstract-data-type-name | Characters | -- |
PLUGIN_ID | Plug-in ID | Decimal number |
DEF_ATTR_NUM | Attributes count | Decimal number |
DEF_ATTR_DTYPE | Attribute data type:
- INTEGER
- SMALLINT
- CHAR
- VARCHAR
- NCHAR
- NVARCHAR
- MCHAR
- MVARCHAR
- FLOAT
- SMALLFLT
- BLOB
| Characters | Definition sequence number of abstract data type attribute definition |
DEF_ATTR_DLEN | Attribute definition length | Decimal number |
DEF_ATTR | Abstract data type type ID | Decimal number |
LOB_RDAREA_NUM | Number of LOB column storage RDAREAs | Decimal number | LOB definition sequence number |
LOB_RDAREA | Name of LOB column storage RDAREA | Characters |
LOB_RDAREA_ID1 | LOB column storage RDAREA definition sequence | Decimal number |
LOB_RDAREA_ID2 | LOB column storage RDAREA storage sequence | Decimal number |
LOB_RDAREA_ID3 | ID of table storage RDAREA corresponding to LOB column storage RDAREA | Decimal number |
LOB_RDAREA_ID | ID of LOB column storage RDAREA | Decimal number |
LOB_RDAREA_SERV | Name of server where LOB column storage RDAREA is located | Characters |
ADT_NUMBER | Number of abstract data type columns defined in table | Decimal number | -- |
UNLOAD_TYPE | Abstract data type unloading and reloading method:
- unload_func:
- Unloading with unload_func statement specified
- reld_func:
- Reloading with reld_func statement specified
- instance:
- Unloading without using unld_func statement or UNLOAD function
- Reloading without using reld_func statement or UNLOAD function
- unload:
- Unloading or reloading with UNLOAD function
| Characters |
FUNC_PARAM_NUM | - aa....aa:
- Number of functions specified by unld_func statement
- bb....bb:
- Number of parameters specified by reld_func statement
| Decimal number | Specification sequence of function parameter of reld_func statement |
FUNC_PARAM_TYPE | Parameter data type (each data type is the same as DEF_ATTR_DTYPE):
- aa....aa:
- Data type of value returned by function specified by unld_func statement
- bb....bb:
- Data type of function parameter specified by reld_func statement
| Characters |
FUNC_PARAM_LEN | Parameter data size
- aa....aa:
- Definition length of value returned by function specified by unld_func statement
- bb....bb:
- Definition length of function parameter specified by reld_func statement
| Decimal number |
- --: Not applicable
- S: Terminates processing
- O: Refer to the action to be taken for the KFPL15313-E message.
KFPL15315-E E+L
Unable to restart pdrorg, status unmatched, kind=aa....aa
- The table reorganization process cannot be restarted because the status of the table does not match.
- When aa....aa is option_control:
- The option and specified control statement during restart do not match the option and specified control statement when table reorganization failed.
- When aa....aa is server:
- The table status of the row partitioning among servers table does not match.
- When aa....aa is unload_time:
- The unload data file specified in the unload statement or lobunld statement during restart and the unload data file specified when table reorganization failed do not match.
- When aa....aa is restart_inf:
- The re-execution information does not match.
- When aa....aa is schema or table_inf:
- The table status of each table in the schema is different.
- aa....aa: Status type
- option_control: Specified option or control statement
- server: Status between servers
- unload_time: Unload time
- restart_inf: Re-execution information
- schema: Table status in the schema
- table_inf: Table information
- S: Terminates processing.
- Action
- When aa....aa is option_control:
- When a different option and control statement is specified, and the table reorganization process is re-executed, specify the option and control statement specified when table reorganization failed.
- When aa....aa is server_status or unload_time:
- Take one of the following actions:
- When one RDAREA is recovered from backup or an RDAREA is initialized, the table reorganization process cannot be restarted. Recover all stored RDAREAs from backup, and then execute the table reorganization process (in this case, no restarting occurs).
- When any applicable tables are manipulated before restart, restarting does not occur. Recover the tables from backup.
- When a different unload data file is specified, specify the unload data file specified when table reorganization failed.
- When actions 1 through 3 are not taken, table reorganization (pdrorg -k rorg) cannot be executed. To forcibly execute table reorganization, specify tblstatus=clear in the option statement, clear the table's status, and then execute.
- When aa....aa is restart_inf, schema or table_inf:
- When the reload process is performed on the applicable table (a table in the schema), restarting cannot be performed. In this case, execute reloading (pdrorg -k reld) and complete the reload process.
KFPL15316-E E+L
Unable to reload table kind unmatched, kind=aa....aa
- An unloaded table cannot be reloaded because the unload file and table to reload are different file types.
- When aa....aa is INSERT ONLY table:
- The unloaded table cannot be reloaded in either of the following situations:
- When the unloaded table is a non-falsification prevented table and the reload destination is a falsification prevented table.
- When the unloaded table is a falsification prevented table and the other table (table of another system) at the reload destination is a falsification prevented table.
- aa....aa: Table type
- INSERT ONLY table: Falsification prevented table
- S: Terminates processing.
- Action
- Specify the correct unload table or table name, and then re-execute.
KFPL15317-E E+L
Table aa....aa.bb....bb not unloaded by cluster key sequence, file=cc....cc
- Table aa....aa.bb....bb in the unload data file was not unloaded in the order of cluster key values of the reload destination table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 157 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Create the unload data file in the order of cluster key values and re-execute the command.
KFPL15318-E E+L
Cluster information not equal to aa....aa.bb....bb on unload file, file=cc....cc
- The cluster key definition for table aa....aa.bb....bb in the unload data file does not match that for the reload destination table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of unload data file
- If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.
- 152 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Create the unload data file for the specified table in the order of cluster key values and re-execute the command.
KFPL15319-E E+L
Unable to unload order by physical, table=aa....aa.bb....bb
- Because a cluster key has been defined for table aa....aa.bb....bb, the table cannot be reorganized in physical order.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Unload the table in the order of cluster key values and re-execute the command.
KFPL15321-E E+L
Index aa....aa not found on table bb....bb.cc....cc
- Specified index aa....aa has not been defined for table bb....bb.cc....cc.
- aa....aa: Index identifier
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: If the index identifier is invalid, correct it and re-execute the command.
KFPL15322-E E+L
aa....aa key not found on table bb....bb.cc....cc
- Key aa....aa is not defined in table bb....bb.cc....cc.
- aa....aa:
- Cluster: Cluster key
- Primary: Primary key
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O:
- If the specified table name is invalid:
Correct the table name and re-execute the command.
- If the specified table name is correct:
Check if key aa....aa is defined in the table. If it is not defined, specify the keys, except for key aa....aa, in the same order as the unloading sequence and re-execute the command.
KFPL15323-E E+L
Unable to unload order by index, index=aa....aa.bb....bb
- The index specified in the order of unloading in the unload function contains one of the following errors:
- The index has multiple structure columns and descending order was specified:
Because the specified index has multiple structure columns, the index cannot be unloaded in descending order.
- A plug-in index was specified:
The specified index is a plug-in index; an unloading operation with an index specification cannot be performed.
- An index with a repetition column was specified:
The specified index is an index for a repetition column; an unloading operation with an index specification cannot be performed.
- A substructure index was specified:
An unloading operation cannot be performed with a substructure index specification.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Terminates processing.
- O: In the -b option, specify the name of an index that is not one of the following, or specify physical, and then re-execute the command.
- An index with an exceptional key value specified
- An index that includes a repetition column among the columns comprising the index
- A plug-in index
- A substructure index
KFPL15327-E E+L
Unable to reload due to DB data compressed in unload file , table=aa....aa. "bb....bb", column="cc....cc", attribute=dd....dd, value=ee....ee
- When reloading data using an unload data file containing compressed data, the data could not be reloaded because the compression specification for the table was different at unload time and at reload time.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of the column where the error was detected
- dd....dd: Compression specification for the column where the error was detected
- COMPRESSED: Compression specification
- partition size: Compression partition size
- ee....ee: Value of compression specification in the unload data file for the column where the error was detected
- The following table indicates the cause of the error based on the information output in dd....dd and ee....ee.
Information about the column where the error was detected | Cause of error |
---|
Compression specification (dd....dd) | Value of compression specification in the unload data file (ee....ee) |
---|
COMPRESSED | use (compression is specified) | The compression specifications do not match. No compression is specified for the table being reloaded. |
no use (no compression is specified) | The compression specifications do not match. No compression is specified for the column in the unload data file. |
partition size | Compression partition size | The compression partition sizes do not match. |
- S: Terminates processing.
- O:
- If the wrong unload data file was specified:
- Specify the unload data file corresponding to the table to be reloaded, and then reload the data.
- If you want to reload the data in the specified unload data file:
- Make sure that the compression specification of the table to be reloaded matches the compression specification of the table at unload time, and then reload the data.
KFPL15326-E E+L
Unable to unload due to specified index except values, index=aa....aa."bb....bb"
- The index aa....aa."bb....bb", specified in the -b option, contains a defined index exclusion value; the index cannot be unloaded.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Terminates processing.
- O: Either specify an index for which an index exclusion value is not defined or omit the specification of the -b option and re-execute the command.
KFPL15331-E E+L
aa....aa not held, RDAREA=bb....bb
- RDAREA bb....bb is not in command hold status.
- aa....aa: {Data dictionary|USER RDAREA}
- bb....bb: RDAREA name
- S: Terminates processing.
- O: Place the corresponding RDAREA on command shutdown status and re-execute the command.
KFPL15333-E E+L
Data dictionary lock request failed
- Data dictionary RDAREA cannot be locked.
- S: Terminates processing.
- O: Refer to the message that was output before this message to eliminate the cause of the error, and re-execute the command.
KFPL15334-E L
Specified data dictionary table not found in system, table=aa....aa
- Specified table aa....aa is not a dictionary table.
- aa....aa: Table identifier
- S: Terminates processing.
- O: Correct the specified table name and re-execute the command.
KFPL15335-E E+L
Specified aa....aa file is many, max=bb....bb
- The number of files specified in the unload statement, lobunld statement, or idxname statement exceeds the maximum specifiable value bb....bb.
- aa....aa: Incorrect specification:
- { unload|lobunld|idxname }
- bb....bb: Maximum number of files that can be specified
- S: Terminates processing.
- O:
- For the unload or lobunld statement
Check the specified table definition and the specification of the unload or lobunld statement, correct the unload or lobunld statement, and re-execute.
If the -g option is not specified, the maximum number of files that can be specified equals the number of partitioned servers. If the -g option is specified, the number is 1.
- For the idxname statement
Check the specified table definition and the specification of the idxname statement, correct the idxname statement, and re-execute.
The maximum number of files that can be specified equals the number of indexes defined in the table. If the asterisk (*) is specified in the name operand of the idxname statement, the maximum number of files that can be specified is 1.
KFPL15336-E E+L
Specified aa....aa name bb....bb of cc....cc file not much
- The server name specified by the unload or lobunld statement or by the server operand of the idxname statement differs from the server name in the table definition.
- aa....aa: server
- bb....bb: Specified server name
- cc....cc: Processing that was attempted:
- { unload|lobunld|idxname }
- S: Terminates processing.
- O:
- For the unload or lobunld statement
Correct the server name in the unload or lobunld statement, and re-execute.
- For the idxname statement
Correct the server name specified by the server operand of the idxname statement, and re-execute.
KFPL15337-E E+L
Specified aa....aa name bb....bb of index file not much
- The index information file name or RDAREA name specified in the index information file (index) To be used is different from the name specified in the index definition of the table subject to processing.
- aa....aa: Specified name:
- { RDAREA|index }
- bb....bb: Index information file name or RDAREA name
- S: Terminates processing.
- O: Correct the index information file name or RDAREA name in the index information file to be used and re-execute the command.
KFPL15338-E E+L
Specified aa....aa name bb....bb of cc....cc directory not much
- The server name for the directory specified in the control information file does not match the information in the table definition subject to processing.
- aa....aa: server
- bb....bb: Server name
- cc....cc: Specified directory type
- { index|sort }
- S: Terminates processing.
- O: Correct the server name for the directory specified in the control information file and re-execute the command.
KFPL15339-E L
Index file no specified, index=aa....aa.bb....bb, RDAREA=cc....cc
- An index information file was not specified for index aa....aa.bb....bb in RDAREA cc....cc.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- cc....cc: RDAREA name
- S: Terminates processing.
- O: Specify the index information file for the corresponding RDAREA and re-execute the command.
KFPL15340-E E+L
RDAREA name not specified in index file, index=aa....aa
- An RDAREA name was omitted for the index information file to be used.
- aa....aa: Specified index identifier
- S: Terminates processing.
- O: Add the RDAREA name to the index information file and re-execute the command.
KFPL15341-E E+L
Server name not specified in aa....aa
- No server name was specified for the directory or file name specified in the control information file.
- aa....aa: Invalid specification:
- { unload file (unload file)
- | index directory (index directory)
- | sort directory (sort directory)
- | lobunld file (LOB unload file) }
- S: Terminates processing.
- O: Specify the server name for the directory or file name specified in the control information file and re-execute the command.
KFPL15342-E E+L
Specified aa....aa directory is too many, max=bb....bb
- The number of directories specified in the control information file exceeds the permitted maximum bb....bb.
- aa....aa: Type of directory
- { index|sort work }
- bb....bb: Permitted maximum
- S: Terminates processing.
- O: Check the table definition, correct the number of directories, then re-execute the command.
KFPL15343-E E+L
Index file duplicated, index=aa....aa.bb....bb, RDAREA=cc....cc
- A duplicated name was specified for the index or RDAREA to be used.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- cc....cc: RDAREA name
- S: Terminates processing.
- O: Correct the duplicated name of the index information file or RDAREA to be used and re-execute the command.
KFPL15344-W E+L
Control character found, skip row=aa....aa, table=bb....bb."cc....cc"
- A NULL or linefeed character was found in row data; this row was not output.
Row data (character data, national character data, or mixed character data) That contains a NULL or linefeed character cannot be output in DAT format. - aa....aa: Number of lines skipped
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Resumes processing.
- O: In the -W option, specify either bin or extdat, and output the file in binary format or extended DAT format.
KFPL15345-E E+L
Unable to execute aa....aa for PLUGIN index bb....bb."cc....cc"
- Function aa....aa cannot be executed for plug-in index bb....bb."cc....cc".
- aa....aa: Function:
- ixor: Index reorganization
- pdreclaim: Free page release utility
- pdpgbfon: Global buffer residence utility
- bb....bb: Authorization identifier
- cc....cc: Index identifier
- S: Terminates processing.
- O: Take one of the following actions:
- When aa....aa is ixor:
- When you want to reorganize the plug-in index:
Instead of reorganizing the plug-in index, reorganize the table in which the plug-in index is defined or re-create the plug-in index.
- When there is no need to reorganize the plug-in index:
Delete the index or idxname statement that specifies the plug-in index, then re-execute index reorganization.
- When aa....aa is pdreclaim:
- When a plug-in index is specified in the idxname statement of pdreclaim, delete the idxname statement. When releasing a plug-in index used free page, re-create the index (pdrorg -k ixrc).
- When aa....aa is pdpgbfon:
- Because the plug-in index cannot be processed by pdpgbfon, terminate the command.
KFPL15346-W E+L
Table aa....aa."bb....bb" cc....cc skipped
- When cc....cc is reload:
During reloading by schema, because the information for table aa....aa."bb....bb" was not found in the unload data file, the reload process was skipped. Or, when resuming table reorganization, the reloading process was skipped because reloading of table aa....aa."bb....bb" is complete. If the timing of the abnormal termination is such that it occurs before the table status is written as reorganizing, the table status becomes like the initial status. In other words, the status is the same as when reloading has completed, such that the reload processing of the unloaded table is skipped. In this case, specify the relevant table only, with the -t option, and re-execute the reloading (-k reld).
- When cc....cc is ixrc:
The index recreation process was skipped because creation of the index for table aa....aa."bb....bb" was complete when table recreation resumed.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Process type
- reload: Reload process
- ixrc: Index reorganization process
- S: Continues processing.
KFPL15347-E E+L
Unmatched aa....aa between bb....bb "cc....cc" of RDAREA "dd....dd" and bb....bb "ee....ee" of RDAREA "ff....ff"
- aa....aa ("cc....cc") of RDAREA "dd....dd", which is the target when executing the utility, and aa....aa ("ee....ee") of RDAREA "ff....ff" do not match.
- aa....aa:
- generation number: Generation number
- inner replica status: Replica status
- bb....bb:
- number: Number
- status: Status
- cc....cc: Generation number
- current: Current RDAREA
- not current: Other than the current RDAREA
- dd....dd: RDAREA name
- ee....ee: Generation number
- current: Current RDAREA
- not current: Other than the current RDAREA
- ff....ff: RDAREA name
- S: Terminates processing.
- O:
- When aa....aa is generation number:
If the utility is executed (during current access) without the generation number (using the -q option) specified, use the pddbchg command to match up the generation number of the RDAREA to be processed, and re-execute.
- When aa....aa is inner replica status:
If the utility is executed with the generation number (using the -q option) specified, use the pddbchg command to match up all replica statuses of the RDAREA to be processed.
KFPL15348-E E+L
No specified generation RDAREA="aa....aa", generation=bb
- No RDAREA "aa....aa" of specified generation bb was found.
- aa....aa: RDAREA name (*** is output when no RDAREA of the specified generation was found)
- bb: Generation number (if a table or index is dropped while the utility is executing, the generation number cannot be determined, and -1 is output)
- S: Terminates processing.
- O:
- If the specified generation number is correct:
- Create a replica RDAREA for the target RDAREA, and then re-execute the utility.
- If the specified generation number is in error:
- Specify the correct generation number, and then re-execute the utility.
- If a definition SQL is executed on a table on which a utility is being executed:
- Execute the definition SQL when the utility is not being executed.
KFPL15349-E E+L
aa....aa scan failed, code=bb
- A data access error occurred during retrieval of BLOB or BINARY column data.
- aa....aa: Attribute of the column that generated the error
- LOB: BLOB column
- BIN: BINARY column
- bb: Error code
- 4: A data access error occurred during acquisition of BLOB or BINARY data.
- 12: Updating of a BLOB column or a BINARY column was detected during acquisition of BLOB or BINARY data.
- S: Terminates processing.
- O:
- Error code 4:
- Refer to the message that was output to the message log file before this message, resolve the error, and then re-execute the command.
- Error code 12:
- Make sure that tables subject to unload processing are not being updated, and then re-execute the command.
KFPL15555-E E+L
Few file descriptors, soft limit=aa....aa, hard limit=bb....bb
- The input file cannot be partitioned because the physical limit value for files that can be opened or locked by a single process set in the kernel parameters for the OS is too small.
- aa....aa: The logical limit (soft limit) for the number of files that can be opened or locked by single processes
- bb....bb: The physical limit (hard limit) for the number of files that can be opened or locked by single processes
- S: Terminates processing.
- O: Raise the physical limit value for files that can be opened or locked by single process set in kernel parameters for the OS. For details about estimating required specification values for HiRDB operations, see Estimating operating system parameters for the OS in the HiRDB Version 9 Installation and Design Guide.
KFPL16300-E E+L
Invalid lobmid file, file=aa....aa
- The specified LOB middle file has not been created correctly.
- aa....aa: Name of the LOB middle file
- If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.
- S: Terminates processing.
- O: Specify a LOB middle file that was output correctly during creation of the LOB column structure base table and re-execute the command.
KFPL16310-E E+L
Divided information of aa....aa.bb....bb not equal to lobmid file, file=cc....cc
- LOB column data loading is disabled because the partitioning definition for table aa....aa.bb....bb in the LOB middle table differs from the partitioning definition for the table for loading the LOB column data.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Name of the LOB middle file
- If the length of the LOB middle file name exceeds the value obtained from the following formula, the last number of characters of the LOB middle file name obtained from the formula are output.
- 152 - authorization-identifier-length - table-identifier-length
- S: Terminates processing.
- O: Use the LOB middle file for the specified table to load the LOB column data.
KFPL16320-E E+L
Unmatched LOB load type "a" in command line with LOB load type "b" of LOBMID file cc....cc
- Value "a"specified in the -k option on the command line during LOB creation does not match value "b" specified in the -k option on the command line during creation of the LOB column structure base table.
- a: LOB creation type specified in the -k option during LOB creation:
- f: Creation of a file for each item of LOB data
- c: Creation of a LOB column input file
- b: LOB creation type specified in the -k option during creation of the LOB column structure base table:
- f: Creation of a file for each item of LOB data
- c: Creation of a LOB column input file
- cc....cc: Name of LOB middle file
- If the length of the LOB middle file name exceeds 66 characters, the last 66 characters of the LOB middle file name are output.
- S: Terminates processing.
- O: For LOB creation, specify the same LOB creation type in the -k option that was specified for creation of the LOB column structure base table.
KFPL16321-E E+L
Unmatched number of "lobcolumn" statements with aa....aa (number of LOB columns)
- The number of lobcolumn statements in the control information file does not match the number of LOB columns.
The number of lobcolumn statements required for creation is aa....aa. - aa....aa: Number of required lobcolumn statements
- S: Terminates processing.
- O:
- LOB creation in units of tables or RDAREAs of LOB column structure base table:
Specify as many lobcolumn statements as there are LOB columns in the table to be created. When a column structure information file is used, specify as many lobcolumn statements as there are LOB columns specified in the column structure information file.
- LOB creation in units of LOB RDAREAs:
Specify one lobcolumn statement.
KFPL16322-E E+L
LOB column "aa....aa" not found, table=bb....bb."cc....cc"
- Specified LOB column "aa....aa" was not found in the table.
- aa....aa: Column name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Specify a LOB column name entered in the table definition and re-execute the command.
KFPL16323-E E+L
RDAREA "aa....aa" conflicted with LOB column "bb....bb"
- LOB RDAREA "aa....aa" specified in the lobmid control statement contradicts the information about LOB column "bb....bb" specified in the lobcolumn statement.
- aa....aa: LOB RDAREA name
- bb....bb: Column name
- S: Terminates processing.
- O: Check the correspondence between the LOB RDAREA name specified in the lobmid control statement and the LOB column name specified in the table definition, then re-execute the command.
KFPL16324-E E+L
Unable to continue LOB load, because of invalid LOB middle file, file=aa....aa
- LOB cannot be created due to invalid LOB middle file aa....aa.
- LOB middle files obtained by using the same input data file as when LOB column structure base table was created:
The order of the LOB middle files specified during LOB creation is invalid.
- LOB middle file obtained by using a different input data file as when LOB column structure base table was created:
LOB middle file specified during LOB creation is invalid.
- aa....aa: LOB middle file name
- If the length of the LOB middle file name exceeds 140 characters, the last 140 characters of the LOB middle file name are output.
- S: Terminates processing.
- O:
- LOB middle files obtained by using the same input data file as when LOB column structure base table was created:
Specify the LOB middle files in the same orde r as the corresponding input data file lines in the LOB column structure base table, then re-execute the command.
- LOB middle file obtained by using a different input data file as when LOB column structure base table was created:
A LOB middle file obtained from a different input data file cannot be specified at the same time. Use a separate control statement to specify a LOB middle file for a different input data file, then execute the command to create its LOB data.
KFPL16325-W E+L
LOBCOLUMN for "aa....aa" ignored, because of not specified LOB column in column structure information file
- The lobcolumn statement for "aa....aa" was ignored, because this control statement is for a LOB column that is not specified in the column structure information file (a LOB column that is not specified in the input file for the LOB column structure base table).
- aa....aa: Name of the ignored LOB column
- S: Ignores the specified lobcolumn statement and resumes processing.
KFPL16326-E E+L
Unable to omit aa....aa in "bb....bb" statement
- aa....aa cannot be omitted from statement "bb....bb" that was specified in the control information file.
- aa....aa: Omitted information:
- column name: Column name
- bb....bb: Name of control statement:
- lobcolumn: lobcolumn statement
- S: Terminates processing.
- O: Specify aa....aa in statement "bb....bb" of the control information file and re-execute the command.
KFPL16327-E E+L
Unable to continue LOB load, because invalid column structure information file
- LOB data cannot be created due to incorrect information in the column structure information file specified in the -c option.
- The LOB column specified during LOB creation is not the one specified in the input data file during LOB column structure base table creation.
- S: Terminates processing.
- O:
- Column structure information file not specified in -c option during LOB column structure base table creation:
- Create LOB data by omitting specification of the column structure information file in the -c option during LOB creation and specifying lobcolumn control statements for all LOB columns.
- Column structure information file specified in -c option during LOB column structure base table creation:
- Check that the column structure information file specified in the -c option for LOB column structure base table creation is the same file specified for LOB creation, specify the corresponding lobcolumn control statement, then re-execute the command.
KFPL16328-W L+S
Unable to check LOB data count, because error data exist in input data file
- During LOB column structure base table creation, erroneous data was found in the input data file for the LOB column structure base table. If the -e option was specified, the system cancels data load processing for the LOB column structure base table, in which case the number of LOB data items in the LOB column input file cannot be verified during LOB data creation.
- S: Resumes processing.
KFPL17000-E E+L
Unmatched aa....aa DB=bbbbbb, UTL=cccccc
- One of the following errors was detected:
- The job name associated with the synchronization point information stored in the database does not match the job name specified in the utility control statement.
- The index creation method associated with the synchronization point information stored in the database does not match the index creation method used during the execution of the utility.
- The utility name associated with the synchronization point information stored in the database does not match the utility that was executed.
- aa....aa: Mismatching information type:
- job name: Job name
- index mode: Index mode
- bbbbbb:
- job name displayed for aa....aa: The job name stored in the database (L in parentheses indicates pdload; R indicates pdrorg)
- index mode displayed for aa....aa: The index creation method stored in the database (value specified in -i option)
- cccccc:
- job name displayed for aa....aa: The job name specified during utility execution (if *** is displayed, no job name was specified)
- index mode displayed for aa....aa: The index creation method specified during utility execution (value specified in -i option)
- S: Terminates processing.
- O:
- job name displayed for aa....aa:
Execute the utility of the abnormally terminated job, then re-execute. If there is no need to re-execute the utility of the abnormally terminated job, specify CLR in the job operand and execute.
- index mode displayed for aa....aa:
Re-execute the utility of the abnormally terminated job without modifying the index creation method (-i option). If there is no need to re-execute the utility of the abnormally terminated job, specify CLR in the job operand and execute.
KFPL17001-E E+L
Unload file not available for aa....aa. bb....bb of RDAREA cc....cc, reason=dd....dd (system=ee....ee, file=ff....ff)
- The unload data file cannot be used because it is not recent.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: RDAREA name
- dd....dd: Reason (Unload-time: Unload data file creation date)
- ee....ee: Date on DB side
- ff....ff: Date on unload data file side
- S: Terminates processing.
- O: Specify a recent unload data file (the last reorganization (-k rorg) executed on the applicable table) and re-execute.
KFPL17010-E E+L
Unmatched row count RDAREA=aa....aa(bb....bb), RDAREA=cc....cc(dd....dd)
- The synchronization point rows counts for a row-partitioned table stored in different RDAREAs do not match.
- aa....aa: RDAREA name
- bb....bb: Rows count
- cc....cc: RDAREA name
- dd....dd: Rows count
- S: Terminates processing.
- O: Take one of the following actions:
- After executing the utility at the level of the RDAREAs that terminated abnormally, re-execute the utility at the table level.
- When re-executing the utility at the RDAREA level is not necessary, specify CLR in the job operand.
- When *** is output to the RDAREA, see the KFPL15036-E message output before this message was output.
KFPL20000-E E+L
Internal function (aa....aa) error occurred, code=bbbbb
- HiRDB detected an error in the extension of the utility process.
- aa....aa: Name of the function where the error was detected
- bbbbb: Error detail code
- S: Terminates processing.
- O: See the error detail code to eliminate the cause of the error, and then re-execute the command. For more information about the error detail code, see 4.1 Detail codes for RPC-related errors, or 4.2 Detail codes for system-related errors. If an error occurs that operators cannot solve, contact the HiRDB administrator. The table below summarizes the most common causes of the error and the required action:
Detail code | Cause | Action |
---|
-307 | A timeout occurred. | If processing does not terminate within the utility execution monitoring time specified in the pd_utl_exec_time operand or the option statement's exectime operand, take the action indicated in the KFPL11111-E message. |
-310 | The communication destination unit or server is not running. | If the unit or server specified in the control statement or on the command line has stopped, have the HiRDB administrator start the unit or server. If the unit or server cannot be started, change the name of the unit or server specified in the control statement or on the command line to the name of a running unit or server. |
-314 | Communication among processes executed by the utility is unavailable. | - If the utility's processes were forcibly terminated by the pdcancel command, ignore this message.
- It is possible that messages cannot be output to standard output and the communication buffer is full of messages that cannot be output, so that the messages cannot be received. In this case, enable messages to be output to standard output on the monitor where the command was executed.
- If the utility's processes are executing in parallel on multiple servers, or if an error occurred in the processes on a server causing processing to be interrupted, such that there are no processes to receive the statements transmitted from processes that are being processed, take action based on the error message that was output from the first server where an error occurred.
|
-364 | An error occurred on the communication destination server. | If the communication destination process was forcibly terminated due to the reason cited in the error message output before this message, take the action indicated in that message. |
-5104 | The number of concurrently executing utilities has exceeded the maximum. | Take one of the following actions:
- If this message is output when XDS is starting up or terminating, start or terminate XDS again, making sure the total number of XDS processes to be started or terminated (the XDS database definition pd_import_export_parallel) does not exceed 64.
- If you are executing the utility at the same time as XDS is starting up or terminating, execute the utility after XDS has finished starting up or terminating.
- If multiple utilities are executing concurrently, reduce the number of concurrently executing utilities.
- If the value of the pd_exec_mode operand in the system common definition is 0, change it to 1.
|
-5303 | HiRDB did not start normally. | Refer to the error message that was output before this message, investigate the cause of the error, and take corrective action. If necessary, re-execute the command. |
- Action
- If the problem is that the unit or server stopped, restart the unit or server. However, if the problem is that a network error caused a temporary stop, HiRDB may automatically restart. In this case, no restart is necessary. For details on when HiRDB automatically restarts, see the HiRDB Version 9 System Operation Guide.
- If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.
KFPL20001-E E+L
Insufficient memory in message buffer pool due to concurrent execution of aa....aa
- A temporary memory shortage occurred in the message storage buffer pool during process allocation when pdload, pdrorg, pdrbal, or a plug-in-provided command was executed concurrently.
- aa....aa: Program name:
- { "pdload"|"pdrorg"|"pdrbal"|"COMMAND" }
- S: Terminates processing.
- O: Re-execute the command after the current execution of pdload, pdrorg, pdrbal, or the plug-in-provided 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 a service was requested from a server being refreshed by the pdpfresh command, re-execute the utility after the pdpfresh command has finished.
- 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.
KFPL20003-E E+L
Unable to send message from aa....aa to bb....bb
- A communication error occurred between servers aa....aa and bb....bb.
- aa....aa: Name of the send source host
- bb....bb: Name of the send destination host
- S: Terminates processing.
- Action
- Take action appropriate to the KFPL20000-E or KFPL20100-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.
KFPL20005-E E+L
Server down detected
- Abnormal server termination was detected. Or, processing cannot be resumed because the system was switched.
- S: Terminates processing.
- O: Correct the cause of the abnormal server termination on the basis of error messages that have already been output and re-execute the command. If system switchover occurred during processing, set the host that executes the command so that it can reference and update files needed for command processing, then re-execute.
KFPL20010-E E+L
aa....aa error occurred, code=bbbb
- Connection establishment or release with HiRDB failed.
- aa....aa: Processing:
- { Connect|Disconnect }
- bbbb: Error detail code
- S: Terminates processing.
- O: See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute the command.
- Note
- If this message is displayed during the execution of a plug-in-provided command, the message is output only to the indicated output device type (L).
KFPL20020-E E+L
Transaction (aa....aa) error occurred, code=bbbbb
- Transaction startup or settlement failed.
- aa....aa: Type of transaction:
- { begin|commit|rollback }
- bbbbb: Error detail code
- S: Terminates processing.
- O: See 4.2 Detail codes for system-related errors to eliminate the cause of the error. If commit or rollback processing, other than during pdrorg unload processing, caused an error, re-execute the command after restoring the database to the status it was in before the utility was executed. If the error cannot be corrected, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPL20041-E E+L
Staticizer Option not setup
- The -q option can only be used when the HiRDB Staticizer Option is embedded.
- S: Terminates processing.
- Action
- Embed the HiRDB Staticizer Option, and then re-execute.
KFPL20050-E E+L
Invalid host name
- This utility cannot be executed with the specified host name.
- S: Terminates processing.
- O: Correct the host name on the command line or in the control information file and re-execute the command.
KFPL20051-E E+L
Invalid server name
- The server name specified in the control statement or command line is invalid.
- S: Terminates processing.
- O: Correct the server name specified in the control statement or command line, and then re-execute the command.
KFPL20060-E E+L
Security Audit inactive, status=aa....aa, reason=bbbbb
- The security audit facility has stopped, so the history of the utility was not output to the audit trail file.
- aa....aa: Run status of the security audit facility
- INACTIVE: The security audit facility has stopped.
- OTHER: Another error occurred.
- bbbbb: Error detail code
- S: Continues processing.
- O: When it is necessary to fetch an audit trail, take one of the following actions according to the run status of the security audit facility:
- INACTIVE: Start the security audit facility.
- OTHER: See the Detail codes for the system-related error. For information on system-related errors, see 4.2 Detail codes for system-related errors. If an error occurs that programmers cannot solve, contact the HiRDB administrator.
- Action
- If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.
KFPL20061-E E+L
Audit trail generation file write error, reason=aaaaa
- The history of this utility was not output to the audit trail file because an error occurred during output to the audit trail file.
- aaaaa: Error detail code
- S: Continues processing.
- O: When it is necessary to fetch an audit trail during re-execution of the utility, see the error detail code to eliminate the cause of the error. For information on system-related errors, see 4.2 Detail codes for system-related errors. If an error occurs that programmers cannot solve, contact the HiRDB administrator.
- Action
- If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.
KFPL20062-E E+L
Audit trail generation file not found, number=aaa
- There are no audit trail files for data loading.
- aaa: Audit trail file number
- S: Terminates processing.
- Action
- Use the pdls command to check the status of the audit trail file specified in the srcuoc control statement, and once there is an audit trail file waiting for data loading, re-execute the command.
KFPL20090-E E+L
Unable to output message to aa....aa
- Messages cannot be output to aa....aa.
- aa....aa: Output destination
- { stdout|stderr }
- S: Resumes processing.
- Action
- Refer to the message that was output before this message to determine the cause of the error.
KFPL20091-E L
Unable to output information to report file
- Information cannot be output to the processing results file.
- S: Continues processing.
- Action
- For the cause and action to be taken, refer to the message that is output immediately before this message.
KFPL20100-E E+L
Communication (aa....aa) error occurred, code=bbbbb
- A communication error occurred.
- aa....aa: Type of communication processing
- bbbbb: Error detail code
- S: Terminates processing.
- O:
- See 4.1 Detail codes for RPC-related errors and eliminate the cause of the error, then re-execute the command. If an error occurs that the programmer cannot handle, contact the HiRDB administrator.
- If aa....aa is p_f_sqa_rcomb_open or p_f_sqa_rcomb_close and the error detail code is 8, there is insufficient memory. In UNIX, if the error detail code is other than 8, an error occurred in combuf communications. If there is insufficient memory, re-estimate the memory. Also, stop any unnecessary processes. In UNIX, if an error occurred in combuf communications, refer to the OS documentation to resolve the error.
- If one of the following codes is output, the error may not be a communication error. In that case, take the appropriate action.
- -307:
- If processing does not terminate within the utility execution monitoring time specified in the pd_utl_exec_time operand or the option statement's exectime operand, take the action indicated in the KFPL11111-E message.
- -314:
- Communication among processes executed by the utility is unavailable. Consider the following causes.
- (1) If the utility's processes were forcibly terminated by the pdcancel command, ignore this message.
- (2) It is possible that messages cannot be output to standard output and the communication buffer is full of messages that cannot be output, so that the messages cannot be received. In this case, enable messages to be output to standard output on the monitor where the command was executed.
- (3) If the utility's processes are executing in parallel on multiple servers, or if an error occurred in the processes on a server causing processing to be interrupted, such that there are no processes to receive the statements transmitted from processes that are being processed, take action based on the error message that was output from the first server where an error occurred.
- -364:
- If the communication destination process was forcibly terminated due to the reason cited in the error message output before this message, take the action indicated in that message.
- Action
- If the error cannot be corrected by the HiRDB administrator, contact the customer support center.
KFPL20200-E E+L
Database access (aa....aa) error occurred, code=b
- An error occurred before or after the database was referenced or updated.
- aa....aa: Processing resulting in the error
- b: Error code:
- 4: Memory shortage
- 8: I/O error
- S: Terminates processing.
- O:
- If the error code is 4:
Allocate enough memory to the process and re-execute the command.
- If the error code is 8:
Refer to the message that is output to standard error or to the message log file, resolve the error, and then re-execute the command.
KFPL21000-E E+L
PLUGIN function error occurred, operation=aa....aa, code=bb....bb, line=cc....cc
- An error occurred in a plug-in function.
- aa....aa: Operation name
- bb....bb: The return code received from the plug-in function
- cc....cc: Row number of the data in which the error occurred
- S: Terminates processing.
- O: Correct the cause of the error by referring to the preceding error message and re-execute the command.
KFPL21111-E E+L
Unable to make parameter, operation=aa....aa, code=bb....bb, line=cc....cc
- Unable to generate the argument to be passed to the constructor function.
- aa....aa: Parameter generation processing type
- bb....bb: Return code from the parameter generation function
- cc....cc: Line number at which the error occurred
- S: Terminates processing.
- O:
- Correct the cause of the error by referring to the preceding error message and re-execute the command.
- When data-loading using a binary-format input data file, if the preceding error message is KFPA11930-E (insufficient memory) and the allocation area size is different from the input parameter size, the problem is an invalid input data file format. In this case, review the input data file.
KFPL21112-E E+L
ADT operation error, operation=aa....aa, code=bb....bb
- An error occurred during abstract data type operation aa....aa.
- aa....aa: Operation function name
- bb....bb: Operation code
- S: Terminates processing.
- O: Correct the error by referring to the error message that was output immediately before this message, and re-execute the command. If no error message has been output, contact the customer support center.
KFPL22000-E E+L
System call error, func=aa....aa, errno=bbb
- A system call (function) error occurred.
- aa....aa: Name of system call (function)
- bbb: Error number set in errno
- S: Terminates processing.
- O:
- Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute the command.
- If errno = 0, eliminate the cause of the error by referring to the KFPL22001-E message output before this message, and re-execute the command.
- In addition, this message is sometimes output when one of the following occurs while XDS is starting up. If this is the case, ignore the message.
- The XDS process was terminated by the pdxdsstop -f command or the pdstop -f command.
- The XDS process was terminated using the kill command or similar means.
- Database import terminated abnormally.
- The XDS process terminated abnormally.
- In some cases, messages are not output to standard output device during the execution of a plug-in-provided command.
KFPL22001-E E+L
aa....aa
- Displays information about an error that occurred during a system call. If the OS's system log facility does not support Japanese character codes, messages may not be output correctly to the system log. In such a case, refer to the HiRDB message log.
- aa....aa: Error information
- S: Terminates processing.
- O: Correct the error by referring to the error information, and re-execute the command.
KFPL22222-I L+S
Max row length=aa....aa
- The maximum row length of the unload data file output in the DAT format is aa....aa bytes.
- aa....aa: Maximum row length
- S: Continues processing.
- O: If the output unload data file will be the input to pdload and the maximum row length displayed in this message is 32 KB or more, specify the maximum row length in the maxreclen operand of the source statement.
KFPL22223-I L+S
Delete row count=aa....aa, table=bb....bb. "cc....cc", file=dd....dd
- aa....aa rows were not output to the unload data file because a UOC issued a deletion request during the unload processing of table bb....bb."cc....cc".
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option: Value specified in -m option | Output destination of message |
---|
lvl0 | Log file (L) and standard output (S) |
lvl1 | Log file (L) |
lvl2 | Neither the log file (L) nor standard output (S) However, the message is output to the work file. |
- aa....aa: The number of rows for which a deletion request was issued
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Unload data file name
- If the name of the unload data file exceeds 101 characters, the last 101 characters of the unload data file name are output.
- S: Continues processing.
KFPL23000-E E+L
Error occurred on server=aa....aa
- An error occurred at the server.
- aa....aa: Server name
- S: Terminates processing.
- O: Refer to the error message that was output immediately before this message to eliminate the cause of the error, and re-execute the command. If the processing is being executed in the no-log mode, re-execute after restoring the database to the status it was in before the utility was executed.
KFPL23001-E E+L
Server aa....aa not running
- A server is not active.
- aa....aa: Server name
- S: Terminates processing.
- O: Activate the server indicated in the message and re-execute the command.
KFPL23100-E E+L
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc
- A HiRDB file access error occurred.
- aa....aa: HiRDB file function:
- close: HiRDB file close processing
- open: HiRDB file open processing
- read: HiRDB file read processing
- write: HiRDB file write processing
- reopen: Opening of HiRDB file or the second or subsequent volume of a multivolume file
- bb....bb: HiRDB system error code
- cc....cc: Name of the HiRDB file
- If the length of the HiRDB file name exceeds 150 characters, the last 150 characters of the HiRDB file name are output.
- S: Terminates processing.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.
KFPL23201-W E+L
Skip load process,audit trail aa....aa file status=(b,c,d),file=ee....ee
- Data loading was skipped because the specified audit trail file is not on hold, and not waiting for data loading. If the param operand of the srcuoc statement specifies all audit trail files, and no audit trail file can be loaded, this message applies to all audit trail files.
- aa....aa: Generation
- b: c (current) or s (not current)
- c: d (waiting for data loading) or - (data loading is complete)
- d: h (currently on hold) or - (not currently on hold)
- ee....ee: Audit trail file name displayed by the absolute path name
- If the length of the file name exceeds 144 characters, the last 144 characters of the file name are output.
- S: Continues processing.
- When data loading resumes, after data loading of the audit trail file is skipped and message KFPL23201-W is output, the return code of pdload will be as follows.
Number of audit trail files loaded into the audit trail table | Value specified in the param operand of the srcuoc statement |
---|
file=audit trail file name | file=all |
---|
mode=normal | mode=force | mode=normal |
---|
1 or more | 0 | 0 | 0 |
0 | 4 | 4 | 4 |
- Legend:
- 0: Terminates normally with return code 0.
- 4: Terminates with a warning and return code 4.
- Note: If an error occurs during data loading due to some other cause, it terminates abnormally with return code 8.
- Action
- Use the pdls command to check the name and file status of the specified audit trail file.
- If the file name is incorrect, correct it and re-execute the command.
- If the specified audit trail file data has been loaded, normally no action is required. If data needs to be loaded, you can specify force in the mode operand to the srcuoc statement and re-execute if necessary.
- Note that when data loading is executed with file=all specified in the param operand to the srcuoc statement, it is not necessary to recover the audit trail table and reload the data, because the audit trail file data will have been loaded.
KFPL23202-E E+L
Error occurred at change audit trail aa....aa file status, file=bb....bb, reason=ccccc
- The data loaded status of the audit trail file cannot be changed.
- aa....aa: Generation
- bb....bb: Audit trail file name displayed by the absolute path name
- If the length of the file name exceeds 128 characters, the last 128 characters of the file name are output.
- ccccc: Error code
- S: Terminates processing.
- Action
- The data from the specified audit trail file has already been registered to the audit trail table. If an error occurs and this audit trail file is again loaded with data, the data is duplicated, therefore deletion of data using the pdaudrm -f command is recommended. To understand why the status of the audit trail file could not be changed, see the error detail code on the message that was output, and eliminate the cause of the error. For details on error detail codes, see 4. Error Detail Codes.
KFPL23203-E E+L
Table aa....aa.bb....bb cc....cc table
- Table aa....aa.bb....bb specified an audit trail data registration UOC even though it is not an audit trail table. Or, this table did not specify an audit trail data registration UOC even though it is an audit trail table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Table type
- not audit: Non-audit trail table
- audit: Audit trail table
- S: Terminates processing.
- Action
- Specify an audit trail data registration UOC for audit trail tables, and then re-execute the command without specifying an audit trail data registration UOC for non-audit trail tables.
KFPL23204-E E+L
Invalid audit trail generation file status, file=aa....aa, generation=bbb
- Because the previously executed data load of an audit trail file terminated abnormally, the data load log in the audit trail table does not match the status of the audit trail file.
- aa....aa: Name of the audit trail file for which data loading was attempted
- If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.
- bbb: Invalid audit trail file generation number (last three characters of the audit trail file name)
- S: Terminates processing.
- O: Take one of the following actions:
- If the facility for automatically loading audit trail table data is not being used:
- In the param operand of the srcuoc control statement, specify only the audit trail file corresponding to the generation number (bbb) output in this message, and then execute data loading for the audit trail table.
- Audit trail file data was not loaded because of abnormal termination; therefore, load that data into the audit trail table if it is necessary to do so.
- Re-execute data loading on the audit trail file (aa....aa) on which loading was previously attempted.
- If the facility for automatically loading audit trail table data is being used:
- See Actions to take when an error occurs while the facility for automatic loading is being used, in the HiRDB Version 9 System Operation Guide.
KFPL23500-E E+L
RDAREA aa....aa bb....bb
- RDAREA is in hold status (error shutdown, logless shutdown, reference-possible backup hold, or updatable backup hold), close status, frozen update status, or online reorganization hold status.
- aa....aa: RDAREA name
- bb....bb: Status of the RDAREA
- held: Held
- closed: Closed
- freezed: Frozen
- ORG: Online reorganization hold
- S: Terminates processing.
- O:
- Other than online reorganization hold
- RDAREA opening attribute set to INITIAL
Place the RDAREA in open, shutdown release, command shutdown, referrable shutdown, or frozen update release status and then re-execute the command.
- RDAREA opening attribute set to DEFER or SCHEDULE
Release the RDAREA from shutdown status, place it in referencing-permitted shutdown status or frozen update release status, and then re-execute the command.
- Online reorganization hold
- Release online reorganization hold and re-execute the command.
KFPL24000-E E+L
Unable to specify configuration file
- A column structure information file cannot be specified using a binary-format input data file.
- S: Terminates processing.
- O: Match the attribute of the input data column of the binary-format input data file with the attribute of the column data of the table so that a column structure information file need not be specified, then re-execute the command.
KFPL24001-E E+L
Unable to specify null-information file
- A null value information file or a function information file cannot be specified for inputting a DAT-format input data file.
- S: Terminates processing.
- O: Specify the null value for inputting the DAT-format input data file, delete the specification for the null value information file or function information file, and then re-execute the command.
KFPL24100-E E+L
Unable to convert data, column=aa....aa
- A data type of the input data file specified in the column structure information file cannot be converted to the data type of the data in column aa....aa of the table.
- aa....aa: Column name
- S: Terminates processing.
- O: Correct any problems found in the data types specified in the column structure information file, and then re-execute the command.
KFPL24101-E E+L
Unable to specify filedir, column=aa....aa
- The filedir operand cannot be specified in column aa....aa in the column structure information file due to one of the following reasons:
- The column is not an XML-type column.
- f is not specified in the -K option.
- aa....aa: Column name
- S: Terminates processing.
- O:
- If the column is not an XML-type column:
- Delete the filedir operand.
- If the column is an XML-type column:
- If you specify a file path in order to load parameter attribute data from an individual file, specify f in the -K option.
- If you are directly processing data from input data files, delete the filedir operand.
KFPL24102-E E+L
Unable to specify sequence,column="aa....aa"
- The sequence generator cannot be specified in column aa....aa in the column structure information file for one of the following reasons:
- Sequence generator data could not be converted to column data.
- The specified column is a repetition column.
- aa....aa: Column name
- S: Terminates processing.
- O: Specify a sequence generator in a column for which this specification is possible, and then re-execute the command.
KFPL24150-E E+L
No aa....aa on table
- Neither table nor index was defined, but an index information file or work directory for sorting was specified. Or, LOB was not defined in the table, but information about a LOB input file or LOB middle file was specified.
- aa....aa: One of the following:
- index: Index information
- LOB: LOB column
- S: Terminates processing.
- O: Delete unnecessary information from the control information file. Or, check the name of the table subject to processing for an error and re-execute the command.
KFPL24151-E E+L
Cannot omit aa....aa name
- Name aa....aa cannot be omitted for a file for a table partitioned by values.
- aa....aa: Missing name:
- RDAREA: RDAREA name
- server: Server name
- S: Terminates processing.
- O: Specify the name of the RDAREA or server that is to use the file or directory and re-execute the command.
KFPL24152-E E+L
Index aa....aa not found, table=bb....bb.cc....cc
- Index aa....aa has not been defined for table bb....bb.cc....cc.
- aa....aa: Index identifier (when name=* is specified in the idxname statement, *** is output when there is no target index in the table)
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Correct the index name specified in the control information file and re-execute the command. When *** is output to the index identifier, check if an index exists in the table.
KFPL24153-E E+L
Index aa....aa not found in RDAREA bb....bb
- Index aa....aa was not found in RDAREA bb....bb.
- aa....aa: Index identifier
- bb....bb: RDAREA name
- S: Terminates processing.
- O: Correct the RDAREA name specified in the control information file and re-execute the command.
KFPL24154-E E+L
Unnecessary aa....aa directory specified
- A work file for index information or sorting was specified for a server for which no index has been defined.
- aa....aa: Type of directory{ { index|sort work }
- S: Terminates processing.
- O: Correct the server name for the directory specified in the control information file and re-execute the command.
KFPL24155-E E+L
Function aa....aa."bb....bb" not found, column="cc....cc"
- The function "bb....bb" cannot be found in the abstract data type of the column "cc....cc". Following are the possible causes of this problem:
- The function specified in the column structure file (with the same name and parameter) is not defined.
- The return value of the function specified in the column structure file is not the abstract data type of the column.
- If you are using the XML type, the function specified in the column structure information file is not consistent with the value specified in the -G option.
- aa....aa: Authorization identifier
- bb....bb: Function name
- cc....cc: Column name
- S: Terminates processing.
- O: Specify the correct function information in the column structure information file, and then re-execute the command. In addition, if you are using the XML type, specify the function corresponding to the value specified in the -G option in the column structure information file, as follows:
- In the case of -G xml: the XMLPARSE function
- In the case of -G esisb: the XML function
KFPL24156-E E+L
Required function not specified
- The constructor function necessary for generating a value to be stored in a column of the abstract data type is not specified. Or, the constructor parameter reverse generation function for reverse-generating a data value of the abstract data type is not specified. Following are possible causes of this problem:
- The indicated function is not one in which a constructor function is plug-in-implemented.
- If a column structure information file was omitted, either a function with the same name as the data type name is not defined as an abstract data type, or multiple functions with the same name are defined.
- A column of abstract data type for which a function is not defined has been found.
- unld_func statement is not specified in the control information file.
- S: Terminates processing.
- O:
- Specify in the column structure information file a plug-in-implemented constructor function that generates the values to be stored in a column of the abstract data type, and then re-execute the command.
- Alternatively, specify a constructor parameter reverse generation function that reverse generates abstract data type data values to the control information file, and then re-execute the command.
KFPL24157-E E+L
Function aa....aa."bb....bb" not found, type=cc....cc,"dd....dd", kind=ee....ee
- Function "bb....bb" specified by ee....ee is not defined in abstract data type "dd....dd".
- aa....aa: Authorization identifier of the function
- bb....bb: Function name
- cc....cc: Authorization identifier of the abstract data type
- dd....dd: Abstract data type name
- ee....ee: Type:
- { unld_func|reld_func }
- S: Terminates processing.
- O: Specify the correct function by referring to the manual for the applicable plug-in of the abstract data type, and re-execute.
KFPL24158-E E+L
Specified type not found in this table, type=aa....aa."bb....bb"
- Abstract data type aa....aa."bb....bb" specified by the type operand of the unld_func statement in the control information file is not defined in this table.
- aa....aa: Authorization identifier of the abstract data type
- bb....bb: Abstract data type name
- S: Terminates processing.
- O: Specify an abstract data type name defined in the table and re-execute.
KFPL24159-E E+L
Function_row missing in Control file, column="aa....aa"
- An unld_func statement corresponding to the abstract data type defined in column "aa....aa" is not specified in the control information file.
- aa....aa: Column name
- S: Terminates processing.
- O: Specify a constructor parameter reverse generation function in the unld_func statement in the control information file by referring to the manual for the plug-in that provides the abstract data type defined in the applicable column, and re-execute. If the constructor parameter reverse generation function is not implemented by the plug-in or if the -j option is specified, delete this option and re-execute.
KFPL24500-E E+L
Unable to continue pdload because of invalid aa....aa length, line=bb....bb
- A negative value was detected in the length section for the length of variable-length data in the binary-format input data file or in an effective element count for a repetition column. Or, the length of the input data exceeded the area reserved by maxreclen.
- aa....aa: Data type
- { VARCHAR|NVARCHAR|MVARCHAR|BINARY|BLOB|ARRAY }
- bb....bb: Line number
- S: Terminates processing.
- O:
- Determine whether an invalid length is specified in the length section for the length of variable-length data or in the effective element count storage area for a repetition column. Also determine whether there is an error in column data in the binary-format input file. If an error is found, correct the contents of the file and then re-execute the command.
- Or, if the length of the input data is greater than the value specified by maxreclen, check the maximum length of the input data, specify a value greater than the maximum length in maxreclen, and then re-execute.
KFPL24509-E E+L
Insert error occurred, line=aa....aa
- An error occurred during data storage processing for line aa....aa.
- aa....aa: Line number
- S: Terminates processing.
- O: Correct the cause of the error by referring to the preceding error message and re-execute the command.
- Note when re-executing:
- If the KFPL15225-E message (rollback) is output concurrently with this message, re-execute from the first row. If the KFPL15225-E message is not output, specify the -r option, and then re-execute from the row output to this message.
KFPL24510-E E+L
Error data detected, process stopped, error code=aa
- An error was detected in the input data during execution of the pdload utility. Processing is terminated.
- aa: Logical error number
- For logical error numbers and their descriptions, see the HiRDB Version 9 Command Reference.
- S: Terminates processing.
- O:
- Data loading:
Correct the data in the row number indicated in the KFPL24509-E message that was displayed together with this message.
If a KFPL15225-E message is displayed, all database storage processing is cancelled (rolled back). Therefore, the command is re-executed to store data from the beginning of the input file. If this command was executed in the no-log mode, the database needs to be restored from its backup.
If a KFPL15225-E message is not displayed, the storage of the data immediately preceding the error was completed (committed); therefore, the command is re-executed to store the data at and following the revised data (by using the -r option).
- File partitioning (creation of the partitioning input data file):
See the error message output to the error information file, correct the relevant data, and re-execute the command.
KFPL24990-E E+L
Only one aa....aa can be specified in Control file
- aa....aa can be specified only once in a control information file.
- aa....aa: Type:
- source_row: source statement row
- mtguide_row: mtguide statement row
- emtdef_row: emtdef statement row
- input_file: Input file
- unload_file: Unload file
- tblname_row: tblname row
- lobmid_row: lobmid statement row
- lobdata_row: lobdata statement row
- idxname_row: idxname statement row
- array_row: array statement row
- option_row: option statement row
- report_row: report statement row
- blobtovarchar_row: blobtovarchar statement row
- execstop_row: execstop statement row
- extdat_row: extdat statement row
- src_work_row: src_work statement row
- fixtext_option_row: fixtext_option statement row
- constraint_row: constraint statement row
- S: Terminates processing.
- O: Take one of the following actions, as appropriate to the displayed type:
- If source_row, mtguide_row, emtdef_row, lobmid_row, lob_data_row, array_row, or blobtovarchar_row is displayed:
Change the source row, mtguide row, emtdef row, lobmid row, lobdata row, array row, or blobtovarchar row in the control information file to one row each, and then re-execute the command.
- If input_file is displayed:
When specifying EasyMT information, specify only one input data file, and then re-execute the command.
- If unload_file is displayed:
When specifying EasyMT information, specify only one unload data file, and then re-execute the command.
- If idxname_row is displayed:
Delete all idxname statements except in rows in which (*) is specified in the name operand, and re-execute the command.
- If tblname_row or fixtext_option_row is displayed:
Specify one tblname or fixtext_option statement and re-execute the command.
- If option_row, report_row, execstop_row, extdat_row, src_work_row, or constraint_row is displayed:
Specify one option, report, execstop, extdat, src_work, or constraint_row statement in the control information file and re-execute the command.
KFPL24991-E E+L
Specified aa....aa conflicted with command line specification
- Information specified in the control information file contradicts the information specified on the command line, as shown below:
- Database load utility:
- The srcuoc statement was specified when using a binary format file to load data into a table with an abstract data type column.
- -f easymt was not specified on the command line, but EasyMT information or the validate operand was specified in the control statement.
- -f easymt was specified on the command line, but file input by a UOC was specified in the control statement.
- -k c was not specified on the command line, but the lobcolumn statement was specified.
- The vv option was specified in the type option of the array statement for control statements even when a fixed-length data-format file was specified.
- The fv option was specified in the type option of the array statement for control statements even when a DAT format file was specified.
- The srcuoc statement was specified in the control statement even when -k d was specified on the command line.
- The job operand was specified in the option statement in the control statement even when -l n, -k f, -k v, or -k c was specified on the command line.
- nowait=yes was specified in the option statement when the -n option or -I s was not specified on the command line.
- The extdat statement was specified, even though no DAT format file was specified.
- The null_string operand was specified in the option statement, even though no DAT format file was specified.
- The enclose_del operand was specified in the option statement for an input data file that is not in the fixed-size data format.
- Although the -b option was specified on the command line, the src_work statement was specified (if a binary format input data file, the partitioning input data file cannot be created).
- The srcendian operand was specified in the option statement in the control statement, even though, on the command line, -W and -b were not specified together or -U was not specified.
- Two or more input data files were specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.
- The host name of the utility special unit was specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.
- An RDAREA name was specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.
- The charset operand was specified in the option statement in the control statement, even though an extended DAT format or fixed-length data format file was not specified.
- Database reorganization utility:
- -f easymt was not specified on the command line, but EasyMT information was specified in the control statement.
- -f hirdb was not specified on the command line, but the HiRDB file information was specified in the control statement.
- -k reld was specified on the command line, but fileno=ADD was specified in the control statement.
- -k reld -c dic was specified on the command line, but the tblname control statement was specified.
- -k reld was specified on the command line, but the lobunld and tblname control statements were specified.
- The idxname statement was specified in the control statement even when -k ixrc was not specified on the command line.
- The job operand was specified in the option statement in the control statement even when -l n, -k unld, -k ixrc, -k ixor, -k ixmk, -c dic, or -t all (reorganization by schema) was specified on the command line.
- The lobunld statement was specified, even though the -j option was specified in the command line.
- Although -W extdat was specified on the command line, multiple unload file names were specified in the unload statement.
- The unldenq operand is specified in the option statement, but -k unld is not specified in the command line.
- The charset operand was specified in the option statement in the control statement, even though neither -W extdat or -W fixtext was specified on the command line.
- Free page release utility or global buffer residence utility:
- The idxname statement cannot be specified when the target resource is a table, when processing a dictionary table, or when processing at the schema level.
- aa....aa: Type:
- array_row: array statement
- easymt_information: EasyMT information
- emtdef_row: emtdef statement
- extdat_row: extdat statement
- fileno: File sequence number
- hirdb_information: HiRDB file information
- idxname_row: idxname statement
- lobcolumn_row: lobcolumn statement
- lobunld_row: lobunld statement
- option_row(charset): option statement charset operand
- option_row(enclose_del): option statement enclose_del operand
- option_row(job): option statement job operand
- option_row(nowait): option statement nowait operand
- option_row(null_string): null_string operand in the option statement
- option_row(srcendian): option statement srcendian operand
- option_row(tblstatus): tblstatus operand in the option statement
- option_row(unldenq): option statement unldenq operand
- src_work_row: src_work statement
- srcuoc_row: srcuoc statement
- tblname_row: tblname statement
- unload_row: unload statement
- S: Terminates processing.
- O:
- aa....aa is array_row:
- Specify either ff or fv if the input data file is a fixed-length data format file and re-execute the command. Or specify either ff or vv if the input data file is a DAT format file and re-execute the command.
- aa....aa is easymt_information or emtdef_row:
- EasyMT used:
Add the -f easymt specification to the command line and re-execute the command.
- EasyMT not used:
Delete the EasyMT information from the source row, the validate operand, or the emtdef row from the control information file and re-execute the command.
- aa....aa is extdat_row:
- The extdat statement is valid only for DAT format files, so when processing fixed-size data format or binary format files, delete the extdat statement, and then re-execute.
- aa....aa is fileno:
- For -k reld specified, correct the specification of fileno=ADD and re-execute the command.
- aa....aa is hirdb_information:
- To use a HiRDB file system as the unload file, specify -f hirdb on the command line and re-execute the command. Otherwise, delete the HiRDB file information from the control file and re-execute the command.
- aa....aa is idxname_row:
- For the database reorganization utility:
To re-create indexes by index, specify -k ixrc and re-execute the command.
- For the free page release utility or global buffer residence utility:
Specify the idxname statement when releasing a specific index, an RDAREA, or free pages on which only a server is using an index; or when reading data into the global buffer.
- aa....aa is lobcolumn_row:
- To use a LOB column input file, specify -k c on the command line and re-execute the command. Otherwise, delete the lobcolumn statement from the control file and re-execute the command.
- aa....aa is lobunld_row(charset):
- For the database load utility
Prepare the input data file in extended DAT format or fixed-length data format.
- For the database reorganization utility
Specify the -W extdat or -W fixtext option on the command line.
- aa....aa is option_row(enclose_del):
- Specify the -a option when the input data file is a fixed-size data format file. For input data files in other formats, delete the enclose_del operand.
- aa....aa is option_row(job):
- For pdload
When the job operand is specified in the option statement, re-execute the command without specifying -l n, -k f, -k v, or -k c.
- For pdrorg
When the job operand is specified in the option statement, re-execute the command without specifying -l n, -k unld, -k ixrc, -k ixor, -k ixmk, or -c dic.
- aa....aa is option_row(nowait):
- To execute a NOWAIT search concurrently with pdload, omit the -n option or specify -i s. If the NOWAIT search is not to be executed concurrently with pdload, specify nowait=no in the option statement.
- aa....aa is option_row(null_string):
- When the null_string operand is specified using the option statement, it is valid only when in the DAT format. For the binary format or fixed-size data format, delete the null_string operand of the option statement.
- aa....aa is option_row(srcendian):
- If the srcendian operand is specified in the option statement, specify both the -W and -b options, or the -U option, and then re-execute the command.
- aa....aa is option_row(tblstatus):
- The tblstatus operand in the option statement can be specified only with -k rorg. Therefore, either delete the tblstatus operand or change to -k rorg.
- aa....aa is option_row (unldenq):
- The unldenq operand of the option statement can be specified only with -k unld. Therefore, either delete the unldenq operand or change it to -k unld.
- aa....aa is src_work_row:
- If the input data file is composed of all columns in fixed length binary format, it is handled as a fixed length data format input data file, and a partitioning input data file can be created. If there are also variable length columns, consider either performing data loading in table units or partitioning the input data file.
- aa....aa is srcuoc_row:
- When -k d is specified
Change the specification so that UOC is not used.
- When -W, -b, and -w are all specified
Change the source statement in the control statement as follows:
Only one input data file is specified
The host name of the utility special unit is not specified
The RDAREA name is not specified
- aa....aa is tblname_row:
- A dictionary table or a table in which a LOB column is defined cannot be reloaded to another table. Check the option on the command line or the tblname statement, correct it, then re-execute the command.
- aa....aa is unload_row:
- If extdat is specified in the -W option, specify a single unload file name and re-execute.
KFPL24992-E E+L
Specified aa....aa conflicted with Control file specification
- One of the following contradictions was found in the control information file:
- This is a multivolume file, but Mtguide is not to be used according to the specified information.
- The mtguide or emtdef statement is not specified at the beginning of the control information file.
- A control statement not necessary for creating a LOB column only is specified.
- A UOC is declared, but the srcuoc or source statement is missing.
- Processing in units of tables is specified for a table containing a LOB column, but an attempt was made to process the LOB column in units of RDAREAs.
- A control statement is specified that is not needed for creation of the LOB column structure base table only. Or, a control statement needed for LOB creation is missing.
- Because the input data file is a binary-format file, the specification of the array data format for a column of variable-length data type is invalid.
- An idxname and an index statement are both specified.
- An unld_func or reld_func statement is specified for an abstract data type with the LOB attribute even when the -j option is not specified.
- The unld_func and reld_func statements are not specified as a pair even when -k rorg is specified.
- The job operand of the option statement is specified at the same time as the lobunld statement.
- An RDAREA name is specified in the source statement even when nowait=yes is specified in the option statement.
- The lobunld statement was not specified when using a UOC (when the unld_uoc statement is specified).
- (UOC) was specified in the unload statement when using a UOC (when the unld_uoc statement is not specified).
- (uoc) or UOC information was specified in the unload statement when not using a UOC (when unld_uoc statement is not specified).
- HiRDB information or EasyMT information was specified when (uoc) is specified in the unload statement.
- Y was specified in the fixrow operand in the unld_uoc statement for a non-FIX table.
- When creating the partitioning input data file (when the src_work statement is specified), the RDAREA name or the report statement is specified in the source statement. Or, the source statement is not specified.
- aa....aa: Conflicting contents:
- multi_volume: Volume names
- mtguide_row: mtguide statement
- emtdef_row: emtdef statement
- srcuoc_row: srcuoc statement
- idxwork_row: idxwork statement
- index_row: index statement
- sort_row: sort statement
- lobmid_row: lobmid statement
- source_row: source statement
- lobcolumn_row: lobcolumn statement
- array_row: array statement
- idxname_row: idxname statement
- func: unld_func or reld_func statement
- option_row(job): option statement job operand
- option_row(nowait): option statement nowait operand
- lobunld_row: lobunld statement
- unload_row(hirdb): HiRDB information in the unload statement
- unload_row(EASYMT): EasyMT information in the unload statement
- unld_uoc_row: fixrow in the unld_uoc statement
- lobunld_row(uoc): (uoc) or UOC information in the unload statement
- src_work_row: src_work statement
- S: Terminates processing.
- O: Take action appropriate to the displayed information and re-execute the command:
- multi_volume:
- To specify a multivolume, specify mtguide use.
- mtguide_row or emtdef_row:
- Specify the mtguide or emtdef statement after the source or unload statement.
- srcuoc_row:
- Specify the source statement or delete the srcuoc statement.
- lobmid_row:
- Delete the RDAREA name in the lobmid statement. Or, add the RDAREA name in the source statement.
- source_row:
- Specify the srcuoc statement. Alternatively, specify the file name in the source statement.
- lobcolumn_row:
- To create only a LOB column structure base table, delete the lobcolumn statement.
- To create LOB data, add the lobdata statement.
- array_row:
- Revise the specification of the array data format.
- idxname_row:
- To re-create indexes by index-storage RDAREA, delete the idxname statement. To re-create indexes by index, delete the index statement.
- In the case of pdreclaim and pdpgbfon, either limit operands to the name operand or avoid mixing an idxname statement that has a server operand specification with an idxname statement that has an rdarea operand specification.
- func:
- If the unld_func and reld_func statements are not specified as a pair in -k rorg, specify them as a pair.
- To specify an unld_func or reld_func statement for an abstract data type with the LOB attribute, specify the -j option concurrently.
- option_row(job):
- To perform data loading or reloading with synchronization point setting specified, delete the lobunld statement.
- option_row(nowait):
- To execute a NOWAIT search concurrently with pdload, do not specify an RDAREA name in the source statement. If the NOWAIT search is not to be executed concurrently with pdload, specify nowait=no in the option statement.
- lobunld_row:
- When using UOC (when specifying the unlduoc statement), the lobunld statement cannot be specified, so delete it.
- unload_row(uoc):
- When not using UOC (when not specifying the unlduoc statement), delete the unload statement (uoc) or the UOC information.
- lobunld_row(hirdb):
- Delete the HiRDB information.
- lobunld_row(ESAYMT):
- Delete the EasyMT specification.
- unld_uoc_row(fixrow):
- Delete the fixrow specification.
- src_work_row:
- Delete the RDAREA name specification or the report statement from the source statement. Also, if the source statement is not specified, specify the source statement.
- Other:
- Delete all the control statements that are not related to LOB creation.
KFPL24993-E E+L
Invalid absolute pathname, file=aa....aa
- The absolute path of file aa....aa exceeded the permitted maximum length of 1,023. This error may occur in the following cases:
- The length of the absolute path exceeded the maximum value of 1,023, including the directory name for the LOB input file specified in the lobdata statement and the name of the LOB column input file specified in the lobcolumn statement in the control information file.
- The absolute path of the LOB column input file specified in the lobcolumn statement of the control information file exceeded the maximum length of 1,023.
- aa....aa: Name of LOB column input file specified in lobcolumn statement
- If the length of the LOB input file name exceeds 150 characters, the last 150 characters of the LOB input file name are output.
- S: Terminates processing.
- O: Check the control information file for the directory name for the LOB input file specified in the lobdata statement and the name of the LOB column input file specified in the lobcolumn statement and correct any error. If the specified information is correct, move the LOB column input file to a location where the absolute path length does not exceed 1023, specify that absolute path in the control statement, then re-execute the command.
KFPL24999-E E+L
aa....aa invalid
- The specified -u option value or the authorization identifier or password specified in an environment variable was invalid during utility execution. Or, the password entered as a response to an input request message was invalid.
- aa....aa: Information resulting in the error:
- Auth_id: Authorization identifier
- Password: Password
- S: Terminates processing.
- O:
- Auth_id displayed:
Check the -u option on the command line, or correct the PDUSER environment variable and re-execute the command.
- Password displayed:
Correct the PDUSER environment variable and re-execute the command. Or, if the password was entered in response to the input request message, re-execute the command by entering the correct password.
- Note on specifying an authorization identifier or a password (Windows edition only):
When omitting the -u option, make sure the character string specifying an authorization identifier or password in the command prompt is not enclosed in single quotation marks (').
Example of correct specification: -u "root"/"root"
When specifying an authorization identifier or password in a client environment definition (hirdb.ini), enclose it in single quotation marks (').
Example of correct specification: PDUSER='"root"/"root"'
KFPL25000-E E+L
Invalid format exists in command line
- The format of the command line is invalid for the utility.
- S: Terminates processing.
- O: Correct the command line and re-execute the command.
KFPL25001-E E+L
Invalid attribute exists in command line
- An invalid value for the utility was specified on the command line. This message is also displayed when an identifier that uses national characters is specified while the LANG environment variable is not set correctly.
- S: Terminates processing.
- O: Take one of the following actions:
- In UNIX:
- Correct the command line and re-execute the command
- Use character codes of the type specified in the LANG environment variable in pdsetup and re-execute the command.
- In Windows:
- Revise the command line, and re-execute the command.
- If the LANG environment variable is defined, remove the LANG environment variable and re-execute the command. To remove the LANG environment variable, execute the following command at the command prompt:
set LANG=
KFPL25002-E E+L
Inconsistent specification in command line
- Mutually exclusive options were specified on the command line for the utility.
- S: Terminates processing.
- O: Correct the command line and re-execute the command.
KFPL25003-E E+L
Mandatory specification missing in command line
- A required option was omitted from the command line for the utility.
- S: Terminates processing.
- O: Specify the required information on the command line and re-execute the command.
KFPL25004-E E+L
Invalid format exists in Control file, line=aa....aa
- The format of line aa....aa in the control information file for the utility is invalid.
- aa....aa: Line number of erroneous line
- S: Terminates processing.
- O: Correct the indicated line in the control information file and re-execute the command.
KFPL25005-E E+L
Invalid attribute exists in Control file, line=aa....aa
- An invalid value was specified on line aa....aa in the control information file for the utility.
- aa....aa: Line number of line containing invalid value
- S: Terminates processing.
- O: Correct the indicated line in the control information file and re-execute the command.
KFPL25006-E E+L
Mandatory specification missing in Control file, line=aa....aa
- A required item was omitted from line aa....aa in the control information file for the utility.
- aa....aa: Line number of erroneous line
- S: Terminates processing.
- O: Specify the required item on the indicated line in the control information file and re-execute the command.
KFPL25007-E E+L
Duplicate attribute aa....aa exists in Control file
- aa....aa was duplicated in the control information file for the utility.
- aa....aa: Duplicated information in the control information file
- S: Terminates processing.
- O: Correct the duplicated information in the control information file and re-execute the command.
KFPL25009-E E+L
Mandatory specification does not exist in Control file
- A control statement required in a control information file for the database load utility (pdload) was not specified.
- The source statement was not specified when data was loaded.
- During LOB loading, either the lobmid or the lobdata statement was not specified.
- S: Terminates processing.
- O: In the control information file, specify the source, lobmid, or lobdata statement, and then re-execute the command.
KFPL25010-E E+L
HiRDB aa....aa interface error occurred, code=bb, file=cc....cc[, contents='dd....dd'x]
- An interface error occurred between HiRDB Dataextractor, DataStage, or XDS and the database load utility (pdload). ", contents='dd....dd'x" is output only if code=2.
- aa....aa: Function type
- Dataextractor: HiRDB Dataextractor or DataStage
- export: XDS
- bb: Maintenance code
- 1:
- The file specified by the file operand in the extractorinf clause is not FIFO.
- 2:
- The content of the file specified by the file operand in the extractorinf clause is not COMPLETED (an error may also occur when there is a newline or other character after COMPLETED).
- cc....cc: Maintenance information 1
- The file name specified by the file operand in the extractorinf clause (if the length of the file name exceeds the maximum character length, only the end of the file name, up to the maximum number of characters, is output).
- dd....dd: Maintenance information 2
- This is the content (displayed in hexadecimal numbers) of the file specified by the file operand in the extractorinf clause. x is displayed when nothing is specified to the file.
- S: Terminates processing.
- O:
- aa....aa is Dataextractor:
- When an error occurs in the HiRDB Dataextractor or DataStage:
See the message output by HiRDB Dataextractor or DataStage, and then take appropriate action.
- When HiRDB Dataextractor or DataStage was cancelled:
Ignore this message.
- Other:
Contact the customer support center.
- aa....aa is export:
- This message is sometimes output under the circumstances listed below. If this is the case, you can safely ignore the message.
- The XDS process was terminated by the pdxdsstop -f command or the pdstop -f command
- The XDS process was terminated using the kill command or similar means
- Database export terminated abnormally
- The XDS process terminated abnormally
- If the message is output in circumstances other than the above, contact the customer support center.
KFPL25011-E E+L
Invalid option specified in command line, option=aa
- Invalid option aa is specified in the command line of a utility.
- aa: Option name
- If more than one invalid option is specified in the command line of a utility, the first invalid option is displayed.
- S: Terminates processing.
- O: Delete option aa or specify a valid option, and then re-execute the command.
- The -K and -G options cannot be specified for tables with no XML-type columns defined. Delete these options.
KFPL25012-E E+L
Invalid option value specified in command line, option=aa
- The value of option aa, specified in the command line of a utility, is invalid.
- aa: Option name
- S: Terminates processing.
- O: Revise the value specified in option aa, and then re-execute the command.
KFPL25013-E E
Inconsistent specification in command line, option=aa, bb
- The command line for a utility to be executed contains mutually exclusive options aa and bb.
- aa: Option name
- bb: Option name
- S: Terminates processing.
- O: Delete either option aa or option bb, and then re-execute the command.
- -b and -K:
- If a binary format file, or the pdload unload file output by pdrorg, is specified as the input data file, you cannot specify f in the -K option. Delete the -K option, or change it to match the format of the input data file.
- -W and -G:
- If a pdload unload file output by pdrorg is specified as the input file, you cannot specify xml in the -G option. Delete the -G option, or change it to match the format of the input data file.
KFPL25040-E E+L
Cannot allocate communication buffer, size=aaaaa, code=b
- Communication buffer cannot be allocated.
- aaaaa: Communication buffer size to be allocated
- b: Reason code:
- 4: Area shortage
- 8: Protocol error
- S: Terminates processing.
- O: Take the following action:
- In UNIX:
- Wait until another process using a large amount of the user space terminates and re-execute the command.
- If row partitioning among servers is performed and commands are executed by table, consider whether commands can be executed by RDAREA instead. The necessary buffer size is reduced to the reciprocal of the number of servers.
- In Windows:
- Wait until another process using a large amount of the user space terminates and re-execute the command.
- If commands are executed by table, consider whether commands can be executed by RDAREA instead. The necessary buffer size is reduced to the reciprocal of the number of servers.
- Action
- Reduce the value of pd_utl_buff_size (length of communication buffer for utility) in the system common definition.
KFPL25100-E E+L
Column name missing in configuration file
- No column name with the NOT NULL constraint has been specified in the column structure information file. Or, no column name has been specified.
- S: Terminates processing.
- O: Specify the required column names in the column structure information file and re-execute the command.
KFPL25101-E E+L
Invalid format existed in dataload file
- The format of an input data file is invalid.
- S: Terminates processing.
- O: Correct the information in the input data file and re-execute the command.
KFPL25102-E E+L
Invalid attribute in configuration/null-information file, line=aaaaa
- The column structure information file, null value information file, or function information file contains erroneous information.
- aaaaa: Row number where erroneous information was detected
- S: Terminates processing.
- O: Correct the information in the column structure information file, null value information file, or function information file, and then re-execute the command.
KFPL25103-E E+L
Unable to specify reserved column to configuration/null-information file, file=aa....aa, line=bb....bb
- A reserved column cannot be specified in a column structure information file, null value information file, or function information file.
- aa....aa: Name of the erroneous column structure information file, null value information file, or function information file
- If the length of the file name exceeds 130 characters, only the last 130 characters of the file name are output.
- bb....bb: Line number where the reserved column is specified
- S: Terminates processing.
- O: Delete the specification of the reserved column from the column structure information file, null value information file, or function information file, and then re-execute the command. If data for the reserved column appears in the input file, delete the data as well.
KFPL25200-E E+L
Unable to get utility definition
- The system common definition could not be read, so default values were assumed for the environment.
- S: Resumes processing.
- Action
- Check the contents of the system common definition file the next time the default values are changed for the utility execution environment.
KFPL25210-E E+L
aa....aa must be executed at unit defined as manager
- aa....aa should be executed at the unit where the system manager is defined.
- aa....aa: Utility or command for which execution was attempted
- pdload: Database Load Utility
- pdrorg: Database reorganization utility (including pdreclaim and pdpgbfon)
- COMMAND: Plug-in-provided command
- pdrbal: Rebalancing utility
- S: Terminates processing.
- O: Log in the remote unit where the system manager (MGR) is defined and re-execute the command.
KFPL25211-E E+L
Cannot specify input file at manager
- The server specified for an input data file was not any of the following:
- Front-end server
- Back-end server
- Dictionary server
- S: Terminates processing.
- O: Change the location of the input data file and re-execute the command.
KFPL25212-E E+L
Default value length too long, column="aa....aa"
- Because the column name statement in the column structure information file was omitted, the default was specified for storage in column "aa....aa", but the default could not be stored because the default is longer than the applicable column.
- aa....aa: Column name
- S: Terminates processing.
- O: Either specify the column name statement of the column structure information file or change the length of the applicable column in the table definition so the default can be stored, and then re-execute.
KFPL25213-E E+L
Unable to execute aa....aa command due to check pending status, table=bb....bb."cc....cc"
- Utility aa....aa cannot be executed because table bb....bb."cc....cc" is in check pending status.
- aa....aa: Utility name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- Action
- Execute the integrity check utility to confirm that there is no row data with a constraint violation. After the check pending status of the table is released, re-execute the utility.
KFPL25214-E E+L
Unable to get sequence number,sequence=aa....aa."bb....bb"
- It is not possible to acquire the sequence number of the sequence generator aa....aa."bb....bb" for the following reason:
- An attempt was made to acquire a sequence number from a sequence generator, but the range in which acquisition is possible was exceeded.
- aa....aa: Sequence generator authorization identifier
- bb....bb: Sequence generator identifier
- S: Terminates processing.
- O: Use the database condition analysis utility to reference the current value of the sequence generator, and check the sequence generator definition. Then take corrective action, such as by changing the acquisition range or cycle specifications of the sequence number, and re-execute.
KFPL25222-W E+L
Unable to output aa....aa file, reason=bb....bb
- An input data error was detected. However, data cannot be output to the error information file or the partitioning input data file for the reasons indicated in bb....bb.
Regardless of how many times data could not be output to the error data file or the partitioning input data file, the message is output only once. - aa....aa: File type
- error data: Error data file
- error information: Error information file
- divided: Partitioning input data file
- bb....bb: Reason code
- ROW LENGTH:
- The row length of the error data exceeds 32 KB or it exceeds the value specified in the maxreclen operand of the source statement.
- UNIQUE_ERROR:
- Although a duplicate key value error was detected in the index for which unique key or primary key was specified, a shortage of error data file edit buffers occurred.
- PLUGIN_ERROR:
- Although an error was detected by a plug-in supplied function, an error data file edit buffer shortage occurred.
- INSUFFICIENT MEMORY:
- The area for editing the dump image list to be output to the error information file could not be allocated due to a memory shortage.
- S: Resumes processing.
- O:
- Error data file:
- Although some data was output to the error information file, other data was not output to the error data file. Therefore, search the relevant data not from the error data file but from the input data file, and correct it.
- If the buffer size is insufficient, for the next data loading, specify a sufficiently large error data file edit buffer size in the errwork operand. Even if the error is detected, the data is output to the error data file.
- Error information file:
- Because a dump image list is not output to the error information file, refer to the error message that is output to the error information file, retrieve the applicable error data from the input data file, and revise the data.
- Partitioning input data file:
- Specify the maximum row length in the maxreclen operand, and re-execute.
KFPL25225-E E+L
Incompatible file format, file=aa....aa
- The aa....aa file was output in a prior version, so it is not compatible.
- aa....aa: File name
- If the file name exceeds the maximum character length, then the maximum number of characters are output as counted from the end of the file name.
- S: Terminates processing.
- Action
- Action during importing (pdload):
- Because the table transfer unload file is not backwards compatible, a table cannot be transferred during export and import.
- Transfer the table using a different means, such as the database reorganization utility and database load utility.
KFPL25226-E E+L
Error occurred in aa....aa library function call, reason=bb....bb, inf=cc....cc
- An error occurred in the processing of a compression library function call.
If this message is displayed during the execution of a command provided by a plug-in, the message is output only to the indicated output device type (L). - aa....aa: Processing type
- compressed: Compression
- bb....bb: Reason for error
- LIBRARY LOAD FAILURE:
The compression library failed to load.
- INSUFFICIENT MEMORY:
A memory shortage occurred during processing of the data compression function.
- cc....cc: When the reason for error is LIBRARY LOAD FAILURE, "********" is displayed.
- When the reason for error is INSUFFICIENT MEMORY, it displays the size of the area that was to be allocated (in bytes). If the size of the area cannot be determined, "********" is displayed.
- S: Terminates processing.
- O:
- If bb....bb is LIBRARY LOAD FAILURE:
- Ask the HiRDB administrator whether your environment is configured to use the data compression function.
- If bb....bb is INSUFFICIENT MEMORY:
- Re-execute. If this error occurs again, contact the HiRDB administrator.
- Action
- If bb....bb is LIBRARY LOAD FAILURE:
- Check whether the compression library has been installed correctly.
- If bb....bb is INSUFFICIENT MEMORY:
- Reduce the number of concurrently executing processes to ensure that sufficient memory is available.
KFPL25338-E E+L
Invalid RDAREA id found in unload file, RDAREA id=aa....aa, file=bb....bb
- The RDAREA for storing the unloaded rows is different from the RDAREA for storing the rows to be reloaded.
- aa....aa: Name of unloaded RDAREA
- bb....bb: Name of unload data file
- If the length of the unload data file name exceeds 143 characters, the last 143 characters of the unload data file name are output.
- S: Terminates processing.
- O:
- RDAREA name specified in the -r option:
- Specify the unload data file containing the rows of the corresponding RDAREA and re-execute the command.
- -r option omitted:
- Specify the correct unload data file and re-execute the command. Or, restore the corresponding table, specify reorganization processing (-k rorg), then re-execute the command.
- -g option specified:
- Because row data that cannot be stored is in the unload file, refer to the table definition before change, add to the partitioning condition an RDAREA in which rows can be stored, and change the table definition. Then specify reload processing (-k reld) and re-execute the command.
KFPL25339-E E+L
Unable to get aa....aa information from unload file, file=bb....bb
- Information aa....aa is not found in the unload data file. Therefore, the data cannot be reloaded.
- aa....aa: Type of information:
- column: Column information
- dictionary: Dictionary information
- divide: Partitioning information
- hash: Hash partitioning information
- index: Index information
- index rdarea: Information about index storage RDAREA
- LOB: LOB information
- ADT: Abstract data type
- multidim: Matrix partitioning information
- bb....bb: Name of unload data file
- If the length of the unload data file name exceeds 148 characters, the last 148 characters of the unload data file name are output.
- S: Terminates processing.
- O: Refer to the message in the message log file that was output before this message to eliminate the cause of the error, then re-execute the command.
KFPL25340-E E+L
aa....aa information not exists on unload file, file=bb....bb
- Because information aa....aa was not found in the unload data file, data cannot be reloaded.
- aa....aa: Type of information:
- Column: Column information
- Dictionary: Dictionary information
- Divide: Partitioning information
- Hash: Hash partitioning information
- Index: Index information
- Index rdarea: Information about index storage RDAREA
- LOB: LOB information
- ADT: Abstract data type
- multidim: Matrix partitioning information
- bb....bb: Name of unload data file
- If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Terminates processing.
- O: Specify the correct unload data file and re-execute the command.
KFPL25341-E E+L
aa....aa lock request failed, id=bb....bb
- Locking resource aa....aa failed.
- aa....aa: Name of resource
- bb....bb: Resource ID
- S: Terminates processing.
- O: Re-execute the command after the user processing currently occupying the corresponding resource has terminated.
KFPL25342-E L
Invalid EOF found in unload file, file=aa....aa
- Indicated unload data file is invalid.
- aa....aa: Name of unload data file
- If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.
- S: Terminates processing.
- O: Specify the correct unload data file and re-execute the command.
KFPL25343-E E+L
Different column information in unload file, table=aa....aa.bb....bb
- Because the table definition in the unload data file is different from the table definition in the table to be reloaded, the table cannot be reloaded.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Unload the corresponding table (-k unld) and re-execute the command. Or, reorganize the database (-k rorg).
KFPL25344-E L
Insufficient index file, index=aa....aa.bb....bb
- Specified index information files are not sufficient for index aa....aa.bb....bb.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Terminates processing.
- O: Specify the remaining index information files and re-execute the command.
KFPL25347-E E+L
No specified aa....aa in Control file
- No unload data file, LOB data unload file, or index information file was specified. Or, no LOB column input file was specified for a LOB column that was specified in the input data file for the LOB column structure base table.
- aa....aa: Type of required file:
- { index (index information file)
- | unload (unload data file)
- | unload (lobunld) (unload data file or LOB data unload file)
- | lobcolumn (LOB column input file) }
- S: Terminates processing.
- O: Take one of the following actions:
- Specify an unload data file, LOB data unload file, or index information file and re-execute the command.
- Specify all the LOB column input files for the LOB columns that were specified in the input data file for the LOB column structure base table.
- To re-create the index (-k ixrc), specify an idxname or index statement and re-execute the command.
KFPL25352-E E+L
Insufficient unload file, table=aa....aa.bb....bb, server=cc....cc
- No unload data file was specified for server cc....cc.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Server name
- S: Terminates processing.
- O: Specify an unload data file and re-execute the command.
KFPL25353-E E+L
Incompatible byte order between unload and reload system
- Reloading cannot be executed because the byte order of the unloaded system differs from the byte order of the system to be reloaded.
- S: Terminates processing.
- O: Unload/reload objects between systems that support the same byte order.
KFPL25354-E E+L
Incompatible character code set, HiRDB=aa....aa, unload file=bb....bb
- The character codes of the unload file do not match the character codes of the reload destination HiRDB.
The character code type of the table transfer unload file does not match the character code type of the import destination HiRDB. - aa....aa: HiRDB character code type:
- CHINESE: EUC Chinese kanji codes
- LANG-C: One-byte character codes
- SJIS: Shift JIS codes
- UJIS: EUC Japanese kanji code
- UTF-8: Unicode (UTF-8)
- bb....bb: Character code type for the unload data file:
- CHINESE: EUC Chinese kanji codes
- LANG-C: One-byte character codes
- SJIS: Shift JIS codes
- UJIS: EUC Japanese kanji code
- UTF-8: Unicode (UTF-8)
- S: Terminates processing.
- O: Unload and reload objects only between systems that support the same character code types.
- Also, import and export only between systems that support the same character code types. However, note that during import, if -w csetnck is specified in the pdload option, the table data in the table transfer unload file will be stored in the database as-is, so the values of the stored table data cannot be guaranteed.
KFPL25355-E E+L
More than aa....aa bytes in bb....bb
- The row length exceeds the maximum length after conversion to DAT format or fixed length data format.
- aa....aa: Maximum length
- bb....bb: Row length
- S: Terminates processing.
- Action
- If necessary, change the format specification to binary format (-W bin) and re-execute.
KFPL25356-E E+L
Incompatible unload file version
- The specified unload data file cannot be used because the version differs from that of the current HiRDB.
- S: Terminates processing.
- O: Check that the correct unload data file is specified. If the wrong unload data file is specified, specify the correct unload file and re-execute.
- Action
- The specified unload data file cannot be reloaded because it was created by a version of HiRDB that is older than the current HiRDB version. If necessary, specify an unload data file that was output by the current HiRDB version and re-execute.
KFPL25357-E E+L
Invalid LOB data, RDAREA="aa....aa"
- LOB data is invalid.
- aa....aa: LOB storage RDAREA name
- S: Terminates processing.
- O:
- For pdrorg:
- During execution in table units:
Reinitialize the LOB data storage RDAREA defined for the table to be processed, specify only lobunld in the control statement, then reload the data in table units.
- During execution in RDAREA units:
Reinitialize the output LOB RDAREA, specify only lobunld in the control statement, then reload the data in RDAREA units.
- For pdload:
- In creation mode:
Reinitialize the LOB RDAREA to be processed and load the LOB data. The RDAREA to be reinitialize is the same as for pdrorg.
- In add mode:
Back up the table and LOB RDAREA and reload the data. Do not update the table and LOB RDAREA with the UAP until they have been backed up.
KFPL25358-E E+L
Invalid LOB data, RDAREA=aa....aa, line=bb....bb
- Row bb....bb of LOB data could not be stored in user LOB RDAREA aa....aa.
Possible reasons: - Another attempt to load data into a LOB column was made even though data loading to the LOB column is complete.
- An attempt to load data (including reloading) was made to a user LOB RDAREA that is in DB disrupted status.
- aa....aa: User LOB RDAREA name
- bb....bb: Number of rows in which errors were detected
- S: Terminates processing.
- O:
- Correct the user LOB RDAREA name or the LOB middle file name, and then re-execute.
- Restore the user RDAREA or user LOB RDAREA from the stored backup, and then re-execute.
KFPL25359-E E+L
Unable to reload table or unload file due to aa....aa defined
- A row cannot be re-registered in another table because a LOB column is defined in that table or in the table in the unload data file.
- aa....aa: LOB column
- S: Terminates processing.
- O: An unloaded table or row cannot be re-registered in a table in which a LOB column is defined. Create another table with the database load utility or a UAP.
KFPL25360-E E+L
aa option not specified when bb option specified
- Option bb is specified, but no option aa is specified.
- aa: Option name
- bb: Option name
- S: Terminates processing.
- O: Check the combination of options, and then re-execute the command.
KFPL25361-E E+L
Lock time out error occurred, RDAREA=aa....aa
- A lock wait timeout occurred during lock processing on RDAREA aa....aa.
- aa....aa: Name of the RDAREA subject to lock processing
- S: Terminates processing.
- O:
- Wait until the processing using the RDAREA terminates, and then re-execute the command.
- Either increase the value specified with the -w option (increasing lock wait time) or increase the value specified with the -n option (increasing the retry count), and then re-execute the command.
KFPL25700-I L+S
UOC information, message=aa....aa, code=bb
- A message output request was received from the UOC.
- aa....aa: Output message requested from UOC
- bb: UOC's return code
- S: If UOC's return code is 4, resumes processing; otherwise, terminates processing.
- O: If processing was cancelled, check the message output by the UOC, eliminate the cause of the error, then re-execute the command.
KFPL25710-E E+L
Invalid value in UOC interface area, code=aa, line=bb....bb
- Invalid value was set by UOC in the UOC interface area.
- aa: Error detail code:
- 10: The address of the data edited by the UOC was not set.
- 20: For a binary input data file, the length of the data edited by the UOC did not match the table definition. For an extended DAT format input data file, the length of data edited by the UOC is set to a negative value.
- 30: No return code or an invalid return code was set by the UOC.
- 40: Data was updated beyond the data length in the input buffer used to store data input from the utility. Or, the UOC interface area was damaged.
- 50: There was no linefeed character at the end of the DAT-format input data file. In the case of a binary input data file with -W specified that is output by the database reorganization utility, the input data contains BLOB data.
- 51: The variable length character string type or large object data type is invalid.
- 52: The sign part of the packed format data is invalid.
- 53: The packed data value or specified range of packed data in the packed format is invalid.
- 54: The actual length of the repetition column does not match the returned data.
- 55: The number of times the repetition column is repeated is invalid.
- 56: The null value flag of the repetition column is invalid.
- 57: The null value setting in a NOT NULL column is invalid.
- 60: The value of the store flag is invalid.
- 70: The parameter of the audit trail data registration UOC is invalid.
- bb....bb: Number of row where the error occurred
- This is the state when the row number is 0, an error occurs during the UOC start process and no lines were processed.
- S: Terminates processing. However, abnormally terminates processing when the error detail code is 40.
- O: Reevaluate the content set in the UOC interface area, correct the program, and then re-execute the command.
KFPL25999-W E+L
Unable to make an entry SQL_DB_MANAGEMENT, RDID=aa....aa, reason=bb....bb
- The result of condition analysis could not be registered in the database management table. Therefore, if only one table or one index is stored in the RDAREA with RDAREA ID aa....aa,# an error may occur in the RDAREA estimated obsolescence time prediction shown by the facility for predicting reorganization time (the obsolescence prediction time is late).
If multiple RDAREAs are to be processed, a message is output only for the first RDAREA where an error was detected.
#: If multiple tables or indexes are stored in a single RDAREA, the RDAREA estimated obsolescence time prediction cannot reference the database management table because, even if some of the tables or indexes in the RDAREA are reorganized, not all of the RDAREA is reorganized, so it is not reflected in the prediction. - aa....aa: RDAREA ID
- bb....bb: Error cause
- MEMORY: Insufficient memory.
- CONNECT: HiRDB connection failed.
- ACCESS: Database management table could not be accessed.
- HOLD: Access not possible due to command hold.
- SQL_ERR: Database management table could not be modified.
- MESSAGE_SEND: Communication error.
- S: Continues processing.
- O:
- See the error message# that was output before this message and eliminate the cause of the error, then re-execute pddbst. Then, when the result of pddbst execution is reflected in the database management table and the facility for predicting reorganization time is executed, the prediction precision increases. If multiple tables or indexes are defined in a single RDAREA, re-execution is not necessary. Also, even without re-execution, the prediction error can be minimized by executing the condition analysis results depository facility every day.
- If the RDAREA estimated obsolescence time prediction is already displayed and most of the reorganization time can be divided, determine the prediction time to be that already displayed in the RDAREA estimated obsolescence time prediction of the previous several days.
- #: With KFPA11204-E, the data dictionary RDAREA that stores the analysis information table and the database management table must be created using pdmod.
KFPL26339-E E+L
Unable to get aa....aa information from lobmid file, file=bb....bb
- aa....aa information cannot be acquired from the LOB middle file.
- aa....aa: Information type:
- column: Column information
- LOB: LOB information
- bb....bb: LOB middle file name
- If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.
- S: Terminates processing.
- O: Referring to the error message that was output before this message, eliminate the cause of the error, and then re-execute the command.
KFPL26340-E E+L
aa....aa information not exists on lobmid file, file=bb....bb
- LOB column data cannot be loaded because aa....aa information does not exist in the LOB middle file.
- aa....aa: Information type:
- Column: Column information
- LOB: LOB information
- bb....bb: LOB middle file name
- If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.
- S: Terminates processing.
- O: Specify the correct LOB middle file and re-execute the command.
KFPL26342-E E+L
Invalid EOF found in lobmid file, file=aa....aa
- LOB middle file is invalid.
- aa....aa: LOB middle file name
- If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.
- S: Terminates processing.
- O: Specify the correct LOB middle file and re-execute the command.
KFPL27100-E E+L
Unable to get UOC aa....aa information, name=bb....bb, errno=ccc
- The system was unable to obtain the following UOC information:
- library: UOC storage library
- function: UOC function
- aa....aa: Type of UOC information:
- library: Shared library name
- function: Function name
- bb....bb: Name of UOC information
- ccc: Error number set in errno
- S: Terminates processing.
- O: Check errno.h and the OS manual for the details of errno (external integer variable indicating the error status) To determine the cause of the error and correct the name specified in the control information file. Or, check the specified library to make sure that it is a shared library and that access permission has been granted, then re-execute the command. If errno = 0, correct the error by referring to the KFPL22001-E message that was output immediately before this message, and re-execute the command.
KFPL27500-E L
aa....aa wait time over,bbbbb=cc....cc."dd....dd",RDAREA=ee....ee
- During processing to release free pages, processing was canceled because the time spent waiting for the transaction to finish, or the time spent waiting for a search using holdable cursor to execute, exceeded the waiting time specified in the -w option.
- aa....aa: {Transaction|Cursor close}
- bbbbb: {INDEX|TABLE}
- cc....cc: Authorization identifier of the index or table
- dd....dd: {index identifier|table identifier}
- ee....ee: RDAREA name
- S: Terminates processing.
- O: If you want to continue to release free pages, take the following actions, and then re-execute pdreclaim.
- If aa....aa is Transaction:
- Take either of the following actions:
- Wait for the UAP of the large object transaction to terminate, and then retry the operation.
- Re-execute with a longer waiting time specified in the -w option.
- If aa....aa is Cursor close:
- Take either of the following actions:
- Close the holdable cursor that has been open for the longest time, terminate the transaction, and then retry the operation.
- Re-execute with a longer waiting time specified in the -w option.
KFPL28000-E E+L
Internal error occurred, code=aaa(bb....bb)
- An internal error occurred.
- aaa: Maintenance code (the following table shows maintenance codes and their meanings)
- bb....bb: Maintenance information (the following table shows maintenance information)
- S: Terminates processing.
- O: Execute this command using the version of HiRDB assumed by the plug-in provided by the command or a newer version.
- Because the HiRDB version does not match the version assumed by the plug-in, upgrade the HiRDB version. If the versions match, contact the customer support center.
- Following is a list of maintenance codes and maintenance information:
Maintenance code | Explanation | Maintenance information |
---|
1 | Invalid execution command line format | -- |
2 | Required option not specified in execution command line | -- |
100 | Duplicate control statements, shown in maintenance information, in control information file | Control statement |
101 | Plug-in type (index statement) not specified in control information file | -- |
102 | Conflicting plug-in type (index statement) specifications in control information file | -- |
104 | Invalid type format for error row number, shown in maintenance information, specified in control information file | Information type and error row number:
- Information type:
library_name: Library name function_name: Function name option_string: Option character string mode_kind: Mode type lock_kind: Lock type table_access_kind: Table access type
|
105 | Number of modecheck statements in the control information file greater than the maximum limit | -- |
107 | Invalid error row number format, shown in maintenance information in control information file | Error-causing row number |
108 | Required items (func statement and func_type statement) not found in control information file | -- |
109 | Input error on control information file shown in maintenance information | Name of control information file |
200 | Specified external routine name not registered | - Detail code:
- 1: Library name
- 2: Plug-in function
|
201 | Not a utility timing | Timing code for specified external routine |
- --: Not applicable
KFPL28002-E E+L
Invalid HiRDB connect aa....aa
- Either the environment variable PDUSER is not specified, or the authorization identifier or the password specified in the environment variable PDUSER is invalid.
- aa....aa: Error type
- user_id: HiRDB connection authorization identifier
- password: HiRDB connection password
- S: Terminates processing.
- O:
- Correct the contents of the environment variable PDUSER and re-execute the command.
- Correct specification: PDUSER="root"/"root"
- When specifying an authorization identifier or password in a client environment definition (hirdb.ini), enclose it in single quotation marks (').
- Example of correct specification: PDUSER='"root"/"root"'
KFPL28101-E E+L
Table aa....aa."bb....bb" not found
- The table to be processed, aa....aa."bb....bb", is not found.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Review and revise the authorization identifier and the table identifier for the table to be processed and re-execute the command.
KFPL28102-E E+L
Index aa....aa."bb....bb" not found
- The index to be processed, aa....aa."bb....bb", is not found.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Terminates processing.
- O: Review and revise the authorization identifier and the index identifier for the index to be processed and re-execute the command.
KFPL28103-E E+L
Column "aa....aa" not found in table bb....bb."cc....cc"
- The column name "aa....aa" is not found in the table bb....bb."cc....cc".
- aa....aa: Column name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Correct the column name and re-execute the command.
KFPL28104-E E+L
Privilege not satisfy
- The command cannot be executed because the user does not have the requisite privilege.
- S: Terminates processing.
- O: Check if the current privilege is valid. If it is invalid, change it, and re-execute the command. If the current privilege is the valid one, ask the HiRDB administrator or the owner of the table to grant the privilege for the indicated table, and then re-execute the command.
- Action
- If a programmer asks to be granted a privilege and his or her request is proper, the requested privilege should be assigned.
KFPL28105-E E+L
Column "aa....aa" not ADT
- The column name "aa....aa" is not an abstract data type (ADT).
- aa....aa: Column name
- S: Terminates processing.
- O: Specify a column of abstract data type and re-execute the command.
KFPL28108-E E+L
PLUGIN not defined in column "aa....aa"
- A plug-in is not defined for the specified column name "aa....aa".
- aa....aa: Column name
- S: Terminates processing.
- O: Change the type of the column to a type defined by a plug-in and re-execute the command.
KFPL28109-E E+L
PLUGIN not defined in index "aa....aa"
- The index "aa....aa" is not a plug-in index.
- aa....aa: Index identifier
- S: Terminates processing.
- O: Change the name of the index to be executed to a plug-in index name and re-execute the command.
KFPL28900-I L
Pdplgexe started, generation=aa
- Execution of the Plug-in Execution Utility (pdplgexe) has started.
generation=aa is displayed when using the inner replica facility. - aa: Generation number
- S: Resumes processing.
KFPL28901-I L
Pdplgexe terminated, return code=aa
- Execution of the Plug-in Execution Utility (pdplgexe) has terminated.
- aa: Return code
- 0: Normal termination
- 8: An error occurred in the plug-in function
- 12: An error occurred in a function other than the plug-in function
- S: Terminates processing.
- O: For a non-0 return code, correct the cause of the error by referring to the error message that was output to either standard output device or the message log file and re-execute the command.
KFPL28904-I L+S
Transaction commit
- The transaction was committed.
- S: Resumes processing.
KFPL28905-E E+L
Transaction rollback
- The transaction was rolled back due to the reason indicated in the message log file that was output prior to this message.
- S: Terminates processing.
- O: Correct the cause of the roll back by reviewing the message log file that was output prior to this message.
KFPL30000-I R
aa....aa name=bb....bb
- Displays the beginning of the message for the data that was to be inserted in RDAREA bb....bb.
- aa....aa:
- Server: Server name
- RDAREA: RDAREA name
- bb....bb: Identifier
- S: Outputs the information message to the error information file and terminates processing.
KFPL30001-I R
Rows successfully loaded=aa....aa
- aa....aa rows of data were loaded successfully.
- aa....aa: Number of rows
- S: Outputs the information message to the error information file and terminates processing.
KFPL30002-I R
aa....aa rows outputed, RDAREA=bb....bb
- Data stored in RDAREA bb....bb yields aa....aa rows output.
- aa....aa: Row count
- bb....bb: RDAREA name
- S: Outputs an information message to the error information file and terminates processing.
KFPL31001-E R
Invalid input data byte, line=aa....aa, column=bb....bb[, element=cc....cc]
- The input data length indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output) is invalid.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- cc....cc: Element number
- S: Outputs the error message to the error information file.
- O: Correct the data on the indicated line of the input data file.
KFPL31002-E R
Invalid pack format value, line=aa....aa, column=bb....bb[, element=cc....cc]
- The packed format data indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output) is invalid.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- cc....cc: Element number
- S: Outputs an error message to the error information file.
- O: Correct the packed format data of the indicated line number in the input data file.
KFPL31003-E R
Invalid varchar length, line=aa....aa, column=bb....bb[, element=cc....cc]
- The length of the variable-length data (VARCHAR, NVARCHAR, MVARCHAR, BINARY) indicated by line=aa....aa, column=bb....bb (if element is output, repetition column element cc....cc) exceeds the column definition length used during table definition; or the -z option is omitted when storing variable-length data with a zero length.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- cc....cc: Element number
- S: Outputs an error message to the error information file.
- O: Correct the data of the indicated line number in the input data file.
KFPL31004-E R
Data conversion error occurred, line=aa....aa, column=bb....bb[, element=cc....cc]
- An error occurred during the conversion processing of the input data indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output).
Consider the following causes: - The data in the input file is incorrect.
- The specification of the charset operand of the option control statement does not match the character encoding of the input data file.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- cc....cc: Element number
- S: Outputs an error message to the error information file.
- P: Correct the data on the indicated line number in the input data file. Alternatively, revise the specification of the charset operand of the option control statement.
KFPL31005-E R
Number of columns in input file not equal to table columns, line=aa....aa
- The number of input data rows at line aa....aa does not match the number of rows to be stored.
- aa....aa: Line number
- S: Outputs the error message to the error information file.
- P: Correct the data of the relevant row number in the input data file.
- If the data includes (00)16, this appears as a space when viewed in a text editor, so that the data can be viewed correctly. However, HiRDB considers (00)16 to represent the end of data, and it may handle it as a column count mismatch. Check the data contents using a binary editor.
- If the data loading target is a FIX table in which a reserved column has been defined, and there is reserved column data in the input data file, delete the reserved column data from the input data file.
KFPL31006-E R
Invalid null value, line=aa....aa, column=bb....bb
- Invalid null value was specified for the input data on line aa....aa, column bb....bb.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- S: Outputs the error message to the error information file.
- O: Correct the data on the indicated line of the input data file.
KFPL31007-E R
Invalid input record for cluster key sequence, line=aa....aa
- The input records at line aa....aa are not sorted in order of cluster key values.
- aa....aa: Line number
- S: Outputs the error message to the error information file.
- O: Correct the data on the indicated line of the input data file.
- If it is difficult to rearrange the data in cluster key order, the data can be stored without checking the order by specifying the -x option. However, with this storage method, there is no cluster key benefit.
KFPL31008-E R
Key duplication error occurred, line=aa....aa[bb....bb]
- The input data key values in line=aa....aa are duplicate. If the message No output for error data is displayed, the work buffer for the creation of an error data file is too small.
- aa....aa: Line number
- bb....bb: (No output for error data)
- S: Resumes processing after outputting an error message to the error information file.
- O: Correct the data associated with the indicated line number in the input data file and re-execute the command. If a message No output for error data is output, error data is not output to the error data file. This problem can be resolved by specifying a large enough size for the work buffer for the creation of an error data file and by re-executing the command.
KFPL31009-E R
Invalid partitioning key value, line=aa....aa
- Input data contains a column value at line aa....aa that does not satisfy the partitioning storage condition for a table to be created.
- aa....aa: Line number
- S: Outputs the error message to the error information file.
- O: Correct the data on the indicated line of the input data file.
KFPL31010-E R
Invalid row length, line=aa....aa
- The length is invalid of the row data in row number aa....aa in the input file.
- Binary-format file:
The row length or column offset is invalid in the binary-format file output by pdrorg.
- Fixed-size data format file:
Data cannot be input at the row length specified in the column structure information file.
- aa....aa: Row number
- S: Outputs the error message to the error information file and terminates processing.
- O:
- Binary-format file:
Correct the row length or column offset in the row data.
- Fixed-size data format file:
Correct the column structure information file so that the column information matches the input data length.
- In either file format, the intended file may not be specified as the input file; in such a case, specify the correct file and re-execute the command.
KFPL31011-E R
Invalid LOB format, line=aa....aa, column=bb....bb
- Specification was invalid for LOB column line = aa....aa, column = bb....bb.
- Length of the LOB input file name specified in the input file for the LOB column structure base table was invalid.
- LOB data length specified in the LOB column input file was invalid.
- Invalid EOF was detected when acquiring 4-byte LOB data from the LOB column input file or when acquiring the specified LOB data.
- aa....aa: Row number
- Row number in the input data file. When a LOB column input file is used, this is the number of the data item in the LOB column input file that resulted in the error.
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- S: Outputs information to the error information file and terminates processing.
- O:
- Separate file is provided for each item of LOB data:
Check that the length of the LOB input file name corresponding to the row number in the input data file for the LOB column structure base table is greater than 0 and not greater than 1023. If the length is invalid, correct it. If the length of the file name is correct, change the specification to the absolute path name.
When EasyMT is being used, check that the length of the file name is greater than 0 and not greater than 17. If the length is invalid, correct it.
- LOB column input file is provided:
Check that the length of the LOB data in the LOB column input file corresponding to the row number in the input data file for the LOB column structure base table is greater than 0 and not greater than the defined length and that the specified LOB data exists. If there is an error, correct it.
KFPL31012-E R
Specified LOB file not found, line=aa....aa
- LOB input file specified in line aa....aa cannot be found.
- aa....aa: Line number
- S: Outputs the message to the error information file and terminates processing.
- O: Check that the LOB input file is on the specified path.
KFPL31013-E R
LOB data too long, line=aa....aa
- Length of the LOB data for row aa....aa specified in the table definition was greater than the defined LOB column length.
- Separate file is provided for each item of LOB data:
- The LOB input file data specified for row aa....aa of the input data file for the LOB column structure base table exceeded the defined length.
- LOB column input file is provided:
- LOB data in the LOB column input file corresponding to row aa....aa of the input data file for the LOB column structure base table exceeded the defined length.
- aa....aa: Row number
- Row number in the input data file. When a LOB column input file is used, this is the number of the data item in the LOB column input file that resulted in the error.
- S: Outputs information to the error information file and terminates processing.
- O:
- Separate file is provided for each item of LOB data:
Correct the LOB input file for the indicated row that was specified in the input data file for the LOB column structure base table.
- LOB column input file is provided:
Correct the LOB data for the indicated row in the LOB column input file.
KFPL31014-E R
LOBMID file conflicted with LOB data file, line=aa....aa
- Information specified for the LOB column structure base table obtained from the LOB middle file (LOBMID file) contradicts the information specified for the LOB column input file:
- NULL was specified for the LOB column structure base table, but data with a length of at least 1 byte was specified for the LOB column input file.
- Default value was specified for the LOB column structure base table, but data with a length of at least 1 byte was specified for the LOB column input file.
- aa....aa: Row number
- Row number in the input data file
- S: Outputs information to the error information file and terminates processing.
- O: Check the specifications for the LOB column at the row number of the input data file of the LOB column structure base table, correct the LOB data at the row number of the LOB column input file that resulted in the error, then re-execute the command.
KFPL31015-E R
Unmatched LOB data count, line=aa....aa
- The number of data items of the input data file of the LOB column structure base table does not match aa....aa the number of LOB data data items in the LOB column input file.
- aa....aa: Row number
- Data number that resulted in the error in the LOB column input file
- S: Outputs the error message to the error information file.
- O: To use a LOB column input file, as many data items are required in the LOB column input file as there are rows in the input data file for the LOB column structure base table. Check the KFPL00703-I message for the number of data items created during creation of the LOB column structure base table and compare that number with the data number displayed in this message. Make sure that the number of data items in the input data file for the LOB column structure base table matches the number of LOB data items in the LOB column input file, then re-execute the command.
KFPL31016-E R
Invalid parameter, line=aa....aa, column=bb....bb, code=cc [dd....dd]
- The input parameter for the constructor function that generates the values to be stored in a column of abstract data type is invalid. If the message No output for error data is displayed, the data length for the last line of data in the input data file is too short.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- cc: Logical error number
- For the logical error numbers, see the HiRDB Version 9 Command Reference.
- dd....dd: (No output for error data)
- S: Resumes processing after outputting an error message to the error information file.
- O:
- By referring to the logical error details, correct the indicated data in the input data file that was specified as an input parameter for the function and re-execute the command.
- If the message No output for error data is displayed, not all error data has been output to the error data file. This problem can be resolved by correcting the data in the last line of the input data file and re-executing the command.
KFPL31017-E R
Specified LOB file permission denied, line=aa....aa
- The user does not have the access privilege to the LOB input file specified in row aa....aa of the data.
- aa....aa: Row number
- S: Outputs the error message to the error information file, and then continues processing.
- O: To enable the HiRDB administrator to read the file, grant the access privilege to the LOB input file.
KFPL31018-E R
PLUGIN function error occurred, line=aa....aa, reason="bb....bb", column="cc....cc" [dd....dd]
- The value to be stored in a column of abstract data type, using a plug-in-provided function, is invalid. If the message No output for error data is displayed, the work buffer for the creation of an error data file is too small.
- aa....aa: Line number
- bb....bb: Description of the error detected by a plug-in-provided function
- cc....cc: Column name
- dd....dd: (No output for error data)
- S: Resumes processing after outputting an error message to the error information file.
- O: Correct the indicated data in the input data file by referring to the error message.
- If the message No output for error data is displayed, error data is not output to the error data file. This problem can be resolved by specifying a large enough size for the work buffer for the creation of an error data file and by re-executing the command.
KFPL31019-E R
Invalid number of element, line=aa....aa, column=bb....bb
- The specification of the element count for the repetition column in line=aa....aa, column=bb....bb contains an error.
- aa....aa: Line number
- bb....bb: Column number
- Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.
- S: Resumes processing after outputting an error message to the error information file.
- O: Determine whether the element count for the repetition column is correct. In addition, check whether the column data in the input data file is error-free. If the element count is invalid or the column data contains an error, correct the file contents and re-execute the command.
KFPL31020-E R
Invalid enclose character detected, line=aa....aa, offset=bb....bb
- An invalid enclosed character was detected at byte bb....bb from the beginning of line aa....aa in the data.
- aa....aa: Row number
- bb....bb: Position where the invalid enclosed character was detected
- S: Outputs the error message to the error information file, and then terminates processing.
- O: For an input data file in the extended DAT format, specify two consecutive values when handling the same value as the enclosed character with data.
KFPL31021-E R
Invalid file path format, line=aa....aa, column=bb....bb
- The specification format for the input file in column bb....bb of row aa....aa is invalid.
The file name length, which is a combination of the path name specified in the column structure information file and the path name in the input data file, is invalid. - aa....aa: Row number
- bb....bb: Column number
- The column number indicates the position from the first data item in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not input by means of a skipdata statement.
- S: Outputs an error message to the error information file.
- P:
- When preparing a file by data item for XML-type parameter attributes, make sure that the length of the file name, which is a combination of the path name specified in the column structure information file and the path name in the input data file, is greater than 0 but less than or equal to 1,023. If there are any errors, correct them.
- If the length of the file name is valid, correct the format of the absolute path specification.
KFPL31022-E R
Specified file not found, line=aa....aa, column=bb....bb
- No files are specified in column bb....bb of row aa....aa.
- aa....aa: Row number
- bb....bb: Column number
- The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.
- S: Outputs an error message to the error information file.
- P: Check whether the specified input file exists in the specified path.
KFPL31023-E R
File data too long, line=aa....aa, column=bb....bb
- The data length of the file specified in column bb....bb of row aa....aa exceeds the defined length specified for table definitions.
- aa....aa: Row number
- bb....bb: Column number
- The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.
- S: Outputs an error message to the error information file.
- P: Correct the file that was specified in the input file.
KFPL31024-E R
Specified file permission denied, line=aa....aa, column=bb....bb
- You do not have access privileges to the file specified in the data in column bb....bb of the aa....aa row.
- aa....aa: Row number
- bb....bb: Column number
- The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.
- S: Outputs an error message to the error information file, and continues processing.
- P: Grant administrative access privileges for the file so that it can be read.
KFPL31090-E R
Input data too long, line=aa....aa, column=bb....bb [,element=cc....cc]
- The input data length of line=aa....aa, column=bb....bb (if an element has been output, the repetition column element cc....cc) exceeds the defined column length for the table definitions.
- For data loading:
The error data and handling data are not stored.
- For file partitioning:
However, data is not output to the divided-input data file.
- aa....aa: Row number
- bb....bb: Column number
- cc....cc: Element number
- S: Outputs an error message to the error information file, and continues processing.
- O: Correct the data that exceeded the definition length, and then re-execute pdload.
KFPL31090-W R
Input data too long, line=aa....aa, column=bb....bb[,element=cc....cc]
- The length of the input data in line=aa....aa, column=bb....bb (and repetition column element cc....cc if element is displayed) exceeds the column definition length at the time the table was defined.
- For data loading:
The data is stored by truncating the data portion that exceeds the defined length.
- For file partitioning (creation of a partitioning input data file):
The data is output to the partitioning input data file.
- aa....aa: Line number
- bb....bb: Column number
- cc....cc: Element number
- S: Outputs an error message to the error information file and continues processing.
- O: Check whether any problems resulted from truncating the data portion that exceeds the defined length. If there is a problem, modify the data that exceeds the defined length, and then re-execute pdload.
KFPL33000- L+S
Pdrbal started, table=aa....aa."bb....bb", execmode=cc....cc
- Rebalancing of table aa....aa."bb....bb" has begun.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Operation mode:
- share: Shared mode
- exclusive: Exclusive mode
- S: Continues processing.
KFPL33001- L+S
Pdrbal terminated, return code=aa
- The pdrbal processing terminated with return code aa.
- aa: Return code.
- 0: Normal termination (all data was rebalanced)
- 4: Normal termination (some data was not rebalanced)
- 8: Abnormal termination
- S: Terminates processing.
- O:
- Return code is 4:
Re-execute pdrbal.
- Return code is 8:
Correct the error by referring to the error message that is output to standard output or the message log file, and re-execute pdrbal.
KFPL33002- L+S
Report file aa....aa assigned
- Processing results file aa....aa has been created.
- aa....aa: Processing results file name
- If the length of the execution result file name exceeds 129 characters, the last 129 characters of the execution result file name are output.
- S: Continues processing.
KFPL33003-l L+S
Activation of dictionary information completed, status=aa....aa
- Dictionary information was activated.
- aa....aa: Dictionary information activation timing:
- START:
- At the time of rebalancing startup:
- If an error occurs after this message has been output, the execution status of pdrbal is rebalancing.
- END:
- At the time of rebalancing termination:
- If an error occurs after this message has been output, rebalancing has been completed, and it is not necessary to re-execute pdrbal.
- S: Continues processing.
KFPL33004- L+S
aa....aa rows bb....bb, table=cc....cc."dd....dd"
- aa....aa rows were processed during rebalancing of table cc....cc."dd....dd".
- aa....aa: Number of rows
- bb....bb:
- processing: Processed
- cc....cc: Authorization identifier
- dd....dd: Table identifier
- S: Continues processing.
KFPL33005- L+S
Pdrbal stopped at execstop, table=aa....aa."bb....bb"
- Rebalancing of table aa....aa."bb....bb" was halted by specification of the execstop statement.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
KFPL33500-E E+L
Unable to specify "aa....aa" in this case
- Cannot specify the following control statements in the control information file when "aa....aa" is specified in the command line:
- "aa....aa" is -k share or -k exclusive:
- index statement
- idxwork statement
- sort statement
- "aa....aa" is -k exclusive:
- option statement (check_itv operand)
- aa....aa: Option name (-k share or -k exclusive)
- S: Terminates processing.
- O:
- "aa....aa" is -k share:
Respecify the command line or the control information file, and then re-execute.
- "aa....aa" is -k exclusive:
Delete the check_itv operand or change the command line to -k share and re-execute.
KFPL33501-E E+L
Unable to execute pdrbal due to aa....aa table
- pdrbal cannot be executed for table aa....aa.
- aa....aa: Table type:
- non base:
- Table other than a base table
- non rebalance:
- Table other than a rebalancing table
- ADT:
- Table in which one of the following abstract data types is specified:
- User-defined type
- One of the following abstract data types provided by a plug-in:
Has a supertype
Has an abstract data type for the attribute
Attribute is BLOB-type but has no unload function
- S: Terminates processing.
- O: Stop execution of pdrbal.
KFPL33502-E E+L
Unable to execute pdrbal without aa....aa privilege
- Access privilege aa....aa has not been granted for the table that is to be processed.
- aa....aa: Access privilege type:
- select: SELECT privilege
- insert: INSERT privilege
- delete: DELETE privilege
- S: Terminates processing.
- O: Have the table owner grant the executor the access privilege for the table to be processed, and re-execute pdrbal.
KFPL33503-E E+L
Unable to execute pdrbal command without addition of RDAREA, table=aa....aa."bb....bb"
- pdrbal cannot be executed without addition of an RDAREA.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: Check that the name of the table to be rebalanced is correct. If it is, add an RDAREA for the rebalancing table and re-execute pdrbal.
KFPL33504-E E+L
Table aa....aa during execution of pdrbal, table_name=bb....bb."cc....cc"
- The rebalancing table was deleted or the table definition was changed during execution of pdrbal.
- aa....aa: Reason code:
- dropped: Rebalancing table was deleted.
- changed: Rebalancing table was changed (or deleted, or created).
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Terminates processing.
- O: Based on the reason code, check the definition of the target table.
KFPL33505-E E+L
Activation of dictionary information failed
- Activation of dictionary information failed.
- S: Terminates processing.
- O: Correct the error based on the error message that was output before this message, and re-execute pdrbal.
KFPL33506-E E+L
Unable to execute pdrbal command because of NONDIV_IDX defined, index_name=aa....aa."bb....bb"
- pdrbal cannot be executed because a non-partitioning key index is defined in the rebalancing table.
- aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Terminates processing.
- O: Delete the non-partitioning key index and re-execute pdrbal.
KFPL33507-E E+L
Unable to recompile routine, type=aa....aa, name="bb....bb"."cc....cc", error_sql_no=dd....dd, err_sql=ee....ee
- Recompilation of the routine failed.
- aa....aa: Routine type:
- PROCEDURE: Procedure
- FUNCTION: Function
- bb....bb: Schema name
- cc....cc: Routine identifier
- dd....dd: Number indicating the SQL procedure statement in the routine that caused the error
- For the numbers that indicate SQL procedure statements, see ERR_SQL_NO in GET DIAGNOSTICS in the HiRDB Version 9 SQL Reference.
- ee....ee: SQL procedure statement in the routine that caused the error
- For SQL procedure statements, see ERR_SQL in GET DIAGNOSTICS in the HiRDB Version 9 SQL Reference.
- S: Terminates processing.
- O:
- Take appropriate action based on ERR_SQL_NO, ERR_SQL, and the message that was output immediately before this message, and recompile the procedure or function using ALTER PROCEDURE or ALTER ROUTINE. (Re-executing the rebalancing utility will not recompile the procedure or function.)
- If START is displayed for STATUS in the KFPL33003-I message that was output before this message, take the above action, and then re-execute the rebalancing utility. If END is displayed for STATUS, there is no need to re-execute (an attempt to re-execute will cause an error).
KFPL33508-E E+L
Unable to execute pdrbal using replicated RDAREA, table=aa....aa. "bb....bb"
- Cannot execute pdrbal because a replica RDAREA is defined in the target table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- O: When executing pdrbal, delete all replica RDAREAs defined in the target table.
KFPL33509-W E+L
Execution time of pdrbal for COMPRESSED table aa....aa."bb....bb"become long, because execmode is share
- When rebalancing a compressed table in shared mode, the time required for rebalancing can be longer than when there are compressed columns, due to the expansion and compression performed during data transfer.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Continues processing.
- O: If you want to shorten the rebalancing execution time, use the pdcancel command to forcibly terminate the rebalancing utility while it is executing, and then re-execute the rebalancing utility in exclusive mode. For details about the pdcancel command, see the manual HiRDB Version 9 Command Reference.
KFPL50000-I L+S
Pdconstck started, func=aa....aa, table=bb....bb."cc....cc"[, constraint=dd....dd."ee....ee"] [, generation=fff]
- The integrity check utility was started.
If the constraint type is check, , constraint=ee....ee."ff....ff" is output. If the HiRDB Staticizer Option is installed, , generation=hhh is output. - aa....aa: Facility
- check: Integrity check facility
- set: Facility to force the setting of check pending status (forced setting)
- release: Facility to force the setting of check pending status (forced release)
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- dd....dd: Authorization identifier (displayed on a constraint-by-constraint basis)
- ee....ee: Generation to be processed
- fff: Generation number (displayed if HiRDB Staticizer Option is installed)
- all: All generations
- 0 to 10: Specified generation
- cur: Generation of the current RDAREA
- S: Continues processing.
KFPL50001-I L+S
Pdconstck terminated, return code=a
- Processing of the integrity check utility terminated.
- a: Return code
- 0: Normal termination
- The integrity check found no row data with a constraint violation.
- 4: Normal termination
- The integrity check found row data with a constraint violation; or the processing of the integrity check utility was terminated because the number of key values indicating a constraint violation exceeded the upper limit.
- 8: Abnormal termination
- S: Terminates processing.
- O:
- Return code 8:
- Refer to the error message that is output to standard error or to the message log file, resolve the error, and then re-execute the command.
- Return code 4:
- Refer to the row data that produced the constraint violation and revise the integrity of the constraint. If necessary, re-execute the command.
- To verify the check pending status of the table, refer to the processing results of the integrity check utility or of the database condition analysis facility.
KFPL51200-E E+L
No constraint defined, table=aa....aa.bb....bb
- A reference constraint (foreign key) or a check constraint is not defined on the specified table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- P: Revise the table name, and then re-execute the command.
KFPL51201-E E+L
Unable to execute aa....aa command, due to lack of privilege
- Command aa....aa cannot be executed because the user has neither of the following privileges on the table:
- DBA privilege
- Owner of the table
- aa....aa: Command name
- S: Terminates processing.
- P: Take one of the following actions:
- Re-execute the command as a user with DBA privilege.
- Re-execute the command by granting the DBA privilege to the user.
- Re-execute the command by specifying a table owned by the user.
KFPL51202-E E+L
Replica RDAREA insufficient, table=aa....aa."bb....bb"
- The utility cannot be executed because there is no replica RDAREA associated with the original RDAREA of table aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Terminates processing.
- Action
- Use the pdrdrefls command to check the RDAREA associated with the indicated table. Next, use the pddbls command to verify that the RDAREA associated with the table satisfies the conditions indicated below, and then re-execute the utility:
- The storage RDAREA does not contain both an RDAREA to which the inner replica facility is applied and one to which it is not applied.
- The numbers defined for replica RDAREAs match.
- Generation numbers for replica RDAREA definitions are consistent.
KFPL51203-E E+L
Check pending status conflicts, table=aa....aa.bb....bb, constraint type=cc....cc
- The check pending status of the dictionary table is inconsistent with the check pending status of the constraint.
- If the constraint type is REF:
- The value specified for the table in SQL_TABLES (CHKPEND column) differs from the value specified for the table in SQL_REFERENTIAL_CONSTRAINTS (CHKPEND column).
- If the constraint type is CHECK:
- The value specified for the table in SQL_TABLES (CHKPEND2 column) differs from the value specified for the table in SQL_CHECKS (CHKPEND2 column).
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc: Constraint
- REF: Reference constraint
- CHECK: Check constraint
- S: Terminates processing.
- Action
- Use the integrity check utility with the -k set parameter (pdconstck -k set) to forcibly set the table into check pending status, and then use the check parameter (pdconstck -k check) to perform a constraint integrity check.
KFPL90001-I S
Process aa....aa started. yyy/mm/dd,hh:mm:ss
- The aa....aa processing has started.
- aa....aa: Processing:
- rorg: Reorganization
- yyyy/mm/dd: Execution start date
- hh:mm:ss: Execution start time
- S: Continues processing.
KFPL90002-I S
Process aa....aa ended. return code=bb,yyy/mm/dd,hh:mm:ss
- The aa....aa processing has terminated.
- aa....aa: Processing:
- rorg: Reorganization
- bb: Return code
- 0: Normal termination (all table reorganization was completed)
- 4: Normal termination (table is being reorganized)
- 8: Error termination (recovered from a backup)
- 12: Error termination (recovery from a backup failed)
- yyy/mm/dd: Execution termination date
- hh:mm:ss: Execution termination time
- S: Terminates processing.
- O:
- Return code is 4:
The time specified in the -m option of pdrorg was not sufficient and the KFPL91101-W message was output; re-editing was not performed. Increase the specification value and re-execute.
- Return code is 8 or 12:
For the error detail, check the contents of the execution information file displayed in KFPL90003-E. Correct the error and take appropriate action based on the execution status indicated by the KFPL90021-I to KFPL90028-I progress messages that are output.
KFPL90003-E E
Eliminating the cause of the error, refer to executed information file="aa....aa"
- The error shown in the execution information file occurred.
- aa....aa: Execution information file name
- S: Terminates processing.
- O: Check the error detail in the execution information file and correct the error.
KFPL90010-I S
Process aa....aa bb....bb/cc....cc ended.table name=dd....dd
- The aa....aa processing, which is number bb....bb out of a total of cc....cc, has terminated.
- aa....aa: Processing:
- rorg: Reorganization
- bb....bb: Number of completed processes
- cc....cc: Total number of processes
- dd....dd: Name of the processed table
- S: Continues processing.
KFPL90021-I S
DB hold step ended
- Database shutdown has terminated.
- S: Continues processing.
KFPL90022-I S
Before backup step ended
- The backup before processing has been completed.
- S: Continues processing.
KFPL90023-I S
aa....aa step started
- The aa....aa processing has started.
- aa....aa: Processing:
- Reorganize: Reorganization
- S: Continues processing.
KFPL90024-I S
aa....aa step ended
- The aa....aa processing has been completed.
- aa....aa: Processing:
- Reorganize: Reorganization
- S: Continues processing.
KFPL90025-I S
After backup step ended
- The backup after processing has been completed.
- S: Continues processing.
KFPL90026-I S
DB release step ended
- Database shutdown release has been completed.
- S: Continues processing.
KFPL90027-I S
DB stop process started
- The database is being stopped for error recovery.
- S: Continues processing.
KFPL90028-I S
Recover step started on aa....aa error
- Database recovery from the backup file is being started.
- aa....aa: Processing:
- rorg: Reorganization
- S: Continues processing.
KFPL90029-I S
Recover step ended on aa....aa error
- Database recovery from the backup file has terminated.
- aa....aa: Processing:
- rorg: Reorganization
- S: Continues processing.
KFPL90030-I S
DB started process ended
- Database startup processing has been completed.
- S: Continues processing.
KFPL90101-I R
aa....aa
- Outputs the command line during HiRDB command execution.
- aa....aa: Command line during pdrorg execution
- S: Continues processing.
KFPL90102-I R
aa....aa
- Displays one control statement line during pdrorg execution.
- aa....aa: Control statement during pdrorg execution
- S: Continues processing.
KFPL91000-I E
Usage:aa....aa[-m time] -k func_name
- Displays the specification format for the aa....aa command.
- aa....aa: Name of the command that was to be executed
- S: Terminates processing.
- O: Correct the command line error and re-execute.
KFPL91001-E E
Mandatory specification missing in command line
- A required option is not specified on the command line.
- S: Terminates processing.
- O: Specify the required option for the command and re-execute.
KFPL91002-E E
Invalid aa....aa option
- Option aa....aa is invalid.
- aa....aa: Invalid option
- S: Terminates processing.
- O: Specify the option correctly and re-execute.
KFPL91003-E E
Invalid value of aa....aa option
- Option aa....aa's specification value is invalid.
- aa....aa: Option
- S: Terminates processing.
- O: Specify the option correctly and re-execute.
KFPL91004-E E
Invalid format exists in command line
- The format of the command line for the executed utility is invalid.
- S: Terminates processing.
- O: Correct the command line and re-execute.
KFPL91100-E E
System call error, func=aa....aa, errno=bb....bb
- An error occurred during the processing of a HiRDB system function.
- aa....aa: Name of the HiRDB system function
- bb....bb: Error code
- S: Terminates processing.
- O: Correct the error based on the error code in this message and the error messages that are output before and after this message.
KFPL91101-W E
Unable to execute aa....aa due to little value of -m option
- The aa....aa processing cannot be executed because the value specified in the -m option is too small.
- aa....aa: Processing:
- rorg: Reorganization
- S: Terminates processing.
- O: Specify an appropriate value in the -m option and re-execute.
KFPL91102-E E
aa....aa process already executed
- Execution of the aa....aa command is already underway.
- aa....aa: Name of the command being executed
- S: Terminates processing.
- O: If necessary, wait for the command being executed to terminate, then re-execute.
KFPL91103-E E
Insufficient memory on PROCESS, size=aa....aa, part=bb....bb, code=cc....cc
- A memory shortage occurred.
- aa....aa: Insufficient memory size (in bytes)
- bb....bb: Part number
- cc....cc: Part code
- S: Terminates processing.
- O: Wait for other programs that are using a significant amount of memory to terminate, then re-execute.
KFPL91104-E E
Unable to aa....aa without bb....bb privilege
- The bb....bb access privilege for the aa....aa processing has not been granted.
- aa....aa: Name of the command to be executed
- bb....bb: Access privilege
- DBA: DBA privilege
- S: Terminates processing.
- O: Obtain the necessary access privilege and re-execute.
KFPL91105-E E
aa....aa invalid
- The authorization identifier or password specified by an environment variable is invalid. Or, the password entered in response to an input prompt message is invalid.
- aa....aa: Error item:
- Auth_id: Authorization identifier
- Password: Password
- S: Terminates processing.
- O: Take one of the following actions, depending on the error item:
- Auth_id displayed for aa....aa:
- Correct the PDUSER environment variable and re-execute.
- Password displayed for aa....aa:
- Correct the PDUSER environment variable and re-execute. Or, if a password was entered in response to the input prompt message, re-execute the command and ensure that the correct password is entered.
- In the case of Windows, make sure that the character string for the specified authorization identifier or password is not enclosed in single quotation marks (') in the command prompt.
- Correct specification example: PDUSER="root"/"root"
KFPL91106-E E
aa....aa error occurred, file=bb....bb
- A file access error occurred.
- aa....aa: Processing during which the error occurred:
- Open: Opening
- Read: Loading
- Write: Writing
- Delete: Deleting
- Close: Closing
- Lock: Locking
- bb....bb: File name (final portion of path name)
- S: Terminates processing.
- O: Correct the error based on the messages that are output before and after this message.
KFPL91107-E E
System call error, func=aa....aa, errno=bb....bb
- A file access error occurred.
- aa....aa: Name of the system function in which the error occurred
- bb....bb: Error number returned by the system function (errno)
- S: Terminates processing (may continue processing in the case of a close error).
- O: Correct the error by referring to errno.h and the error number (errno) in the reference manual that describes the applicable function, and re-execute.