Skip to content
Puede usar nuestro buscador para encontrar información sobre los productos y soluciones de InterSystems, las oportunidades de desarrollo profesional, los casos de uso, novedades y mucho más.

Advisory: The UpdatePlan for all cubes and cube groups is set to be Manual instead of BuildSynch

March 23, 2020 – Advisory: The UpdatePlan for all cubes and cube groups is set to be Manual instead of BuildSynch

InterSystems has corrected a defect affecting the UpdatePlan setting and how often all cubes are built and synchronized.

This problem exists for:

  • HealthShare Health Insight customers upgrading from 15.03 to 2018.1 or above.

When a Health Insight customer is upgrading from Health Insight version 15.03 to a later version of Health Insight, the Cube Registry UpdatePlan should be set to “Manual”, which allows Health Insight to manage cube updates during and after the upgrade process.

However, if the HSAA.CubeRegistry has all of the cubes using a "BuildSynch" UpdatePlan, when the Registry is activated (either by a user or as one of the Upgrade Steps), a task will be created that schedules all cubes to be built once per week and synchronized once per day, which does not allow Health Insight to manage updates.

Setting the Cube Registry UpdatePlan to “Manual” resolves this issue.

Starting with version Health Insight 2019.1.2, the UpdatePlan for all cube groups and cubes in Health Insight is correctly set to Manual.

The correction for this defect is identified as HSHI-3350 and will be included in all future product releases. It is also available via Ad hoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC).

If you have any questions regarding this advisory, please contact the WRC.

RELATED TOPICS

Latest Alerts & Advisories

Aug 15 2024
InterSystems has corrected a defect that can cause database corruption or errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.
Jul 24 2024
There are four alerts in the HS2024-03 Alert Communication. A summary of each alert is shown below. Details for each alert are contained in the linked document.
Jun 24 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
May 30 2024
Beginning with the release of InterSystems IRIS® data platform 2022.3, InterSystems corrected the license enforcement mechanism to include REST and SOAP requests. Due to this change, environments with non-core-based licenses that use REST or SOAP may experience greater license utilization after upgrading. To determine if this advisory applies to your InterSystems license, follow the instructions in the FAQ linked below.
May 01 2024
InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results. See below for the specifics on impacted queries.
Apr 08 2024
InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an error.
Mar 19 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
Feb 27 2024
There is 1 alert in the HealthShare HS2024-limited Alert communication. An alert summary for the issue is shown is in the table below. Details for the alert are contained in the attached document: HS2024 Limited Communication.
Feb 01 2024
There are 2 alerts in the HealthShare HS2024-02 Alert communication. An alert summary for each issue is shown is in the table below. Details for each alert are contained in the attached document: HS2024-02-Communication.