In the errpt output, Roger, it looks like something made your disks unavailable.

LABEL:          LVM_SA_QUORCLOSE
IDENTIFIER:     CAD234BE

Date/Time:       Mon Jun 20 16:50:40 -03 2022
Sequence Number: 21297
Machine Id:      00FB42D74C00
Node Id:         SISMED1
Class:           H
Type:            UNKN
WPAR:            Global
Resource Name:   LVDD            
Resource Class:  NONE
Resource Type:   NONE
Location:        

Description
QUORUM LOST, VOLUME GROUP CLOSING

Probable Causes
PHYSICAL VOLUME UNAVAILABLE

Detail Data
MAJOR/MINOR DEVICE NUMBER
8000 0028 0000 0000
QUORUM COUNT
           2
ACTIVE COUNT
       65535
SENSE DATA
0000 0000 0000 0A9E 00F9 8DEE 0000 4C00 0000 014B 506D D812 0000 0000 0000 0000
---------------------------------------------------------------------------
LABEL:          LVM_GS_CHILDGONE
IDENTIFIER:     4B219AEA

Date/Time:       Mon Jun 20 16:50:40 -03 2022
Sequence Number: 21296
Machine Id:      00FB42D74C00
Node Id:         SISMED1
Class:           U
Type:            PERM
WPAR:            Global
Resource Name:   LIBLVM          
Resource Class:  NONE
Resource Type:   NONE
Location:        

Description
Concurrent LVM daemon forced Volume Group offline

Probable Causes
Unrecoverable event detected by Concurrent LVM daemon

Failure Causes
Lost communication with remote nodes
Lost quorum

    Recommended Actions
    Ensure Cluster daemons are running
    CHECK ERROR LOG FOR ADDITIONAL RELATED ENTRIES
    Attempt to bring the Concurrent Volume Group back online
    IF PROBLEM PERSISTS, CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
Volume Group ID
00F9 8DEE 0000 4C00 0000 014B 506D D812
MAJOR/MINOR DEVICE NUMBER
0028 0000
SENSE DATA
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

Make sure your hardware is healthy.

Nicki, I would start with your account manager and have a chat about how best to migrate.  Since Ensemble and IRIS for Health are different products, the specific versions involved matter a great deal.  A sales engineer on your account team probably has seen migrations such as the one you propose.

As for differences between IRIS and Ensemble, check the Migration Guide which you can download from the WRC.  There's a lot there, but it includes the result of a lot of testing and migration experience.

And of course, if you are finding something that doesn't work as it should, reach out to the WRC.

Earlier ODBC driver versions should be compatible with Caché 2018.1, but we recommend updating clients to the latest driver for your Caché version.  There aren't any 2021.x ODBC drivers for Caché on the WRC download page.  If you have one and you want to be sure you have a good driver, reach out to the WRC so we can understand your specific situation.

Erik

Hi Hoi, nice to see you in the community. You piqued my curiosity about FASP and I found this white paper about it: https://www.ibm.com/downloads/cas/7D3KBL9Z.

I don't see any support for this in our class reference.  If you are looking for support for this in InterSystems IRIS, I would start with your InterSystems account team to explore what you need and what alternatives might serve.

It should work.  Windows privileges need to be correct, and in recent Windows versions, it is not as simple as running as an Administrator.  If you have specified a user to run the IRIS instance, rather than the Local System account, run the irisinstall setserviceusername command (details are in the documentation) to set privileges correctly.

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

The InterSystems WRC can also help if you are truly stuck.

The InterSystems IRIS data platform is the engine in InterSystems' current product set.  IRIS for Health adds capabilities related to healthcare applications and DeepSee (part of the older Caché database engine) allows you to embed business intelligence capability into your applications.

For new development, or if you are just getting started, I would look to InterSystem IRIS and the products built on it, unless you know you have a specific need for Caché.

James,

The system-provided audit events are documented here:

https://docs.intersystems.com/iris20201/csp/docbook/Doc.View.cls?KEY=GCAS_audit#GCAS_audit_sys_events

Check to see if these events will give you what you need:

  • %System/%DirectMode/DirectMode audits commands run at the IRIS terminal.
  • The events under %System/%SQL audit SQL commands.
  • %System/%System/OSCommand audits $ZF calls.

There are many others that track logins and system changes.

Erik

Yossi, I'm not familiar with CommVault and the VMTools (although the VMs I use here do have them installed).  I have seen a variety of troubles cured by making sure the VMTools are up-to-date.  VMWare or CommVault support might be best for that. 

As for Caché, make sure that EnableVSSBackup is set to 1 (true) in your CPF and that SYS.VSSWriter.1 is running (check the process list in the Portal).  The VSS writer for Caché can be started only by an administrator on Windows.

I don't have much more advice, if this doesn't get you working, I would contact WRC directly.

Others, including me, were noting this message in the log you posted

02/08/21-09:17:54:464 (7016) 3 [Utility.Event] Error: Invalid Community Edition license, may have exceeded core limit. - Shutting down the system : $zu(56,2)= 0

which is definitely unhappy about the core count.  Rich has good advice if you are able to start the instance but are unable to run only some jobs.   If you have a full license and you are still unable to sort this out, reach out to the WRC and an advisor can assist.

Please let us know if you have progress, several of us are interested in your success.

Erik

Priya, there is a limit of eight CPU cores for the Community Edition of InterSystems IRIS products.  If you are using a Docker image, add

--cpuset-cpus=0-7
to your 'docker run' command.  On a native server, or VM, you need to limit the cores available using the methods for that server (or use one with fewer cores).

https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=AC...

Let us know if this resolves your trouble, and all best in migrating to IRIS.

Erik