Cube refresh - restricting user access while rebuilding
Robert Latorre
Customer
Hi, running on 10.6, on premises.
When we run our nightly refresh, it takes about an hour to fully update all of the cubes, most of that time is in the refresh of 3 shipped sales related cubes.
If a user accessed Board in that window, the data is not accurate since the cube builds are partial and in progress.
OPTION 1
I'm considering stopping the Web API service at the start of the refresh procedure and restarting it at the end to prevent users from accessing Board while the refresh is running. That will solve the problem, but:
In Cognos, I would build cubes in a second environment, allowing me to validate the data before publishing to production by copying the cube objects to the production environment folders. Ideally, I'd like to do the same in Board so the refresh period doesn't affect user access at all. I checked with Board support and they don't have a folder(s) that contain the cube data that I could just refresh from the build environment to the prod environment.
Does anyone have suggestions or alternatives to preventing user access during cube refreshes or limit the down time related to the cube refreshes?
------------------------------
Robert Latorre
CIO
Horizon Group
United States
------------------------------
When we run our nightly refresh, it takes about an hour to fully update all of the cubes, most of that time is in the refresh of 3 shipped sales related cubes.
If a user accessed Board in that window, the data is not accurate since the cube builds are partial and in progress.
OPTION 1
I'm considering stopping the Web API service at the start of the refresh procedure and restarting it at the end to prevent users from accessing Board while the refresh is running. That will solve the problem, but:
- I'd like to redirect to a web page that posts a message saying that "Board is currently being refreshed with new data". Currently, when the WEB API service is offline, the URL fails with an error that URL isn't available, which implies that the system is crashed.
- When the API service is bounced, users that had the page up at the time that the service is stopped, lose connection and can only reconnect by fully exiting the browser and relaunching it, this is a training issue, but I would like to add that to the redirect page to remind people to fully close out the browser before accessing the system again.
In Cognos, I would build cubes in a second environment, allowing me to validate the data before publishing to production by copying the cube objects to the production environment folders. Ideally, I'd like to do the same in Board so the refresh period doesn't affect user access at all. I checked with Board support and they don't have a folder(s) that contain the cube data that I could just refresh from the build environment to the prod environment.
Does anyone have suggestions or alternatives to preventing user access during cube refreshes or limit the down time related to the cube refreshes?
------------------------------
Robert Latorre
CIO
Horizon Group
United States
------------------------------
0
Answers
-
Hi Robert, I solved this problem in this way :
in the main screen of the capsule I setup a label with visibility option linked to a cube,
during the update I setup the cube value to 1, so the label is visible and the users are informed
that update is in progress, and at the end of the update set the value to 0 to reset the message.
------------------------------
Gianni La Mantia
IT Manager
VAY SPA
Italy
------------------------------
-------------------------------------------0 -
Thank you Gianni!
I was hoping to broadcast a message sooner without needing to go into each capsule. But that is a good solution. I may add it to the mask in each capsule instead so it is available on every screen.
------------------------------
Robert Latorre
CIO
Horizon Group
United States
------------------------------
-------------------------------------------0
