C. Error Codes Returned from Access Requests for an Embedded Database File System
The following table lists the error reason codes returned from access requests for an embedded database file system.
Error code |
Description |
Action |
---|---|---|
-1511 |
The path name is specified incorrectly.
|
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.
|
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 |
|
|
-1534 |
An exclusivity error occurred. |
|
-1535 |
|
|
-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. |
|
-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. |
|
-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:
|
-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. |
- Legend:
-
--: Not applicable