C. Error Codes Returned from Access Requests for an Embedded Database File System

-1511

The path name is specified incorrectly.

• An invalid character is specified in the path name.

• The length of the path name exceeds the limit (167 characters).

• The length of the embedded database file system area name exceeds the limit (165 characters).

• The length of the embedded database file name exceeded the limit (30 characters).

Recheck the path name specified on the command line.

If there is no problem, contact the system administrator.

-1514

The sector length is specified incorrectly.

• The system does not support embedded database file system areas that are created with a sector length specified.

Use an embedded database file system area that is created without a sector length specified.

If this situation does not apply, contact the system administrator.

-1532

• A file other than an ordinary file is specified.

• The embedded database file system area was not found.

• Recheck the path name specified on the command line.

• A file other than an ordinary file cannot be used as an embedded database file system area.

• Check whether the embedded database file system area indicated in the message is deleted and whether the symbolic link is broken.

-1534

An exclusivity error occurred.

• If a command is using the embedded database file system area indicated in the message, wait until the command terminates, and then retry.

• If command execution results in this error, stop the embedded database and then execute the command (only for commands that are executed when the embedded database is not running).

• If you cannot correct the problem by taking the above actions, contact the system administrator.

-1535

• There is not enough free space in the embedded database file system area.

• The disk on which the embedded database file system area was created became full because free space was insufficient.

If the disk was full during operation of the embedded database file system area for an ordinary file, delete other files or expand disk capacity to increase free space.

-1538

This area is not an embedded database file system area.

The embedded database file system area may have been corrupted. Contact the system administrator.

-1539

The embedded database was not found.

If an error occurred in an embedded database file in the RDAREA during operation of the embedded database, the probable cause is that a backup existing before the RDAREA configuration was changed was used for recovery. Another probable cause is that the embedded database file was forcibly deleted. Recover the RDAREA using the correct recovery procedure or re-initialize it.

If the situation above does not apply, contact the system administrator.

-1540

You do not have access permission.

• Review the access permissions for the files specified on the command line and in the system definition file.

• In Windows, if an error occurred in an area using direct disk access, check whether a formatted disk was specified.

-1541

The embedded database file has already been defined.

The embedded database file specified on the command line already exists. Specify a unique name for the embedded database file.

If there is no file that has the same name as the specified file, contact the system administrator.

-1543

Versions are inconsistent.

• The version of the operating embedded database is older than the version with which the embedded database file system area was created. Areas created with a new version of HiRDB cannot be used with an old version of the embedded database.

• When multiple versions of embedded databases are installed, check the absolute path name you want to use for execution.

-1544

An I/O error occurred.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog.

If the KFPO00107-E message is not output, contact the system administrator.

-1548

Lock segments are insufficient.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog. If errno is 46 (ENOLCK), OS lock segments are insufficient.

In HP-UX, recheck nflock.

For other OSs, wait until another process using the lock terminates, and then retry.

If you cannot correct the problem by taking the above actions, contact the system administrator.

-1549

The number of open files exceeded the maximum for the system. Alternatively, it exceeded the maximum for the process.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog.

Check the following values:

• In HP-UX

  nfile and maxfiles_lim

• In Solaris

  rlim_fd_max

• In AIX 5L

  nofiles_hard

• In Linux

  NR_FILE, NR_OPEN

-1550

Memory is insufficient.

Review the memory estimate. If you find any problems, take action such as increasing memory or reducing the number of resident processes.

If you cannot correct the problem by taking the above action, contact the system administrator.

-1555

In the parallel I/O function, lock segments are insufficient, the number of open files exceeds the maximum, or memory is insufficient.

Take the actions provided for error codes -1548, -1549, and -1550.

If you cannot correct the problem by taking these actions, contact the system administrator.

Others

--

Contact the system administrator.