ID | Message text | Meaning and action |
|---|---|---|
012001024w | "No file, the database environment definition file." | Check whether the usage database environment definition file exists. If this message is output even though the usage database environment definition file exists, back up the database that produced the error and all of the files in the "log" directory under the variable file storage directory, and then contact an SE. |
101002200e | "Cannot get memory." | Memory is insufficient. |
102001001e | "Cannot read a internal file, '%s'. ('%s', error:%.2u)" | Internal error. Back up files in the log directory under the variable file storage directory, and then contact an SE. |
102001002e | "Cannot write a internal file, '%s'. ('%s', error:%.2u)" | Internal error. Back up files in the log directory under the variable file storage directory, and then contact an SE. |
102001101e | "Cannot get memory." | Memory is insufficient. |
102002001e | "Cannot read a log file, '%s'. ('%s')" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102002002e | "Cannot read a log file, '%s'. ('%s', errno:%.2u)" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102002101e | "Cannot get memory." | Memory is insufficient. |
102003101e | "Cannot get memory." | Memory is insufficient. |
102004001e | "Cannot read a log file, '%s'. ('%s')" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102004002e | "Cannot read a log file, '%s'. ('%s', errno:%.2u)" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102005001e | "Cannot read a log file, '%s'. ('%s')" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102005002e | "Cannot read a log file, '%s'. ('%s', errno:%.2u)" | An operation (the value in parentheses is a keyword indicating the operation) related to the log file failed. Check the log file path and the log-recording format defined in the Usage DB Environment Definition File. |
102005021e | "Invalid path, '%s'." | Check the log file defined in the Usage DB Environment Definition File. |
102005022e | "Cannot read a directory, '%s'. ('%s', errno:%.2u)" | Check the log file defined in the Usage DB Environment Definition File. |
102005023w | "Invalid log form detected in a log file '%s', continuously." | A log read from the log file does not match the log format defined in the Usage DB Environment Definition File. Check the definition of the log format in the Usage DB Environment Definition File. |
102005101e | "Cannot get memory." | Memory is insufficient. |
103001003e | "[server=%s][log=%s]Database register engine stopped, because an error occurred." | Error message. Because an error occurred during analysis of analysis server log symbol: sss and analysis target log symbol: nnn of the Usage DB Environment Definition File, the Usage DB Registration Engine stopped. Search for related messages before this message and take the required action. |
103001004w | "[server=%s][log=%s]Database recovery started." | Warning message. Because an error occurred during database registration of analysis server log symbol: sss and analysis target log symbol: nnn of the Usage DB Environment Definition File, recovery of the Usage DB Registration Engine was started. |
103001005w | "[server=%s][log=%s]Database recovery succeed." | Warning message. Recovery of the database of analysis server log symbol: sss and analysis target log symbol: nnn of the Usage DB Environment Definition File was completed normally. |
103001006e | "[server=%s][log=%s]Database recovery error." | Recovery of the database was not completed. Recovery of the database of analysis server log symbol: sss and analysis target log symbol: nnn of Usage DB Environment Definition File failed. Back up files in the log directory under the variable file storage directory and in the database that failed, then contact an SE |
103001007e | "[server=%s][log=%s]Database was abnormal." | Error message. If this message is output frequently, back up files in the log directory under the variable file storage directory and in the database that failed, then contact an SE. |
103001100e | "No database environment definition file." | Check whether the Usage DB Environment Definition File exists. If this message is output even when this file exists, back up files in the log directory under the variable file storage directory and in the database that failed, then contact an SE. |
103001303e | "Invalid parameter. "" | In correct parameter. If this message is output frequently, back up files in the log directory under the variable file storage directory and in the database that failed, then contact an SE. |
103003100e | "No log file for analysis." | Check whether the path specified in the Usage DB Environment Definition File is correct. |
103019100e | "The database serial number exceeded was over limit." | Since the database count that can be managed by the agent was reached, analysis can no longer be conducted using this database name. Specify another database name. |
1030nn200e | "Cannot get memory." | Memory is insufficient. |
105001101e | "Database register engine stopped, because an error occurred." | Because an error preventing the continuation of operation occurred, the Usage DB Registration Engine stopped. Search for related messages before this message and take the required action. If no related messages are found, back up files in the log directory under the variable file storage directory, then contact an SE. |
402001008e | "Cannot get memory." | Memory is insufficient. |
