Scalable Database Server, HiRDB Version 8 Messages

[Contents][Back][Next]

5.1 Error codes returned from HiRDB file system access requests

Table 5-1 lists the error cause codes returned from HiRDB file system access requests.

Table 5-1 Error cause codes returned from HiRDB file system access requests

Error Code Description Action
-1511 Specified path name is invalid:
  • The path name contains an invalid character.
  • The length of the path name exceeds the maximum (167 characters).
  • The length of the HiRDB file system area name exceeds the limit (165 characters).
  • The length of the HiRDB file name exceeds the maximum (30 characters).
 Review the path name specified in the control statement, command line, and system definition file.
In a facility in which HiRDB automatically generates HiRDB files, in some cases the path length exceeds the limit, depending on the length of the HiRDB file system area length. HiRDB file system areas should be specified in conformance to the respective limits, as follows:
  • Work table file (server definition pdwork operand): 141 characters maximum
  • Plug-in index delay batch updating (server definition pd_plugin_ixmk_dir operand): 136 characters maximum
If there are no problems in this regard, but the error persists, contact a customer engineer.
-1514 The sector length specification is invalid.
  • The HiRDB file system area created with the specified sector length is not supported.
  • The RDAREA page length is not an integral multiple of the HiRDB file system area sector length.
  • Use a HiRDB file system area created without specifying a sector length.
  • Correct the RDAREA page length.
-1532
  • A file other than a regular file or a character-type special file (for Windows, direct disk access) was specified.
  • HiRDB file system area is not found.
  • Review the path name specified in the control statement, command line, or system definition file to be sure that it is not in error.
  • Files other than a regular file or a character-type special file (direct disk access for Windows) cannot be used as a HiRDB file system area.
  • Check to see if the HiRDB file system area indicated in the message has been deleted or the symbolic link is broken.
-1534 Lock error occurred.
  • Execute the pdfls-L command on the HiRDB file system area or the HiRDB file indicated in the message to check for any process exercising lock control. If a process exercising lock control is identified, execute the affected command after that process has terminated. If a process exercising lock control is not identified, re-execute the command after a period of time.
  • If the HiRDB file system area indicated in the message is being used by a command, wait until that command terminates, and then re-execute the affected command.
  • If this error occurs because of the execution of a command, terminate HiRDB, and then re-execute the command (provided that the command can be executed while HiRDB is stopped).
  • If the above measures fail to resolve the problem, contact a customer engineer.
-1535
  • There is not enough free space in the HiRDB file system area.
  • There is not enough free space on the disk on which the HiRDB file system area was created, and the disk is full.
  • Use the pdfstatfs command to check the amount of free space in the HiRDB file system area that was specified in the control statement, the command line, and the system definition file. If there is not enough free space to accommodate the size of the file to be created, specify another HiRDB file system area.
  • If the disk became full when operations were performed on the HiRDB file system area for regular files, either delete other files or expand the disk to increase the amount of free space.
  • In UNIX, if a character special file HiRDB file system area is in use, the disk will not become full. However, if operations are performed using a symbolic link, check to see if a link is established to regular files.
-1536 The limit on the number of files that can be created in the HiRDB file system area has been exceeded.
  • Increase the maximum number of files (specified in the pdfmkfs -l command) and recreate the HiRDB file system area.
  • In the control statement, the command line, and the system definition file, specify another HiRDB file system area that has more space for file creation.
-1538 Specified area is not a HiRDB file system area.
  • Determine whether the file initialized as a HiRDB file system area is specified in the control statement, the command line, and the system definition file.
  • It is possible that the HiRDB file system area is corrupt. Execute the pdfls command on the indicated path to determine whether the HiRDB file system area has been destroyed.
-1539 HiRDB file was not found.
  • Determine whether the correct HiRDB file is specified in the path name specified in the control statement, the command line, and the system definition file. HiRDB file names can be verified by using the pdfls command.
  • If an error occurred in a HiRDB file that is a part of the RDAREA during HiRDB operations, a possible cause of the problem may be that the RDAREA was recovered from a backup taken before RDAREA reorganization, or the HiRDB file was forcibly removed through the use of the pdfrm command. If this is the case, either recover the RDAREA using the proper recovery procedures or reinitialize the RDAREA.
If neither possibility applies, contact a customer engineer.
-1540 Access privilege is undefined.
  • Review the access privilege for the file specified in the control statement, the command line, and the system definition file.
  • For Windows, if the error occurred in an area on which direct disk access was used, check to see if a formatted disk was specified.
-1541 HiRDB file has already been defined. The HiRDB file specified in the control statement, the command line, and the system definition file already exists. Specify a HiRDB file in a manner that avoids duplication.
If there are no duplicate HiRDB files, but the error persists, contact a customer engineer.
-1543 Versions do not match.
  • The version of HiRDB currently running is older than the version that created the HiRDB file system area. Areas created using a new version of HiRDB cannot be used with an older version of HiRDB.
  • If HiRDB with more than one version is installed, review the absolute path name specified in command execution.
-1544 I/O error occurred. Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile).
If there is no KFPO00107-E message, contact a customer engineer.
-1548 There are not enough lock segments. Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile). If the errno is 46 (ENOLCK), it is an indication that there are not enough OS lock segments. In the HiRDB Version 8 Installation and Design Guide, see the section on how to estimate operating system parameters, and increase the upper limit.
For HP-UX, review the nflock operand.
If any other OS is being used, wait for the other process that is using the lock to terminate, and then reexecute.
If the above measures fail to resolve the problem, contact a customer engineer.
-1549 The system open count exceeds the limit. Or the process open count exceeds the limit. Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile).
In UNIX, refer to estimating operating system parameters in the manual HiRDB Version 8 Installation and Design Guide, and if insufficient, increase the limit.
Review the following values:
  • HP-UX:
    nfile, maxfiles_lim
  • Solaris:
    rlim_fd_max
  • AIX 5L:
    nofiles_hard
  • Linux:
    NR_FILE, NR_OPEN
-1550 Memory is insufficient. Review the memory requirements. If there is a problem, take corrective action such as increasing the memory or reducing the number of resident processes.
If the corrective action fails to resolve the problem, contact a customer engineer.
-1555 There are insufficient log segments, the number of open files exceeded the limit, or there is insufficient memory. Take the corrective action indicated in error codes -1548, -1549, and -1550.
If these actions do not solve the problem, contact a customer engineer.
-1556 During creation of an RDAREA
  • An attempt was made to allocate multiple, fragmented free spaces to a file; however, allocation failed either because of the lack of a specification for a maximum increment count (pdfmkfs -e) for the HiRDB file system area or the specified value is too low.
  • The number of HiRDB file allocation extents is greater than the limit of 24; extents cannot be allocated.
During expansion of an RDAREA
  • An attempt was made to allocate a new free space to files. However, either there is no specification for a maximum increment count (pdfmkfs -e) for the HiRDB file system area or the specified value is too low. Therefore, space cannot be allocated.
  • The number of HiRDB file allocation extents is greater than the limit of 24; extents cannot be allocated.
 HiRDB file for RDAREA
Take one of the following actions:
(1) Follow the procedures outlined below to consolidate the extents and the fragmented free spaces in the HiRDB file system area:
  1. Normally terminate HiRDB*.
  2. Use the pdfbkup command to back up the area.
  3. Use the pdfmkfs command to initialize the area.
    Before taking these actions, execute the pdfstatfs command on the area that generated the error to check the difference between the total increment count (current expand count) and the increment count limit (available expand count). If the difference is less than 23, it is an indication that the maximum increment count is too low. If this is the case, increase the maximum increment count (the -e option) when the area is initialized.
  4. Use the pdfrstr command to recover the area.
  5. Normally start HiRDB*.

* Items 1 and 5 can also be accomplished by the following procedures:
1. Put the RDAREA allocated to the area in command shutdown and closed states, and then refresh (pdpfresh) the corresponding server process.
5. Put the RDAREA allocated to the area in shutdown release and open states.
(2) When creating an RDAREA, allocate the files that compose the RDAREA to another HiRDB file system area. When expanding an RDAREA, specify a HiRDB file in another file system area, and expand the RDAREA using that file.
HiRDB file for work tables
Execute the pdfstatfs -d command on the HiRDB file system area for work tables, and check the value of the maximum user area (peak capacity). If there is adequate space in the total capacity (user area capacity) of the area, increase the specified value in the maximum increment count (the -e option), and initialize the area using the pdfmkfs command. If the maximum user area is close to the total capacity, increase the size of the HiRDB file system area (the -n option), and reinitialize the area using the pdfmkfs command.
HiRDB file for utilities
Take one of the following actions:
(1) Increase the specified value in the maximum increment count (the -e option), and reinitialize the area using the pdfmkfs command.
(2) For a utility in which an initial allocation size and an increment size can be specified, increase the initial allocation size and the increment size.
-1562 The purpose of the file being created does not match the purpose of the HiRDB file system area.
  • Check to see if the purpose of use of the HiRDB file system area specified in the control statement, the command line, and the system definition file is correct. The pdfstatfs command can be used to verify the purpose of use of the HiRDB file system area.
  • For a Linux version, there are HiRDB files that cannot be created on a character-type special file. In this case, the HiRDB file system area set up on a regular file should be used.
  • An attempt was made to create a shared RDAREA in a HiRDB file system area for which the purpose is not SDB. When using a shared RDAREA, specify SDB as the purpose, and create the shared RDAREA in an initialized HiRDB file system area.
-1565 A large file is being used (in Windows, files exceeding 2 GB), but pd_large_file_use is not specified. Specify Y in the pd_large_file_use operand.
Other [Figure] Contact the customer engineer.

[Figure]: Not applicable

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.