proCube Server is a memory resident OLAP database engine, and it is crucial that it is saved and shutdown properly. proCube Server can consume 100 percent of single or multiple processors, which may cause the server to appear “locked” when it is actually calculating your data and working as designed.
Safely Shutting Down proCube Server
proCube can contain a gigabyte or more of data loaded into memory, and simply stopping the proCube service may not give the process enough time to save the database and shutdown properly. A clean shutdown requires proCube to write the entire memory footprint to the hard drive.
If the proCube server is shutdown or restarted without first saving the database, the database may become corrupted and unusable. A restore from backup process would then become necessary.
Here's how to shut down or restart the proCube server:
Open proCube from the Start Menu as shown in Figure. 1.
Figure 1. Opening proCube
Selecting proCube opens proCube Management Studio. On the left side, the Servers View displays as shown in Figure 2.
Figure 2. proCube Management Studio - Servers View
From the Server View, highlight an instance of the server and right-click it to open the pop up menu.
From the pop up, select Manage Server to open the Server Manager tab showing the current users.
Figure 4. Server Manager
If users are logged on, each user needs to be disconnected from the server either voluntarily (inform them that the server is going down at a certain time) or forcefully (highlight a user and click Disconnect User Session). If Block Users is selected, all users are blocked from logging on to the server, but an administrator is also blocked from performing any server activity.
Once all users have been disconnected from the server, return to the Server View and highlight a connected database, and right-click to open the pop up menu.
Figure 5. Database Commands
From the pop up menu, select Save to save the database, and then click Disconnect to disconnect the database. Repeat this procedure for each database and/or proCube Server Instance loaded on the server.
The server may appear locked while the save operation runs. Some databases can take several minutes to finish a save operation.
From this same pop up menu, click Backup to create a backup copy of the database to the corresponding \Backup Directory, which creates an independent file that can be copied or moved.
Once each of the *.OLP files (databases) have been saved, backed up and closed, return to the Server Manager (see Figure 4.), highlight a server, and click Stop.
Due to the time it takes to shutdown the services, check with Task Manager to make sure all of the proCube Server instances are stopped. The following Figure shows an instance that is still running
Figure 6. Windows Task Manager - Server Instance
Once all of the instances have been stopped, the computer can be shutdown and restarted. For the purpose of freeing memory, stop and start the proCube Service. When the server restarts it will automatically start the proCube Service(s), but it won‟t load the database. A database needs to be opened manually.
Check the Task Manager if there is a question as to what is happening. Repeat this for each instance that has a database loaded. If you intend to reboot the server several times in a row, consider setting the proCube Service Startup type to Manual (via Services). If your proCube Server is set to Manual Startup, you may need to start Services once the system is up and running.
To specify a length of time that the service control manager must wait for services to complete the shut-down request, go to http://support.microsoft.com/kb/146092 to access the article "How to Increase Shutdown Time for Services to Close Properly".