I am trying to migrate our SQL Connections from HealthShare Health Connect 2018.1.3 to IRIS HealthShare Health Connect 2022.2 using the Data Export/Import Wizard through the Management Portal. I am able to export the data fine, but I am running into issues trying to Import it into 2022.2 using the Data Import Wizard. When I run through the steps it is not importing everything from the txt file I created from 2018.1.3. I would rather not have to rekey all the connections if possible.
I've seen a few password change posts, but I wasn't 100% sure it was the same process, so I am asking here. We periodically have to change the passwords for a few Cache user accounts across several servers. Is there a process/script to change these passwords without having to go into the web portal on each server? Thanks so much, and I apologize if this was covered in some of the other articles that I've run across. Just looking for the best method.
Mirroring provides an admin capability to Stop Mirroring on this member, which causes a non-primary member to temporarily disconnect from the primary, stop dejournaling, etc. While most system administrators may never need or use this function, some employ it for certain kinds of maintenance or other special cases.
Is there any API equivalent (within Config.Databases class, or elsewhere) that has the same functionality as the 'Recreate a database' option in the ^DATABASE routine?
This option was added to ^DATABASE (according to internal Devlog CFL1263):
I am wondering about upgrading our Healthshare mirrored environment to the latest release. Has anyone upgraded recently to what version and what kind of effort was put into it. I am thinking it will take 2 analysts full time for 3 months. Am I out of the ball park on this estimate? We have bout 600 operations, Processes and services. What are some of the benefits we get from upgrading and what are some of the problems you ran into during the upgrade? Any information you have to share would be greatly appreciated.
Thanks
I have one in my testing environment. According to https://community.intersystems.com/post/licensing-ubuntu-and-suse-20171-and-later, I should move to native Ubuntu build with 2017.2. So I downloaded Cache for UNIX (Ubuntu Server LTS for x86-64) 2017.2.1 and tried to update my existing 2015.1.4 installation. What I got was:
Hi All,Cache is not starting ,I checked the cconsole log it is showing the below error.
The following parameters are missing from section [Journal]: '2,12' at line 143,but i checked in last cpf file,
In cpf file consist of that particular line
[Journal]
AlternateDirectory=C:\InterSystems\CACHE16\mgr\journal\
BackupsBeforePurge=2
CurrentDirectory=C:\InterSystems\CACHE16\mgr\journal\
DaysBeforePurge=2
FileSizeLimit=1024
FreezeOnError=0
JournalFilePrefix=
JournalcspSession=0
I have a question about the Private Global Blocks when viewing a process's details. This number is growing while my process runs - is this due to variables, process-private-globals, or both?
Does anyone know how to return the sys.process table with the corresponding configname item for each process? Also, is there a key for the Job Type field?
Is there a group in or outside of this community for discussion of DTM issues? I am working on a conversion to Caché for a client but in the meantime, he is still live with his DTM system and a system management issue has arisen. The convo:
Client: Do you know how to increase the page limit in MUMPS DTM? One version of my database I use for one customer is telling me I have reached my page limit. I have increased the page limit in the database you are reviewing; so I figure there is a setting I am missing.
I followed the Documentation instructions to install Caché on my Linux box and it seems to be running fine except when I try to modify the configuration. I keep getting errors that a previous cache.cpf file (e.g., cache.cpf_8503) cannot be opened. Is my Linux "user who owns instance" account deficient in Linux permissions?
We will have a Arbiter, Two Failover members (A,B), and a Async (DR) member (C). I have the two failover members in sync and are configured for Arbiter Control.
My question is about the Async member, when I initially set it up I pointed it to the mirror on the primary node A.
I'm trying to write an installer manifest that can create a namespace, resources (%DB_namespace) and a role (with the resource, above), based on the namespace. So you could pass in "ABC", or "XYZ", and it would create the %DB_ABC resource and the ABC role with %DB_ABC:RW permissions; or it will create the %DB_XYZ resource and the XYZ role with %DB_XYZ:RW permissions, accordingly.
I'm using HealthShare on Cache 2017.2. I'm trying to find out how I can get a list of all the custom classes, routines and globals in %SYS namespace (if it's even possible).
We're about to perform an upgrade, and in the docs it mentions needing to check for anything custom in %SYS to avoid important stuff being overwritten. Some of our solutions have been developed by an external consultancy and we want to make sure that none of their code or data will be affected by the upgrade.
I was hoping to be able to print the Authentication Enabled properties of a system from the command line using the Get or GetProperties class method. Currently, however, I am only able to get a return 1 or Invalid Oref error.
I followed the instructions to setup the Port Authority Report in our new IRIS instances, but noticed if I tell it to run every hour I am getting the following error message...
We are Using Ensemble 2014, Windows Server 2012 64 bit operating System.
We need to sense whether Htpps is alive or not.
In Cache we tried %HttpsRequest Library we set https property and port=443. But it doesn't work.
Anyone help us plz.
I asked previously about the DR server in the cloud but actually, I'm curious about the backup server to use as analytics server more than for recovery in DR case.
There is a recommended practice to use an async mirror as a server for BI (InterSystems Analytics, DeepSee)
The question is if I have PRIMARY in the cloud (AWS, Google, Azure, etc) "how far" should async mirror member be placed? Same cloud, same private cloud or it doesn't matter at all for analytics purposes?