Cube Daemon
The Cube daemon has the same setup, control, and monitoring options as other daemons. However, the feeding queue of the Cube daemon is created by the History daemon. If the History daemon is not running, the Cube daemon cannot receive any updates. You can only generate or rebuild cubes after you have stopped the Cube daemon. (The History daemon can keep running. The Cube daemon catches up on the missed updates when it is restarted).
The Cube daemon is always successful. This means that in the Daemon Monitor, it always displays as successful, even if the update failed for some cubes. That is because the daemon feeds all the cubes in the system with the status Operational. During the update, some cubes are successfully updated and others may not be. The errors that occur in the update process (for example, missing exchange rates or missing COA Cross Ref translations) are logged in the Cube Build Log and can be checked using Cube Build Log Browse. When an error occurs for a cube, that cube is automatically assigned the status Needs Rebuild and the daemon stops further updates to that cube. You have to fix the root cause of the failure and use Report Cube Generate to rebuild the cube so it becomes operational again.
Further reasons that a cube update might fail include:
• The posting has a posting date that falls outside the cube calendar.
• The posting is in a layer that is not selected for the cube.
• The posting has the daybook type Year Closing. Year closing postings are not included in the cube.
No warning is given in any of these cases.