Home > OLAP Dialog Boxes and Wizards > Build: Scheduling
![]() Previous |
![]() Next |
Use this panel to identify the time at which you want to execute the build. Because loading and summarizing data can be a long and resource-intensive process, you may want to schedule it for off-peak hours.
Run maintenance task immediately in this session: Starts the maintenance task immediately after you complete the wizard.
Submit the maintenance task to the Oracle Job Queue: Enters the build in the Oracle job queue where it can run in the background, independent of your client computer. In this mode, you can allocate additional processes to speed up the job.
Run immediately: The job will run as soon as resources are allocated to it by the job queue.
Run at a future time: The job will run at the scheduled time.
Date and Time: Set the time for starting the build. Select the area of the time stamp that you want to change (such as the day or hour), and then use the arrow keys to increase or decrease the start time.
Maximum number of parallel processes: Enter the number of processes that you want Oracle Database to allocate to this job. Some parts of a job can be parallelized and thus can use multiple processes:
Multiple cubes: Each cube can be loaded and summarized in a separate process. For example, an analytic workspace with five cubes can use up to five processes for loading and summarization.
Partitioned cubes: Each partition can be summarized in a separate process, if each partition has its own composite. For example, an analytic workspace with two small cubes and one large cube with five partitions can use up to three processes for the data load and up to seven processes for summarization.
The actual number of processes that you should request depends on the resources available to you and the time constraints for the job. Oracle Database allocates the specified number of processes regardless of whether all of them can be used simultaneously at any point in the job. For example, if you request eight processes for a job that can use a maximum of three, then Oracle Database may still allocate eight processes to the job.