KFPS01279-W
Unable to use log file. element file: aa....aa, system A/B: b,reason code=cccc-dd (L)
The status of the aa....aa log file cannot be referenced for the reason indicated in cccc. This log file will be ignored.
aa....aa: Log file name
b: The system where an error occurred (a or b)
cccc: Reason code
dd: System maintenance information
- (S)
-
Continues processing, ignoring the log file.
- (O)
-
There is no problem if you do not use the log file indicated in the message, or if the message KFPS01278-W for the file group containing the log file is not output immediately after this message. If neither of the above is applicable, determine the cause of the error according to the reason code, and then contact the administrator.
- Action
-
There is no problem if the log file shown in the message is not required for executing the ajsembdbrstr command. If the log file is required for executing this command, determine the cause of the error according to the reason code, and perform recovery by following the instructions in the message KFPS01278-W, and then, retry. The following lists the reason codes.
Reason code
Meaning
Operator action
Action by the embedded database system administrator
101
A memory shortage occurred.
Wait until the currently running process terminates, and then re-execute the command.
Re-estimate memory.
201
The file name is invalid.
Probable causes are:
-
An invalid character is specified in the path name.
-
The length of the embedded database file name exceeded the limit (30 characters).
Specify the file name correctly, and then re-execute the command
--
202
The name of the embedded database file system area for the specified path is not an embedded database file system area.
Check the name of the embedded database file system area for the specified path, and then re-execute the command
Check the file specification in the pdlogadpf operand.
203
The specified path device is not initialized for the embedded database file system.
--
207
The upper limit was exceeded when the embedded database file system area for the specified path was opened.
--
208
You do not have permission to access the embedded database file system area for the specified path.
Check access permissions for the embedded database file.
Check the file specification in the pdlogadpf operand.
209
An I/O error occurred.
Determine the cause of the I/O error, and take action.
--
210
The version of the embedded database file system is inconsistent.
--
Check the file specification in the pdlogadpf operand.
211
You do not have permission to access the specified file.
Check the access permission for the log.
--
212
The specified file is not found.
--
Check the file specification in the pdlogadpf operand.
221
Lock segments are insufficient.
Check the number of record lock segments that is specified when the OS is started.
222
The system log file is being used by another process.
Check the operation status of the system log file or its file group, and then re-execute the command.
--
603
Management information on the file is corrupted.
Initialize this file.
605
The file structure of the file differs from the current file structure. The file structure might have been changed.
Contact the embedded database system administrator to find out if the file structure has been changed. If the file structure has not been changed, initialize this file.
Check the definition to make sure that the file group that uses the file and the system log file have not been changed. If the file structure has been changed, return the file structure in the definition to its original state.
1607
The file has not been used in the embedded database.
Check the file group.
--
- Legend:
-
--: Not applicable
-