Nonstop Database, HiRDB Version 9 Command Reference
![[Contents]](FIGURE/CONTENT.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
- The table below lists and describes the return codes of pdconstck and explains the actions to be taken.
Table 13-27 Return codes of pdconstck and actions to be taken
| Return code |
Description |
Action |
| 0 |
Terminated normally. |
None |
| 4 |
Terminated normally, but there was a constraint that lacked integrity as a result of integrity checking (this includes cases such as when integrity checking on constraints was cancelled because the number of violation key values exceeded the specified maximum). |
Correct the integrity of the constraints resulting in check pending status and then re-execute. |
| 8 |
Terminated abnormally. |
If necessary, eliminate the cause of the error and then re-execute. |
- Note
- If an error occurs during pdconstck's termination processing after return code 0 or 4 has been output with the KFPL50001-I message, the return code remains 0 or 4, not 8.
- When pdconstck is executed while the security audit facility is being used, the audit trails that are acquired depend on the return code:
- When the return code is 0 or 4:
- Audit trails are acquired if SUCCESSFUL or ANY is specified for WHENEVER in CREATE AUDIT.
- When the return code is 8:
- Audit trails are acquired if UNSUCCESSFUL or ANY is specified for WHENEVER in CREATE AUDIT.
- If you selected utf-8 or utf-8_ivs as the character encoding in the pdsetup command, a BOM is not added to the file that is output by pdconstck.
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.