KFPH00031-E L
RDAREA "aa....aa" not initialized, file=bb....bb, reason code=cc
- HiRDB file bb....bb in RDAREA "aa....aa" has not been initialized.
- aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.
- cc: Reason code:
- 1: Reinitialization of RDAREA not completed
- 2: Deletion of RDAREA not completed
- 3: Integration of the RDAREA is not complete.
- 10 to 19: RDAREA management information not set
- S:
- For user RDAREA:
- Shuts down the corresponding RDAREA and resumes processing.
- For any other RDAREA:
- Terminates processing. However, if this message is output when a HiRDB was being executed, continues processing by closing the affected RDAREA.
- Action
- Check the cause of the error, as listed below, correct the RDAREA, and then re-execute the processing:
- This RDAREA cannot be used because the following processes of the database structure modification utility terminated abnormally:
Reinitialization of the RDAREA
Deletion of the RDAREA
Matching of the RDAREAs
- Recovery of the RDAREA failed.
- HiRDB file system areas are mismatched.
- Synchronization was lost between HiRDB file system area containing the master directory RDAREA or the data dictionary RDAREA and HiRDB file system area where the error occurred.
- The contents of the RDAREA are damaged.
- If none of the above applies, contact the customer support center.
KFPH00035-W L
Global buffer pool not allocated for RDAREA aa....aa
- Global buffer pool is not allocated to the RDAREA.
- aa....aa: RDAREA name
- S: Places the RDAREA on CLOSE status and resumes processing.
- Action
- Allocate a global buffer pool for the RDAREA with the pdbuffer operand of the system common definition.
KFPH00110-I L+S
aa....aa command completed
- Processing of HiRDB command aa....aa has been completed.
- aa....aa: Name of command
- S: Resumes processing.
KFPH00115-I L+S
aa....aa command failed
- HiRDB command aa....aa cannot be processed.
- aa....aa: Name of command
- S: Ignores the entered command and terminates processing.
- However, some processing might be executed in the following cases:
- If the pdhold command with the -c option or the pdrels command with the -o option is specified, processing of the command might be only partially executed.
- If multiple RDAREAs or servers are specified, command processing might execute on only some of the RDAREAs or servers.
- For a shared RDAREA, command processing might execute on only some of the servers.
- Action
- The following are the administrator's actions corresponding to system actions 1 to 3 above:
- After taking corrective action based on the error message that was output immediately before this message, use the pddbls command to check the status of the RDAREAs, and then re-execute the command.
- If the pdbufmod command was being executed, after taking corrective action based on the error message that was output immediately before this message, use the pdbufls command to check the status of the global buffer, and then re-execute the command.
If a command other than the pdbufmod command was being executed, after taking corrective action based on the error message that was output immediately before this message, use the pddbls command to check the status of the RDAREAs, and then re-execute the command.
- After taking corrective action based on the error message that was output immediately before this message, use the pddbls -m command to check the status of shared RDAREAs on all back-end servers, and if there are any inconsistencies, make sure that the RDAREAs have the same status, and then re-execute the command.
KFPH00130-I L+S
RDAREA aa....aa,RDAREA=bb....bb
- The specified RDAREA was shut down, released from shutdown, opened, closed, had updates frozen or unfrozen, or was changed to the current RDAREA.
- aa....aa: Type of RDAREA processing:
- held: RDAREA was shut down (access prohibited)
- held(inq): RDAREA was shut down (referencing permitted)
- held(bu i): Reference-possible backup hold
- held(bu iw): Reference-possible backup hold (update WAIT mode)
- held(bu): Updatable backup-hold
- held(bu w): Updatable backup-hold (WAIT mode)
- held(sync): Synchronization hold
- held(org): Online reorganization hold
- released: RDAREA was released from shutdown status
- opened: RDAREA was opened
- closed: RDAREA was closed
- freezed: Updating of RDAREA is frozen
- unfreezed: Update freeze of the RDAREA was cancelled
- current changed: RDAREA was changed to the current RDAREA
- bb....bb: RDAREA name
- S: Resumes processing.
KFPH00131-E L+S
pdhold command failed due to RDAREA already held, RDAREA="aa....aa"
- The indicated RDAREA cannot be shut down by the command, because it is already on error shutdown status.
- aa....aa: RDAREA name
- S: Ignores this RDAREA processing and continues processing.
- O: Check the RDAREA status with the pddbls command. Eliminate the cause of the RDAREA being placed on error shutdown status, release the RDAREA from shutdown status, then re-execute the command.
KFPH00132-E L+S
aa....aa command failed due to HiRDB error, bb....bb=cc....cc code=ddd[, server = ee....ee]
- HiRDB command aa....aa cannot be processed, because a HiRDB server error occurred.
- aa....aa: Command name
- bb....bb: Invalid specification (one of the following is displayed):
- RDAREA
- server
- buffer pool
- index
- cc....cc: Name of RDAREA, server, global buffer, or index (if the name cannot be obtained, ***** is displayed)
- ddd: Error code:
- -2: Access error in dictionary RDAREA
- -4: Memory shortage at the communication destination
- -7: PRC communication error
- -20: Reinitialization of RDAREA not completed
- -21: Deletion of RDAREA not completed
- -22: Page length longer than the buffer length
- -23: Integration of RDAREA not completed
- -24: A falsification prevented table with incomplete data was found in the applicable RDAREA
- ee....ee: Shared RDAREA runtime server name
- This is displayed when an error occurs in a shared RDAREA.
- The server name is output only when the error code is -4 or -7. However, if server is output in bb....bb, nothing is output here. In addition, nothing is output if the error code is -2, which indicates an error in the dictionary server.
- S:
- RDAREA:
- Invalidates the applicable RDAREA processing and continues processing.
- Server:
- Invalidates the server process causing the error and continues processing.
- Global buffer:
- Invalidates the applicable global buffer process and continues processing.
- Index:
- Invalidates the applicable index process and continues processing.
- O:
- Error code is -24:
- Use the database reorganization utility (pdrorg) to complete the reloading of falsification prevented tables that are in reload-not-completed data status. Then, use the pdrels command to cancel the hold and resume work.
- Error code is not -24:
- Refer to the message output to the message log file, eliminate the cause of the error, and then re-execute the command.
- When a shared RDAREA is used, and server is output in bb....bb or the server name is displayed:
- Refer to the message output to the message log file, remove the cause of the error from the relevant server, and re-execute the command.
KFPH00133-E L+S
RDAREA release failed due to not recovered, RDAREA="aa....aa"
- The error shutdown could not be released because RDAREA aa....aa that was shut down due to the error was not recovered.
Or, synchronization hold RDAREA aa....aa could not be released because it was updated with invalid data. - aa....aa: RDAREA name
- S: Invalidates the command's processing for this RDAREA and continues processing.
- Action
- Use the pddbls command to check the status of the RDAREA. If the RDAREA is on error shutdown status, take one of the following actions to release its error shutdown status:
- Use the pdrstr command to recover the RDAREA.
- Use the pdmod command to reinitialize the RDAREA (note that all data in the RDAREA will be deleted).
- Update using a duplicate RDAREA that has valid data in the inner replica group for synchronization holding when using the inner replica facility, and then re-execute the command.
KFPH00134-I L+S
aa....aa command completed, server = bb....bb
- Operation command aa....aa processing is complete on server bb....bb.
- aa....aa: Command name
- bb....bb: Server name
- S: Terminates processing.
KFPH00135-E L+S
aa....aa command failed, server = bb....bb
- Operation command aa....aa processing could not be performed on server bb....bb.
- aa....aa: Command name
- bb....bb: Server name
- S: Invalidates processing of the server where the error occurred, and then continue processing.
- Action
- Refer to the output message, eliminate the cause of the error, and then re-execute this command.
KFPH00141-E L+S
aa....aa command failed due to specified name invalid, RDAREA=bb....bb
- HiRDB command aa....aa could not be processed because the specified RDAREA name is invalid.
Another possibility is that the specified RDAREA is not subject to processing by HiRDB command aa....aa. - aa....aa: Name of command
- bb....bb: RDAREA name
- S: Invalidates the corresponding RDAREA processing and resumes processing.
- Action
- Specify the correct RDAREA name and re-execute the command. If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.
- Alternatively, re-execute the command without the RDAREA that is not able to be processed. For details about the RDAREAs that can be processed by HiRDB command aa....aa, see the manual HiRDB Version 9 Command Reference.
KFPH00142-E L+S
aa....aa command failed due to specified name not found, bb....bb=cc....cc[, server = dd....dd]
- Specified RDAREA name, server name, buffer pool name, or table name not found. HiRDB command aa....aa cannot be processed.
- aa....aa: Name of command
- bb....bb: Invalid specification:
{ RDAREA |server |buffer pool |table }
- cc....cc: Name of RDAREA, server, buffer pool, or table
- dd....dd: Shared RDAREA runtime server name
- This is displayed when an error occurs in a shared RDAREA during execution of the pddbls command.
- S: Performs the following processing for cc....cc.
- If an RDAREA, invalidates the corresponding RDAREA processing and resumes processing.
- If a server, invalidates the server processing resulting in the error and resumes processing.
- If a buffer pool, invalidates the corresponding buffer pool processing and resumes processing.
- For a table name, processing is interrupted.
- O: Specify the correct RDAREA name, server name, buffer pool name, or table name, and then re-execute the command. If multiple RDAREA names are specified and ALL is specified as the second or subsequent RDAREA name, specify ALL by itself, and then re-execute the command.
KFPH00145-E L+S
aa....aa command failed due to HiRDB error, code=bbb[, server = cc....cc]
- A HiRDB system error occurred and HiRDB command aa....aa cannot be processed.
- aa....aa: Name of command
- bbb: Error code:
- -4: Memory shortage
- -5: Lock error
- -6: Lock release error
- -8: RDAREA information management block maintenance error
- -9: Transaction startup error
- -10: Information collection error in HiRDB file system area
- -11: Object cache not released
- -12: Lock of object cache disabled
- -13: Unlock of object cache disabled
- cc....cc: Shared RDAREA runtime server name
- This is displayed when an error occurs in a shared RDAREA.
- S: Terminates processing.
- O: Eliminate the cause of the error on the basis of the message output to the message log file and re-execute the command.
- When the server name is displayed
Refer to the message output in the message log file, remove the cause of the error from the relevant server, and re-execute the command.
- When the pdorbegin -u command is executed
Check that the RDAREA can be released from online reorganization hold.
KFPH00153-E L+S
aa....aa command failed due to RDAREA status invalid, RDAREA=bb....bb
- Unable to execute aa....aa command due to an invalid RDAREA status.
- aa....aa: Name of command
- bb....bb: RDAREA name
- S: Cancels the processing on the RDAREA, and continues processing.
- O:
- Check the RDAREA's status with the pddbls command, correct the status, then re-execute the command.
- When shared RDAREAs are used, check the status of the shared RDAREA for each server using the pddbls -m command, and place all shared RDAREAs in the correct status. Then, re-execute the command.
- When temporarily changing from online reorganization hold status to reference-possible hold status, the RDAREA cannot hold backups. Use the pdrels command to release the reference-possible hold. In addition, if the pdorchg command has not been executed, use the pdorbegin command; if pdorchg has been executed, use the pdorend command to release the online reorganization hold, and then re-execute the command.
- For more information about whether commands can be executed depending on the status of the RDAREA, see Availability of utility or UAP execution depending on RDAREA status in the manual HiRDB Version 9 Command Reference. However, for the pdorbegin command, see RDAREA status transitions in the manual HiRDB Version 9 Command Reference to verify the correct status for the original RDAREA. In the case of a replica RDAREA, verify that the area is on hold and closed.
KFPH00154-E L+S
RDAREA open failed due to not recovered, RDAREA="aa....aa"
- RDAREA that was shut down due to an error has not been recovered and could not be opened.
- aa....aa: RDAREA name
- S: Invalidates the command for this RDAREA and resumes processing.
- Action
- Eliminate the cause of the RDAREA shutdown error and release its CLOSE status with the pdrels command.
KFPH00155-W L+S
RDAREA status changed, though not recovered, RDAREA="aa....aa"
- Even though RDAREA aa....aa that was shut down has not been recovered, its status was changed. Or, the RDAREA status was changed without reflecting difference data in synchronization-hold RDAREA aa....aa.
- aa....aa: RDAREA name
- S: Resumes processing.
- Action
- Check the cause of the RDAREA shutdown error and eliminate the cause if it affects operations.
KFPH00156-E L+S
Backup hold canceled due to deadlock occurred, RDAREA = "aa....aa"[, server = bb....bb]
- Backup-hold was cancelled because deadlock occurred.
- aa....aa: RDAREA name
- bb....bb: Shared RDAREA runtime server name
- This is displayed when an error occurs in a shared RDAREA.
- S: Terminates processing.
- O:
- If there is an RDAREA that is in reference-possible backup-hold status of the update WAIT mode or that is in updatable backup-hold status, refer to the deadlock information (for a shared RDAREA, the server deadlock information) and find the RDAREA that is securing the lock on the backup-held RDAREA (resource type 0602). Then use the pdrels command to release that RDAREA's held status, and re-execute the pdhold command.
- In all other cases, wait a while, and then re-execute the pdhold command. For details on deadlock information, see HiRDB Version 9 System Operation Guide.
KFPH00157-W L+S
Unable to recover without log file because of update in backup hold, RDAREA=aa....aa
- RDAREA aa....aa was updated while it was in updatable backup-hold status (WAIT mode). Recovery of the database using this backup requires the unload log file into which were unloaded the system logs from the most recent synchronization point before the backup was made.
- aa....aa: RDAREA name
- S: Continues processing.
- Action
- To recover the RDAREA, use the backup file and unload log file.
KFPH00210-I L
Clustering disordered, table id=aa....aa
- In the case of a table for which clustering is specified, rows can no longer be stored in the specified segment and the benefits of clustering are beginning to be lost.
- aa....aa: Table number
- S: Resumes processing.
- O: Reorganize the corresponding table.
KFPH00211-I L
RDAREA usage aaa%, RDAREA="bb....bb"cc....cc
- The meaning depends on the circumstances:
- System definition pd_rdarea_warning_point not specified:
- Master directory RDAREA, data directory RDAREA:
- No message is output.
- Data dictionary RDAREA, user RDAREA, user LOB RDAREA, registry, and registry LOB RDAREAs:
- The system started using the segment with relative location aaa% among all the segments of the last file in RDAREA "bb....bb".
- System definition pd_rdarea_warning_point specified:
- Master directory RDAREA, data directory RDAREA, data dictionary RDAREA, user RDAREA, registry RDAREAs:
- The system started using the segment with usage factor aaa% among all the segments in RDAREA "bb....bb". The current number of unused segments is cc....cc.
- User LOB RDAREA, registry LOB RDAREAs:
- The system started using the segment with relative location aaa% among all the segments in RDAREA "bb....bb". The number of remaining segments that can maintain effective performance is cc....cc.#
- #
- In the case of a user LOB RDAREA, the highest throughput can be achieved when the database area has not been used through the end. The effective performance indicates the high throughput status. Once a database is used through the end, throughput becomes lower. Therefore, some action such as database reorganization must be taken beforehand.
- aaa: One of the following is displayed:
- Relative location of the segment being used in the last file in the RDAREA
- Segment usage factor in the entire RDAREA
- Relative location in the RDAREA of the segment being used
- bb....bb: Applicable RDAREA name
- cc....cc: Additional information about segment usage factor, dd....dd segments unused (dd....dd: number of remaining segments)
- S: Resumes processing.
- If there is not enough space to allocate a new segment in this RDAREA but there is some space in existing segments used for addition or updating, the system continues processing using those segments.
- This message is displayed again if the indicated segment is used after it was released due to table deletion, reorganization, etc.
- P: Contact the HiRDB administrator.
- Action
- Use the command or utility shown below to check the remaining space in the RDAREA, then take the appropriate action shown in the table.
- Command for checking the remaining space:
- Database status display command (pddbls)
Specifying the -a option displays the RDAREA usage status. This command can be used for all RDAREAs.
- Database condition analysis utility (pddbst)
Analyzes the RDAREA usage status using physical or logical analysis. This utility can be used for data dictionary RDAREAs, user RDAREAs (except temporary table RDAREAs), and LOB RDAREAs.
- Action
- The table below shows the actions:
RDAREA type | System definition pd_rdarea_warning_point not specified | System definition pd_rdarea_warning_point specified |
---|
Master directory RDAREA or data directory RDAREA | No message is output. | - Check the usage status of the RDAREA by using the database status display command (pddbls) or check the additional information about segment usage factor displayed in the message.
- Extend the RDAREA as required.
- The database condition analysis utility (pddbst) is not applicable to this RDAREA. Additionally, this RDAREA cannot be reorganized.
|
Data dictionary RDAREA | - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).
- Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.
| - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.
- Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.
|
User RDAREA (non-temporary table RDAREA) | - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).
- Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.
| - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.
- Reorganize the tables in units of RDAREAs or tables according to the usage status. Or, extend the RDAREA.
|
User RDAREA (temporary table RDAREA) | Expand the RDAREA or add an RDAREA, depending on the situation. |
LOB RDAREA | - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).
- Reorganize the RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.
| - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.
- Reorganize the RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.
|
List RDAREA | Take the corrective actions described in Space shortage in a list RDAREA under RDAREA space shortage in the HiRDB Version 9 System Operation Guide. |
KFPH00212-I L
Table should be reorganized, RDAREA="aa....aa", AUTHID=bb....bb, TABLE=cc....cc
- A table needs to be reorganized.
- aa....aa: RDAREA name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Resumes processing.
- Action
- Reorganize the table with the database reorganization utility (pdrorg). The size of the RDAREA must be increased in the following cases:
- This message is issued frequently for tables in the same RDAREA.
- This message is issued during or immediately after table reorganization.
KFPH00213-W L
All segments in RDAREA "aa....aa" allocated
- An attempt was made to allocate a new segment for a table or index, but all segments in RDAREA aa....aa are in use.
This message is output for data dictionary RDAREAs, data dictionary LOB RDAREAs, user RDAREAs, and user LOB RDAREAs. Furthermore, this message is output once per RDAREA after the server has started, and the next event is released from warning message output status. - HiRDB server startup
- RDAREA hold release
- RDAREA open by operation command
- RDAREA expansion
- aa....aa: RDAREA name
- S: Continues processing.
- Even if the RDAREA indicated in this message is too small, and new segments cannot be allocated, if there are any existing empty segments among those added or changed, those segments are used, and processing continues.
- Furthermore, if the segments referred to in this message are released when a table is dropped or reorganized, and then the same segments are used later, this message is re-displayed.
- Action
- See the actions of the KFPH00211-I message.
KFPH00306-E L
RDAREA "aa....aa" hold due to bb....bb
- RDAREA aa....aa was placed on error shutdown status for reason bb....bb.
For an in-memory RDAREA, this results in a buffer error. - aa....aa: RDAREA name
- bb....bb: Reason for shutting down the RDAREA:
- LIST RDAREA error:
- An error was detected in a list RDAREA.
- error occurred in log less utility:
- An error was detected during processing of a utility that does not collect log information, so the RDAREA was shut down.
- error occurred in log less uap:
- Error was detected during processing of a UAP that does not collect log information, so the RDAREA was shut down.
- error occurred in table of RECOVERY NO option at BLOB column:
- The RECOVERY NO option was set in the BLOB column, so the RDAREA was shut down.
- i/o error occurred:
- An I/O error occurred.
- open error occurred:
- An open error occurred.
- page corrupted:
- Internal conflict was detected on a page.
- rollback failed:
- Rollback failed.
- time stamp invalid:
- Time stamp mismatch was detected on a page.
- object ID invalid:
- Object ID mismatch was detected on a page.
- S: In the case of input from the RDAREA (with the exception of log application site processing when the database recovery utility, rerun, rollback, or Real Time SAN Replication with the log-only synchronous method is being used), terminates processing and rolls back; in all other cases, continues processing.
- Action
- For an in-memory RDAREA, perform the error recovery steps in Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator. Otherwise, take the following action:
- LIST RDAREA error:
- This error is output when HiRDB is started forcibly without recovering a list RDAREA that had been placed on error shutdown status. Reinitialize the list RDAREA, then use the pdrels command to release its shutdown status, then resume the operation.
- error occurred in log less utility:
- Recover the RDAREA as follows:
- When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.
- When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the pdclose command to close the RDAREA to be recovered, and then use the database structure modification utility to re-initialize the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then restore the initial data back into the table and resume the operation.
- For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.
- error occurred in log less uap:
- Recover the RDAREA as follows:
- When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.
- When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the PURGE TABLE statement to delete the row data from all the tables updated by the UAP, and then use the pdrels command to release the shutdown. Next, restore the initial data back into the table and resume the operation.
- For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.
- error occurred in table of RECOVERY NO option at BLOB column:
- Recover the RDAREA as follows:
- When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.
- When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the PURGE TABLE statement to delete the row data from the tables containing LOB columns in the tables in the RDAREA that was shut down, and then use the pdrels command to release the shutdown. Next, restore the initial data back into the table and resume the operation.
- For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.
- i/o error occurred:
- Refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error and correct the I/O error. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown, then resume the operation.
- open error occurred:
- Refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error and correct the open error. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown, then resume the operation.
- time stamp invalid:
- Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.
- Other cases:
- RDAREA recovery may have failed; check for the following:
- The RDAREA had been placed on error shutdown status earlier, but has not been recovered; or, the RDAREA was released forcibly from error shutdown status and was used after the database recovery utility failed.
- HiRDB has been started forcibly.
- Status or log files were initialized after HiRDB was terminated forcibly or terminated abnormally, and then HiRDB was restarted and used.
- When the RDAREA was recovered from a backup earlier, at least one RDAREA related to the recovered RDAREA was not recovered from the backup.
- Backup was restored and HiRDB was restarted after HiRDB had been terminated forcibly or terminated abnormally.
- If any of the above is applicable, use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.
- If none of the above is applicable, contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.
- Log application site using Real Time SAN Replication with the log-only synchronous method
- The log application is disabled. Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take corrective action.
KFPH00307-E L
RDAREA "aa....aa" HELD(CMD) due to bb....bb
- RDAREA "aa....aa" was shut down for reason bb....bb.
- aa....aa: RDAREA name
- bb....bb: Reason for shutting down the RDAREA:
- time stamp invalid:
- Time stamp mismatch was detected on a page.
- i/o error occurred:
- An I/O error occurred.
- open error occurred:
- An open error occurred.
- object ID invalid:
- Object ID mismatch was detected on a page.
- page corrupted:
- Page corruption was detected.
- data unfinished:
- A falsification prevented table in reload-not-completed data status was detected.
- S: Shuts down and rolls back the applicable RDAREA.
- Action
- time stamp invalid:
- Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. If the KFPH00306-E message has not been output for the applicable RDAREA, its shutdown status can be released with the pdrels command and the operation can be resumed. If the KFPH00306-E message has been output, the RDAREA must be recovered; take the action indicated by the KFPH00306-E message.
- i/o error occurred:
- If the KFPH00306-E message has not been output for the applicable RDAREA, refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error, and correct the I/O error. Then use the pdrels command to release the shutdown status, then resume the operation.
- If the KFPH00306-E message has been output, the RDAREA must be recovered; take the action indicated by the KFPH00306-E message.
- open error occurred:
- If the KFPH00306-E message has been output for the applicable RDAREA, the RDAREA must be recovered. Take the action indicated by the KFPH00306-E message.
- If the KFPH00306-E message has not been output for the applicable RDAREA, refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error, and correct the open error. Then use the pdrels command to release the shutdown status, then resume the operation.
- data unfinished:
- A falsification prevented table in reload-not-completed data status is in the applicable RDAREA. Use the database reorganization utility (pdrorg) to completely reload the falsification prevented table in reload-not-completed data status. Then, use the pdrels command to release the shutdown status and resume work.
- Other cases:
- RDAREA recovery may have failed; check for the following:
- The RDAREA had been placed on error shutdown status earlier, but has not been recovered; or, the RDAREA was released forcibly from error shutdown status and was used after the database recovery utility failed.
- HiRDB has been started forcibly.
- Status or log files were initialized after HiRDB was terminated forcibly or terminated abnormally, and then HiRDB was restarted and used.
- When the RDAREA was recovered from a backup earlier, at least one RDAREA related to the recovered RDAREA was not recovered from the backup.
- If any of the above is applicable, use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.
- If none of the above items is applicable, contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. If the KFPH00306-E message has been output for the applicable RDAREA, the RDAREA must be recovered. Take the action indicated by the KFPH00306-E message. If the KFPH00306-E message has not been output, the shutdown status can be released with the pdrels command and the operation can be resumed.
KFPH00308-E L
Page corrupted, RDAREA = "aa....aa", file name = bb....bb, offset = cc....cc
- Page corruption was detected.
For an in-memory RDAREA, page corruption was detected on the in-memory data buffer. - aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.
- cc....cc: Location relative to the beginning of HiRDB file (shows in decimal the location of the corrupted page)
- S: Shuts down this RDAREA and outputs a simple dump file. For an in-memory RDAREA, this results in a buffer error.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center. Use the database recovery utility to recover the RDAREA that was shut down. For an in-memory RDAREA, perform the error recovery steps in Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.
KFPH00309-E L
DB error inf1=(file=aa....aa, offset=bb....bb, pno=cc....cc, fno=dd)
- Outputs maintenance information at the time of a database error.
- aa....aa: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.
- If unclear, ****** is displayed.
- bb....bb: Offset from the beginning of HiRDB file page to where the error was detected. (****** is displayed when the file name is unknown)
- cc....cc: Page number
- dd: File number
- S: Continues processing.
- Action
- Take the action indicated by the abort code in the message KFPH00306-E, KFPH00307-E, KFPH22025-E, KFPH22026-E, KFPH23023-I, or KFPH23040-I that was output after this error.
KFPH00310-E L
DB error inf2=(func=aa....aa, line=bbbbb, RDAREA="cc....cc", RDID=dd....dd, ptype=e, TBLID=ff....ff, IDXID=gg....gg, LISTID=hh....hh, opcode=iiiii, sttype=jj)
- Outputs maintenance information at the time of a database error.
- aa....aa: Name of the function in which the error was detected
- bbbbb: Row number in which the error was detected
- cc....cc: RDAREA name (****** is displayed when the RDAREA name is unknown)
- dd....dd: RDAREA ID
- e: Detected page type:
- I: Index
- T: Data
- D: Directory
- L: List
- B: LOB
- ff....ff: ID of the applicable table (if unknown, ****** is displayed)
- gg....gg: ID of the applicable index (if unknown, ****** is displayed)
- hh....hh: ID of the applicable list (if unknown, ****** is displayed)
- iiiii: Operation code (if unknown, *** is displayed)
- jj: Scan type (if unknown, ** is displayed)
- S: Continues processing.
- Action
- Take the actions indicated by the abort code in the KFPH00306-E, KFPH00307-E, KFPH22025-E, KFPH22026-E, KFPH23023-I, or KFPH23040-I message that was output after this error.
KFPH00311-E L
RDAREA "aa....aa" held in Real_Time_SAN_Reprication backup site, due to bb....bb in Real_Time_SAN_Reprication usually site
- At the log application site, RDAREA "aa....aa" was shut down due to reason bb....bb.
- aa....aa: RDAREA name
- bb....bb: Reason for shutdown
- log less utility executed:
- At the transaction execution site, a utility was executed either in no-log mode or in pre-update log acquisition mode.
- log less uap executed:
- At the transaction execution site, a UAP was executed in no-log mode.
- table of RECOVERY NO/PARTIAL option at BLOB column is changed:
- At the transaction execution site, a table with a BLOB column was updated with either the RECOVERY NO or RECOVERY PARTIAL option.
- database structure modification utility executed:
- At the transaction execution site, the database structure modification utility (pdmod) was executed.
- This reason code is output when one of the following facilities is used on the RDAREA undergoing system log application processing:
- RDAREA expansion (expand rdarea statement)
- RDAREA re-initialization (initialize rdarea statement)
- RDAREA deletion (remove rdarea statement)
- RDAREA move (move rdarea statement)
- RDAREA attribute modification (alter rdarea statement)
- held:
- The RDAREA at the transaction execution site was shut down due to an error.
- S: Continues processing.
- Action
- The log application is disabled. Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take corrective action.
KFPH00312-E L
RDAREA "aa....aa" HELD(CMD) in Real_Time_SAN_Reprication backup site, due to bb....bb in Real_Time_SAN_Reprication usually site
- At the log application site, RDAREA "aa....aa" was shut down due to reason bb....bb.
- aa....aa: RDAREA name
- bb....bb: Reason for shutdown
- HELD(CMD):
- A command shutdown was performed at the transaction execution site.
- S: Continues processing.
- Action
- If a KFPH00311-E message is not output on the RDAREA in question, take corrective action by referring to the KFPH00307-E message that is output at the transaction execution site. If a KFPH00311-E message is output, take corrective action according to the KFPH00311-E message.
KFPH00313-E L
Time stamp invalidity information, (header value=aa....aa, footer value=bb....bb)
- Outputs maintenance information when a time stamp inconsistency is found in a page.
- aa....aa: Page header time stamp acquisition value
- bb....bb: Page footer time stamp acquisition value
- S: Continues processing.
- Action
- Take corrective action according to the KFPH00306-E, KFPH00307-E, KFPH22025-E, or KFPH22026-E message or the abort code that is output following this message.
KFPH00372-I L
RDAREA "aa....aa" not recovered from hold status
- RDAREA that was shut down due to an error has not been recovered.
- aa....aa: RDAREA name
- S: Resumes processing.
- Action
- Recover the RDAREA and release its SHUTDOWN status.
KFPH20001-E L
Invalid HiRDB ID for database, HiRDB ID=aaaa, database initialize HiRDB ID=bbbb
- Identifier aaaa of the started HiRDB differs from identifier bbbb of HiRDB whose database was initialized.
- aaaa: Identifier of HiRDB that was started
- bbbb: Identifier of HiRDB that was initialized
- S: Terminates abnormally.
- Action
- Re-execute after correcting HiRDB identifier specified in the pd_system_id operand of the system common definition to the following HiRDB identifier:
- Identifier of HiRDB whose database was initialized
- Or, execute the database initialization utility.
KFPH20003-E L
Server aa....aa initialization failes, function=bb....bb,return code=cccc
- When server aa....aa was started, bb....bb resulted in error cccc.
- aa....aa: Server name
- bb....bb: Function resulting in the error
- cccc: Return code
- S: Terminates server processing.
- O: Contact the HiRDB administrator.
- Action
- Take action appropriate to the return code:
bb....bb | cccc | Action |
---|
malloc | -- | There is insufficient process private area. Take the following actions to be sure more than enough memory is available:
- Reduce the number of concurrently executing processes.
- Increase the swap area.
- Add real memory.
|
p_f_dbh_buf_defmk | -150 | In the system common definition, the pdbuffer operand is invalid. Correct the pdbuffer operand. |
Other than the above | Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center. |
p_f_dbh_hba_mmap_copy | -100 | The process for acquiring HiRDB database environment information file from the running system failed. Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center. |
-110 -120 | The rcp command from the running system failed, a time-out occurred in the running HiRDB, or startup of the running system failed. Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center. |
-140 | The rsh command to the running system failed. Set up the environment to enable execution of a remote shell, and then restart the standby HiRDB. |
Other than the above | Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center. |
p_f_dbh_dint_rblk_set | -160 | - While the rapid system switchover facility was being used, the running HiRDB executed the database structure modification utility, but the standby HiRDB did not restart. Therefore, system switching failed. Restart the standby HiRDB.
- While the standby less switchover facility was being used, the database structure modification utility was executed, but after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, the database structure modification utility was executed during alternating, but the normal BES unit did not restart. Therefore, system switching failed. Normally terminate, and then restart HiRDB/Parallel Server.
|
-161 | - While the rapid system switchover facility was being used, the master directory RDAREA was updated, and then the dictionary server was independently normally terminated and restarted. However, system switchover failed because the standby HiRDB did not restart.
- While the rapid system switchover facility was being used, the master dictionary RDAREA was updated, and then the dictionary server was independently normally terminated and restarted. However, after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, the master directory RDAREA was updated during alternating, and then the dictionary server was independently normally terminated and restarted. However, system switchover failed because the normal BES unit did not restart. Normally terminate, and then restart HiRDB/Parallel Server.
|
-162 | - While the rapid system switchover facility was being used, HiRDB system definition was modified, and then the running system server was independently normally terminated and restarted. However, system switchover failed because the standby HiRDB did not restart. Restart the standby HiRDB.
- While the rapid system switchover facility was being used, HiRDB system definition was modified, and then the normal BES unit was independently normally terminated and restarted. However, after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, HiRDB system definition was updated during alternating, and then the alternate BES unit was independently normally terminated and restarted. However, system switchover failed because the normal BES unit did not restart. Normally terminate, and then restart HiRDB/Parallel Server.
|
Other than the above | Refer to the message output before this message was output, eliminate the cause of the error, and then restart HiRDB. If no message was output, contact the customer support center. |
pdi_omm_mget | -143 -147 | (1) From the following server definitions, increase the value of the appropriate server specification.
- pd_sds_shmpool_size (single server definition)
- pd_bes_shmpool_size (back-end server definition)
- pd_dic_shmpool_size (dictionary server definition)
(2) If the above definitions are omitted, specify the following system common definition values:
- pd_assurance_table_no operand
At least 102 + the number of tables using the free space reusage facility#
- pd_assurance_index_no operand
Single server: (130 + number of defined indexes#) 1.2 or more Parallel server: (number of defined indexes#) 1.2 or more
#: For details about the number of tables and the number of defined indexes, see the manual HiRDB Version 9 System Definition. (3) If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. |
Other than the above | Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center. |
pdi_omm_getseg | -147 | If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. |
Other than the above | Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center. |
Other than the above | -- | Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center. |
- Legend:
- --: Not applicable
KFPH20004-E L
Server aa....aa termination failed, function=bb....bb, return code=cccc
- When server aa....aa was terminated, bb....bb resulted in error cccc.
- aa....aa: Server name
- bb....bb: Function resulting in the error
- cccc: Return code
- S: Terminates server termination processing.
- O: Contact the HiRDB administrator.
- Action
- Refer to the message that was output before this message to eliminate the cause of the error, then restart the server. If no message was output before this message, contact the customer support center.
KFPH20005-E L
Failed to aa....aa 1st file in MASTER DIRECTORY, return code=bbbb
- Processing aa....aa on the first HiRDB file in the master directory RDAREA failed.
- aa....aa: Processing:
- close: Close processing for the first file in the master directory RDAREA
- open: Open processing for the first file in the master directory RDAREA
- read: Loading from the first file in the master directory RDAREA
- bbbb: Return code
- S: Cancels HiRDB startup processing and terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute HiRDB.
KFPH20006-W L
Unable to use work HiRDB file system area, return code=bbbbb, HiRDB file system area name=aa....aa
- HiRDB file system area aa....aa specified as a work table file cannot be used.
- aa....aa: Name of HiRDB file system area
- If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.
- bbbbb: Return code
- S: Resumes processing.
- O: Contact the HiRDB administrator.
- Action
- During execution of database initialization utility:
- If the database initialization utility terminated normally, see 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute the database initialization utility.
- During server startup:
- See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then restart the server if necessary.
KFPH20007-W L
Work HiRDB file system area not specified expansion, HiRDB file system area name = aa....aa
- Secondary allocation has not been specified for HiRDB file system area aa....aa, specified as a work table file.
- aa....aa: Name of HiRDB file system area
- If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.
- S: Resumes processing.
- O: Contact the HiRDB administrator.
- Action
- During execution of database initialization utility:
- If the KFPA11959-E message is output during execution of the database initialization utility, specify a HiRDB file system area for which a secondary allocation is specified, then re-execute the database initialization utility.
- During server startup:
- Specify a HiRDB file system area for which a secondary allocation is specified, then restart the server if necessary.
KFPH20008-W L
No work HiRDB file system area
- There is no HiRDB system file area available for a work table file.
- S: Resumes processing.
- O: Contact the HiRDB administrator.
- Action
- During execution of database initialization utility:
- If the pdwork operand was not specified in the dictionary server definition or single server definition and the database initialization utility does not terminate normally, specify a HiRDB file system area and re-execute the database initialization utility.
- If the pdwork operand is specified in the dictionary server definition or single server definition and the database initialization utility does not terminate normally, refer to the KFPH20006-W message that was output before this message to eliminate the cause of the error, then re-execute the database initialization utility.
- During server startup:
- If the pdwork operand was not specified in the server definition, specify HiRDB file system area if necessary, then restart the server.
- If the pdwork operand is specified in the server definition, refer to the KFPH20006-W message that was output before this message to eliminate the cause of the error, then restart the server if necessary.
KFPH20009-W L
Duplicate work HiRDB file system area aa....aa
- HiRDB file system area specified as a work table file has already been specified.
- aa....aa: Name of the duplicate HiRDB file system area
- If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.
- S: Ignores the name of HiRDB file system area that was specified more than once and resumes processing.
- O: Contact the HiRDB administrator.
- Action
- During execution of database initialization utility:
- If the database initialization utility does not terminate normally, correct the name of HiRDB file system area for storing the work table in the pdwork operand of the dictionary server definition or single server definition so that it is not duplicated, then restart the database initialization utility.
- During server startup:
- Correct the name of HiRDB file system area for storing the work table in the pdwork operand of the server definition so that it is not duplicated, then restart the server.
KFPH20010-W L
Number of work HiRDB file system area exceeds 16
- The number of HiRDB file system areas specified for work table files exceeds the maximum (16).
- S: Ignores all but the first 16 HiRDB file system area names and resumes processing.
- O: Contact the HiRDB administrator.
- Action
- During execution of database initialization utility:
- If the database initialization utility does not terminate normally, correct the number of HiRDB file system area names for storing work tables in the pdwork operand of the dictionary server definition or single server definition to 16 or less, then re-execute the database initialization utility.
- During server startup:
- Correct the number of HiRDB file system area names for storing work tables in the pdwork operand of the server definition to 16 or less, then restart the server.
KFPH20011-E L
Incompatible character code set for database, character code set=aa....aa, database initialize character code set=bb....bb
- Character codes type aa....aa of the started file does not match character codes type bb....bb of the initialized HiRDB.
- aa....aa: Character codes type of the started HiRDB:
- bb....bb: Character codes type of the initialized HiRDB
- CHINESE: EUC Chinese kanji codes
- LANG-C: One-byte character codes
- SJIS: Shift JIS codes
- UJIS: EUC Japanese kanji code
- UTF-8: Unicode
- CHINESE-GB18030: Chinese character encoding GB18030
- *******: Invalid character code
- S: Terminates processing.
- Action
- In UNIX, this message may be output if $PDDIR/lib is not assigned in addition to the environment variable SHLIB_PATH (in Solaris or Linux, LD_LIBRARY_PATH; in AIX, LIBPATH). Revise the environment variable, and restart HiRDB.
- For character codes type aa....aa:
- Execute the Database Load Utility to regenerate the database.
- For character codes type bb....bb:
- In UNIX, use the pdsetup -d command to delete the HiRDB system under the HiRDB directory from the OS, and then re-execute the pdsetup -c command. For details about the pdsetup command, see the manual HiRDB Version 9 Command Reference. In Windows, execute the pdntenv -c command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.
- If the activated HiRDB character code type aa....aa is *******:
- An internal conflict was detected. Contact the customer support center.
- If the character code type bb....bb is *******:
- Either the database is invalid or the master directory RDAREA is corrupted. Either re-create the database by executing the database initialization utility or, if the master directory RDAREA is corrupted, recover it by using the database recovery utility.
KFPH20012-E L
Incompatible HiRDB version for database, HiRDB version=aaaaa, database version=bb....bb
- HiRDB indicated version is invalid.
- The version of HiRDB system that created the database is newer than the version of HiRDB system being used. Therefore, the database cannot be accessed.
- The database cannot be transferred from the version of HiRDB that created it to the version of HiRDB that is being used.
- aaaaa: Version of HiRDB that was activated
- bb....bb: Internal information that shows the database version
- S:
- Single-unit configuration using HiRDB/Single Server or HiRDB/Parallel Server:
- Terminates abnormally with an abort code PsadsA8.
- Multiple-unit configuration using HiRDB/Parallel Server:
- The unit containing the dictionary server terminates abnormally with an abort code PsadsA8. Other units also are forced to terminate.
- Action
- Take one of the following actions:
- To make the database version equal to aa....aa, use the pdstart -i command to activate HiRDB system. After a KFPS05201-Q message is output, execute the Database Initialization Utility (pdinit).
- To use the database in version bb....bb of HiRDB, restore the old version of HiRDB (for details, see HiRDB Version 9 Installation and Design Guide).
KFPH20013-E L
Incompatible database format with HiRDB, database data model=64-bit, HiRDB data model=32-bit
- A database created by a 64-bit-mode HiRDB cannot be accessed by a 32-bit-mode HiRDB.
- You cannot migrate from a 64-bit-mode HiRDB to a 32-bit-mode HiRDB.
- S: Terminates abnormally with abort code PsadsA8.
- Action
- Set HiRDB to the 64-bit mode. For the migration method, see HiRDB Version 9 Installation and Design Guide.
KFPH20015-I L
Copying HiRDB database environment information files necessary for server aa....aa initialization from online unit
- HiRDB database environment information files necessary for server aa....aa initialization are being acquired from the executing unit.
- aa....aa: Server name
- S: Continues processing
KFPH20016-E L
Overflow Error occurred by size calculation of memory, server aa....aa
- An overflow occurred during the calculation of memory size.
- aa....aa: Server name (or ****** if the server name is unknown)
- S: Terminates abnormally.
- Action
- aa....aa is ******:
- Revise the system definition so that the result of the I/O server algorithm for the shared memory algorithm used by the unit controller is less than 231 - 1 for the 32-bit mode, or less than 263 - 1 for the 64-bit mode. For I/O server algorithms, see Shared memory algorithm used by unit controller in HiRDB memory requirements in the manual HiRDB Version 9 Installation and Design Guide.
- aa....aa is a server name:
- Revise the system definition so that the result of the respective algorithm below is less than 231 - 1 for the 32-bit mode, or less than 263 - 1 for the 64-bit mode:
- HiRDB/Single Server: Shared memory algorithm used by a single server
- HiRDB/Parallel Server: Shared memory algorithm used by the server on which the error occurred
- For the respective algorithm, see the manual HiRDB Version 9 Installation and Design Guide.
KFPH21001-E L
Error occurred at aa....aa code=bbbb on cc....cc
- When server cc....cc was started, error aa....aa with code bbbb occurred.
- aa....aa: Error detail:
{ Process Communication |Get Work Area
|Define pd_rdarea_list_no_wrn_pnt
|Get Control Area(rerun ctrl)
|Call hbuf_ucbint| Call adm_complete
|Call p_f_pls_call_by_timing
|Get Environment| Get Control Area| Get Log Area
|Init. SQA | Init. DBH | Init. DIC | Call plugin(start process)
|Call plugin(terminate process) | Call adm_rerun_end }
- bbbb: Error code (displays -1 when aa....aa is Define pd_rdarea_list_no_wrn_pnt)
- cc....cc: Server name (if acquisition of the server failed, ******** is displayed)
- S: Terminates server process activation processing.
- O: Contact the HiRDB administrator.
- Action
- Process Communication displayed as aa....aa:
- See 4.1 Detail codes for RPC-related errors in order to take appropriate action on the basis of the displayed code (bbbb).
- aa....aa is Get Work Area or Get Log Area:
- Increase the size of the process private area by one of the following methods, then re-execute:
- Reduce the number of processes that execute concurrently.
- Increase the swap size.
- Increase the real memory.
- aa....aa is Define pd_rdarea_list_no_wrn_pnt:
- Reset the pd_rdarea_list_no_wrn_pnt operand in the system definition to a value within the permissible range and restart HiRDB.
- Other:
- Refer to the message that was output before this message to eliminate the cause of the error, then restart the server. If no message was output, contact the customer support center.
KFPH22001-E L
Invalid DIRECTORY data in RDAREA "aa....aa", reason code=b
- A contradiction was detected in the RDAREA control information for RDAREA "aa....aa".
- aa....aa: RDAREA name
- b: Reason code
- S: Terminates abnormally, shuts down the corresponding RDAREA, and invalidates the processing.
- Action
- Check the RDAREA for an operation error based on the reason code. If there is an operation error, recover the RDAREA, and then retry the processing. If there is no operation error and no corresponding cause, contact the customer support center.
Reason code | Cause | Action |
---|
1 2 3 4 9 | There is a contradiction in a segment of the corresponding RDAREA or the page management information. One of the following might have occurred:
- The RDAREA was not recovered after an error shutdown (logless shutdown) when an abnormality was detected during execution of a UAP or utility in no-log mode.
- The RDAREA was not recovered after an error shutdown (logless shutdown) when an abnormality was detected during execution of the UAP or utility when NO is specified in the RECOVERY option for a BLOB column.
- The RDAREA was recovered to a backup state in which some of the HiRDB files that make up the RDAREA are different.
| Recover the RDAREA.
- To recover to the point when the database backup was made:
- Recover the corresponding RDAREA using the backup.
- To recover the RDAREA to it's initial state without using the backup:
- Use the pdclose command to close the RDAREA to be recovered, and then the database structure modification utility (pdmod) to re-initialize the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then restore the initial data back into the table.
For details about operations in no-log mode and how to recover an RDAREA, see the HiRDB Version 9 System Operation Guide. |
5 6 7 | The corresponding RDAREA does not match the information in a system RDAREA (master directory RDAREA or dictionary RDAREA, for example). Only some of the related RDAREAs might have been recovered using backups made before or after the database structure modification utility (pdmod) or definition SQL statement was executed. Another possibility is that a related RDAREA might have been recovered from a backup made at a different time. | Use the backups to recover to the same point when a backup was made of the related RDAREAs. For details about RDAREAs that need to be backed up at the same time, see the HiRDB Version 9 System Operation Guide. |
- Note
- If Real Time SAN Replication with the log-only synchronous method is being used, refer to the HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.
KFPH22002-E L
Insufficient memory on PROCESS, size = aa....aa
- A memory shortage occurred in the process private area.
- aa....aa: Size (in bytes) of the area that was to be allocated
- S: Terminates abnormally.
- Action
- Check the memory size estimate for an error, allocate adequate memory, and re-execute.
KFPH22003-E L
HiRDB file "aa....aa" failed, return code=bb....bb, RDAREA="cc....cc", file=dd....dd
- "aa....aa" for HiRDB file dd....dd terminated with return code bb....bb.
- aa....aa: HiRDB file system function:
{ open |close |lseek |read |write |fstat | creat | sttfs | sttdk }
- bb....bb: Return code
- cc....cc: RDAREA name:
- *MASTER*: Master directory RDAREA
- dd....dd: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 122 characters, the last 122 characters of HiRDB file path name are output.
- S:
- HiRDB file comprising the master directory RDAREA:
- Cancels processing.
- Other HiRDB file:
- Shuts down the corresponding RDAREA and resumes processing.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute. In the case of a master directory RDAREA error, start HiRDB with the pdstart -r command and recover the master directory RDAREA with the database recovery utility.
- If Real Time SAN Replication with the log-only synchronous method is being used, it is possible that the database structure modification utility (pdmod) was executed on the transaction execution site. If that is the case, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.
KFPH22004-W L
aa....aa reserve Number bb....bb exceeds assurance Number cc....cc, server=dd....dd
- The aa....aa reserve number bb....bb exceeds the value cc....cc specified in the operand. The server that generated it is dd....dd.
- aa....aa: {Table | Index}
- bb....bb: Reserve number of aa....aa
- cc....cc: Specified value of pd_assurance_table_no operand or pd_assurance_index_no operand
- dd....dd: Server name
- S: Continues processing.
- Action
- After this message is output, if the server does not start due to a shared memory pool insufficiency, take the following action:
- shmpool_size operand omitted:
- Specify a value of bb....bb or higher in the pd_assurance_table_no operand or pd_assurance_index_no operand, and re-execute.
- shmpool_size operand specified:
- Increase the value assigned to the shmpool_size operand, and re-execute the UAP.
KFPH22005-E L
Number of aa....aa exceeds limit bb....bb, current=cc....cc, server=dd....dd
- There are more entities (cc....cc) than the maximum (bb....bb) that was specified by the user in definition aa....aa. The name of the server is dd....dd.
- aa....aa: Specified operand:
{ pd_max_rdarea_no |pd_max_file_no | pd_max_tmp_table_rdarea_no }
- bb....bb: Maximum value specified in aa....aa
- cc....cc: Number of entities
- dd....dd: Server name
- S: Cancels startup or recovery processing.
- O: Contact the HiRDB administrator.
- Action
- If the number of existing RDAREAs exceeds the maximum, increase the value of the pd_max_rdarea_no operand in the system common definition and re-execute (when the value of the pd_max_rdarea_no operand is increased, the size of the status file must be reviewed).
- If the number of existing RDAREA component files exceeds the maximum, increase the value of the pd_max_file_no operand in the system common definition, and then retry the operation.
- If the number of existing temporary table RDAREAs exceeds the maximum, increase the value of the pd_max_tmp_table_rdarea_no operand in the system common definition, and then retry the operation.
KFPH22006-E L
UNIX file "aa....aa" failed, return code=bb....bb, file=cc....cc
- "aa....aa" for internal work file cc....cc terminated with return code bb....bb.
- aa....aa: HiRDB file system function:
{ open|close|lseek|read|write }
- bb....bb: Return code
- cc....cc: Name of the internal work file:
- If the work file path name exceeds 131 characters, HiRDB directory name is changed to %PDDIR% for output.
- S: Cancels processing.
- Action
- See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute. If the cause of the error cannot be identified, contact the customer support center.
KFPH22007-E L
HiRDB System "aa....aa" failed, return code=bb....bb
- Function "aa....aa" of the single server (HiRDB/Single Server) or system manager (HiRDB/Parallel Server) terminated with return code bb....bb.
- aa....aa: HiRDB system facility
- bb....bb: Return code
- S: Cancels processing.
- Action
- See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute. If the cause of the error cannot be identified, contact the customer support center.
KFPH22008-E L
SORT program error occurred, code=aa....aa
- An error occurred during sorting.
- aa....aa: Error code
- S: Cancels processing.
- O: Contact the HiRDB administrator.
- Action
- Take corrective action according to the error code:
Error code | Action |
---|
-202 | Memory shortage. Reduce the size of the work buffer specified in the sort operand. |
-290 | Size of the work buffer is insufficient. Reduce the size of the work buffer specified in the sort operand. |
-210 and -230 | An I/O error occurred. It is possible that the capacity of the sort work disk is insufficient. If there is a capacity shortage, specify a disk with large enough capacity in the sort operand, and 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.
KFPH22009-E L
Unknown server name found in system, server=aa....aa, RDAREA="bb....bb"
- Server name aa....aa was not found in the server definition. The invalid server name was found in RDAREA "bb....bb".
- aa....aa: Server name
- bb....bb: RDAREA name
- S: Cancels processing
- O: Contact the HiRDB administrator.
- Action
- Correct the server type with the pdstart -t command in the system common definition.
KFPH22010-E L
System call error occurred, func="aa....aa", errno=bb....bb
- A system call error occurred.
- aa....aa: System call name (**** is displayed if the system call cannot be identified)
- bb....bb: Error code
- S: If rerun or rollback was underway, resumes processing; otherwise, terminates abnormally.
- Action
- Refer to errno.h or the applicable OS manual to check the meaning of the error code, eliminate the cause of the error, then re-execute.
KFPH22011-E L
System call error occurred, func="system", cmd="aa....aa", code=bb....bb, inf="cc....cc"
- A command executed by a system function resulted in an error.
- aa....aa: Command name
- bb....bb: Shell or command termination code
- cc....cc: Command error output information
- S: Terminates abnormally.
- Action
- Using the error output information and the shell or command termination code, refer to the OS documentation, resolve the error, and re-execute the command.
- In Windows, if "****" is indicated in "cc....cc", resolve the error based on the contents of one of the following files, and re-execute the command:
- %PDDIR%\spool\pdrshs1.log
- %PDDIR%\spool\pdrshs2.log
KFPH22012-W L
Ignore number of aa....aa, assumed limit bb....bb, server=cc....cc
- Operand aa....aa of HiRDB system definition was changed, but the previous specification value bb....bb has been assumed since HiRDB restarted. The target server is cc....cc.
- aa....aa: Changed operand
- { pd_max_rdarea_no|pd_inner_replica_control }
- bb....bb: Specification value before the operand was changed
- cc....cc: HiRDB server name
- S: Processing continues. The changed values of these operands take effect at the next HiRDB normal startup.
KFPH22013-E L
RPC "aa....aa" failed, return code=bb....bb, server=cc....cc
- If cc....cc is ********, the RPC function aa....aa that was issued when the unit started terminated with error code bb....bb.
If cc....cc is something other than ********, the RPC function aa....aa that was issued from server cc....cc terminated with error code bb....bb. - aa....aa: RPC function
- bb....bb: Error code
- cc....cc: Server identifier
- For an RPC error when the unit starts, ******** is displayed.
- S: Terminates processing.
- Action
- If this message is displayed while a back-end server or unit is starting, and the dictionary server is not running, start the dictionary server, and then retry the operation. Otherwise, eliminate the cause of the error based on 4.1 Detail codes for RPC-related errors, and then retry the operation.
KFPH22014-E L
RDAREA "aa....aa" not found in dictionary server
- RDAREA "aa....aa" that is required for the dictionary server cannot be found.
- aa....aa: RDAREA name
- *masterdirectory*: Master directory
- *datadirectory*: Data directory
- *datadictionary*: Data dictionary
- S: Terminates abnormally.
- Action
- Specify the pdstart statement for defining the dictionary server in the system common definition so that it matches the correct configuration. If the RDAREA is damaged, recover the data and re-execute.
- If Real Time SAN Replication with the log-only synchronous method is being used, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.
KFPH22015-E L
HiRDB file system area aa....aa not found, RDAREA="bb....bb"
- HiRDB file system area aa....aa for RDAREA "bb....bb" cannot be found in the system.
- aa....aa: Name of HiRDB file system area
- If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.
- bb....bb: RDAREA name
- S: Resumes processing.
- Action
- Create HiRDB file system area in which the error occurred in order to recover the RDAREA, then reopen the RDAREA.
- If Real Time SAN Replication with the log-only synchronous method is being used, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.
KFPH22016-E L
MASTER DIRECTORY RDAREA was already used
- The master directory is already being used by another HiRDB system.
- S: Terminates abnormally.
- O: Contact the HiRDB administrator.
- Action
- HiRDB systems that use the same name for the first HiRDB file in the master directory RDAREA of the system common definition cannot be started concurrently. Check the system common definition and restart.
KFPH22017-I L
Table should be reorganized, RDAREA="aa....aa", AUTHID=bb....bb, TABLE=cc....cc because disordered LOB DIRECTORY
- Management information items in the LOB RDAREA are fragmented.
- aa....aa: RDAREA name
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Resumes processing.
- Action
- RDAREA is a user LOB RDAREA:
- Because retrieval performance for the LOB data may deteriorate, reorganize the user LOB RDAREA whose name is displayed in the message.
- RDAREA is a data dictionary LOB RDAREA:
- Reorganize the dictionary table for the stored procedure and the stored function.
- If affected RDAREA is a registry LOB RDAREA:
- Reorganize the registry table.
KFPH22018-W L
Status file "aa....aa" failed, return code=bb....bb, server=cc....cc
- "aa....aa" for the status file of server cc....cc terminated with return code bb....bb.
- aa....aa: File access facility
{ alloc |dealloc |read |write }
- bb....bb: Error code
- cc....cc: Server identifier
- S: Makes preliminary queries to the dictionary server about processing that uses the status file and resumes processing. Furthermore, because HiRDB queries the dictionary server, the performance of startup processing is less efficient than when the status file is used.
- Action
- Normalize the status file for future operation; see 4.2 Detail codes for system-related errors to eliminate the cause of the error.
- If the cause cannot be located, contact the customer support center.
KFPH22019-I L
Information type=aa....aa, detail="bb....bb", code=cc....cc
- An event of type aa....aa, detail "bb....bb", and return code cc....cc occurred.
- aa....aa: Information type
- bb....bb: Internal information
- cc....cc: Internal code
- S: Resumes processing because the error can be handled by the system.
KFPH22020-W L
Server aa....aa waiting until dictionary server start
- Because the dictionary server is required for starting back-end server aa....aa, HiRDB system is waiting until the dictionary server is started.
- aa....aa: Server identifier
- S: Monitors the status of the dictionary server.
- During dictionary server startup:
- Resumes processing
- When startup cannot be checked within the appropriate amount of time:
- Resumes processing without checking dictionary server startup.
- Action
- Start the dictionary server or a unit that contains the dictionary server.
- If a network error can be assumed, eliminate the cause of the error.
KFPH22021-W L
Number of index exceeds reserved number, current reserved number=aa....aa, server=bb....bb
- The number of indexes defined has exceeded the reserved number. The currently reserved number of indexes is aa....aa, and this condition occurred at server bb....bb.
- aa....aa: Currently reserved number of indexes
- bb....bb: Server name
- S: Resumes processing. Once this message is output, the following operational benefits might not be obtained, depending on the index:
- Performance improvement realized by making index management information resident in memory
- Acquisition of statistical information on indexes
- Suppression of output of duplicated messages
- Preferential allocation of unused pages in used segments after free pages have been released from indexes
- Action
- Take one of the following actions:
- If a KFPH22004-W or KFPH22035-I message is output when the target server is activated, take corrective action based on the message.
- If a KFPH22004-W or KFPH22035-I message is not output when the target server is activated, and if the three operational benefits shown in (S) are required, take the following action according to the specification given in the pd_sysdef_default_option operand, and then restart HiRDB:
If the pd_sysdef_default_option operand is omitted, or is set to recommendable:
Specify a value greater than aa....aa (the currently reserved number of indexes) in the pd_assurance_index_no operand of the system common definition.
Either v6compatible or v7compatible specified in the pd_sysdef_default_option operand:
If the number of indexes required between startup and termination of HiRDB is greater than 1.2 times the number of indexes available at HiRDB startup time, set the operand pd_assurance_index_no in the system common definition to the sum of the current number of indexes and the number of indexes to be defined before HiRDB is started normally next time. If aa....aa (the currently reserved number of indexes) already exceeds the value specified in the pd_assurance_index_no operand, the number of indexes reserved represents an automatically increased value; in this case, specify a value greater than aa....aa (the currently reserved number of indexes) in the pd_assurance_index_no operand.
KFPH22022-E L
RDAREA information build failed, reason code=Time out.
- A timeout occurred while acquiring RDAREA information during the following:
- Startup processing for a back-end server
- Unit startup processing in an environment where the standby-less system switchover (effects distributed) facility is being applied
- The logging of RDAREA information is taking time either because the dictionary server is not activated or the dictionary server has a high load.
- S: Terminates abnormally.
- Action
- Take one of the following actions:
- If the dictionary server is not activated, activate the dictionary server, and then activate this server or unit.
- If the dictionary server has a high load, activate this server or unit after the load on the dictionary server has decreased.
KFPH22023-W L
Using resource for "aa....aa" reached bb....bb%, cc....cc
- bb....bb% of "aa....aa" is now in use.
- aa....aa: Resource type:
- rdarea-list-no
- Number of lists that can be created at a server
- bb....bb: Warning value percentage
- cc....cc: Additional information
- This information is output in the following format:
- number-of-lists-created-at-server / number-of-lists-that-can-be-created-at-server, server=server-name
- S: Continues processing.
- Action
- Delete unneeded lists or add a list RDAREA.
KFPH22024-I L
Extension completed in RDAREA "aa....aa", FILE "bb....bb", ccccc(dd....dd) segments created
- The size of HiRDB file "bb....bb" in RDAREA "aa....aa" has been increased by ccccc segments. The total number of segments is dd....dd.
- aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 112 characters, the last 112 characters of HiRDB file path name are output.
- ccccc: Number of added segments
- dd....dd: Total number of segments
- S: Continues processing.
KFPH22025-E L
Error occurred while Extension, RDAREA "aa....aa", FILE "bb....bb", reason code ccccc
- An error occurred while automatically extending HiRBD file "bb....bb" in RDAREA "aa....aa". The reason code is ccccc.
- aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 121 characters, the last 121 characters of HiRDB file path name are output.
- ccccc: Reason code
- S: Continues processing.
- Action
- Take one of the following corrective actions:
- Reason code -1544:
- Take one of the following actions depending on the contents of the KFPO00107-E message that was output immediately before this message:
- Reason code 303:
- If the database recovery utility was executed, execute it again.
- If the database recovery utility was not executed, continue the transaction without change.
- If the KFPH22025-E message is output repeatedly, contact the customer support center.
- Reason code other than above:
- See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.
KFPH22026-E L
Auto extend function suppressed, RDAREA "aa....aa", FILE "bb....bb", reason code ccccc
- The automatic extension function for HiRDB file "bb....bb" in RDAREA "aa....aa" was suppressed. The reason code is ccccc.
- aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 119 characters, the last 119 characters of HiRDB file path name are output.
- ccccc: Reason code
- S: The automatic extension function for the applicable RDAREA is suppressed until one of the following triggers:
- HiRDB activation
- Execution of a command to release RDAREA shutdown
- Execution of a command to open the RDAREA
- Execution of the database structure modification utility for reinitialization or extension of the RDAREA
- Action
- Correct the error by referring to the error code and release suppression of the RDAREA automatic extension function.
Reason code | Action |
---|
-1556 | Take one of the following actions:
- Combine the extents of the HiRDB file system areas containing the HiRDB file in question.
- Use the database structure modification utility to expand the RDAREA.
If Real Time SAN Replication with the log-only synchronous method is being used, also perform system log application processing.
|
-1544 | Take one of the following actions depending on the contents of the KFPO00107-E that was output immediately before this message:
|
1 | Execute the pdrels command on the RDAREA. |
303 | If the database recovery utility was executed, execute it again. If the database recovery utility was not executed, reset the suppression state of the RDAREA automatic extension facility, and continue the transaction without change. If the KFPH22026-E message is output repeatedly, contact the customer support center. |
Other | Refer to 5.1 Error codes returned from HiRDB file system access requests to resolve the error. |
KFPH22027-E L
Number of aa....aa exceeds limit bb....bb,current=cc....cc,server=dd....dd
- The number of inner replica groups exceeds value bb....bb specified by operand aa....aa in the system definition. The number of inner replica groups is cc....cc, and the source HiRDB server is dd....dd.
- aa....aa: Name of operand in HiRDB system definition
- bb....bb: Value of operand aa....aa
- cc....cc: Number of current inner replica groups
- dd....dd: HiRDB server name
- S: Stops HiRDB startup process.
- O: Contact the HiRDB administrator.
- Action
- Specify a value greater than or equal to the current number of inner replica groups in the d_inner_replica_control operand.
- If Real Time SAN Replication with the log-only synchronous method is being used, start HiRDB after taking all of the following actions:
- Reset the definition provided in Designing system definitions in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide and in the pd_inner_replica_control operand to the definition information previously used by the system, and then start HiRDB.
- Delete all the replica RDAREAs defined in HiRDB, and then stop HiRDB normally.
- For details about using Real Time SAN Replication with the log-only synchronous method, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
KFPH22028-E L
Staticizer Option required
- HiRDB Staticizer Option is required to use the inner replica facility.
- S: Terminates processing.
- Action
- Install HiRDB Staticizer Option to use the inner replica facility.
KFPH22029-E L
RDAREA aa....aa last file freezed, file=bb....bb fileNO=cc
- An automatic extension of the RDAREA could not be specified because the final HiRDB file bb....bb in RDAREA aa....aa, file number cc....cc is in frozen update status.
- aa....aa: RDAREA name
- bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.
- cc: HiRDB file number
- S: Terminates processing.
- Action
- Extend the RDAREA to increase capacity.
- If Real Time SAN Replication with the log-only synchronous method is being used, also perform system log application processing.
KFPH22030-W L
Number of table exceeds reserved number,current reserved number=aa....aa,server=bb....bb,RDAREA="cc....cc",AUTHID="dd....dd",TABLE="ee....ee"
- The number of defined tables exceeded the number of reserved tables while processing table "ee....ee" with authorization identifier "dd....dd" for RDAREA "cc....cc" on server bb....bb.
After this error message is output, the free space reusage facility may not be effective on some tables. - aa....aa: Current number of reserved tables
- bb....bb: Server name
- cc....cc: RDAREA name
- dd....dd: Authorization identifier
- ee....ee: Table name
- S: Continues processing.
- Action
- Take one of the following actions:
- Specify SEGMENT REUSE NO in the ALTER TABLE statement to stop the reuse of free space for tables in the free space reusage facility table that do not require the reuse of free space.
- If a KFPH22004-W or KFPH22035-I message is output when the target server is activated, take corrective action based on the message.
- If a KFPH22004-W or KFPH22035-I message is not output when the target server is activated, terminate HiRDB, change the value specified in the pd_assurance_table_no operand to a value greater than aa....aa (the currently reserved number of tables), and then restart HiRDB.
KFPH22031-W L
No reuse area,RDAREA="aa....aa",AUTHID="bb....bb",TABLE="cc....cc"
- The user executed the free space reusage facility in table "cc....cc" using authorization identifier "bb....bb" in RDAREA "aa....aa", but no free space was found.
- aa....aa: RDAREA name
- bb....bb: Authorization identifier
- cc....cc: Table name
- S: Continues processing.
- P: Take one of the following actions:
- Execute the DELETE command to create free space.
- Redefine the segment count by specifying SEGMENT REUSE in the ALTER TABLE statement.
- Stop reuse of free space by specifying SEGMENT REUSE NO in the ALTER TABLE statement.
KFPH22032-W L
Processing of SQL skipped,tableID=aa....aa,generation number=bb,server=cc....cc
- Definition update processing was skipped because all RDAREAs to be processed in generation number bb, server cc....cc are command held and are in closed status.
For the held RDAREAs indicated by the generation number, the definition information in the RDAREAs has not changed. Therefore, if the database entities are separated from the original RDAREA (not in a paired status with the original), they will not match the data dictionary table and index definition information. If you release the shutdown and use the replica RDAREA in this state, an SQL error will result, or the RDAREA will shut down. - aa....aa: Number of the target table for definition SQL, or the number of the table with a defined target index in definition SQL
- Asterisks (********) indicate a table definition (CREATE TABLE).
- bb: Generation number
- cc....cc: Server name
- S: Continues processing.
- Action
- If the definition SQL terminates normally and this message is output, and if the entities in the replica RDAREA in which processing was skipped are separated from the original RDAREA, recreate the entities in the replica RDAREA before releasing the shutdown, and make sure that the table definition and index definition match the status of the replica RDAREA. For details about the inner replica facility, see the HiRDB Version 9 Staticizer Option Description and User's Guide.
KFPH22033-E L
Not available without specification of aa....aa operand
- If a shared RDAREA is used, specify Y for the aa....aa operand.
- aa....aa: pd_shared_rdarea_use
- S: Interrupts start processing.
- O: Contact the HiRDB administrator.
- Action
- Specify Y in the system common definition pd_shared_rdarea_use operand, and re-execute.
KFPH22034-I L
Table status set to check pending status,tableID=aa....aa, RDAREA="bb....bb", constraint type=ccccccc
- Table aa....aa stored in RDAREA "bb....bb" was placed in check pending status.
- aa....aa: Table number of the table that was placed in check pending status
- bb....bb: Name of the RDAREA storing the table that was placed in check pending status
- ccccccc: Type of constraint defined in the table that was placed in check pending status
- REF: Reference constraint
- CHK: Check constraint
- REF, CHK: Reference and check constraints
- S: Continues processing.
KFPH22035-I L
aa....aa reserve Number bb....bb exceeds assurance Number cc....cc, server=dd....dd
- bb....bb, which is the reserve number of aa....aa, exceeds the value cc....cc specified in the operand. The server generating this error is dd....dd.
- aa....aa: {Table|Index}
- bb....bb: Reserve number of aa....aa
- cc....cc: Specification value in the pd_assurance_table_no or pd_assurance_index_no operand
- dd....dd: Server name
- S: Continues processing.
- Action
- If aa....aa is Table:
- If the currently defined number of tables is less than or equal to the number of tables reserved, table management information can be made resident in memory; therefore, the free space reusage facility can be used.
- If the currently defined number of tables is greater than the number of tables reserved, HiRDB can continue normal operations. However, in this case, the free space reusage facility cannot be used.
- To use the free space reusage facility, increase the value specified for the pd_assurance_table_no operand in the system common definition to a value greater than bb....bb, and start HiRDB normally.
- If aa....aa is Index:
- If the currently defined number of indexes is less than or equal to the number of indexes reserved, index management information is made resident in memory; therefore, the following operational benefits can be expected:
- Improved performance by making index management information resident in memory
- Acquisition of index-related statistical information
- Suppression of duplicate output of messages
- Preferential allocation of unused pages in used segments after free pages have been released from indexes
- If the currently defined number of indexes is greater than the number of indexes reserved, HiRDB can continue normal operations. However, in this case, the operational benefits listed above cannot be expected.
- To use the free space reusage facility, increase the value specified for the pd_assurance_index_no operand in the system common definition to a value greater than bb....bb, and start HiRDB normally.
KFPH22036-E E+L
RDAREA held due to restart, RDAREA = "aa....aa"
- Because the HiRDB server restarted during in-memory processing, an error-induced shutdown was performed on the RDAREA aa....aa, which was in DB asynchronous state.
- aa....aa: RDAREA name
- S: Continues processing.
- Action
- Refer to Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator, and recover the RDAREA.
KFPH22037-W L
File usage aaa%(bb....bb/cc....cc), RDAREA "dd....dd", FILE "ee....ee"
- The HiRDB file ee....ee of the RDAREA dd....dd was allocated to an area of aaa% or higher of the maximum disk size to which automatic extension can expand the HiRDB file.
- aaa: The proportion of the maximum disk size that expands by automatic extension and is used by the automatically-extending HiRDB file.
- bb....bb: HiRDB file space that automatically extends (units: KB)
- cc....cc: The maximum disk size to which the HiRDB file can automatically extend (units: KB)
- dd....dd: RDAREA
- ee....ee: HiRDB-file-system-area-name\HiRDB-file-name
- If the path name of the HiRDB file exceeds 112 bytes, the last 112 bytes of the HiRDB file path name are output.
- S: Continues processing.
- Action
- The HiRDB file can only automatically extend to a certain point. The limits to which HiRDB files can automatically extend are as follows:
- Until the automatically extended space exceeds the free space of the HiRDB file system.
- Until the automatically extended space exceeds the combined total free space on the disk and in the HiRDB file system.
- Until the HiRDB file exceeds 64 GB
- Before the maximum automatic extension of this HiRDB file is reached, do the following.
- For a user RDAREA that is not a temporary table RDAREA:
- Use the pddbls command (display the condition of the RDAREA), database condition analysis utility (pddbst), or pdfstatfs command (display the condition of the HiRDB file system area) to check the usage conditions of the target RDAREA or the HiRDB file system area, and then perform one of the following actions according to the usage conditions:
- Reorganize the RDAREA
- Expand the RDAREA
- For a temporary table RDAREA:
- Perform one of the following actions according to the situation:
- Expand the RDAREA
- Add an RDAREA
- For the applicable procedure, see the HiRDB Version 9 System Operation Guide.
KFPH22038-W L
Extent Count = aa, RDAREA "bb....bb", FILE "cc......cc"
- The number of extents of HiRDB file cc....cc of RDAREA bb....bb is equal to or greater than aa.
- aa: The extent count of the HiRDB file that undergoes automatic extension.
- {20|22|24}
- bb....bb: RDAREA name
- cc....cc: name-of-HiRDB-file-system-area\name-of-HiRDB-file
- If the path name of the HiRDB file exceeds 112 bytes, the last 112 bytes of the HiRDB file path name are output.
- S: Continues processing.
- Action
- Once the maximum number of extents for an HiRDB file (24) is reached, no further automatic extensions are possible. Before this HiRDB file reaches the maximum number of extents, do the following.
- For a user RDAREA that is not a temporary table RDAREA:
- Use the pddbls command (display the condition of the RDAREA) or database condition analysis utility (pddbst) to check the usage conditions of the RDAREA, and then take one of the following actions according to those usage conditions:
- Reorganize the RDAREA
- Consolidate the extents in the HiRDB file system area
- Expand the RDAREA
- For a temporary table RDAREA:
- Take one of the following actions according to the situation:
- Consolidate the extents in the HiRDB file system area
- Expand the RDAREA
- Add an RDAREA
- For the applicable procedure, see the HiRDB Version 9 System Operation Guide.
KFPH22039-I L
RDAREA information build retry due to RPC error occurred, return code=aa....aa, bb....bb=cc....cc
- Because an RPC error occurred when acquiring RDAREA information during back-end server or unit start processing, retry RDAREA information acquisition processing.
- aa....aa: Error code
- For details, see 4.1 Detail codes for RPC-related errors.
- bb....bb: Processing target
- server: Back-end server
- unit: Unit
- cc....cc: Back end server name or unit name
- S: Continues processing.
KFPH23001-E L
No "pdbuffer" statements
- The pdbuffer operand is missing in the system common definition.
- S: Terminates abnormally.
- Action
- Add the pdbuffer operand to the system common definition.
KFPH23002-E L
Invalid "pdbuffer" statement due to aa....aa bb....bb
- Invalid pdbuffer operand was detected.
- aa....aa: Cause of error:
- duplicate buffer pool name: Buffer pool name is duplicated.
- duplicate RDAREA: RDAREA is duplicated.
- invalid index name: Index name is invalid.
- invalid RDAREA name: The RDAREA name is invalid.
- bb....bb: RDAREA name, index name, or buffer pool name
- S: Terminates abnormally.
- Action
- Revise the pdbuffer operand in the system common definition, and restart HiRDB.
KFPH23003-E L
Insufficient memory on PROCESS, size=aa....aa
- A memory shortage occurred in the process private area during server startup.
- aa....aa: Size (in bytes) of area that was to be allocated
- S: Terminates abnormally.
- Action
- Re-evaluate the number of processes, etc., and restart HiRDB.
KFPH23004-E L
Insufficient memory on DYNAMIC_SHMPOOL for global buffer pool, size=aa....aa
- There is not enough shared memory to use a global buffer pool.
- aa....aa: Size (in bytes) of area that was to be allocated
- S: Terminates abnormally.
- Action
- Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action.
KFPH23005-E L
Failed to allocate global buffer pool, errno=aa
- Allocation of global buffer failed.
- aa: Error code:
- 4: Shared memory page fixing failed.
- 8: Internal HiRDB resource shortage occurred.
- 16: Number of shared memory segments exceeded the maximum.
- 20: Memory shortage occurred.
- 24: Shared memory segment size exceeded the maximum.
- 28: Number of global buffers exceeded the maximum.
- 32: Overflow occurred during calculation of shared memory size.
- 36: Number of shared memory identifiers exceeded the maximum.
- S: Terminates abnormally.
- Action
- Take action based on the error code:
- 4: An attempt to page-fix shared memory segments failed.
- Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and take either of the following actions:
- If KFPO00107-E "shmctl(ommfixed)" failed errno=1 is output:
See message KFPO00107-E and take the corrective actions described there.
- If KFPO00107-E "shmctl(ommfixed)" failed errno=12 is output:
If shared memory segments do not need to be page-fixed, specify free in the pd_dbbuff_attribute operand, or omit specification of the operand.
If you want to page-fix the shared memory segments, take either of the following actions:
Increase the real memory.
Reduce the size of the shared memory by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.
- 8: Take either of the following actions:
- Other than Windows edition (32-bit mode):
- HiRDB can manage up to 16 shared memory segments, but this maximum has been exceeded. Take one of the following actions:
- Increase the value specified for the SHMMAX operand in the system common definition or unit control information definition.
In UNIX, use the OS's sam command to set the value of the shmmax parameter (kernel parameter) to a value greater than or equal to the specified value for the SHMMAX operand. After shmmax is modified, the operating system must be rebooted.
- Reduce the number of shared memory segments to no more than 16 by decreasing the number of global buffers or buffer sectors defined in the server where the error occurred.
- Windows edition (32-bit mode):
- The number of shared memory segments that HiRDB can manage has exceeded the maximum value (the value specified in the pd_max_dbbuff_shm_no operand in the system definition). Set the values of the global buffer pool shared memory size, pd_max_dbbuff_shm_no operand, and SHMMAX operand such that the following formula is satisfied:
Global buffer pool shared memory size (in MB) < value of pd_max_dbbuff_shm_no value of SHMMAX |
- 16: Use the OS's sam command to increase the value of the operating system parameter (kernel parameter) shmseg. After shmseg is modified, the operating system must be rebooted.
- 20: Refer to system call=shmat, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action. Note that no action is required if this message is output during termination processing of HiRDB, and processing terminates normally (message KFPS01850-I is output).
- If this does not resolve the problem, it is possible that contiguous free space (memory) for allocating global buffer shared memory for processes was not allocated because the value specified in the SHMMAX operand in the system common definition (pdsys) is too large. Take either of the following actions:
- Other than Windows edition (32-bit mode):
No. | Operand in the system common definition (pdsys) (abnormal termination status) | Action |
---|
pd_dbbuff_modify | pd_jp1_use |
---|
1 | N, or not specified | -- | Recover according to the following steps:
- Reduce the value specified in the SHMMAX operand to be the minimum value that satisfies the formula below, and then allocate the global buffer by partitioning the current global buffer shared memory into segments.
(value specified in SHMMAX) 16 (global buffer pool shared memory size)
- Use pdstart command to restart HiRDB.
|
2 | Y | Y | Recover according to the following steps:
- Set the pd_jp1_use operand to N, and then use the pdstart command to restart HiRDB. If you cannot restart, skip step 2 and proceed to step 3.
- Use the pdstop command to terminate HiRDB normally.
- Reduce the value specified in the SHMMAX operand to be the minimum value that satisfies the formula in No. 1.
- Set the pd_jp1_use operand back to Y, and then use the pdstart command to start HiRDB normally.
Note that, because the pd_jp1_use operand is temporarily set to N, JP1 is not notified of HiRDB events that occur while responding to this error (steps 1 and 2). Therefore, make copies if necessary of the syslogfile or message log files to which HiRDB messages are output. If any of these events require corrective action, check the syslogfile or message log files and take the necessary action.
|
3 | Y | N, or not specified | If this error occurred during normal startup of HiRDB, take the actions in No. 1. Otherwise, change the value specified in the SHMMAX operand, and then perform a forced startup of HiRDB. At that point, the database will need to be recovered. The procedure is as follows:
- Reduce the value specified in the SHMMAX operand to the minimum value that satisfies the formula in No.1.
- Unload the logs since the logs shown in the last synchronization point completion message (KFPS02183-I).
- Use the pdstart -r command to start HiRDB.
- Use the pdrstr command to recover the master directory RDAREA to the most recent synchronization point.
- Use the pdstop command to terminate HiRDB normally.
- Use the command pdstart dbdestroy to perform a forced startup of HiRDB.
- Use the pdrstr command to recover the RDAREAs other than the master directory RDAREA to the most recent synchronization point.
|
- Legend:--: Not applicable
- Windows edition (32-bit mode):
No. | Operand in the system common definition (pdsys) (abnormal termination status) | Action |
---|
pd_dbbuff_modify | pd_jp1_use |
---|
1 | N, or not specified | -- | Recover according to the following steps:
- Set a value in the SHMMAX operand that is smaller than the value at the time of abnormal termination, reduce the maximum partition size for the shared memory in a single global buffer.
- Set the pd_max_dbbuff_shm_no operand to a value that is greater than or equal to global buffer pool shared memory size
value of SHMMAX, and then increase the maximum number of shared memory segments. - Use pdstart command to restart HiRDB.
|
2 | Y | Y | Recover according to the following steps:
- Set the pd_jp1_use operand to N, and then use pdstart command to restart HiRDB. If you cannot restart, skip step 2 and proceed to step 3.
- Use the pdstop command to terminate HiRDB normally.
- Execute steps 1 and 2 in No. 1 above.
- Set the pd_jp1_use operand back to Y, and then use the pdstart command to start HiRDB normally.
Note that, because the pd_jp1_use operand is temporarily set to N, JP1 is not notified of HiRDB events that occur while responding to this error (steps 1 and 2). Therefore, make copies if necessary of the syslogfile or message log files to which HiRDB messages are output. If any of these events require corrective action, check the syslogfile or message log files and take the necessary action.
|
3 | Y | N, or not specified | If this error occurred during normal startup of HiRDB, take the actions in No. 1. Otherwise, change the value specified in the SHMMAX operand, and then perform a forced startup of HiRDB. At that point, the database will need to be recovered. The procedure is as follows:
- Execute steps 1 and 2 in No. 1 above.
- Unload the logs since the logs shown in the last synchronization point completion message (KFPS02183-I).
- Use the pdstart -r command to start HiRDB.
- Use the pdrstr command to recover the master directory RDAREA to the most recent synchronization point.
- Use the pdstop command to terminate HiRDB normally.
- Use the command pdstart dbdestroy to perform a forced startup of HiRDB.
- Use the pdrstr command to recover the RDAREAs other than the master directory RDAREA to the most recent synchronization point.
|
- Legend:--: Not applicable
- 24: Take either of the following actions:
- In UNIX:
The management area size used by the global buffer shared memory exceeded 16
value of shmmax in the operating system parameters, or exceeded the value specified in the SHMMAX operand value in the system definition. This management area cannot be partitioned using the value of the SHMMAX operand. Therefore, calculate the value of shmmax or the value of the SHMMAX operand in the system definition using the formula below, and then change them to the largest value. The OS's sam command can be used to modify the specified shmmax value. After shmmax is modified, the operating system must be rebooted.
- In Windows:
The management area size used by the global buffer shared memory exceeded the value specified in the SHMMAX operand value in the system definition. This management area cannot be partitioned using the value of the SHMMAX operand in the system definition. Therefore, calculate the value of the SHMMAX operand using the formula below, and then change it to the largest value. If this memory size did not exceed the specified SHMMAX operand value, the work file in the HiRDB installation directory might have been deleted while HiRDB was operating. In this case, restart the HiRDB service.
No. | HiRDB type | Value specified in pd_dbbuff_modify operand | Management area size used by the shared memory for one global buffer (MB) |
---|
1 | Single Server, or Parallel Server (non-effects distributed environment) | N | A p![[Figure]](figure/zueng010.gif) p 1,024 1,024![[Figure]](figure/zueng010.gif) |
2 | Y | A p![[Figure]](figure/zueng010.gif) p 1,024 1,024 + B 1,024![[Figure]](figure/zueng010.gif) |
3 | Parallel Server (effects distributed environment) | -- | C p![[Figure]](figure/zueng010.gif) p 1,024 1,024![[Figure]](figure/zueng010.gif) |
- A: Use the value calculated from Formula 1 in When the standby-less system switchover (effects distributed) facility is not used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide.
- B: Use the value calculated from Formula 2 in When the standby-less system switchover (effects distributed) facility is not used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide. Use the following value for the value of a in formula 2:
- a =
A
p![[Figure]](figure/zueng010.gif)
p
1,024
- C: Use the value calculated from the management region part in When the standby-less system switchover (effects distributed) facility is used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide.
- p: In Windows, if fixed is specified in the pd_dbbuff_attribute operand in the system common definition or unit control information definition, use the Windows Large Page page size. Otherwise, use a value of 1.
- 28: The upper limit on the number of global buffers that can be defined on a server was exceeded. Reduce the number of global buffers defined on this server.
- 32: Take the following action:
- In 32-bit mode:
Overflow occurred during calculation of the shared memory size; reduce the shared memory size to no more than 231 - 1 bytes by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.
- In 64-bit mode:
Overflow occurred during calculation of the shared memory size; reduce the shared memory size to no more than 263 - 1 bytes by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.
- 36: See system call=shmget, errno=28, mnemonic=ENOSPC in 4.3 System call return codes to investigate and resolve the error, and take corrective action.
KFPH23006-E L
Failed to allocate semaphore, errno=aa....aa
- Allocation of a semaphore resource failed.
- aa....aa: Error cause code:
- 4: The semaphore count per semaphore identifier exceeded the maximum value of the system.
- 8: The number of semaphores used by the entire system or the number of semaphore identifiers exceeded the maximum value of the system.
- S: Terminates abnormally.
- Action
- Take the following action according to the error cause code:
- 4: Set the maximum semaphore count (in Solaris, seminfo_semmsl; in Linux, SEMMSL) per semaphore identifier in the operating system parameters to 64 or more.
- 8: Take one of the following actions:
- Increase the maximum semaphore count in the system (in HP-UX, semmns; in Solaris, seminfo_semmns; and in Linux, SEMMNS).
- Increase the maximum semaphore identifier count (in HP-UX, semmni; in Solaris, seminfo_semmni; in Linux, SEMMNI; and in Windows, PDUXPLSEMMAX).
- Decrease the specified count of the pdbuffer operand.
- Decrease the value of the pd_max_users operand.
KFPH23007-E L
File aa....aa bb....bb error
- File access failed.
- aa....aa: File name
- The file name is displayed by the absolute path. If it exceeds 159 characters, the last 159 characters of the file path name are output.
- bb....bb: File access function:
- close: Close file
- create: Create file
- open: Open file
- read: Read file
- write: Write to file
- S: Terminates abnormally.
- Action
- Take action appropriate to the KFPO00107-E message that was issued immediately before this message.
KFPH23008-W L
No file "pdbufenv"
- The pdbufenv file that was created during single server (HiRDB/Single Server) or dictionary server (HiRDB/Parallel Server) startup was not found.
- S: Resumes processing.
- Action
- The system creates the corresponding file according to the pdbuffer operand specification. Therefore, if the buffer structure is different from the previous session and the specification is made so that a buffer is not allocated to the RDAREA subject to recovery during restart, the corresponding RDAREA will be placed on shutdown status. In such a case, recover the RDAREA with the database recovery utility.
KFPH23009-E L
System call error func=aa....aa, errno=bb....bb
- A system call error occurred.
- aa....aa: Name of system call
- bb....bb: Error number set in errno
- S: Terminates abnormally.
- Action
- Check the meaning of the errno (external integer function indicating the error status), refer to errno.h or the applicable OS manual to eliminate the cause of the error, then restart HiRDB.
KFPH23010-E L
Insufficient memory on PROCESS for work I/O buffer, size=aa....aa
- Buffer for batch I/O cannot be allocated due to a shortage in the process private area.
- aa....aa: Size (in bytes) of area that was to be allocated
- S: Terminates processing.
- Action
- Reduce the number of batch I/O pages and re-execute the database load utility or database reorganization utility.
KFPH23011-W L
Invalid SHMMAX statement due to aa....aa bb....bb
- The SHMMAX operand is invalid in the system common definition or unit control information definition.
- aa....aa: Cause of error:
- out of range: Specified value is outside the permitted range.
- no value: Specified value is not a numeric value.
- bb....bb: Specified value (up to the first 30 characters)
- S: Resumes processing assuming the default value of the SHMMAX operand as the maximum segment size for shared memory.
- Action
- If the sum of the sizes of global buffer pools in the server exceeds the default value of the SHMMAX operand, multiple shared memory segments are allocated, thereby reducing throughput. Correct the SHMMAX operand.
KFPH23012-E L
No necessary option for "pdbuffer" aa....aa
- A required option is missing in the pdbuffer operand specification.
- aa....aa: Name of required option
- S: Terminates abnormally.
- Action
- Specify the required option and restart HiRDB.
KFPH23013-W L
Failed to allocate index buffer pool aa....aa due to DATA DICTIONARY search failed SQLCODE=bbbb
- A global buffer pool dedicated to indexes cannot be allocated because dictionary retrieval failed.
- aa....aa: Name of buffer pool
- bbbb: SQL code
- S: Resumes processing without creating a global buffer pool dedicated to indexes. If a buffer pool has been defined for index RDAREAs, uses that buffer pool. If there is no such buffer pool definition but a buffer pool has been defined for OTHER (pdbuffer -o specification), uses the defined buffer pool.
- Action
- If the global buffer pool dedicated to indexes is necessary, take action appropriate to the SQL message issued immediately before this message and restart HiRDB.
KFPH23014-W L
Failed to allocate index buffer pool aa....aa due to no index bb....bb
- A global buffer pool dedicated to indexes cannot be allocated, because the index specified in the pdbuffer operand was not found.
- aa....aa: Name of buffer pool
- bb....bb: Name of index
- S: Resumes processing without creating a global buffer pool dedicated to indexes. If a buffer pool has been defined for index RDAREAs, uses that buffer pool. If there is no such buffer pool definition but a buffer pool has been defined for OTHER (pdbuffer -o specification), uses the defined buffer pool.
- Action
- If the specified index has been deleted, delete the corresponding definition from the pdbuffer operand. If the specified index name is invalid, correct the pdbuffer operand specification and restart HiRDB.
KFPH23015-E L
System error, func "aa....aa", code=bbbbbb
- A HiRDB function error occurred.
- aa....aa: Function name
- bbbbbb: Error code
- S: Terminates abnormally.
- Action
- From the event log (in UNIX, syslogfile) or the message log file, determine if any messages were output before or after this message. If any other messages were output, take action according to those messages. If there are no other messages, find bbbbbb in 4.2 Detail codes for system-related errors, eliminate the cause of the error, and then restart HiRDB. If you cannot determine the cause of the error, contact the customer support center.
KFPH23016-E L
Invalid "pdbuffer" statement due to operand combination error, global buffer pool name=aa....aa
- Contradictory operands were specified in the pdbuffer statement.
- aa....aa: Name of buffer pool
- S: Terminates abnormally.
- Action
- Mutually exclusive options (-r, -i, -o) were specified in a pdbuffer operand specified in the system common definition. Correct the specification so that the -r, -i, and -o options are specified in a different pdbuffer operand.
KFPH23017-W L
Invalid "pdbuffer" statement due to no RDAREA aa....aa
- The RDAREA specified with the -r in the pdbuffer operand cannot be found in HiRDB system.
- aa....aa: RDAREA name
- S: Resumes processing.
- Action
- Correct the pdbuffer operand in the system common definition.
KFPH23018-W L
Failed to allocate global buffer pool aa....aa due to page size exceeds buffer size for RDAREA bb....bb
- System could not allocate a global buffer pool, because the RDAREA page size was greater than the global buffer size.
- aa....aa: Global buffer pool name
- bb....bb: RDAREA name
- S: Resumes processing without allocating a global buffer pool for this RDAREA.
- O: To access this RDAREA, either increase the buffer size specified in the -l option of the pdbuffer statement in the system common definition or delete the -l option, then restart HiRDB.
KFPH23020-E L
Failed to allocate LOB buffer pool aa....aa due to invalid RDAREA type bb....bb
- A LOB global buffer is not allocated to areas other than the LOB RDAREA.
- aa....aa: Name of the global buffer pool
- bb....bb: RDAREA name
- S: Terminates abnormally.
- Action
- Specify the LOB RDAREA in the pdbuffer operand of the system common definition.
KFPH23021-E L
Unmatched global buffer definition(standby=aa....aa,current=bb....bb)
- The global buffer definitions in the standby system and running system do not match. This error message is output when all of the following conditions are met:
- The running global buffer definition was modified when the standby system was in standby status.
- After independently stopping, and then restarting the running system, the running system was switched over to the standby system without restarting.
- aa....aa: Maintenance information 1
- bb....bb: Maintenance information 2
- S: Abnormally terminates.
- Action
- Restart HiRDB.
KFPH23022-E L
Global buffer pool undefined in standby server,RDAREA="aa....aa" standby unit=bbbb standby server=cc....cc
- No global buffers were defined in the RDAREA in the alternate BES.
- aa....aa: RDAREA name
- bbbb: Unit identifier of the alternate BES unit
- cc....cc: Alternate BES name
- S: Abnormally terminates.
- Action
- Allocate the global buffer that the alternate BES uses by specifying the -c option or -o option of the pdbuffer operand. Then, restart HiRDB.
KFPH23023-I L
Unit is down because pd_db_io_error_action=unitdown
- When unitdown is specified in the pd_db_io_error_action operand, HiRDB (unit for HiRDB/Parallel Server) abnormally terminates because an RDAREA I/O error occurred.
- S: Abnormally terminates.
- Action
- Eliminate the cause of the I/O error based on the error message KFPH22003-E, KFPH22007-E, or KFPH23100-E that was output before this message.
KFPH23024-I L
pd_db_io_error_action=unitdown is ineffective
- When unitdown is specified in the pd_db_io_error_action operand, the error shutdown process is performed on the RDAREA because HiRDB (unit for HiRDB/Parallel Server) abnormally terminated and another I/O error was issued.
- S: Continues processing.
KFPH23025-E L
Insufficient memory on PROCESS for work I/O buffer,size=aa....aa
- No local buffers for random access could be secured due to insufficient process private area.
- aa....aa: Area size attempted to be secured (in kilobytes).
- S: Terminates processing.
- Action
- Reduce the number of buffer sectors for local buffers for random access, and then re-execute pdload or pdrorg.
KFPH23026-E L
Insufficient memory on PROCESS,size=aa....aa
- There was insufficient process private area when creating the local buffer environment.
- aa....aa: Area size attempted to be secured (in kilobytes).
- S: Terminates processing.
- Action
- Re-evaluate the process count and other values, and then re-execute pdload or pdrorg.
KFPH23027-W L
Undefined global buffer pool with '-c' option,RDAREA="aa....aa"
- A global buffer pool with the -c option specification has not been defined.
- aa....aa: RDAREA name
- S: The RDAREA is placed in closed status, and processing continues.
- Action
- RDAREAs of units for which the standby-less system switchover (effects distributed) facility applies must have a global buffer assigned with the -c option specified. Specify the -c option with the system common definition pdbuffer operand, and assign global buffers to unallocated RDAREAs.
KFPH23028-W L
Too small '-o' option global buffer size,added RDAREA="aa....aa",global buffer size=bbbbb,page size=ccccc
- The buffer size bbbbb of the global buffer specified with the -o option is smaller than the page length ccccc of the added RDAREA "aa....aa".
- aa....aa: RDAREA name
- bbbbb: Buffer size of global buffer
- ccccc: Page length of added RDAREA
- S: Continues processing.
- O: If the global buffer was assigned to RDAREA "aa....aa" specifying the -o option, use the pdstop command to perform a normal termination or a planned termination of HiRDB, restart HiRDB, and assign the global buffer. If the pdstop -u command is used to terminate the unit, which is then restarted and the global buffers assigned, the buffer size of the global buffers will be different from that of other units specified with the -o option, which may cause the RDAREA to shut down during system switchover.
KFPH23029-E E+L
Number of "pdbuffer" statements exceeds the limit
- The number of pdbuffer system definitions exceeded the upper limit.
- S: Terminates abnormally.
- Action
- The upper limit on the number of pdbuffer system definitions is 2,000,000 for HiRDB/Single Server, and 2,147,483,647 for HiRDB/Parallel Server. Reduce the number of pdbuffer system common definition, and restart HiRDB.
KFPH23030-I L
Dynamic update of global buffer information,(server=aa....aa, additional poolno=bb....bb, addtional shmno=cc....cc)
- Displays information about the dynamic update of global buffers for each server.
- aa....aa: Server identifier
- bb....bb: Number of global buffer pools that can be added
- cc....cc: Number of shared memory segments that can be added
- S: Continues processing.
KFPH23031-E L
The definition related to global buffer pool is disagreement, last time=aa....aa this time=bb....bb, errno=cc
- HiRDB could not be restarted after the following operations:
- Deleting a global buffer using the pdbuffer operand
- Reducing the value of the pd_max_add_dbbuff_no operand
- Reducing the value of the pd_max_add_dbbuff_shm_no operand
- aa....aa: Information about the previous operation
- For each error code, server-specific information about the previous operation is displayed.
- 4: Sum of the number of global buffers and the number of global buffers that can be added dynamically
- 8: Sum of the number of index global buffers and the number of global buffers that can be added dynamically
- 16: Number of shared memory segments that can be added
- bb....bb: Information about the current operation
- For each error code, server-specific information about the current operation is displayed.
- 4: Sum of the number of global buffers and the number of global buffers that can be added dynamically
- 8: Sum of the number of index global buffers and the number of global buffers that can be added dynamically
- 16: Number of shared memory segments that can be added
- cc: Error code
- S: Terminates abnormally.
- Action
- Take action appropriate to the error code:
Error code | Action |
---|
4 | Either the pdbuffer operand was added or the value of the pd_max_add_dbbuff_no operand was reduced. Reset the pdbuffer and pd_max_add_dbbuff_no operands to their previous values, and then restart HiRDB. |
8 | Either the pdbuffer -i operand was added or the value of the pd_max_add_dbbuff_no operand was reduced. Reset the pdbuffer-i and pd_max_add_dbbuff_no operands to their previous values, and then restart HiRDB. |
16 | The value of the pd_max_add_dbbuff_shm_no operand was reduced. Restore the pd_max_add_dbbuff_shm_no operand to its previous value, and then restart HiRDB. |
KFPH23032-E L
Overflow error occurred by size calculation of memory
- An overflow occurred during memory size calculation.
- S: Terminates abnormally.
- Action
- Take the following steps to ensure the memory size is less than or equal to 231-1 (or 263-1 in 64-bit mode) bytes:
- Reduce the number of global buffers specified in the system common definition
- If in-memory data processing is being used, reduce the values of the operand pd_max_resident_rdarea_no (the number of in-memory RDAREAs) and the operand pd_max_resident_rdarea_shm_no (the number of shared memory segments used by in-memory data buffers)
KFPH23033-E L
Status file allocation failed due to exceed the allocate limit size, server=aa....aa, key=bbbb, size=cc....cc
- The size of data to be stored in the status file exceeded 2,147,483,647 bytes; on server aa....aa, allocation of status file records failed.
- aa....aa: Server identifier
- bbbb: Maintenance information
- cc....cc: Allocation data size
- S: Terminates abnormally.
- Action
- Change the specified values so that the result of the following formula does not exceed 2,147,483,647:
- (16 + (
(
(A
8)![[Figure]](figure/zueng010.gif)
8)
)
8)
(B + C) - A: Value specified for the pd_max_rdarea_no operand of the system common definition
- B: Number of index global buffers defined on the server
- C: Value specified for the pd_max_add_dbbuff_no operand in the server definition
KFPH23034-E L
Unable to execute dynamic update of global buffer due to use rapid or standby less system switchover facility
- The dynamic update of global buffer facility cannot be used because either the rapid system switchover facility or the standby-less system switchover facility is being used.
- S: Terminates abnormally.
- Action
- Either omit the pd_dbbuff_modify operand from the system common definition or specify N, and restart HiRDB.
KFPH23035-I L
Update page cache limit available, server name=aa....aa, limit=bb....bb
- The update buffer volume suppression facility was enabled.
- aa....aa: Server name
- bb....bb: Upper limit on the total number of update buffers on this server
- S: Continues processing.
KFPH23036-I L
Update page cache limit unavailable, server name=aa....aa
- The update buffer volume suppression facility was disabled.
- aa....aa: Server name
- S: Continues processing.
KFPH23037-I L
Changed update page cache limit, server name=aa....aa, limit=bb....bb
- The upper limit on the total number of update buffers was changed.
- aa....aa: Server name
- bb....bb: Upper limit on the total number of update buffers on this server
- S: Continues processing.
KFPH23038-E L
Number of commit write use pdreclaim exceeded "pd_max_commit_write_reclaim_no" server name=aa....aa
- The number of pdreclaim commands executed simultaneously on the server using commit output exceeds the specification value in the pd_max_commit_write_reclaim_no operand.
- aa....aa: Server name
- S: Terminates the processing.
- O: Re-execute the command after the free page release utility (pdreclaim) has terminated. Alternatively, execute the free page release utility (pdreclaim) without specifying the -p option.
- Action
- Increase the value assigned to the pd_max_commit_write_reclaim_no operand in the system common definition.
KFPH23040-I L
Unit is down because pd_db_access_error_action=unitdown
- The unit shut down because a file access error was detected in the RDAREA while a facility that shuts down the unit when a file access error is detected was enabled. Another possibility is that a file access error with respect to the master directory RDAREA was detected, so the unit shuts down.
- S: Terminates abnormally.
- Action
- Refer to one of the following messages, output immediately before this message: KFPH20005-E, KFPH22003-E, KFPH22007-E, or KFPH23100-E. Then, eliminate the cause of the file access error and restart HiRDB.
KFPH23041-I L
File for pd_db_access_error_action=unitdown "aa....aa" failed, return code=bb....bb
- The is the internal file for the shutdown if the file access error facility fails to operate.
- aa....aa: File operation contents
- {create|delete}
- bb....bb: Error codes
- S: Continues processing.
KFPH23042-E L
Insufficient system resource for access tables,max access TRNGID=aa....aabb....bb TRNBID=aa....aacc....cc tables=dd....dd,current access TRNGID=ee....eeff....ff TRNBID=ee....eegg....gg tables=hh....hh
- System resources required for accessing the table are insufficient.
On HiRDB/Parallel Server, only the number of system resources required to access the tables are prepared for each dictionary server and back-end server (system common definition pd_max_access_tables operand value
pd_max_users operand value). Whenever a transaction accesses a table, the HiRDB allocates one system resource, and then it releases that system resource when the transaction finishes. Therefore, once a transaction has accessed a table of a value equal to or greater than the pd_max_access_tables operand, there might be a shortage of system resources when a subsquent transaction attempts to access a table.
TRNGID indicates the global identifier of a transaction, and TRNBID indicates the branch identifier of a transaction. - aa....aa: Unit identifier and system identifier of the HiRDB system of the transaction that accessed the most base tables at the time the error was detected
- bb....bb: Global transaction number of the transaction that accessed the most base tables at the time the error was detected
- cc....cc: Transaction branch number of the transaction that accessed the most base tables at the time the error was detected
- dd....dd: Number of base tables accessed by the transaction that accessed the most base tables at the time the error was detected
- ee....ee: Unit identifier and system identifier of the HiRDB system of the transaction in which the error was detected
- ff....ff: Global transaction number of the transaction in which the error was detected
- gg....gg: Transaction branch number of the transaction in which the error was detected
- hh....hh: Number of base tables accessed by the transaction in which the error was detected
- S: If the error is detected in a user process, the user process terminates abnormally. If the error is detected in a rollback process, the HiRDB system terminates abnormally.
- Action
- Check whether the dd....dd value in the SQL statement in the transaction indicated by aa....aa, bb....bb, and cc....cc is equal to or less than the largest number assumed for base table accesses. If the dd....dd value is less than the assumed maximum number of base table accesses, set the value of the pd_max_access_tables operand to at least the value of dd....dd or higher. If the dd....dd value is higher than the assumed maximum number of base table accesss, revise the SQL statement so that the dd....dd value is at or below this assumed maximum.
KFPH23045-W L
Unable to fix the shared memory in the real memory,shmid=aa....aa,size=bb....bb
- The shared memory segment pages used by the global buffer pool failed to lock. Continue without locking pages.
- aa....aa: Shared memory segment identifier
- bb....bb: Size of shared memory segment (units: bytes)
- S: Continues processing.
- Action
- If you do not need to page lock the shared memory, take the following actions:
- If the shared memory is to be page-locked, perform one of the following actions:
- Restart Windows. There are times when contiguous space is established in the real memory and page locking succeeds.
- After stopping HiRDB, increase real memory and restart HiRDB.
- Stop HiRDB, lower the global buffer pool count or the buffer sector count, decrease the size of the shared memory, and then restart HiRDB.
KFPH23046-E E+L
Invalid pd_max_dbbuff_shm_no statement due to aa....aa set value=bbb before value=ccc
- HiRDB could not restart because the system definition was changed as follows:
- If the pd_dbbuff_modify operand is set to N (do not dynamically update global buffers), the value of the pd_max_dbbuff_shm_no operand was reduced.
- If the pd_dbbuff_modify operand is set to Y (dynamically update global buffers), the value of the pd_max_dbbuff_shm_no operand was changed.
- aa....aa: Cause of error
- low value: The current value is smaller than the value that was specified the last time HiRDB was started.
- different value: The current value is different from the value that was specified the last time HiRDB was started.
- bbb: Current value
- ccc: Value that was specified the last time HiRDB was started
- S: Terminates abnormally.
- Action
- Take the following action:
- If the cause of error (aa....aa) is low value:
In the pd_max_dbbuff_shm_no operand, specify a value that is greater than or equal to the value that was specified the last time HiRDB was started, and then restart HiRDB.
- If the cause of error (aa....aa) is different value:
Restore the value of the pd_max_dbbuff_shm_no operand to the value before the change, and then restart HiRDB.
KFPH23047-I L
Unit is down because pd_db_hold_action=unitdown
- The unit was shut down due to detection of an RDAREA access error, which occurred because the unit shutdown facility was being used when a physical error was detected.
- S: Terminates abnormally.
- Action
- Refer to the error messages output before this one, eliminate the cause of the error shutdown, and restart HiRDB. Error messages output before this one might include KFPH22003-E, KFPH22015-E, KFPH23100-E, and KFPH27007-E.
- If it is not possible to eliminate the cause of the error shutdown, change the value of the pd_db_hold_action operand in the system common definition to dbhold, and then restart HiRDB. Because the RDAREA was shut down due to an error, recover the RDAREA if necessary.
KFPH23048-I L
Sum of memory for global buffer pool size=aa....aa, server=bb....bb
- On server bb....bb, shared memory of size aa....aa was allocated as a global buffer.
If the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server. - aa....aa: Size of shared memory allocated as global buffer (bytes)
- bb....bb: For a server, the server name is output. For a unit, ******** is output.
- S: Continues processing.
KFPH23049-W L
Sum of memory for global buffer pool too large, server=aa....aa
- On server aa....aa, the shared memory allocated as a global buffer exceeded 1.2 GB. HiRDB might not start because the shared memory allocated as a global buffer is too large for the shared memory to be attached.
Note that if the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server. - aa....aa: For a server, the server name is output. For a unit, ******** is output.
- S: Continues processing.
- Action
- In Windows in 64-bit mode, and when HiRDB is running in 32-bit emulation mode
- Ignore this message. If you want to suppress the output of this message, you can set the pd_shared_memory_report operand in the system definition to N, or use suppression of output messages to the event log (the pdmlgput operand in the system definition).
- If this message is output when the HiRDB environment is being created
- A list of explanations and actions is provided in the following table:
Explanation | Action |
---|
In 32-bit mode Windows, up to 2 GB of memory can be allocated per process. When a process is attached to the shared memory of the global buffer pool, it allocates a process memory area that is the size of the pool. Because it is using memory outside the global buffer pool, there might not be enough free memory when the pool size is greater than 1 GB. | Do not allocate more than 1 GB of shared memory per server as a global buffer pool. |
Memory is allocated when a process loads a library, but when multiple libraries are loaded, fragmentation of the memory area can occur. As a result, even when there is enough free memory to attach the process to shared memory, a memory shortage error might occur if the required contiguous area cannot be allocated. This is more likely to occur when plug-ins are used or the system is linked to JP1. Even when HiRDB starts successfully, depending on the amount of fragmentation of the memory area, memory shortage errors might cause an online unit to shut down, or prevent HiRDB from restarting, or leave HiRDB unable to start. | In the cases listed below, use the SHMMAX operand in the HiRDB system definition and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments. For details about these operands, see the manual HiRDB Version 9 System Definition.
- A large shared memory is allocated as a global buffer pool.
- Plug-ins are used.
- The system is linked to JP1 (the pd_jp1_use operand is set to Y).
|
- If this message is output when HiRDB is already running:
- Perform the operational checks listed below and check for problems. Note that these operational checks must be repeated if you make changes to definitions that affect the size of the shared memory (including outside the global buffer pool), or start using JP1/Base or a new plug-in. The operational checks are as follows:
- Because HiRDB might fail to start if problems occur during these operational checks, make backups and other preparations for recovery. If the pd_dbbuff_modify operand is set to Y, change the value to N temporarily, because when problems occur it will be necessary to perform a forced startup of HiRDB and recover the database.
- While the transaction that is updating the database is executing, terminate HiRDB forcibly, restart, and then make sure that the rollback was successfully completed. In HiRDB/Parallel Server, all the back-end servers must be checked.
- If HiRDB fails to restart as a result of check 2 above and message KFPH23005-E is output with error code 20, it is not able to operate with the current global buffer allocation. After restarting in accordance with the corrective actions in message KFPH23005-E, it will be necessary to review and, if necessary, revise the allocation of the global buffer.
- If problems are discovered when you perform these operational checks, take one of the corrective actions listed below, and then repeat the operational checks.
- Change the allocation of the global buffer to reduce the shared memory size.
- Reduce the size of shared memory used by HiRDB outside of the global buffer.
- Use the SHMMAX operand and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments.
KFPH23050-I L
Max of memory for global buffer pool management area size=aa....aa, server=bb....bb
- On server bb....bb, the maximum management area size used by the global buffer shared memory is aa....aa.
If the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server. - aa....aa: Maximum management area size used by the global buffer shared memory (bytes).
- bb....bb: For a server, the server name is output. For a unit, ******** is output.
- S: Continues processing
KFPH23051-W L
Maximum-shared-memory-segment-size for global buffer pool too large,server=aa....aa
- On server aa....aa, the value specified in the SHMMAX operand exceeds 200 MB (50 MB if the global buffer dynamic update function is used (pd_dbbuff_modify=Y)). HiRDB might not be able to start because the maximum shared memory segment size (the value specified in the SHMMAX operand) is too large and the shared memory cannot be attached.
If the standby-less system switchover (effects distributed) facility is used, this message is output per-unit rather than per-server. - aa....aa: For a server, the server name is output. Forf a unit, ******** is output.
- S: Continues processing
- Action
- In Windows in 64-bit mode, and when HiRDB is running in 32-bit emulation mode
- Ignore this message. If you want to suppress the output of this message, you can set the pd_shared_memory_report operand in the system definition to N, or use suppression of output messages to the event log (the pdmlgput operand in the system definition).
- If this message is output when the HiRDB environment is being created
- Take the following actions:
- Under normal conditions:
Omit specification of the SHMMAX operand (the assumed default value is 200) and the pd_max_dbbuff_shm_no operand (the assumed default value is 16).
However, if pd_dbbuff_modify = Y is specified, specify a value less than or equal to 50 in the SHMMAX operand. In the pd_max_dbbuff_shm_no operand, specify a value greater than the result of the following calculation:
amount of shared memory required for global buffer
value of SHMMAX operand![[Figure]](figure/zueng010.gif)
To calculate the amount of shared memory required for the global buffer, see Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide, or check the KFPH23048-I message that was output during HiRDB startup.
- If message KFPH23005-E (error code 24) is output when HiRDB starts:
Estimate the management area size used by the global buffer shared memory, and then specify the smallest possible value in the SHMMAX operand. To calculate the amount of shared memory required for the global buffer, see Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide, or check the KFPH23048-I message that was output during HiRDB startup.
If the management area size used by the global buffer shared memory is greater than 200 MB (50 MB if the global buffer dynamic update funtion is used), revise the value specified in the operand for the global buffer (the pdbuffer operand).
In addition, if the value of the SHMMAX operand changes, re-estimate the number of required resources (size of required shared memory) specified in the pd_max_dbbuff_shm_no operand and the value of the system environment variable PDUXPLSHMMAX.
- If this message is output when HiRDB is already running
- Take one of the actions indicated below:
- Change the allocation of the global buffer to reduce the shared memory size.
- Reduce the size of shared memory used by HiRDB outside of the global buffer.
- Use the SHMMAX operand and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments.
- After taking one of these actions, perform the operational checks listed below and check for problems. Note that the operational checks must be repeated if you make changes to definitions that affect the size of the shared memory (including outside the global buffer pool), or start using JP1/Base or a new plug-in. The operational checks are as follows:
- Because HiRDB might fail to start if problems occur during these operational checks, make backups and other preparations for recovery. If the pd_dbbuff_modify operand is set to Y, change the value to N temporarily, because when problems occur it will be necessary to perform a forced startup of HiRDB and recover the database.
- While the transaction that is updating the database is executing, terminate HiRDB forcibly, restart, and then make sure that the rollback was successfully completed. In HiRDB/Parallel Server, all the back-end servers must be checked.
- If HiRDB fails to restart as a result of check 2 above and message KFPH23005-E is output with error code 20, it is not able to operate with the current global buffer allocation. After restarting in accordance with the corrective actions in message KFPH23005-E, it will be necessary to review and, if necessary, revise the allocation of the global buffer.
KFPH23100-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: Close HiRDB file
- creat: Create HiRDB file
- open: Open HiRDB file
- read: Read HiRDB file
- write: Write to HiRDB file
- bb....bb: HiRDB system error code
- cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file system area exceeds 131 characters, the last 131 characters of HiRDB file system area path name are output.
- S: Terminates processing.
- Action
- Refer to 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.
- If the inner replica facility is used, and aa....aa is write, and bb....bb is -1544:
- It is possible that a replica RDAREA is not in command shutdown or closed status and is paired with a volume. This phenomenon can occur when a system in this state executes any of the following:
- Definition SQL (For details about definition SQL when using the inner replica facility, see the HiRDB Version 9 Staticizer Option Description and User's Guide)
- Integrity check utility (pdconstck)
- Update SQL for the relevant RDAREA (INSERT statement, UPDATE statement, DELETE statement, and PURGE TABLE statement)
- Utilities for the relevant RDAREA (pdload, pdrorg, pdreclaim, and plug-in utilities)
- If this phenomenon occurs, check the status of the volume.
- If it is paired
Separate the pair volume, and then use the pdrels command to release the shutdown. If the relevant RDAREA is no longer going to be used, use the pdhold command to put it in command shutdown and closed status.
- If it is not paired
If the RDAREA is shut down, recover it with the database recovery utility.
- Other than above:
- If the RDAREA is shut down, recover it with the database recovery utility.
KFPH23101-E L
DB destruction information, requst=(rdid=aa....aa, pgid=bb....bb, pgno=cc....cc, fno=dd....dd), buff=(pgid=ee....ee, pgno=ff....ff, fno=gg....gg)
- Displays maintenance information when a buffer error was detected.
- aa....aa: Requested RDAREA ID
- bb....bb: Requested table number or index number
- cc....cc: Requested page number
- dd....dd: Requested file number
- ee....ee: Table number or index number in buffer
- ff....ff: Page number in buffer
- gg....gg: File number in buffer
- S: Terminates processing. At this time, the RDAREAs (excluding master directory RDAREAs) might shut down.
- Action
- Contact the customer support center. If any RDAREAs were shut down, use the database recovery utility to recover them.
- If Real Time SAN Replication with the log-only synchronous method is being used and this message is output with respect to a master directory RDAREA at a log application site, it is possible that system log application processing was not performed, even though the database structure modification utility (pdmod) was executed at the transaction execution site. If that is the case, perform system log application processing.
KFPH23201-W L
HiRDB file open retry due to insufficient open resource, code=aaaaa
- A resources shortage occurred when a HiRDB file was being opened.
- aaaaa: HiRDB system error code
- S: Continues processing.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.
KFPH23202-W L
HiRDB DB read retry due to time stamp invalid, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc
- Reading from the database will be retried because of an invalid page time stamp.
- aa....aa: RDAREA name
- bb....bb: HiRDB file name
- If the name of HiRDB file exceeds 91 characters, the last 91 characters of HiRDB file name are output.
- cc....cc: Relative byte position (in decimal) from the beginning of HiRDB file of the page where the invalid time stamp was detected
- S: Continues processing.
- O: If the RDAREA is shut down immediately after this message is output, contact the customer support center. Save the summary dump that is output under %PDDIR%\spool.
- If the RDAREA is not shut down immediately after this message is output, a temporary disk I/O failure has occurred. Examine the disk that holds HiRDB file displayed in the message.
- Action
- Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool.
KFPH23203-E L
Process wait count unmatch,server name=aa....aa wait buffer count=bb....bb wait process count=cc....cc
- A process waiting counter conflict was detected during the default write process.
- aa....aa: Server name
- bb....bb: number of buffer resources that are being waiting upon
- cc....cc: Number of processes waited on by the semaphore
- S: Continues processing.
- Action
- See Facility for acquiring syncpoint output synchronization control information in the HiRDB Version 9 System Operation Guide.
KFPH23204-E L
Process wait count unmatch,process id=aa....aa flag count=bb....bb semaphore count=cc....cc
- A process wait count conflict was detected.
For HiRDB/Single Server:
A process wait counter conflict was detected in the single server process.
For HiRDB/Parallel Server:
A process wait counter conflict was detected in the back-end server process or the dictionary server process. - aa....aa: Conflict detection process number
- bb....bb: Flag change count
- cc....cc: Semaphore operation count
- S: Terminates abnormally (shuts down the unit).
- Action
- See Facility for acquiring syncpoint output synchronization control information in the HiRDB Version 9 System Operation Guide.
KFPH23205-E L
Number of resident RDAREA exceeds "pd_max_resident_rdarea_no", resident RDAREA no=aa....aa, request=bb....bb, server=cc....cc
- The number of in-memory RDAREAs exceeded the value of the pd_max_resident_rdarea_no operand.
- aa....aa: Number of RDAREAs already allocated in memory
- bb....bb: Number of RDAREAs requested to be allocated in memory
- cc....cc: Server identifier
- S: Terminates processing.
- Action
- See Amount of memory required during in-memory data processing in the HiRDB Version 9 Installation and Design Guide, and check that no errors were made in the estimation of the required amount of memory.
KFPH23206-E L
Number of shared memory segment for resident RDAREA exceeds "pd_max_resident_rdarea_shm_no", allocate shm no=aa....aa, request=bb....bb, server=cc....cc
- The number of shared memory segments for in-memory RDAREA exceeded the value of the pd_max_resident_rdarea_shm_no operand.
- aa....aa: Number of shared memory segments that have already been allocated
- bb....bb: Number of shared memory segments required for in-memory allocation
- cc....cc: Server identifier
- S: Terminates processing.
- Action
- See Amount of memory required during in-memory data processing in the HiRDB Version 9 Installation and Design Guide, and check that no errors were made in the estimation of the required amount of memory.
KFPH23207-E L
Unmatched RDAREA page size RDAREA="aa....aa",memory=bb....bb DB=cc....cc
- An RDAREA page length mismatch occurred during in-memory processing.
- aa....aa: RDAREA name
- bb....bb: Page length of the RDAREA during in-memory allocation
- cc....cc: Current RDAREA page length
- S: Terminates processing.
- Action
- Recover the RDAREA from backup at the point when in-memory processing or synchronization was performed, and execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.
KFPH23208-E L
Failed to allocate in-memory data buffer,server=aa....aa, size=bb....bb, reason=cc....cc
- Allocation of the in-memory buffer failed.
- aa....aa: Server identifier
- If the server identifier is unknown, five asterisks (*) are output.
- bb....bb: Size of the area that was to be allocated
- If the error code is insufficient physical memory, five asterisks (*) are output.
- cc....cc: Cause of the error:
- page fixed failed: Shared memory page lock failed.
- HiRDB segment over: The common memory segment count exceeded the maximum value for HiRDB.
- process segment over: The number of shared memory segments that can be added in a process exceeded the maximum value for the OS.
- insufficient virtual memory: There is insufficient memory for allocating the in-memory buffer.
- insufficient physical memory: The work area is not sufficient for attaching shared memory.
- shmmax over: The shared memory segment size exceeded the maximum value.
- segment ID over: The number of shared memory identifiers exceeded the maximum value.
- S: Terminates processing.
- Action
- Take one of the following actions according to the cause of the error.
- If the cause of the error is page fixed failed:
- Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and then take one of the following actions:
- If KFPO00107-E "shmctl(ommfixed)" failed errno=1 was output
Refer to message KFPO00107-E, take corrective action, and then re-execute the pdmemdb command.
- If KFPO00107-E "shmctl(ommfixed)" failed errno=12 was output
If you do not need to page-lock the shared memory, either specify free in the -p operand of the pdmemdb command, or omit the -p option and then re-execute.
If the shared memory is to be page-locked, perform one of the following actions:
- Increase the real memory and then re-execute the pdmemdb command.
- Decrease the RDAREA specified in the pdmemdb command, and then re-execute the command.
- If the cause of the error is HiRDB segment over:
- The number of shared memory segments that can be used in HiRDB per server is the sum of 16 + pd_max_add_dbbuff_shm_no specification value + pd_max_resident_rdarea_shm_no specification value. Increase the value of the pd_max_resident_rdarea_shm_no operand, and then re-execute the pdmemdb command.
- Also, in order to use the shared memory segments effectively, you should exercise caution when gathering together multiple RDAREAs to process in memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator.
- If the cause of the error is process segment over or shmmax over:
- Revise the algorithm for the required amount of memory. For details about the amount of memory required during in-memory processing, see the HiRDB Version 9 Installation and Design Guide.
- In UNIX, also revise the estimation of the OS operating system parameters. For details about estimating operating system parameters, see the HiRDB Version 9 Installation and Design Guide or the OS documentation.
- Note that in order to use the shared memory segments effectively, you should exercise caution when gathering together multiple RDAREAs to add to the in-memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator.
- If the cause of the error is insufficient virtual memory:
- Refer to system call = shmget, errno = 12, mnemonic = ENOMEM in 4.3 System call return codes and take corrective action.
- If the cause of the error is insufficient physical memory:
- Either decrease the required amount of shared memory by decreasing the number of in-memory RDAREAs, or expand the real memory.
- If the cause of the error is segment ID over:
- Refer to system call = shmget, errno = 28, and mnemonic = ENOSPC in 4.3 System call return codes, and take corrective action as appropriate.
KFPH23209-E L
Unmatched HiRDB file page number HiRDB file name="aa....aa",memory=bb....bb DB=cc....cc
- A HiRDB page count mismatch occurred during in-memory processing.
- aa....aa: HiRDB file name
- If there are 162 or more characters in the HiRDB file path name, the last 161 characters are output.
- bb....bb: Page count during in-memory allocation
- cc....cc: Current page count.
- S: Terminates processing.
- Action
- Recover the in-memory RDAREA from backup at the point when in-memory processing or synchronization was performed, and then execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.
KFPH23210-E L
Unmatched HiRDB file number RDAREA="aa....aa",memory=bb....bb DB=cc....cc
- A mismatch in the number of RDAREA configuration files occurred during in-memory processing.
- aa....aa: RDAREA name
- bb....bb: Number of RDAREA configuration files during in-memory allocation
- cc....cc: Current number of RDAREA configuration files
- S: Terminates processing.
- Action
- Recover the in-memory RDAREA from backup at the point when in-memory processing or synchronization was performed, and then execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.
KFPH23212-I L
RDAREA "aa....aa" bb....bb end
- bb....bb of RDAREA aa....aa was terminated.
- aa....aa: RDAREA name
- bb....bb: In-memory data processing state
- MEMORY_LOAD: Data being is loaded from the RDAREA to the in-memory data buffer
- DB_SYNC: Synchronization is being acquired between the RDAREA and in-memory data buffer
- S: Continues processing.
KFPH23213-E L
Insufficient memory on PROCESS for in-memory data buffer,size=aa....aa
- When the in-memory data buffer was allocated, there was a shortage of process-private memory.
- aa....aa: Size of area that was to be allocated
- S: Terminates processing.
- Action
- Re-evaluate the number of processes, and then re-execute the command.
KFPH24003-E L
Invalid "pd_plugin_ixmk_dir" statement, errno=aaaaa, directory or HiRDB file system= bb....bb
- An error was detected in the specification of the pd_plugin_ixmk_dir operand in the system definition.
- aaaaa: HiRDB file system error code
- bb....bb: pd_plugin_ixmk_dir operand specification
- If this specification exceeds 120 characters, the last 120 characters are output.
- S: Continues processing.
- O: Contact the HiRDB administrator.
- Action
- Terminate HiRDB normally, correct the error by referring to 5.1 Error codes returned from HiRDB file system access requests, then start HiRDB.
- In Unix:
If the error code is -1538, either a regular file not in a HiRDB file system area is specified (a regular file system area), or a character special file is specified. In either case, specify either a HiRDB file system area or directory name.
- In Windows:
If the error code is -1538, a file not in the HiRDB file system area is specified. If that is the case, specify either a HiRDB file system area or a directory name.
KFPH24004-I L
pd_redo_allpage_put information=(Server=aa....aa,SKIP=bb....bb,APPLY=cc....cc,WRITE=dd....dd,BFPUT=ee....ee)
- This displays the internal information related to the database write during full recovery processing of server aa....aa when the pd_redo_allpage_put operand was specified.
- aa....aa: Server name
- bb....bb: Number of update logs that were not rolled forward, because writing into the database had been completed
- cc....cc: Number of update logs that were rolled forward, because writing into the database had not been completed
- dd....dd: Number of WRITEs issued during full recovery processing
- ee....ee: Internal information
- S: Continues processing.
KFPH25000-E L
Error occurred on aa....aa(bbbb), code=ccccc(dd....dd)
- An error with error code ccccc occurred in aa....aa(bbbb).
- aa....aa: Processing resulting in the error
- bbbb: Detail code of the processing resulting in the error
- ccccc: Error code
- dd....dd: Error detail code
- S:
- During HiRDB startup: Resumes processing.
- During transaction rollback: Terminates processing.
- Action
- Use the database recovery utility to recover the RDAREA indicated in the KFPH00306-E message (shutdown message) that was output before this message and report the contents of the embedded character to the customer support center.
KFPH25001-E L
Error occurred on aa....aa(bbbb), code=cc(dd....dd)
- An error with error code cc occurred in aa....aa(bbbb).
- aa....aa: Processing resulting in the error
- bbbb: Detail code of the processing resulting in the error
- cc: Error code
- dd....dd: Error detail code
- S: Terminates processing.
- Action
- Use the database recovery utility to recover the RDAREA indicated in the KFPH00306-E message (shutdown message) that was output before this message and report the contents of the embedded character to the customer support center.
KFPH25002-E C+L
aa....aa wait time over,RDAREA=bb....bb,ccccc=dd....dd
- Processing by the free page release utility was suspended because the transaction completion wait time, or the time to execute a search using a holdable cursor, exceeded the specified time.
- aa....aa: Reason why the free page release utility was waiting
- Transaction: Timeout on transaction completion
- Cursor close: Timeout on closing the cursor on a search using a holdable cursor, thereby transaction completion
- bb....bb: Name of RDAREA
- ccccc: Processing target of the free page release utility
- TABLE: Table
- INDEX: Index
- dd....dd: Name of the processing target of the free page release utility
- If ccccc is TABLE, displays the table name
- If ccccc is INDEX, displays the index name
- S: Terminates processing.
- O:
- When aa....aa is Transaction:
- Re-execute the free page release utility.
- If a transaction requires a lengthy access time, re-execute after the transaction has terminated. Alternatively, increase the concurrently executing transaction completion wait time.
- When aa....aa is Cursor close:
- Re-execute the free page release utility.
- If there is a holdable cursor that has been open for a long time, re-execute after the cursor is closed and the transaction has terminated. Alternatively, increase the concurrently executing transaction completion wait time.
KFPH25003-E L
Unusable page accessed,tableID=aa....aa,RDAREA name=bb....bb,file name=cc....cc,code=dd....dd,ee....ee
- A page that cannot be used was accessed during operations on the table ID aa....aa, which is defined in RDAREA bb....bb. If WAIT was specified in pd_lock_uncommited_delete_data, HiRDB file areas in excess of the following sizes cannot be used in the RDAREA stored in the table that defines the index.
- If the page length is 4096: 32 GB
- If the page length is 6144: 48GB
- Note that when this message is output once, output is suppressed until one of the following triggers:
- HiRDB start time
- Execution of the pdopen (RDAREA open) command
- aa....aa: table ID
- bb....bb: RDAREA name
- cc....cc: HiRDB file name
- If the path name of HiRDB file exceeds 100 characters, the last 100 characters of the HiRDB file path name are output.
- dd....dd: Internal information
- ee....ee: Internal information
- S: Invalidates this transaction.
- Action
- Revise the HiRDB file size of the RDAREA that stores the table. For details about the maximum HiRDB file size when WAIT is specified in the pd_lock_uncommited_delete_data operand, see the manual HiRDB Version 9 System Definition. If you have exceeded the maximum size for the RDAREA structure file, use the database structure modification utility (pdmod) to change the configuration so that the maximum size is not exceeded.
KFPH25004-I L
Waiting for transaction completion. RDAREA="aa....aa",bb....bb="cc....cc",TRNGID=dd....ddee....ee,TRNBID=dd....ddff....ff,ACTID=gg....gg,code=hh....hh,iii
- The free page release utility is waiting for completion of the transaction displayed in this message.
- aa....aa: RDAREA name
- bb....bb: Types of processing targets of the free page release utility
- cc....cc: Identifier of the processing targets of the free page release utility
- dd....dd: HiRDB identifier and unit identifier
- If the HiRDB identifier and unit identifier cannot be acquired, eight asterisks (*) are displayed.
- ee....ee: Global transaction number
- If the global transaction number cannot be acquired, eight asterisks (*) are displayed.
- ff....ff: Transaction branch number
- If the transaction branch number cannot be acquired, eight asterisks (*) are displayed.
- gg....gg: User identity sequence number
- hh....hh: Waiting for completion
- TRAN: Waiting for transaction completion
- CURSOR: Waiting for closing of the holdable cursor
- iii: Internal information
- S: Continues processing.
- Action
- If a value of 1 or larger was specified in -w when a timeout occurs, wait for the total completion of the transaction output in this message, and execute the free page release utility again. If the value 0 was specified for -w or if the specification was omitted, check whether you can terminate the transaction that the system is waiting for. If you are waiting for a transaction that can be terminated, terminate it. For details, see Free page release utility (pdreclaim) in the manual HiRDB Version 9 Command Reference.
KFPH25100-I L
Index information file assigned, file=aa....aa, index=bb....bb.cc....cc, RDAREA=dd....dd
- An index information file was created for the index bb....bb.cc....cc that is stored in the RDAREA dd....dd, with a file name aa....aa.
- aa....aa: Name of the index information file
- bb....bb: Authorization identifier
- cc....cc: Index identifier for the plug-in index
- dd....dd: One of the following:
- Plug-in index storage RDAREA name, or
- Plug-in index storage RDAREA name (replica RDAREA generation number)
When using HiRDB Staticizer Option and the plug-in index storage RDAREA is the replica RDAREA, this message outputs the plug-in index storage original RDAREA name and replica RDAREA generation number.
- S: Continues processing.
KFPH25101-E L
Index information file aa....aa error, file name=bb....bb kind=cc....cc index inf=dd....dd errno=ee....ee
- Processing aa....aa for the index information file failed when the index information file was being created or updated.
- aa....aa: Error type
- bb....bb: Name of the index information file
- Only the last 100 characters of the file name are output when the length of the index information file name exceeds 100 characters.
- cc....cc: Error information
{ 0|1|2 }
- dd....dd: Index information
{ 0|1 }
- ee....ee: Error code
- If the error occurred in HiRDB file system area, HiRDB file system area error code is displayed. For details on errors in a HiRDB file system area, see 5.1 Error codes returned from HiRDB file system access requests. In such a case, the error information displayed in cc....cc is not meaningful.
- S: Continues processing if rollback is in progress. Otherwise, invalidates the transaction.
- Action
- Take actions in the indicated order based on error information and index information.
- Error information:
- 0: Based on the error code (an external integer variable that indicates the condition of the error) and by referring to the errno.h file and the OS manual, check the cause of the error. Take an appropriate action according to the following error cause:
Error cause | Explanation | Action |
---|
ENOSPC | The directory holding the index information file is full. | Delete any unneeded files from the directory. |
- 1: The directory holding the index information file is full. Delete any unneeded files from the directory.
- 2: Records were not read completely. Contact the customer support center.
- Index information:
- 0: Re-execute the UAP.
- 1: Re-create the index.
KFPH26000-E L
Error occurred on aa....aa(bbbb),code=ccccccc(dddddddd)
- An error with error code ccccccc was detected in aa....aa(bbbb).
- aa....aa: Processing resulting in the error
- bbbb: Detail code of the processing resulting in the error
- cccccccc: Error code
- dddddddd: Error detail code
- S: Terminates abnormally.
- Action
- Report the contents of the error to the customer support center.
KFPH26001-I L
Information=aa....aa
- Displays internal information aa....aa.
- aa....aa: Internal information
- S: Resumes processing.
- Action
- If the system terminates abnormally after this message has been output, contact the customer support center.
KFPH26010-I L
Start to assign used page, because pdload used up new pages in RDAREA "aa....aa", table_id="bb....bb"
- All new pages for the RDAREA "aa....aa" were used during the data-loading of the table ID "bb....bb". Data is stored in unused free areas.
- aa....aa: Name of the RDAREA
- bb....bb: Table ID
- S: Continues processing.
- O: Based on the number of data items stored in the table, review the required RDAREA size. Use the Database Reorganization Utility (pdrorg) to reorganize the table.
KFPH27000-E L+S
System error, func "aa....aa", code=bbbb
- A HiRDB system function error occurred.
- aa....aa: Name of function
- bbbb: Error code
- S: Terminates processing.
- Action
Function name (aa....aa) | Action by administrator |
---|
p_f_dbh_dint_envcp | - When the rapid system switchover facility is used:
Resolve the error by referring to message KFPH27028-E, which is output in the standby system unit. Then restart the standby system unit.
- When the standby-less system switchover (1:1) facility is used:
Resolve the error by referring to message KFPH27028-E, which is output on the alternate portion to be started in waiting status or on the normal BES unit. Then restart the alternate portion or the normal BES unit in waiting status.
|
p_f_dbh_buf_envcp |
p_f_hba_envcp |
Other than above | Refer to 4.2 Detail codes for system-related errors to resolve the error, and then re-execute the function. If you cannot determine the cause of the error, contact the customer support center. |
KFPH27002-E S
Message output failed, return code = aaaa, msgno = bb....bb
- A message output error occurred.
- aaaa: Error code
- bb....bb: Message number
- S: Terminates processing.
- Action
- Refer to the system function error code details list, and eliminate the cause of the message output error. If you cannot identify the cause of the error, contact the customer support center. Also, refer to the message number to see which message the system attempted to output, eliminate the cause of the error, and re-execute the command.
KFPH27003-E E+L+S
System call error, func=aa....aa, errno=bbbb
- An error has occurred in an operating system function.
- aa....aa: Name of system function
- bbbb: Value of errno
- S: Terminates processing.
- Action
- Check the description for the errno value in errno.h or the applicable OS documentation to resolve the error, and then re-execute the command.
KFPH27004-E L+S
Work file open failed, aa....aa
- A work file open error occurred.
- aa....aa: Cause of the error:
- errno = bbbb: Error code bbbb was issued
- no such file: Specified file was not found
- permission denied: The user is not authorized to write data to the directory
- S: Terminates processing.
- Action
- Refer to the file created under %PDDIR%\tmp to eliminate the cause of the error, and re-execute the command.
KFPH27005-E E+L+S
Insufficient memory on PROCESS, size = aa....aa
- An attempt to allocate a process private area failed due to a memory shortage.
- aa....aa: Size of area that was to be allocated
- S: Terminates processing.
- O: Re-evaluate the number of processes and re-execute the command.
KFPH27006-E L+S
DATA DICTIONARY RDAREA information get error
- An error occurred during collection of information about the data dictionary RDAREA.
- S: Terminates processing.
- O: Refer to the message log that was output before and after the message to eliminate the cause of the error, and re-execute the command.
KFPH27007-E L
HiRDB file system information get error, code=aaaaa, area=bb....bb
- An error occurred during collection of information about a HiRDB file system area.
- aaaaa: Error code
- bb....bb: Name of HiRDB file system area
- If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.
- S: Invalidates processing on the corresponding RDAREA and resumes processing.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute the command.
KFPH27008-E L+S
aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, RDAREA = cc....cc
- Because the data dictionary RDAREA bb....bb cannot be referenced, the database operation command aa....aa of the specified RDAREA cc....cc cannot be processed.
- aa....aa: Command name
- bb....bb: Name of data dictionary RDAREA
- cc....cc: RDAREA name (if the RDAREA name cannot be obtained, ***** is displayed)
- S: Invalidates processing on the corresponding RDAREA and resumes processing.
- O: Correct the status of the data dictionary RDAREA and re-execute the command.
KFPH27009-E L+S
SORT program error occurred, code=aaaa
- An error occurred during sort processing.
- aaaa: Error code
- S: Terminates processing.
- Action
- Take corrective action according to the error code:
Error code | Action |
---|
-202 | There is a memory shortage. Reduce the work buffer size specified in the sort operand. |
-290 | There is a work buffer shortage. Increase the work buffer size specified in the sort operand. |
-210 -230 | An I/O error occurred. The available capacity on the sort work disk may be insufficient. If the problem is caused by a capacity shortage, specify a disk having sufficient free space in the sort, and 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.
KFPH27010-E L
Unable to send message from aa....aa to bb....bb
- During command processing, a communication error occurred between hosts aa....aa and bb....bb.
- aa....aa: Send source host name#
- bb....bb: Send destination host name#
- #: If the system switching facility is being used, the host name of the primary system is indicated.
- S: Terminates processing.
- Action
- If the command is executed while HiRDB is starting, wait until HiRDB has finished starting, and then re-execute the command. Otherwise, take the appropriate action as indicated by the KFPH27000-E message that was output before this message. If the error was not a physical communication error, there might 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 then retry the operation.
KFPH27011-E L+S
aa....aa command failed due to data dictionary RDAREA (bb....bb) status invalid, buffer pool=cc....cc
- Specified buffer pool cc....cc cannot be processed by HiRDB command aa....aa, because HiRDB area for data dictionary bb....bb cannot be referenced.
- aa....aa: Command name
- bb....bb: Name of data dictionary for RDAREA
- cc....cc: Name of buffer pool
- S: Name of buffer pool invalidates processing on the corresponding buffer pool area and resumes processing.
- Action
- If RDAREA for the data dictionary is shut down, eliminate the cause of the error, then re-execute the command. If closed, release close, then re-execute the command.
KFPH27012-I E+L
Usage: pdbufls [-k sts|def|all] [-d] [-x [-y]] [-M]
[{-s server_name[,server_name]...|-a buffer_pool_name[,buffer_pool_name]...}]
- Shows how to use the command (pdbufls) to display the status of global buffer pool. This message is displayed when the command option or argument is wrong.
- S: Terminates processing
- Action
- Reenter the command specified correctly.
KFPH27013-I E+L
Usage: pddbchg -q n {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...]|-r ALL} [-w]
- This message shows the usage of the pddbchg command, which changes the current RDAREA. It is output when a command option or argument is invalid.
- S: Terminates processing.
- Action
- Correct the command format, and then re-execute the command.
KFPH27014-E L+S
No original rdarea named aa....aa[, server = bb....bb]
- The specified RDAREA is not the original RDAREA.
- aa....aa: RDAREA name
- bb....bb: Shared RDAREA runtime server name
- This is displayed when an error occurs in the shared RDAREA.
- S: Performs one of the following processing actions:
- For the pddbchg command, terminates the command without performing any processing on any specified RDAREA.
- For the pddbls command, continues processing without performing any processing on the specified RDAREA.
- When the -r option of the pdorbegin command is specified
If the RDAREA names are batch-specified, continues processing without performing any processing on the specified RDAREA.
If the RDAREA names are specified directly, terminates the command without performing any processing on any specified RDAREA.
- Action
- Specify the original RDAREA name and re-execute the command.
KFPH27015-E L+S
aa....aa command failed, RDAREA = bb....bb,code = ccc[, server = dd....dd]
- Processing of the pddbchg command could not be performed.
- aa....aa: Command name
- bb....bb: RDAREA name
- ccc: Error code
- -30: The specified RDAREA cannot be locked.
- -31: The dictionary table and back-end server memory information do not match.
- -32: The master directory information cannot be updated.
- -33: The dictionary table cannot be updated.
- -34: An error occurred in the system function.
- dd....dd: Shared RDAREA runtime server name
- This is displayed when an error occurs in the shared RDAREA.
- S: Terminates processing.
- Action
- Take the action appropriate for the error code:
- -30
Terminate other transactions (if the server name is displayed, other transactions on the server) and re-execute the command. Or, shut down all target RDAREAs inside the inner replica and re-execute the command. Also, if there are RDAREAs shut down through online reorganization hold, the pddbchg command cannot be executed. Release online reorganization hold by executing the pdorbegin command before the pdorchg command and the pdorend command after the pdorchg command, and then re-execute the command.
- -31
Check for errors in the system RDAREAs. If there is no error, contact the customer support center.
- Other error codes
Check the error message output before this error message, and eliminate the cause of the error. If the server name is displayed, check the message that was output before this message was output, and remove the cause of error from the server. If the cause of the error is unknown, contact the customer support center.
KFPH27016-E L+S
No specified generation RDAREA=aa....aa
- No RDAREA of the specified generation could be found.
- aa....aa: RDAREA name
- S: Terminates processing.
- Action
- Use the replicate rdarea statement of the database structure modification utility of the specified generation, and then re-execute the command.
KFPH27017-W L+S
replica status changed though MASTER DIRECTORY invalid
- The current information on the RDAREA for the master directory is invalid, but the replica status was updated.
- S: Continues processing.
KFPH27018-E E+L
pddbchg command not available without Staticizer Option
- HiRDB Staticizer Option is required to execute the pddbchg command.
- S: Terminates processing.
- Action
- Check to determine if HiRDB Staticizer Option is being used. Install HiRDB Staticizer Option if necessary.
KFPH27023-E E+L
specified option not available without Staticizer Option
- HiRDB Staticizer Option is required for the specified option.
- S: Terminates processing.
- Action
- Check if the environment can be used by HiRDB Staticizer Option. Install HiRDB Staticizer Option if necessary.
KFPH27024-I L+S
HiRDB file freezed, file=aa....aa
- HiRDB file aa....aa was put into frozen update status.
- aa....aa: HiRDB file name
- S: Terminates processing.
KFPH27025-I E+L
Usage:pddbfrz [-d] {-r RDAREA[,RDAREA ...]|-r ALL} [-q generation_number]
- This message shows the format of the pddbfrz command. It is output when the command was specified incorrectly.
- S: Terminates processing.
- Action
- Correct the command specification, and then re-execute the command.
KFPH27026-I L+S
HiRDB file freeze skipped, file=aa....aa, reason=bb....bb
- Frozen update processing of HiRDB file aa....aa was skipped due to reason bb....bb.
- aa....aa: HiRDB file name
- bb....bb: Reason code
- topfile: This is the first file comprising the RDAREA.
- already: The file is already in frozen update status.
- plug-in: Plug-in logical files were found.
- unused: Nonallocated segments were found.
- S: Continues processing.
KFPH27027-E L+S
RDAREA freeze failed, RDAREA=aa....aa
- Updating of the specified RDAREA could not be frozen because the RDAREA stores the plug-in index or is an unused RDAREA.
- aa....aa: RDAREA name
- S: Invalidates processing of the applicable RDAREA, and then processing continues.
- Action
- Respecify the RDAREA, and then re-execute.
KFPH27028-E E+L
File copy failed, server name = aa....aa, return code = bbbb
- When the rapid system switchover facility is used:
Copying of HiRDB database environment information files from the running system server to the standby server failed.
- When the standby-less system switchover (1:1) facility is used:
Copying of HiRDB database environment information files from the normal BES unit to the alternate portion, or from the alternate portion to the normal BES unit, failed.
- aa....aa: Server name
- bbbb: Return code
- S: Terminates processing.
- Action
- Take corrective action according to return code bbbb:
Return code | Cause and action |
---|
100 | You cannot execute a remote shell in this environment. In an environment using an alias IP address, the following causes are possible:
- When the rapid system switchover facility is used:
The host with the alias IP address for the running system unit and the standby system unit may be stopped. If that is the case, activate the server unit that has the alias IP address, and then restart the standby system unit.
- When the standby-less system switchover facility is used:
The host with the IP address for the normal BES unit and the alternate portion may be stopped. If that is the case, activate the server unit that has the alias IP address, and then restart either the normal BES unit or the alternate portion.
|
UNIX edition only A network failure has occurred. In a system switchover configuration that does not inherit IP addresses, lan_updown is not specified in the server definition statement for the HA monitor. Further, the HA monitor environment setting directory contains network up.down shells named server-id-name.up and server-id-name.down, which are identical to the server identification names specified in the server definition statement for the HA monitor (or the Hitachi Toolkit Extension). This caused a network failure when the system switchover facility was started. If the system switchover configuration being used does not inherit IP addresses, delete the server-id-name.up and server-id-name.down shells. |
101 | A time-out occurred. Review the value of the pd_system_complete_wait_time operand. If the rapid system switchover facility is being used, restart the standby system unit. If the standby-less system switchover (1:1) facility is used, restart either the normal BES unit or the alternate portion. |
102 | Check whether the Hitachi HA Toolkit Extension is being used. If it is not being used, contact the customer support center. If it is being used, take the following action:
- If the rapid system switchover facility is used:
An attempt was made to copy HiRDB database environment information files to the standby unit during startup of a secondary system. Check if the running unit started normally. (1) If the running unit did not start normally: Check if the Hitachi HA Toolkit Extension process started, and start either the primary system or the secondary system as the running system unit. After the running unit finishes starting, start the standby unit. (2) If the running unit started normally: Contact the customer support center.
- If the standby-less system switchover facility (1:1) is used:
An attempt was made to copy HiRDB database environment information files from the normal BES unit during startup of the alternate portion in waiting status. Check if the normal BES unit started normally. (1) If the normal BES unit did not start normally: Check if the Hitachi HA Toolkit Extension process started, and start the normal BES unit normally, or start the alternate portion as alternating.
If starting the normal BES unit normally: After the normal BES unit finishes starting, start the alternate portion in waiting status.
If starting the alternate portion as alternating: After the alternate portion finishes starting, start the normal BES unit in waiting status. (2) If the normal BES unit started normally: Contact the customer support center.
|
Others | Contact the customer support center. |
KFPH27030-E L+S
pdhold command required specification of -q option
- If the -r ALL or -s option is specified with the pdhold command, the -q option also has to be specified.
- S: Terminates processing.
- Action
- Correct the command format, and then re-execute the command.
KFPH27031-E L+S
Failed to allocate global buffer pool,server=aa....aa,size=bb....bb,errno=cc
- Allocation of the global buffer failed.
- aa....aa: Server name
- bb....bb: Size of the space to be secured (0 is displayed if digit overflowing occurred during the calculation)
- cc: Error cause code
- S: Terminates processing.
- Action
- Take the action appropriate for the error cause code, and then re-execute the pdbufmod command.
Error cause code | Error description | Action |
---|
4 | Page fixing of common memory failed | An attempt to page-fix shared memory segments failed. Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and take one of the following actions:
- If KFPO00107-E was output with "shmctl(ommfixed)" failed errno=1
See message KFPO00107-E and take the corrective actions described there.
- KFPO00107-E was output with "shmctl(ommfixed)" failed errno=12
If shared memory segments do not need to be page-fixed, stop HiRDB normally, specify free in the pd_dbbuff_attribute operand or omit specification of the operand, and then restart HiRDB. If you want to page-fix the shared memory segments, take either of the following actions:
Increase the real memory.
Reduce the buffer sector count value specified in the pdbufmod command.
|
8 | The common memory segment count exceeded HiRDB maximum. | The number of shared memory segments that can be added per server in HiRDB exceeded the maximum value specified in the pd_max_add_dbbuff_shm_no operand. If in-memory data processing is being used, it exceeds the value 16 + value of pd_max_add_dbbuff_shm_no + value of pd_max_resident_rdarea_shm_no. Delete any unnecessary global buffers. In addition, define dynamically updated global buffers in the pdbuffer operand. This will decrease the number of common memory segments HiRDB manages. |
16 | The common memory segment count exceeded the operating system maximum. | The number of common memory segments a process can add exceeded the value of the operating system parameter shmseg in the operating system. Delete any unnecessary global buffers. |
20 | A memory shortage occurred. | Refer to system call= shmget, errno=12, mnemonic= ENOMEM in 4.3 System call return codes to investigate the cause of the error, and take corrective action. |
24 | The common memory segment size exceeded the maximum. | Either the common memory size for global buffers exceeded the value of the operating system parameter shmmax in the operating system or the SHMMAX operand value. Decrease the excessive value to decrease the number of buffer sectors in the global buffer. |
28 | The global buffer count exceeded the maximum. | The maximum number of global buffer pools that can be dynamically added or changed per server (the value specified in the pd_max_add_dbbuff_no operand) has been exceeded. Delete any extraneous global buffer pools, and re-execute the command. |
32 | Digit overflow occurred during the common memory size calculation. | Decrease the buffer sector count of the global buffer so the common memory size does not exceed 231-1 (263-1 for the 64-bit mode). |
36 | The number of common memory identifiers exceeded the maximum. | Refer to system call= shmget, errno=28, mnemonic= ENOSPC in 4.3 System call return codes to investigate the cause of the error, and take corrective action. |
KFPH27032-E L+S
Global buffer pool already allocated,global buffer pool name=aa....aa
- The global buffers were already allocated.
- aa....aa: Global buffer name
- S: Terminates processing.
- Action
- Use the pdbufls -k def command to check the global buffer names already being used. Specify a unique global buffer name and re-execute the pdbufmod command.
KFPH27033-I E+L
Usage: pdbufmod -k {add|del|upd} -a pool name [{-r RDAREA[,RDAREA ....]|-b RDAREA[,RDAREA ....]|-i ID.INDEXNAME|-o}] [-n NUM] [-l SIZE] [-m PRMAX] [-p PRNUM] [-w WRATIO] [-y TRBUFNUM]
- Shows how to use the pdbufmod command to dynamically change global buffers. It is output when an invalid command option or argument is used.
- S: Terminates processing.
- Action
- Correct the specification format and re-execute the command.
KFPH27034-E L+S
Unable to execute pdbufmod command, server=aa....aa
- The pdbufmod command could not be executed for one of the following reasons:
- The rapid system switchover facility was being used
- The standby less system switchover facility was being used
- The pd_dbbuff_modify operand was omitted or N was specified.
- aa....aa: Server name
- S: Continues processing.
- Action
- When using the rapid system switchover facility or the standby less system switchover facility, use the online system configuration modification facility to modify the specification of the pdbuffer operand (change the definition of the global buffer).
- When not using the rapid system switchover facility or the standby less system switchover facility, specify Y in the pd_dbbuff_modify operand.
KFPH27035-I E+L
Usage: pdorbegin {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...] |-t [AUTHID.]TABLE[-s server[,server...]] [-c CONSTRAINT_TYPE]} [-w LOCK_WAIT_TIME] [-q GENERATION_NUMBER] [-e] [-u]
pdorbegin {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...] |-t [AUTHID.]TABLE [-c CONSTRAINT_TYPE]} [-s server[,server...]] [-w LOCK_WAIT_TIME] [-q GENERATION_NUMBER] -u
- This is the specification format of the pdorbegin command.
- S: Continues processing.
- Action
- Check the specification format, and then retry the operation.
KFPH27036-I E+L
Usage: pdorchg [-s server[,server....]]
- This is the specification format of the pdorchg command.
- S: Continues processing.
- Action
- Check the specification format, and then re-execute.
KFPH27037-I E+L
Usage: pdorend [-s server[,server....]] {[-n RETRY_COUNT] [-w MAX_REFLECT_WAIT_TIME] [-t MAX_TRN_WAIT_TIME] [-m REF_PROCESS_CNT] [-z] | [-f reflection control file] [-p] | [-u]}
- This is the specification format of the pdorend command.
- S: Continues processing.
- Action
- Check the specification format, and then re-execute.
KFPH27038-E E+L
Not available without aa....aa option, command = bb....bb
- The bb....bb command could not be executed because the aa....aa option was not embedded.
- aa....aa: Option name
- Staticizer
- bb....bb: Command names
- {pdorbegin|pdorchg|pdorend}
- S: Continues processing.
- Action
- Embed the option, and then re-execute the command.
KFPH27039-E E+L
Not available without specification of aa....aa operand, command = bb....bb
- The bb....bb command could not be executed because the aa....aa operand in the system definition was not specified.
- aa....aa: System definition operand name
- {pd_inner_replica_control|pd_max_reflect_process_count}
- bb....bb: Command names
- {pdorbegin|pdorchg|pdorend}
- S: Continues processing.
- Action
- Terminate HiRDB, add the system definition aa....aa operand, restart HiRDB, and then re-execute the command.
KFPH27040-I E+L
Reflection completed, server = aa....aa
- Reflection processing completed on the indicated server.
- aa....aa: Name of server
- S: Continues processing.
KFPH27041-W E+L
Reflection retry, server = aa....aa, count = bb, code = cccc, wait_time = dddd
- Retries discrepancies application processing on server aa....aa.
- aa....aa: Server name
- bb: Retry count
- cccc: Reason code
- lock: Time-out occurred during the locking procedure.
- sync: Time-out occurred in discrepancies application processing after the locking procedure completed.
- dddd: Locking wait time (seconds)
- S: Continues processing.
- O: If discrepancies application processing is repeatedly retried and terminates abnormally, take one of the following actions and re-execute the pdorend command.
- Increase the specification value of the -n option.
- Increase the specification value of the -w option.
- Increase the specification value of the -t option.
- If discrepancies application processing terminates abnormally even after taking these actions, reduce the amount of transaction processing and execute the pdorend command.
KFPH27042-W L+S
No held(org) RDAREA, command = aa....aa
- There is no RDAREA that can perform updatable online reorganization.
- aa....aa: Command name
- {pdorchg|pdorend}
- S: Terminates processing.
- O: Check the operation procedure for updatable online reorganization, and then re-execute the command. For details about how to perform updatable online reorganization, see HiRDB Version 9 Staticizer Option Description and User's Guide.
KFPH27043-E E+L
aa....aa command failed, server = bb....bb, code = ccc
- The aa....aa command failed on server bb....bb.
- aa....aa: Command name
- bb....bb: Server name
- ccc: Error code
- -50: The maximum wait time of discrepancies application processing elapsed.
- -51: The retry count exceeded the specified value.
- -52: An error occurred in the pdorend application process.
- -53: A communication error occurred.
- -54: The applicable server is executing updatable online reorganization.
- -55: The execution sequence of updatable online reorganization is incorrect.
- -56: It is possible that the pdorchg command has not completed.
- -57: The specified option, RDAREA, table, or constraint type is invalid.
- S: Terminates processing.
- O: Take corrective action according to the error code:
- When the error code is -50:
- Either increase the value specified for the maximum wait time of discrepancies application processing or reduce the amount of transactions with the replica RDAREA and re-execute the command.
- When the error code is -51:
- Take one of the following actions, and then re-execute the command:
- Increase the value specified for the transaction maximum wait time.
- Increase the retry count.
- Reduce the amount of transactions with the replica RDAREA.
- When the error code is -52:
- Take one of the following actions:
- If the -u option is not specified in the pdorend command, take action according to the previous error message.
- If the -u option is specified in the pdorend command and online reorganization hold of all RDAREAs in the applicable server is released, re-executing this command is not necessary. Use the pddbls command to check the status of the RDAREA. If there is even one RDAREA on the relevant server that is on online reorganization hold, see the description on troubleshooting in the manual HiRDB Version 9 Staticizer Option Description and User's Guide.
- When the error code is -54:
- Wait for the first pdorend command executed to terminate, and then re-execute the command.
- When the error code is -55:
- Check the execution sequence of the pdorbegin, pdorchg, and pdorend commands. If the execution sequence is correct, use the pddbls command to check whether the status of the RDAREA is correct.
- When the error code is -56:
- Check the return code from the pdorchg command. If the system has not normally terminated, use the pdorchg command to normally terminate the system, and then re-execute the pdorend command. If the system has normally terminated, the pddbchg command or the database structure modification utility may be running at the same time as the pdorend command. In this case, re-execute the pdorend command.
- When the error code is -57:
- When the -u option is not specified
The pdorbegin command cannot be executed because the server containing the RDAREAs to be processed contains an RDAREA or table that has been placed in online reorganization hold. Check the specified RDAREAs or table names.
- When the -u option is specified
Specify the option (-r, -t, or -c) and the flag argument (RDAREA, table, or constraint type) that were specified for online reorganization hold, and re-execute the pdorbegin command.
If the -r option is specified, specify any RDAREA among those specified by the -r option that was released during online reorganization hold, and re-execute the pdorbegin command.
If the -t option is specified, specify the table specified in the -t option during online reorganization hold.
If the -c option is specified, specify the constraint type that was specified during online reorganization hold, and re-execute the pdorbegin command.
- For other error codes:
- Check the message output before this message, eliminate the error cause, and then re-execute the command. If the cause of the error is unclear, contact the customer support center.
KFPH27044-I E+L
aa....aa command started
- The aa....aa command started.
- aa....aa: Command name
- {pdorbegin|pdorchg|pdorend}
- S: Continues processing.
KFPH27045-I E+L
aa....aa command ended, return code = bb
- The aa....aa command ended.
- aa....aa: Command name
- {pdorbegin|pdorchg|pdorend}
- bb: Return code
- 0: Normal termination
- 4: Warning termination
- 8 and 12: Abnormal termination
- S: Terminates processing.
- Action
- When the return code is not 0, take actions according to the previously output error message.
KFPH27046-E L+S
Refrection management table not found, command = aa....aa
- No reflection status management table was found.
- aa....aa: Command name
- {pdorbegin|pdorchg|pdorend}
- S: Terminates processing.
- Action
- Use the pdorcreate command to create a reflection status management table, and then re-execute command aa....aa.
KFPH27047-E L+S
Reflection management table existed in RDAREA to hold(org), RDAREA = aa....aa
- The reflection status management table was found in the RDAREA used for updatable online reorganization.
- aa....aa: RDAREA name
- S: Terminates processing.
- Action
- Delete the reflection management status table, and then create a new RDAREA.
KFPH27048-E L
Enter aa....aa command, due to incomplete operation, RDAREA = bb....bb, SERVER = cc....cc
- Some operation commands did not complete processing.
- aa....aa: Command name {pdorbegin|pdorend}
- bb....bb: Original RDAREA name (******** is displayed for the pdorend command)
- cc....cc: Server name (******** is displayed for the pdorbegin command)
- S: Terminates processing.
- Action
- Specify the displayed RDAREA or server and re-execute the pdorbegin or pdorend command.
KFPH27049-E L+S
Another RDAREA of the same server already held(org),command = aa....aa,SERVER = bb....bb
- This command cannot be executed because another RDAREA on the same server is already in online reorganization hold status.
- aa....aa: Command name (pdorbegin)
- bb....bb: Server name
- S: Terminates processing.
- Action
- Take the following action to add an RDAREA in updatable online reorganization status on the same server:
- When the pdorchg command is not executing
For an RDAREA already in updatable online reorganization hold status, execute the pdorbegin command (-u), release the updatable online reorganization hold status, and re-execute the pdorbegin command.
- When the pdorchg command is executing
For an RDAREA already in updatable online reorganization hold status, execute the pdorbegin command (-u), release the updatable online reorganization hold status, use the pddbchg command to change the current RDAREA, and re-execute the pdorbegin command.
- For details, see HiRDB Version 9 Staticizer Option Description and User's Guide.
KFPH27050-E L+S
Unable to execute aa....aa command,RDAREA = bb....bb,reason = cc....cc
- Cannot execute the aa....aa command for reason cc....cc.
- aa....aa: Command name (pdorbegin)
- bb....bb: RDAREA name
- cc....cc: Reason
- invalid RECOVERY type: The column recovery restriction of the RDAREA for storing LOB columns is not ALL.
- S: Terminates the server processing the applicable RDAREAs.
- Action
- If the reason is invalid RECOVERY type, take either of the following actions, and then re-execute the command:
- Redefine the RDAREA for LOB column storage as an RDAREA for storing tables that will not be put in online reorganization hold status.
- In the table definitions containing a LOB column storage RDAREA, set all column recovery constraints in the LOB column, and execute ALTER TABLE.
KFPH27051-E E+L+S
Number of RDAREA exceeds maximum value
- The upper limit on the number of RDAREAs that can be processed has been exceeded.
- S: Terminates processing.
- Action
- The upper limit on the number of RDAREAs that can be processed using the pdorbegin command is 4,096.
- With the -r option specified:
Revise the batch specification of RDAREAs specified in the -r option, and then re-execute the command.
- With the -t option specified:
Check the total number of tables and related RDAREAs specified in the -t option. Use the pdrdrefls command to check the RDAREAs related to a specified table.
Group the RDAREAs so that the number of RDAREAs to be processed does not exceed 4,096, and then specify the RDAREAs in the -r option and re-execute the command.
KFPH27052-W L+S
Shared RDAREA released hold(org), specified option "-s", server = aa....aa, RDAREA = bb....bb
- For a shared RDAREA, specify server aa....aa to release online reorganization hold.
- aa....aa: Server name
- bb....bb: RDAREA name
- S: Continues processing.
- Action
- Remove the reason why all of the back-end servers cannot be processed in batch, and use the pddbls -m command to check the hold status of the RDAREAs of all back-end servers. Then, release the online reorganization hold of the shared RDAREAs of all back-end servers.
KFPH27053-E E+L+S
Unable to use specified command option aa for bb....bb, command = cc....cc
- For bb....bb, command cc....cc, option aa cannot be specified.
- aa: Option name
- -s
- bb....bb: Error cause
- shared RDAREA: Shared RDAREA
- RDAREA: Non-shared RDAREA
- shared table: Shared table on a HiRDB/Parallel Server
- cc....cc: RDAREA name
- {pdorbegin | pdorchg | pdorend}
- S: Terminates processing.
- Action
- Take the following action to eliminate the cause of the error:
- When the error cause is shared RDAREA or RDAREA
- When cc....cc is the pdorbegin command
Execute shared RDAREAs and non-shared RDAREAs separately. For shared RDAREAs, execute the command specifying only shared RDAREAs in the -r option. For non-shared RDAREAs, execute the command specifying non-shared RDAREAs in the -r option and drop the -s option. Confirm the information for shared RDAREAs by specifying the -m option of the pddbls command.
- When cc....cc is the pdorchg and pdorend commands
Delete the -s option, and re-execute the command.
- When the error cause is shared table
- Drop the -s option and execute the command.
KFPH27054-E L
Transaction may not determine commit or rollback command=aa....aa
- A communication or other error occurred, such that the transaction might not have been completed or rolled back by the system.
- aa....aa: Command name
- S: Terminates processing.
- Action
- Check that the transaction of the executed command does not remain using the pdls -d prc and pdls -d trn commands. If the transaction has not completed, cancel it with the pdcancel command and re-execute the command.
KFPH27055-E E+L+S
aa....aa command failed,reason=bb....bb
- An error occurred during the execution of aa....aa command.
- aa....aa: Command name
- bb....bb: Reason
- ANALYZE FAILED: An error occurred during analysis of the attached reflection control file.
- ANY BES FAILED: An error occurred during processing of one or more back-end servers.
- Auth_id INVALID: The default value of an authorization identifier omitted with the -t option is invalid.
- SPECIFIED SERVER INVALID: A server not related to a table specified with the -t option was specified with the -s option.
- S: Terminates processing.
- Action
- When bb....bb is Auth_id INVALID: Set or revise the environment variable PDUSER, and re-execute the command.
- When bb....bb is SPECIFIED SERVER INVALID: In the -s option, specify the table specified in the -t option of the pdorbegin command or specify the server linked with a referenced table or referencing table of that table, and then re-execute the command. Check the server related to the table using the pdrdrefls command.
- When bb....bb is ANY BES FAILED:
- When the immediately previous KFPH00132-E message displayed servers not involved in processing:
- To continue online reorganization processing, execute one of the following:
- Eliminate the cause of the error in the server displayed in the KFPH00132-E message, and re-execute the command.
- When online reorganization hold was effected by using the pdorbegin command and specifying the -t option:
If none of the tables specified in the -t option or their referenced tables is a shared table on a HiRDB/Parallel Server, specify the server to be processed in the -s option, and re-execute the command.
If a table specified in the -t option or its referenced table is a shared table on a HiRDB/Parallel Server, re-execute the command without specifying the -s option.
- Other than the above:
- Take action based on the immediately preceding message that was output, and re-execute the command.
- If bb....bb is other than the above: Take action based on the immediately preceding message that was output, and re-execute the command.
KFPH27056-W E+L+S
Warning occurred in reflect service,server=aa....aa
- A warning was returned from the pdorend application process.
- aa....aa: Server name
- S: Continues processing.
- Action
- Take corrective action according to the KFPT (-W) warning message that is output before this message.
KFPH27058-E L+S
Unable to use specified command option aa for bb....bb, command=cc....cc, RDAREA name="dd....dd"
- With command cc....cc, option aa cannot be specified for bb....bb.
- aa: Option name
- -u
- bb....bb: Error cause
- resident RDAREA: In-memory RDAREA
- cc....cc: Command name
- pdhold
- dd....dd: RDAREA name
- S: Invalidates RDAREA "dd....dd" processing, and continues processing.
- Action
- Drop the aa option, and re-execute the command.
KFPH27059-I E
Usage: pdmemdb -k {stay|reload|rels|cancel} {-r RDAREA[,RDAREA ...]|-r ALL} [-p {free|fixed}] [-d]
- An error was found in the pdmemdb option specification format.
- S: Terminates processing.
- Action
- Revise the option specification and re-execute the command.
KFPH27060-I L+S
RDAREA aa....aa, RDAREA="bb....bb"
- aa....aa processing was performed on RDAREA bb....bb.
- aa....aa: Type of RDAREA processing
- stayed: Adding to in-memory
- reloaded: Reloading
- released: Releasing in-memory adding
- canceled: Canceling the update content of the in-memory buffer
- bb....bb: RDAREA name
- S: Continues processing.
KFPH27061-W L+S
Resident RDAREA held due to force released, RDAREA = "aa....aa"
- Because in-memory allocation was forcibly released, the RDAREA aa....aa error was shut down.
- aa....aa: RDAREA name
- S: Continues processing.
- Action
- Take one of the following actions:
- See Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator, and recover the RDAREA.
- The RDAREA is allocating in-memory or synchronizing. To restart operations in that state, use the pdrels command to release error shutdown.
KFPH27062-E L+S
"pdmemdb" command failed, RDAREA="aa....aa", reason=bb....bb
- The pdmemdb command was executed on the RDAREA aa....aa, but an error caused by bb....bb occurred.
- aa....aa: RDAREA name
- bb....bb: Cause of the error
- INVALID_RDKIND: Invalid RDAREA type (an RDAREA other than the user RDAREA, user LOB RDAREA, or list RDAREA is specified)
- INVALID_STATUS: Invalid RDAREA status or in-memory data buffer status
- EXIST_PDORRFST: RDAREA that stores the table performing the reflection processing
- EXIST_SCHEDULE: SCHEDULE attribute RDAREA
- EXIST_SHARED_RDAREA: Shared RDAREA
- EXIST_REPLICA_RDAREA: Replica RDAREA
- NO_GBUF: No global buffer has been allocated.
- S:
- For HiRDB/Single Server:
- Terminates processing.
- For HiRDB/Parallel Server:
- If the cause of the error is INVALID_RDKIND, EXIST_PDORRFST, or EXIST_SHARED_RDAREA:
Terminates processing.
- If the cause of the error is INVALID_STATUS, EXIST_SCHEDULE, EXIST_REPLICA_RDAREA, or NO_GBUF:
Stops all processing of RDAREAs at the back-end server where the RDAREA aa....aa exists. Continues processing RDAREAs that are at locations besides the back-end server.
- Action
- Take one of the following actions:
- If bb....bb is INVALID_RDKIND, EXIST_SHARED_RDAREA, or EXIST_REPLICA_RDAREA:
- Exclude the RDAREA with the error, and re-execute.
- If bb....bb is INVALID_STATUS:
- Execute the pddbls -M command, check the status of the RDAREA and in-memory data buffers, perform the necessary corrective actions, and then re-execute the command.
- If bb....bb is EXIST_PDORRFST:
- Take one of the following actions:
- Re-execute excluding the RDAREA stored in the table performing reflection processing.
- Use the pdorcreate -d command to release the table that performs reflection processing, and then re-execute.
- If bb....bb is EXIST_SCHEDULE:
- Take one of the following actions:
- Use the database structure modification utility to change the RDAREA opening trigger attribute to an attribute other than the SCHEDULE attribute, restart HiRDB, and then re-execute.
- When an invalid RDAREA is being alternated and you are using the standby-less system switchover (1:1) facility, reactivate the system, and then re-execute.
- Exclude the RDAREA with the error, and then re-execute.
- If bb....bb is NO_GBUF:
- Take one of the following actions:
- Use the pdbufmod -k add command to add a global buffer, and then re-execute.
- Restart HiRDB and re-execute with the OTHER buffer allocated.
- Exclude the RDAREA with the error, and then re-execute.
KFPH27064-E E
Unable to execute pdmemdb command because of using Real_Time_SAN_Replication, kind=aa....aa
- If the Real Time SAN Replication facility aa....aa is being used, the pdmemdb command cannot be executed.
- aa....aa: Method of reflecting data to a remote site
- sync: All-synchronous method
- async: All-asynchronous method
- hybrid: Hybrid method
- S: Terminates processing.
- Action
- If in-memory data processing is to be applied, change the system definition so that you are not using the abovementioned data reflection method.
KFPH27065-E E+L
Resident RDAREA held due to HiRDB file error, RDAREA = "aa....aa"
- An HiRDB file access error occurred, so an error-induced shutdown was performed on the in-memory RDAREA aa....aa.
- aa....aa: RDAREA name
- S: Terminates processing.
- Action
- After taking corrective action according to the error message output directly prior to this message, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator and recover the RDAREA.
KFPH27066-E E
Number of RDAREA exceeded aaaa
- The number of RDAREAs specified in the flag argument (after eliminating duplicates) exceeded the maximum value (aaaa).
- aaaa: Maximum value
- S: Terminates processing.
- Action
- Decrease the number of RDAREAs specified in the flag argument (after eliminating duplicates) to a value less than or equal to the maximum. For the maximum number of RDAREAs that can be specified, see Specification of RDAREAs in operation commands and utilities in the manual HiRDB Version 9 Command Reference.
KFPH27100-E L+S
Unable to aaaaaa global buffer pool due to bb....bb, RDAREA="cc....cc"
- Global buffers could not be added or removed for reason bb....bb.
- aaaaaa: Processing content
- add: Add
- delete: Delete
- bb....bb: Reason
- invalid RDAREA type: The RDAREA type is invalid.
- RDAREA cannot specified: The RDAREA cannot be specified.
- cc....cc: RDAREA name
- S: Terminates processing.
- Action
- When the RDAREA type is invalid, an RDAREA other than an RDAREA for LOB is specified in the global buffer for LOB. Specify the correct RDAREA and re-execute the pdbufmod command.
- When no RDAREA can be specified, specify an RDAREA in the global buffer for indexes. No RDAREA can be specified in a global buffer for indexes. Re-execute the pdbufmod command without specifying an RDAREA.
KFPH27101-E L+S
Too small buffer size, buffer size=aaaaa,RDAREA="bb....bb", page size=ccccc
- The global buffer was not allocated to RDAREA "bb....bb" because the buffer was too small.
- aaaaa: Buffer size
- bb....bb: RDAREA name
- ccccc: RDAREA page length
- S: Terminates processing.
- Action
- The buffer size must be equal to or greater than the RDAREA page length. Allocate a global buffer to meet this condition.
KFPH27102-E L+S
Invalid option is specified, reason code=aa
- An invalid combination of pdbufmod command options was found.
- aa: Reason code
- 1: An invalid option was specified in the specified modification type.
- 10: The -r, -b, -i, or -o option was not specified even though a modification type was added (-k add).
- 11: Even though the -n option was not specified when adding a modification type (-k add), the -l, -m, -p, -w, or -y option was specified.
- 12: Even though the -i or -o option was specified when adding a modification type (-k add), the -n option was not specified.
- 22: Even though the modification type was modified (-k upd), the modified option was not specified. Or, when the concurrent execution maximum prefetch count is 0, only the -p option is specified.
- 40: The -r option was specified in the global buffer for LOB.
- 41: The -b option was specified in an RDAREA other than one for the LOB global buffers.
- S: Terminates processing.
- Action
- Specify the correct option and re-execute the pdbufmod command.
KFPH27103-I L+S
Global buffer pool aaaaaaa,global buffer pool name=bb....bb, server=cc....cc
- The specified global buffer was added, removed, or modified.
- aaaaaaa: Processing content
- added: A global buffer was added.
- deleted: A global buffer was removed.
- updated: A global buffer was updated.
- bb....bb: Global buffer name
- cc....cc: Server name
- S: Terminates processing.
KFPH27104-I L+S
RDAREA "aa....aa" bb....bb,global buffer pool name=cc....cc, server=dd....dd
- The specified RDAREA was allocated to or removed from the global buffer.
- aa....aa: RDAREA name
- bb....bb: Processing content
- added: An RDAREA was allocated to a global buffer
- deleted: An RDAREA was removed from a global buffer
- cc....cc: Global buffer name
- dd....dd: Server name
- S: Continues processing.
KFPH27105-E L+S
Unable to execute aa....aa command due to command in process
- The aa....aa command could not be executed because it is in progress.
- aa....aa: Command name (pdbufmod)
- S: Terminates processing.
- Action
- After the command in progress terminates, re-execute the pdbufmod command.
KFPH27106-E L+S
Unable to execute aa....aa commnad due to specified index name not found
- The aa....aa command could not be executed because the specified index was not found.
- aa....aa: Command name (pdbufmod)
- S: Terminates processing.
- Action
- Specify the correct index name, and then re-execute the pdbufmod command.
KFPH27107-E L+S
aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, index = cc....cc
- The aa....aa command in specified index cc....cc could not be executed because data dictionary RDAREA bb....bb could not be referenced.
- aa....aa: Command name (pdbufmod)
- bb....bb: Data dictionary RDAREA name
- cc....cc: Index name
- S: Invalidates this operation and continues processing.
- Action
- After the data dictionary RDAREA returns to normal status, re-execute the pdbufmod command.
KFPH27108-E L+S
Failed to allocate semaphore
- Allocation of a semaphore resource failed.
- S: Terminates processing.
- Action
- Take one of the following actions before re-executing the pdbufmod command:
- Increase the maximum (in HP-UX, semmns; in Solaris, seminfo_semmns; and in Linux, SEMMNS) semaphore count in the system.
- Increase the maximum (in HP-UX, semmni; in Solaris, seminfo_semmni; in Linux, SEMMNI; and in Windows, PDUXPLSEMMAX) semaphore identifier count.
- Delete any unnecessary global buffers.
KFPH27109-E L+S
Unable to add aa....aa global buffer pool due to already allocated, global buffer pool name=bb....bb
- An index or -o option global buffer could not be added because the target global buffer was already in use.
- aa....aa: Global buffer types
- index: Index global buffer
- other: Global buffer with the -o option
- bb....bb: Global buffer name
- S: Terminates processing.
- Action
- Use the dbufls -k def command to check the global buffers currently in use. Re-execute the command if necessary.
KFPH27110-E L+S
Unable to add global buffer pool due to no RDAREA
- A global buffer could not be added because no RDAREA was found to which to allocate the global buffer.
- S: Terminates processing.
- Action
- Use the dbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.
KFPH27111-E L+S
Unable to delete due to no RDAREA "aa....aa", global buffer pool name=bb....bb
- Global buffer bb....bb could not be deleted because RDAREA "aa....aa" was not allocated.
- aa....aa: RDAREA name
- bb....bb: Global buffer name
- S: Terminates processing.
- Action
- Use the pdbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.
KFPH27112-E L+S
pdbufmod command failed due to specified name not found, global buffer pool name=aa....aa, server=bb....bb
- The pdbufmod command could not be executed because the specified global buffer aa....aa was not defined on server bb....bb.
- aa....aa: Global buffer name
- bb....bb: Server name
- S: Continues processing.
- Action
- Use the pdbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.
KFPH27113-E L+S
Unable to execute pdbufmod command due to HiRDB Advanced High Availability not setup
- The pdbufmod command could not be executed because HiRDB Advanced High Availability was not set up.
- S: Terminates processing.
- Action
- Set up HiRDB Advanced High Availability, and then re-execute the command.
KFPH27114-E L+S
Unable to delete global buffer pool due to resident RDAREA, RDAREA="aa....aa"
- It is not possible to release the global buffer to which the in-memory RDAREA aa....aa was allocated.
- aa....aa: RDAREA name
- S: Terminates processing.
- Action
- Use the pdmemdb -k rels command to release in-memory allocation of the RDAREA in question, and then re-execute.
KFPH28001-E L
Insufficient memory on DYNAMIC_SHMPOOL for DB exclusive control, server=aa....aa
- For server aa....aa, the shared memory used for exclusive control is insufficient.
- aa....aa: Server name
- S: Invalidates the transaction.
- P:
- When NO is specified in the client environment definition PDDBLOG and the transaction is executed to update a shared table:
Consider changing PDDBLOG to YES.
- When the transaction involves executing the LOCK statement with the IN EXCLUSIVE MODE specification for multiple shared tables:
Consider reducing the number of shared tables.
- When the transaction involves executing in non-shared tables using the UNTIL DISCONNECT specification LOCK statement:
Consider dropping the UNTIL DISCONNECT specification.
- Action
- The value of the pd_lck_until_disconnect_cnt operand is inappropriate. Revise it by increasing the specified value, and restart HiRDB.
KFPH29005-W L
Unable to check work HiRDB file system area, return code=aa....aa, file system=bb....bb (cc....cc)
- An error occurred during a utilization rate check on HiRDB file system area for work tables.
- aa....aa: Return code
- bb....bb: Name of HiRDB file system area
- If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.
- cc....cc: Server name
- S: Continues processing by temporarily skipping checking the utilization rate on the affected HiRDB file system area for work tables. However, the system does not discontinue checking the utilization rate. If the same error persists in utilization rate checks on the same area, the system outputs this error message at the first occurrence of the error, without generating subsequent messages.
- O: Notify HiRDB administrator.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error. Utilization rate checks are done on HiRDB file system area for work tables according to the specification made in pd_watch_resource or pdwork_wrn_pnt.
KFPH29006-W L
HiRDB file "aa....aa" information, return code=bbbbb, HiRDB file name=cc....cc
- The "aa....aa" processing for HiRDB file cc....cc terminated with error code bbbbb.
- aa....aa: Type of HiRDB file processing:
- create: HiRDB file creation
- delete: HiRDB file deletion
- bbbbb: Error code
- cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of HiRDB file exceeds 148 characters, the last 148 characters of HiRDB file path name are output.
- S: Continues processing.
- Action
- See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.
- However, if "aa....aa" is create and the error code is -1541, HiRDB file the user tried to create has already been defined. It is possible that the deletion of HiRDB file failed first. In this case, see the KFPH29006-W message issued before this message to check the delete error code for "aa....aa" in 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.
KFPH29008-I L
Work buffer expanded, server=aa....aa, process ID=bb....bb
- The work table buffer size specified in the pd_work_buff_size operand in the system definition was insufficient, but a work table buffer extension was available because the pd_work_buff_expand_limit operand was specified.
- aa....aa: Server name
- bb....bb: Process ID
- S: Continues processing.
- Action
- Operation premised on availability of the work table buffer extension:
- To suppress the outputting of this error message, use the pd_work_table_option operand to specify that message output be suppressed when extending the work table buffer length.
- Operation not premised on availability of the work table buffer extension:
- Re-evaluate the specification value of the pd_work_buff_size operand so that securing an extension of the work table buffer is not necessary.
- Notes
- When extending the work table buffer, release the secured extended work table buffer when the work table usage count in the applicable server processes is 0. The work table usage count becomes 0 in the following situations:
- When all cursors in use were closed (however, the work table usage count may not become 0 in some internal processes)
- When not using a holdable cursor and transactions ended normally or transactions were cancelled
- When using a holdable cursor and the UAP is isolated from HiRDB
- When using a HiRDB edition other than Linux or Windows and extending the work table buffer, terminate processes, including even resident processes, at the following events to free up memory:
- For HiRDB/Single Server:
- Terminate single server processes when detaching a UAP from HiRDB.
- For HiRDB/Parallel Server:
- Terminate the back-end server process or dictionary server process when not using a holdable cursor, when transactions terminate normally, or when transactions are deleted.
- When using a holdable cursor, terminate the back-end server process or the dictionary server process when detaching a UAP from HiRDB.
KFPH29009-W L
Unable to expand work buffer due to insufficient memory, server=aa....aa,process ID=bb....bb,size=cc....cc
- An attempt to secure a work table buffer extension according to specification of the operand pd_work_buff_expand_limit was made, but it failed because of insufficient process private area.
- aa....aa: Server name
- bb....bb: Process ID
- cc....cc: Total work table buffer size in the applicable process (in kilobytes)
- S: Continues processing.
- Action
- Operation premised on availability of the work table buffer extension:
- Reduce the specification value of the pd_work_buff_expand_limit operand to no greater than cc....cc.
- Operation not premised on availability of the work table buffer extension:
- Do not specify the pd_work_buff_expand_limit operand.