Hey y'all.
I already have a Support ticket open that I've had to reopen 3 times now, as this issue keeps circling back... We are a self-hosted environment running analytics between our Test (data warehouse) and Analytics (cubes) servers (this will change in FY21, but it is currently not feasible to throw these on the same server). About every two weeks, my incremental load fails on Step 2. PROCESS_CUBES with the following error:
Contributions cube build unsuccessful, the cube does not exist [SQLSTATE 42000] (Error 50001)
Checking the server console, I find my cubes have stopped, but I'm able to restart with no issue. I've restarted the following services (all set to Automatic Delayed Start) on our Analytics server.
Sisense.CLRConnectorsContainerSisense.DiscoverySisense.ECMLogsPersistenceServiceSisense.HouseKeeperSisense.JVMConnectorsContainerSisense.OrchestratorSisense.OxygenSisense.PulseSisense.Repository
All our servers are set to restart weekly - on Monday's at 4am. So far, I'm not seeing a direct correlation between the server restarts and the incremental loads failing. We were failing all through the holidays, so at this point, my log viewer doesn't go back far enough to compare time/dates of the last failure.
Anyone have ANY ideas as to what could be causing this error to continue to rear it's ugly head?
Please and thank you!
Emily -
We are also self-hosted, have Tessitura servers split into API, DB, and Analytics, and are running 15.1.3. We have had a ticket in for a while, because Analytics does not come up automatically after a server restart. With Tessitura help, I am down to 2 steps after a reboot that makes everything hunky-dory:
I am happy with that, but the ticket is still open.
Clarke
SLSO is also self-hosted and I have been doing step 1 every ten day for the past several months. Is there a Tessitura resolution to this yet?
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
Hi Ashley,
Unfortunately, this is a Sisense defect in our current release version. We expect this to be a non-issue in v16. The only "resolution" in v15 to date, when encountered, has been mitigation, best handled through automation when possible. For example, a batch file similar to:
NET STOP ElastiCubeManagementService NET START ElastiCubeManagementService
Then a Windows Scheduled Task on the Analytics Cube Application Server to run the batch file with elevated permissions. This might be nightly, or weekly, as the best results vary by site. If you continue to have frustrations around this issue, please open a support ticket and we'll see whether a closer look by our support teams can improve the matter.
Thanks!Chris
Thank you, Chris. We have this automated now via the Windows Task Scheduler.
Ashley