Cause | Insufficient shared memory remaining. |
Action | To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter. |
Cause | Insufficient shared pool memory remaining. |
Action | To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter. |
Cause | The system memory is full. |
Action | Increase the system memory space, or close other running programs. |
Cause | Cannot open the log file. |
Action | Check the log file path and permissions. |
Cause | Insufficient buffer space. |
Action | Increase the size of the buffer. |
Cause | This feature is not yet implemented. |
Action | Check whether a feature which is not yet implemented was used. |
Cause | An environment variable (database home and database sid) has not been defined. |
Action | Define the variable. |
Cause | The target directory is the same as the log directory currently being used. |
Action | Specify a directory that is different from the current log directory. |
Cause | Unable to rename the log file. Refer to the server error log for more detail. |
Action | Examine the log file permissions and check the server error log. For more information, contact the technical support team. |
Cause | The target directory has insufficient space. |
Action | Examine the target directory space and initial parameters such as LOG_TOTAL_SIZE_LIMIT. Ensure the directory has sufficient space by deleting or moving unnecessary files. For more information, contact the technical support team. |
Cause | An error occurred while remapping a new log file. Check the error log at server. |
Action | Examine the error log in the server. For more information, contact the technical support team. |
Cause | There is already a log file with identical name in the target directory. |
Action | Modify the filename or remove the log file in the target directory. |
Cause | Unable to create a directory for the new log file due to invalid path or authority. |
Action | Check whether a path and its authority of the new log file are valid. Also examine the error log of the server. For more information, contact the technical support team. |
Cause | Type of the JSON value is different from expected type. |
Action | Examine the error log in the server. For more information, contact the technical support team. |
Cause | Expected JSON key not found. |
Action | Check the inventory of Horde. |
Cause | Too many objects referred (%1$d). |
Action | Contact the technical support team. |
Cause | Insufficient shared pool memory remaining. |
Action | To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter. |