Mining/Search Engine messages
IUSS0001E
Failed to get child categories: category_id_1={0} category_id_2={1}
- Explanation
- The error occurred when comparing the categories.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0002W
Database configuration error: value for the {0} is not a sub-root (direct subcategory of the root category) category. category_entry@value={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0003E
Database configuration error: value for the {0} is invalid. category_entry@value={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0004E
Database configuration error: application entry is not set. application_name={0} database={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0005E
InstantiationException: {0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0006E
IllegalAccessException: {0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0007E
ClassNotFoundException: {0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0008E
Database configuration error: factory implemetation class not found. application={0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0009E
Database configuration error: unknown impl name. impl={0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0011E
Database configuration error: parameter not set. impl={0} param={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0012E
Database configuration error: parameter must be an integer value. impl={0} param={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0013E
Database configuration error: multiple entry for one interface found. interface={0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0015W
Database configuration error: language not set.
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0018E
Database configuration error: path property not set. path_entry={0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0019E
Failed to read dbConfig file: {0}
- Explanation
- The error occurred when reading the database configuration.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0022E
Database configuration error: {0}
- Explanation
- The error occurred when reading the database configuration.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0024W
Database configuration error: empty category entry is found. (name, value)=({0},{1}) ignored.
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0026E
Database configuration error: parameter (common impl) {0} is not set or not integer.
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0034E
Database configuration error: missing tags. tag={0}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0035E
System property TAKMI_HOME is not set.
- Explanation
- TAKMI_HOME is not set.
- User Response
- Check the environment variable.
Parent Topic : Mining/Search Engine messages
IUSS0036E
Invalid directory: TAKMI_HOME={0}
- Explanation
- TAKMI_HOME is invalid directory.
- User Response
- Check the environment variable.
Parent Topic : Mining/Search Engine messages
IUSS0037I
TAKMI_HOME={0}
- Explanation
- TAKMI_HOME is set.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0038E
Global configuration error: {0}
- Explanation
- There is a setting error of the global configuration.
- User Response
- Check the setting of global_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0039E
Global configuration error: attribute {0} is not set. tag={1}
- Explanation
- There is a setting error of the global configuration.
- User Response
- Check the setting of global_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0040E
Global configuration error: unknown {0} value={1}
- Explanation
- There is a setting error of the global configuration.
- User Response
- Check the setting of global_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0041E
Global configuration error: directory not found. db_name={0} directory={1}
- Explanation
- There is a setting error of the global configuration.
- User Response
- Check the setting of global_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0042E
Database configuration error: multiple implementations are specified for a single interface. interface={0}
- Explanation
- The error occurred when adding the search function to the search engine.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0043I
Search function added. interface={0} impl={1}
- Explanation
- The search function was added to the search engine.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0044E
Failed to add search function. interface={0} impl={1}
- Explanation
- The error occurred when adding the search function to the search engine.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0046I
Mining function added. interface={0} impl={1}
- Explanation
- The mining function was added to the mining engine.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0047E
Failed to add mining function. interface={0} impl={1}
- Explanation
- The error occurred when adding the mining function to the mining engine.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0048I
Database started. name={0}
- Explanation
- The database was started.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0049I
The search engine closed.
- Explanation
- The search engine was closed.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0050I
The mining engine closed.
- Explanation
- The mining engine was closed.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0051I
The index reader closed.
- Explanation
- The index reader was closed.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0053E
Failed to close the search engine.
- Explanation
- The error occurred when closing the search engine.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0055E
Failed to close the mining engine.
- Explanation
- The error occurred when closing the mining engine.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0057E
Failed to close the index reader.
- Explanation
- The error occurred when closing the index reader.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0058E
Failed to close the database. name={0}
- Explanation
- The error occurred when closing the database.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0059I
Database closed. name={0}
- Explanation
- The database was closed.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0060I
Application configuration entry is added: config_class={0}
- Explanation
- The application configuration entry was added.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0061E
Database not found. name={0}
- Explanation
- The database was not found.
- User Response
- Check the setting of global_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0062E
Failed to close the database. name={0}
- Explanation
- The error occurred when closing the database.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0063E
Null IndexWriter.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0064E
Failed to parse the text : rawText=[{0}]
- Explanation
- The error occurred when parsing the text.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0065E
Failed to parse the text : rawText=[{0}]
- Explanation
- The error occurred when parsing the text.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0066E
Failed to write to the indices : rawText=[{0}]
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0067E
Failed to close resources.
- Explanation
- The error occurred when closing the resource.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0069E
Failed to initialize SAX parser.
- Explanation
- The error occurred when initializing the sax parser.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0070E
I/O error occurred during the read from {0}
- Explanation
- The error occurred when reading the atml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0071E
Severe runtime error occurred during the read from {0}
- Explanation
- The error occurred when reading the atml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0072E
Severe error occurred during the read from {0}
- Explanation
- The error occurred when reading the atml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0073E
Failed to parse the docString[{0}]
- Explanation
- The error occurred when parsing the atml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0074I
Load map: {0}
- Explanation
- The category fragment label map files were loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0075I
Load pattern template: {0}
- Explanation
- The pattern template files were loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0076I
No pattern template.
- Explanation
- The pattern template file did not exist.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0077I
Pattern file generated: {0}
- Explanation
- The pattern file was generated.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0078I
Backup: {0} to {1}
- Explanation
- The pattern file was backed up.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0079E
[{0}] is not a directory.
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0080E
Error occurred when reading database_config.xml.
- Explanation
- The error occurred when reading database_config.xml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0081W
Duplicate id : {0} and it does not override the previous element.
- Explanation
- The specified occurrence id of the keyword feature element was duplicated.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0082E
Null DateFormat.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0084E
Failed to parse the given date string[{0}] with an severe error.
- Explanation
- The error occurred when parsing the date string.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0085E
Search function registration error: impl class must be subclass of the abst class (specified by name attribute). abst_class={0} impl_class={1}. See database_config.xml.
- Explanation
- The error occurred when adding the search function to the search engine.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0086E
Failed to initialize the index reader function. index_reader_function_class={0}
- Explanation
- The error occurred when initializing the index reader function.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0087E
Search function registration error: multiple entries for the interface. abst_class={0}. See database_config.xml.
- Explanation
- The error occurred when adding the search function to the search engine.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0088I
Loading SearchQueryValidator done.
- Explanation
- The search query validator was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0089I
Null SearchQuery.
- Explanation
- The search query is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0090I
Null SearchCondition.
- Explanation
- The search condition is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0091I
Null SearchConditionNode.
- Explanation
- The search condition node is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0092I
Duplication of nodes was found.
- Explanation
- The search condition node has the duplicate node.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0093I
Too many nodes in the search query.
- Explanation
- The search condition node has too many nodes.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0094I
Null children in a [And|Or]SearchConditionNode.
- Explanation
- The children of the search condition node is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0095I
A [And|Or]SearchConditionNode has no children.
- Explanation
- The search condition node has no children.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0096I
Null child in a [And|Or]SearchConditionNode.
- Explanation
- The child of the search condition node is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0097E
Invalid range : -from[{0}],-to[{1}]
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0098W
-from[{0}] is greater than -to[{1}], no entries will be processed.
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0099I
DataEntry processing start.
- Explanation
- This is the start message of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0100I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0101E
Directory cannot be created : [{0}]
- Explanation
- The error occurred when creating the directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0102I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0103I
{0}-th DataEntry[{1}] is skipped.
- Explanation
- The processing of the data entry was skipped.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0104I
DataEntry[{0}] processing start.
- Explanation
- This is the start message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0105I
DataEntry[{0}] processing done.
- Explanation
- This is the end message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0106I
DataEntry processing done.
- Explanation
- This is the end message of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0107I
Time : {0} sec.
- Explanation
- This is the processing time of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0108E
Exception occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0109E
Error occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0110E
Throwable occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0111I
DataEntry processing start.
- Explanation
- This is the start message of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0112I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0113E
Directory cannot be created : [{0}]
- Explanation
- The error occurred when creating the directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0114I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0115I
DataEntry[{0}] processing start.
- Explanation
- This is the start message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0116I
DataEntry[{0}] processing done.
- Explanation
- This is the end message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0117I
DataEntry processing done.
- Explanation
- This is the end message of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0118I
Time : {0} sec.
- Explanation
- This is the processing time of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0119E
Exception occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0120E
Error occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0121E
Throwable occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0123E
Failed to get a list of data entries.
- Explanation
- The error occurred when getting the data entries.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0124I
No diff data entries were found.
- Explanation
- The different data entries did not exist.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0125I
DataEntry processing start.
- Explanation
- This is the start message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0126I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0127E
Directory cannot be created : [{0}]
- Explanation
- The error occurred when creating the directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0128I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0129I
DataEntry[{0}] processing start.
- Explanation
- This is the start message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0130I
DataEntry[{0}] processing done.
- Explanation
- This is the end message of the data entry processing.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0131I
DataEntry processing done.
- Explanation
- This is the end message of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0132I
Time : {0} sec.
- Explanation
- This is the processing time of the data entry indexer.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0133E
Exception occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0134E
Error occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0135E
Throwable occurred.
- Explanation
- The error occurred when processing the data entry.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0136I
File Merge start.
- Explanation
- This is the start message of the file merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0137I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0138E
Invalid minId and maxId : (minId,maxId)=({0},{1})
- Explanation
- The invalid data entry was registered.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0139E
Duplicate id interval is found : (minId, maxId)=({0},{1}) and ({2},{3})
- Explanation
- The invalid data entry was registered.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0140E
No valid DataEntries are registered in the database_config.xml.
- Explanation
- The valid data entry was not registered.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0141E
Original file [{0}] does not exist.
- Explanation
- The original file of the data entry did not exist.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0145E
Output directory already exists : [{0}]
- Explanation
- The output directory already exists.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0146I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0147I
File Merge done.
- Explanation
- This is the end message of the file merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0148I
Time : {0} sec.
- Explanation
- This is the processing time of file merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0149E
Exception occurred.
- Explanation
- The error occurred when marging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0150E
Error occurred.
- Explanation
- The error occurred when marging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0151E
Throwable occurred.
- Explanation
- The error occurred when marging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0152E
No intervals are specified.
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0153E
Illegal min id : {0}
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0154E
Min id must be smaller than max id : min={0},max={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0155E
Illegal min id and max id : min={0},max before the min={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0156E
Failed to parse the arguments.
- Explanation
- The error occurred when parsing the arguments.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0157I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0158I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0159I
Total merging process done.
- Explanation
- This is the end message of the file mid merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0160I
Time : {0} sec.
- Explanation
- This is the processing time of the file mid merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0161E
Exception occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0162E
Error occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0163E
Throwable occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0164E
Failed to access the index directory.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0165E
Error occurred during merge process.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0166I
File Merge done for multiple intervals.
- Explanation
- This is the end message of the file mid merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0170I
Merge target : {0},minId={1},maxId={2}
- Explanation
- This is the target message of the file mid merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0171E
Output directory already exists : [{0}]
- Explanation
- The output directory already exists.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0173I
File Merge done for single intervals.
- Explanation
- This is the end message of the file mid merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0175I
Group Merge start.
- Explanation
- This is the start message of the group merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0176I
Loading DatabaseConfiguration done.
- Explanation
- The database configuration was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0177E
Input directory does not exist : [{0}]
- Explanation
- The input directory did not exist.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0178E
Input directory is not a direcotry : [{0}]
- Explanation
- The input directory was not a directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0179E
Input directory cannot be read : [{0}]
- Explanation
- The input directory could not be read.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0180E
Output directory already exists : [{0}]
- Explanation
- The output directory already exists.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0181I
Loading CategoryTree done.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0182I
Group Merge done.
- Explanation
- This is the end message of the group merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0183I
Time : {0} sec.
- Explanation
- This is the processing time of the group merger.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0184E
Exception occurred.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0185E
Error occurred.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0186E
Throwable occurred.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0187E
Illegal entries in database_config.xml.
- Explanation
- The invalid data entry was registered in database_config.xml.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0188E
Failed to remove directory [{0}]
- Explanation
- The error occurred when removing the directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0189I
Inactive directory [{0}] has been removed.
- Explanation
- The directory was removed.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0192I
No directories were removed.
- Explanation
- There was no directory to remove.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0193E
Failed to remove inactive index files/directories.
- Explanation
- The error occurred when removing the directories.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0194E
The directory for the category tree does not exist. directory={0}
- Explanation
- The category tree directory did not exist.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0195E
The directory for the category tree is write-protected. directory={0}
- Explanation
- The category tree directory could not be write.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0197E
IO error: Failed to serialize the category tree file. file={0}
- Explanation
- The error occurred when serializing the category tree.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0198E
IO error: Failed to close the category tree file. file={0}
- Explanation
- The error occurred when closing the category tree.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0199I
The category tree generated. file={0}
- Explanation
- The category tree file was generated.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0200E
The category path is null. id={0} name={1}
- Explanation
- The category path is null.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0201E
Invalid category path found. path={0} id={1} name={2}
- Explanation
- The category path is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0202E
The category tree file does not exist. file={0}
- Explanation
- The category tree file did not exist.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0203E
The file for the category tree is not readable. file={0}
- Explanation
- The category tree file could be read.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0204I
Missing ids: {0}
- Explanation
- This is the list of the category id not assigned to the category.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0205I
Category tree loaded. file={0}
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0206E
The node tag must be inside the category_tree tag.
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0207E
The category id must be an integer value. id={0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0208E
Duplicated category id found. id={0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0209E
The category path must not be null. id={0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0210E
The category name must not be null. id={0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0211E
Invalid xml: too much found. id={0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0212E
The category features must not be null. id={0} path={1} name={2}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0213E
The category id must be positive (Root category must not be included in the category tree file). id={0} path={1} name={2}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0214E
Duplicated category path found. id={0} path={1} name={2}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0215E
Failed to add the category. id={0} path={1} name={2}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0216E
Invalid tag name : {0}
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0217E
Invalid xml: Too much found.
- Explanation
- The error occurred when reading the category tree file.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0218E
Input file cannot read : {0}
- Explanation
- The input file could not be read.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0219E
Duplicate entry : {0}
- Explanation
- The data entry was duplicated.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0220E
All available doc id ranges are exhausted. Please re-index all the existing entries first.
- Explanation
- The doc id ranges of the data entry were enhausted.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0221E
Failed to rename the original database_config.xml temporarily.
- Explanation
- The error occurred when renaming database_config.xml file temporary.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0222W
Failed to delete temporary file (the previous database_config.xml) {0}.
- Explanation
- The error occurred when deleting temporary database config file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0223E
Failed to append an entry.
- Explanation
- The error occurred when appending the data entry to database_config.xml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0226E
Failed to remove entries.
- Explanation
- The error occurred when removing the data entries from database_config.xml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0227W
All of DataEntry are removed.
- Explanation
- All of the data entries are removed from database_config.xml file.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0229E
Failed to initialize SAX parser.
- Explanation
- The error occurred when initializing the sax parser.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0230E
Arguments are invalid.
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0231E
Error occurred during the process.
- Explanation
- The error occurred when generating the database configuration.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0232I
database_config.xml file has been generated successfully.
- Explanation
- The end message of the database config file generator.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0233W
Duplicate option : {0}
- Explanation
- The option value was duplicated.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0239W
-importlist cannot be used with -absolute
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0240W
Unknown option : {0}
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0241E
Illegal options.
- Explanation
- The error occurred when checking the option parameter.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0242E
Mandatory option -dbdir is not found.
- Explanation
- The parameter is invalid.
- User Response
- Check the parameter.
Parent Topic : Mining/Search Engine messages
IUSS0244E
Failed to initialize SAX parser.
- Explanation
- The error occurred when initializing the sax parser.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0245E
Failed to parse the file[{0}]
- Explanation
- The error occurred when parsing the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0246W
No input files exist in the directory [{0}].
- Explanation
- The inpt files did not exist.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0247I
File[{0}] has been added to the index entry list.
- Explanation
- The input file was added to the data entry.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0251W
FeatureHandler of type {0} has been already registered.
- Explanation
- The feature handler has already been registered.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0253E
Failed to initialize SAX parser.
- Explanation
- The error occurred when initializing the sax parser.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0254E
I/O error occurred during the read from {0}
- Explanation
- The error occurred when reading the miml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0255E
Severe runtime error occurred during the read from {0}
- Explanation
- The error occurred when reading the miml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0256E
Severe error occurred during the read from {0}
- Explanation
- The error occurred when reading the miml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0257E
Failed to parse the docString[{0}]
- Explanation
- The error occurred when parsing the atml file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0259E
Failed to process start()
- Explanation
- The error occurred when serializing the document set.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0261E
end() cannot be called twice.
- Explanation
- The error occurred when serializing the document set.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0262E
end() is called before start() is called.
- Explanation
- The error occurred when serializing the document set.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0263E
Failed to process end()
- Explanation
- The error occurred when serializing the document set.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0264E
IO error: failed to read the category pointer index file: {0}
- Explanation
- The error occurred when reading the category pointer index file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0265E
IO error: failed to close the category pointer index file: {0}
- Explanation
- The error occurred when closing the category pointer index file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0266E
IO error: failed to open the category pointer file: {0}
- Explanation
- The error occurred when opening the category pointer file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0267E
IO error: failed to read the category pointer file: {0}
- Explanation
- The error occurred when reading the category pointer file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0268E
IO error: failed to close the category pointer file: {0}
- Explanation
- The error occurred when reading the category pointer file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0269E
IO error: failed to open the category index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0270E
Error: category ids put in this category pointer index writer must be monotonically increasing.
- Explanation
- The error occurred when writing the index.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0271E
IO error: failed to write to the cateogry index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0274E
IO error: failed to close the cateogry index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0275E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0276E
IO error: failed to create the output directory: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0278E
IO error: failed to read or write the index file: in_file={0} out_file={1}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0279E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0281E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0282E
IO error: failed to create the output directory: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0284E
IO error: failed to merge the indices: in_directory={0} out_directory={1}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0286E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0288E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when opening the virtual file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0289E
Invalid parameter: category id is negative or over the upper bound. category_id={0} upper_bound={1}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0291E
Index file is broken: requested_category_id={0} cat_pointer={1} category_id_at_cat_pointer={2}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0292E
IO error: failed to read the index file: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0293E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0294I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0295E
IO error: failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0296E
IO error: failed to write int_to_ints index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0297E
IO error: failed to close int_to_ints index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0298I
category_tree.xml is copied to {0}
- Explanation
- The category tree file was copied.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0299W
Configuration : Date categoy not set. tag={0} attribute={1}
- Explanation
- The date category was not setted.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0300E
Configuration error: Date category not found. tag={0} attribute={1} specified_path={2}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml and category_tree.xml files.
Parent Topic : Mining/Search Engine messages
IUSS0301E
Configuration error: Date format not set. tag={0} attribute={1}
- Explanation
- There is a setting error of the database configuration.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0302W
Unusual input data: multiple values found for the date category. path={0}
- Explanation
- The document has two or more dates.
- User Response
- Check the input data.
Parent Topic : Mining/Search Engine messages
IUSS0303I
The format of the date ,{0} in {1} is not supported.
- Explanation
- The date format was not supported.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0305E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0306E
IO error: failed to create the output directory: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0309E
IO error: failed to read the index file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0310E
IO error: failed to write the index file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0311E
IO error: failed to read or write the index file: in_file={0} out_file={1}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0312E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0314I
Loading the category tree.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0315I
The category tree is loaded.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0316E
IO error: failed to create the output directory: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0317I
Create IntToIntsFile done.
- Explanation
- The int to ints file was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0318I
Create DocPointerHashFile done.
- Explanation
- The doc pointer hash file was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0319E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0321E
IO error: failed to merge the indices: in_directory={0} out_directory={1}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0322E
Failed to close CatPointerIndexSequentialReader.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0323E
Failed to close VirtualFileReader.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0324E
Failed to close CatPointerIndexWriter.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0325E
Failed to close VirtualFileWriter.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0326E
Index file may be broken : {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0327E
Failed to merge the indices: in_directory={0} out_directory={1}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0332I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0333E
IO error: failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0334E
IO error: failed to write id-to-id-set index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0335E
IO error: failed to close id-to-id-set index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0336I
Loading the category tree.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0337I
The category tree is loaded.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0338I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0339E
IO error: failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0340E
An error occurs in postprocess: indexer={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0341E
An error occurs in closing indexer: indexer={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0342E
Failed to create the directory : {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0343E
Failed to initialize OutputStream
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0344E
Failed to write to OutputStream
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0345E
Failed to create the directory : {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0346E
Failed to copy the offset file.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0347E
File not found.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0348I
No data entry is registered in database configuration.
- Explanation
- There is no data entry in the database configuration.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0349E
Duplicate id interval is found : (minId,maxId)=({0},{1}) and ({2},{3})
- Explanation
- The error occurred when reading the index.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0350E
The union of ranges of doc id in the target DataEntries is not equal to (minId,maxId)=({0},{1})
- Explanation
- The error occurred when reading the index.
- User Response
- Check the data entry of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0352E
Error in registering a miml file.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0354E
Failed to initialize SAX parser.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0355E
Document is too large to retrieve : id={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0356E
Failed to read the document of id={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0357E
Failed to parse XML string.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0359E
Failed to close the cache for RandomAccessFile.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0362I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0363E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0364E
Failed to write offset information to {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0365E
Failed to close OutputStream.
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0366E
I/O error occurred during the read from {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0367I
Loading the category tree.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0368I
The category tree is loaded.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0369I
Loading the category tree.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0370I
The category tree is loaded.
- Explanation
- Tne category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0371E
IO error: failed to open the virtual file: file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0373E
Invalid parameter: searchDocs=null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0374E
Invalid parameter: category id is over the upper bound. category_id={0} upper_bound={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0375E
Invalid parameter: max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0376E
IO error: failed to get doc-pointer hashtable: file={0} category_id={1} offset={2}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0377E
IO error: failed to read the doc-pointer file: file={0} category_id={1} document_id={2}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0385E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0387E
IO error: failed to write int_to_ints index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0390E
Invalid parameter: max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0392E
Index validation error: wrong size of int_to_str file. size={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0393E
IO error: failed to open the int_to_str and str_to_int files: {0}, {1}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0394E
Invalid parameter: String id in the group is not in the valid range of [number_of_strings_per_group*{0}, number_of_strings_per_group*{1}+{2}]. group_id={3} local_string_id(in_group)={4} string_id=number_of_strings_per_group*{5}+{6}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0395E
IO error: Failed to convert string id to string. group_id={0} local_string_id(in_group)={1} string_id=number_of_strings_per_group*{2}+{3}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0396E
Failed to close the int_to_str file: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0397E
Failed to close the str_to_int file: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0398E
IO error: failed to open the int_to_str file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0399I
The int_to_str files were loaded: group_id={0}
- Explanation
- The int to str files were loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0400E
IO error: failed to add string to int-to-string index. pointer_file={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0402E
IO error: failed to generate int-to-string index. file={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0403E
IO error: failed to close file={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0404I
The keyword id index reader loaded: count={0}
- Explanation
- The keyword id index reader was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0405E
Invalid parameter: Keyword id is negative: keyword_id={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0406E
Invalid parameter: Keyword id over number_of_keywords_in_keyword_group * number_of_keyword_groups requested. keyword_id={0} Check the database configuration.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0407I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0408E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0409I
Standard features will be added to the root category.
- Explanation
- The keywords of the standard feature are indexed in the root category.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0410W
Unknown flag is specified [{0}] for {1}, this flag will be set false.
- Explanation
- There is a setting error of the database configuration. The keywords of the statndard feture are not indexed in the root category.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0411E
Invalid parameter: keyIds=null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0412E
Invalid parameter: keyIds includes negative value. index={0} value={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0414E
The number of the keyword in one group exceeded the limit. Please see the database_config.xml parameter (impl=standard). number_of_kewords_per_group={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0417E
Exception occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0418E
Error occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0421E
IOException occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0425E
Failed to close CatPointerIndexSequentialReader.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0427E
Failed to close VirtualFileReader.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0431E
Failed to close CatPointerIndexWriter.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0433E
Failed to close VirtualFileWriter.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0442W
Internal buffer for document list has been expanded to {0} Please check java heap size is sufficiently large.
- Explanation
- The internal buffer of the document was expanded.
- User Response
- Check the heap size of JVM.
Parent Topic : Mining/Search Engine messages
IUSS0443E
IOException occurred.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0444E
Failed to delete the file [{0}]
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0445E
Failed to delete the directory [{0}]
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0446E
Failed to close CatPointerIndexSequentialReader.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0448E
Failed to close CatPointerIndexWriter.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0450E
Failed to close VirtualFileReader.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0452E
failed to close VirtualFileWriter.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0454I
Loading the category tree.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0455I
The category tree is loaded.
- Explanation
- The category tree was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0456E
IO error: failed to open the virtual file: file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0459E
IO error: failed to close the virtual file: file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0462I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0463E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0464E
Null docToKeysTables.
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0465E
Invalid parameter: category id is negative or over the upper bound. category_id={0} upper_bound={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0466E
Invalid parameter: max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0473E
IO Error: failed to read the virtual files: rank_file={0} darray_file={1}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0474E
IO Error: failed to read the virtual file: rank_file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0481E
Inconsistent index: darray category pointer not found although rank category pointer was found. cat={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0486E
Invalid parameter: category id is negative or over the upper bound. category_id={0} upper_bound={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0487E
Invalid parameter: keyword id is over the maximum. keyword_id={0} group={1}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0488E
IO Error: failed to read the virtual files: search_file={0}-{1} rank_file={2} darray_file={3}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0492W
Incomplete param was found : name=[{0}], value=[{1}]
- Explanation
- The error occurred when reading the metadata file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0493E
Parse error: {0}
- Explanation
- The error occurred when reading the metadata file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0494E
Parse error: {0}
- Explanation
- The error occurred when reading the metadata file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0495E
Error in reading the metadata file [{0}]
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0496E
Null argument(s).
- Explanation
- The error occurred when writing the index.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0497E
IO error: failed to create the directory: directory={0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0498E
File [{0}] cannot be read.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0499E
Invalid keywordFeatureNum : {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0500E
Invalid standardFeatureNum : {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0501E
Error occurred in parsing the file [{0}]
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0502E
Failed to write metadata to file [{0}]
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0503E
Metadata file [{0}] cannot be read.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0504E
IO error: failed to create the directory: directory={0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0505E
Failed to write metadata to file [{0}]
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0506I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0507E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0508E
Failed to write metadata to file [{0}]
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0509E
Exception occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0511E
IOException occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0514E
Error occurred.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0515E
Failed to close CatPointerIndexSequentialReader.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0516E
Failed to close VirtualFileReader.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0518E
Failed to close CatPointerIndexWriter.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0519E
Failed to close VirtualFileWriter.
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0521E
Throwable occurred.
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0523E
Failed to open a VirtualFile.
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0525E
Index may be broken : categoryID={0}, nlistPointer={1}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0532I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0533E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0534W
Category for date [{0}] is not defined in the category tree and will be ignored by the indexer.
- Explanation
- The date category is not definde in the category tree.
- User Response
- Check the setting of database_config.xml and category_tree.xml files.
Parent Topic : Mining/Search Engine messages
IUSS0535W
Illegal value format : [{0}]
- Explanation
- The value specified to be a integer category is not integer.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0536I
{0} documents does not contain the standard date information.
- Explanation
- This is the information message about the number of documents do not contain the standard date category.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0537W
{0} documents contain annotations of the reserved date categories.
- Explanation
- This is the information message about the number of documents contain the reseved date categories.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0538E
Failed to load string-to-int hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0539E
Failed to serialize string-to-int hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0542E
Failed to load the int-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0543E
Failed to read the int-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0544E
Failed to load int-to-long hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0545E
Failed to serialize int-to-long hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0548E
Failed to load the int-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0549E
Failed to read the int-to-long hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0550E
Failed to load string-to-int hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0551E
Failed to close string-to-int hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0552E
UnsupportedEncodingException: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0556E
Failed to serialize string-to-int hashtable: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0559E
Failed to load the string-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0562E
Failed to read the string-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0563E
Failed to close the string-to-int hashtable: {0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0565W
The current document id exceeds to the maximum document id. maximum_id={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0567W
The maximum number of the positions reached the warning level. bi-gram={0} number_of_positions={1}
- Explanation
- The maximum number of the positions is too large.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0568W
Invalid configuration: The database configuration parameter the stop bi-grams must be even-length. param={0}
- Explanation
- The database configuration is invalid.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0569I
The default set of stop characters is not used.
- Explanation
- The default set of stop characters was not used.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0570E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0571E
IO error: failed to create the output directory: directory={0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0573E
IO error: failed to read or write the index file: in_file={0} out_file={1}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0574E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when merging the file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0576E
IO error: failed to create the output directory: directory={0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0577E
Failed to create the temp index directory: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0578E
IO error: failed to open the virtual file: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0581E
IO error: failed to merge the indices: in_directory={0} out_directory={1}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0582E
IO error: failed to close the virtual file: {0}
- Explanation
- The error occurred when merging the group.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0585E
IO error: failed to read the virtual file: file={0}
- Explanation
- The error occurred when reading the virtual file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0587E
IO error: failed to write to the virtual file: file={0}
- Explanation
- The error occurred when writing the virtual file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0589E
IO error :failed to delete string search temp merged index directory. directory={0}
- Explanation
- The error occurred when removing the directory.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0590W
The maximum number of the positions reached the warning level. number_of_positions={0} bi_gram={1}
- Explanation
- The maximum number of the positions is too large.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0591I
The maximum number of the positions: number_of_positions={0} bi_gram={1}
- Explanation
- This is the information message about the maximam number of the positions.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0592E
IO error: failed to open the virtual file: file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0594E
Invalid parameter: Search string must not be null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0596E
IO error: failed to search positions for bi-gram. file={0} bi-gram={1}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0597E
IO error: failed to close the virtual file: file={0}
- Explanation
- The error occurred when reading the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0599I
The index directory is created: {0}
- Explanation
- The index directory was created.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0600E
Failed to create the index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0601E
Failed to create the temp index directory: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0602I
The input of the document is null. ext_document_id={0} document_id={1}
- Explanation
- The input of the document is null.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0603E
IO error: failed to write to the index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0604E
IO error: failed to close the index file: {0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0605E
IO error: failed to merge temporary files. files={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0606E
IO error: failed to close the temporary index file. file={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0608E
IO error :failed to delete string search temp file index directory. directory={0}
- Explanation
- The error occurred when writing the index.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0609E
IO error: file not found: file={0}
- Explanation
- The error occurred when reading the virtual file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0610W
Failed to close the file: file={0}
- Explanation
- The error occurred when reading the virtual file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0611I
New file is loaded: {0}
- Explanation
- The new virtual file was loaded.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
IUSS0612W
Failed to close the file: {0}
- Explanation
- The error occurred when writing the virtual file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0613E
Invalid query: query=null
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0614E
Inconsistent sort mode: category!=integer, sort=intval
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0615E
Unexisting category id found. category_id={0}
- Explanation
- There is category not existing in the index.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0616W
Not int value (skipped): {0}
- Explanation
- The value not an integer is skipped when sorting.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0617E
Invalid parameter: The category parameter is null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0618E
Invalid parameters: Unsupported sort type is specified. sort_type={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0619E
Invalid parameters: The maxLinesToDisplay parameter must be more than 0. max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0620E
Null MiningQuery.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0621E
Invalid type of query.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0622E
Negative fromIndex : {0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0623E
Negative pageSize : {0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0624W
Many documents({0}) are going to be retrieved at one time.
- Explanation
- There are too many documents listed at once.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0627E
Invalid parameter: docIdArray is null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0628E
Invalid parameter: the database configuration is null.
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0629E
Invalid parameter: the index reader is null.
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0630E
Invalid parameter: the search engine is null.
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0631E
Mining function registration error: impl class must be implementation of interface class (specified by name attribute). interface_class={0} impl_class={1}. See database_config.xml.
- Explanation
- The error occurred when adding the mining function to the mining engine.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0632E
Mining function registration error: multiple entries for the interface. interface={0}
- Explanation
- The error occurred when adding the mining function to the mining engine.
- User Response
- Check the setting of database_config.xml file.
Parent Topic : Mining/Search Engine messages
IUSS0633E
date_year_start_month must be between 1 and 12 : [{0}]
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0634E
Invalid timeScale : {0}
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0635E
Invalid sort : {0}
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0636E
Invalid query: query=null
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0637E
Internal error: the parameter is not validated by the query. time_scale={0}
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0638E
Configuration error: time category not solved. time_scale={0} time_category_path={1}
- Explanation
- The parameter is invaliid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0639W
Big display size : {0}
- Explanation
- There are too many lines displayed at once.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0640E
Inconsistent sort mode: category!=integer, sort=intval
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0641W
Not int value (skipped): {0}
- Explanation
- The value which is not an integer is skipped when sorting.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0642E
Internal error: parameter not validated. sort={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0643E
Invalid parameters: Unsupported indicator is specified. indicator={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0644E
Invalid parameter: Unsupported time_scale is specified. time_scale={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0645E
Invalid parameters: The category parameter is null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0646E
Invalid parameters: Unsupported sort type is specified. sort_type={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0647E
Invalid parameters: The maxLinesToDisplay parameter must be more than 0. max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0648E
Invalid query: query=null
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0649E
Inconsistent vertical sort mode: category!=integer, sort=intval
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0651E
Unexisting category id found. category_id={0}
- Explanation
- There is category not existing in the index.
- User Response
- Check category_tree.xml file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0652W
Not int value (skipped): {0}
- Explanation
- The value not an integer is skipped when sorting.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0655E
Invalid parameters: The verticalCategory parameter is null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0656E
Invalid parameters: Unsupported sort type is specified. vertical_sort={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0657E
Invalid parameters: The verticalMaxLinesToDisplay parameter must be more than 0. vertical_max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0658E
Invalid parameters: The horizontalCategory parameter is null.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0659E
Invalid parameters: Unsupported sort type is specified. horizontal_sort={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0660E
Invalid parameters: The horizontalMaxLinesToDisplay parameter must be more than 0. horizontal_max_lines_to_display={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0661E
Failed to read adic file: {0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0664E
Failed to close the file input stream: {0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0665E
Error occurred: {0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0666E
Failed to get the categories. entry_id={0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0667W
Failed to parse entry@mtime. Modification time is set to 0. id={0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0668E
Failed to create the entry object. entry_id={0}
- Explanation
- The error occurred when reading the adic file.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0670E
Metadata file [{0}] cannot be read.
- Explanation
- The metadata file cannot be read.
- User Response
- Check the log file to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0673W
Null key is given. value=[{0}]
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0674W
Null value is given. key=[{0}]
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0675W
Null pair is given.
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0676E
Language is not supported. laugage={0}
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0677E
Failed to instanciate the string converter. language={0}
- Explanation
- The error occurred when instanciating the string converter.
- User Response
- Check the stack trace to find out the exact error.
Parent Topic : Mining/Search Engine messages
IUSS0678E
Invalid query: query=null
- Explanation
- The parameter is invalid.
- User Response
- Check the program which is calling.
Parent Topic : Mining/Search Engine messages
IUSS0679I
Read {0} entries from {1}
- Explanation
- The adic entries are read from the adic file.
- User Response
- No action required.
Parent Topic : Mining/Search Engine messages
(C) Copyright IBM Corporation 2008. All Rights Reserved.