KFAA51503-E
The aa....aa is invalid. (path = bb....bb, reason = cc....cc, errno = dd....dd) (E+M)
One of the following specifications is invalid:
-
Synonym list definition file name
-
Name of the storage directory for synonym dictionary files
-
Name of the multi-node synonym dictionary storage directory
- aa....aa: Invalid item
-
-
synonym-list-definition-file: Synonym list definition file name
-
synonym-dictionary-storage-directory: Name of the storage directory for synonym dictionary files
-
multi-node-synonym-dictionary-storage-directory: Name of the multi-node synonym dictionary storage directory
-
- bb....bb: Specified path name
-
If cc....cc is No-definition, an asterisk (*) is displayed.
- cc....cc:
-
Cause of the error
- dd....dd:
-
Error number
- S:
-
Terminates processing.
- Action:
-
Take the corrective action for the cause of the error indicated by cc....cc.
Display of cc....cc
Cause of the error
Corrective action to take
No-file
The synonym list definition file specified in the dictionary creation file does not exist. Alternatively, anything other than a file is specified.
Correct the synonym list definition file name specified in the dictionary creation file.
Invalid-permission
Access privilege (read or write privilege) for the file or directory has not been granted.
Grant access privilege (read or write privilege) for the file or directory by using the OS's chmod command or the like.
No-definition
The adb_syndict_storage_path operand or adb_syndict_node_storage_path operand is not specified in the server definition.
Add the adb_syndict_storage_path operand or adb_syndict_node_storage_path operand to the server definition.
Not-directory
The specified path does not exist. Alternatively, the specified path is not a directory.
Correct the specified path name.
Illegal-symbolic-link
The link destination for the specified symbolic link cannot be acquired.
Other-access-error
An access system call error other than the above occurred.
Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.
If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.