Code not always updated in Mirror?
This past weekend we ran into something odd. When we failed over our mirror from 2022.1.3 to 2025.1.3 the one of the Business Rules that was on what became the Primary (2025.1.3), had a rule within it that was removed back in January. When the Failover occurred, we had to scramble to backup, disable, and remove the Rule that shouldn't have been there.
Both the Data and Code live within the same IRIS.dat that is the main MIRROR database for that Namespace.
If this happened to one Class file, could it happen to others we do not know about? Seeing that I ran CompileAllNamespace, it is kind of hard to track down based on compiled date.
Has anyone had this issue before? Have you been able to track down the culprit?
Comments
AI bot answer is not relevant to the question.
You say that code/data is in the same DB that is mirrored. 2025 and 2022 are using different version of journaling, but 2025 is capable of de-journaling journals from previous version (but not the vice versa).
1. When you upgraded the failover to 2025 (the one which is the new primary) did you had any issues with journal files? (might be that some files were dropped in the upgrade and not processed).
2. is that "missing rule" mapped to another DB that is not in mirror?
- never thought about reviewing messages.log, or the journalling log to see if there is an error, but I will double check.
- The Business Rule in question has always been a part of the database that is part of the mirror.
Maybe DataCheck could be useful?
https://docs.intersystems.com/iris20261/csp/docbook/DocBook.UI.Page.cls…
I got the sense that Data Check was only looking at data not code.