Hello Sachin,

Can you provide the version of your product from the about page in the management portal or "w $zv" from the terminal? This behavior varies across versions so you can probably find more information in the relevant version of our documentation.

Also, please be clear about whether you are referring to namespaces or databases.

This documentation may be what you are referring to:

Where Ensemble Stores Temporary Data
 

Hello,

First of all I wonder what version of Caché you are using as ^MSU has been replaced by ^DATABASE for a long time.

That being said, I can't imagine there being any problems with interrupting using ctrl+c. In fact, as you didn't get an <INTERRUPT> error it seems likely that ^MSU/^DATABASE has accounted for a user trying to ctrl+c out and so just returns you to the previous menu.

Hello Vandrei,

Your question is a bit vague but hopefully this helps:

https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GOBJ_methods

##class(Package.Class).Method(Args)

Hello Jeffrey,

You're absolutely right that normal read only databases and mirrored databases operate differently. It is not possible to take out locks for a mirrored database on a backup failover member as locks would prevent the member from taking over as primary.

If you have a DR async and take out a lock on a mirrored database, then when you try to promote to failover member you'll see a message like this:

Unfortunately, that means I don't have a workaround for you unless you have a DR where you can dump the messages instead.

Thanks to @Pete Greskoff who I talked to about this behavior.

Hello Sergey,

Can you confirm if you are getting that kit from the Download Caché button in the sidebar here in the Developer Community? If so, then that alleviates my primary concern that it might actually be a threat.

Beyond that, the question would be one of setting up an anti-virus exclusion or disabling it briefly. This is something you might need to do for any software kit that is improperly flagged by your antivirus, which is not really a question of InterSystems technology but of whatever antivirus you are using.

Further down the line you may want to add some additional exclusions so Caché can operate properly per this documentation:

https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?…

After thinking about this a bit more you could probably use the open command which would be even simpler if you want to output to a file.

https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_iodevcomms

ex.

set file = "</path/to/log/file.txt>"

open file:"WNS" use file do $System.OBJ.CompileAll() close file

Try using the errlog parameter, something like:

w $SYSTEM.OBJ.CompileAll(,.err)

https://irisdocs.intersystems.com/healthconnect20191/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25SYSTEM.OBJ#METHOD_CompileAll

Then you can pull the errors from the err variable and put it into a file however you want, for example using %Library.File.

https://irisdocs.intersystems.com/healthconnect20191/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25Library.File

Hope that helps!

Hello Scott,

I'm not sure of the full background and context of your upgrade process so I would definitely recommend running this by your sales team, who might refer you to the WRC.

A normal Caché based HealthShare to Caché based HealthShare upgrade won't affect your user databases so why do you need to restore backups at all? What kind of databases are you concerned about? Through your upgrade process won't the databases be preserved and converted as necessary? You can then compile after the conversion.

Have you reviewed the IRIS adoption document available on the WRC distributions page, and have you received a copy of the Health Connect conversion guide from the WRC or your sales team?

Hello Reinhard,

Using Sample.Person I just did a quick test and switching the order of the where clauses did not effect either performance or the query plan.

Some people design or generate very complex SQL queries so I'm not certain if this holds true in all cases (though I agree I would expect it to - if not it may be worth reporting to InterSystems!). If you are interested in comparing performance and query plans this is pretty easy to do from the System Explorer > SQL page in the system management portal.

Hope that helps!

Hi Scott,

I'm not aware of an easy way to access the older HealthShare or Health Connect documentation. If you need those docs it might be a bit of extra effort but you can install a kit with the version you want to review and access the docs that way.

If you're specifically looking for an online solution then I'm afraid I don't have an answer for you.

What version of Caché are you attempting to install? Windows 10 began being supported with Caché 2016.1.

Given that there was an incomplete install I would recommend uninstalling Caché, restarting, and then trying a fresh install.

For posterity:
On a minimal security install unauthenticated access is the only authentication method enabled for most services. We document the risk of modifying roles for UnknownUser (used for unauthenticated access) and cover some other security considerations here:

https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_tighten

If you end up in a situation where your security settings no longer allow you to access Caché, you can use emergency startup mode as documented to log into Caché and fix your settings:
https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_secmgmt#GCAS_secmgmt_emerg

Much appreciation to my colleague Jon who walked through these steps with Joshua.

Hello Zdeněk,

The answer to your question probably depends on the specifics of what you are trying to do and what your constraints are. Is there any consideration to combining the two installer manifests into one? In your previous post you mention an unattended install, so I assume this is related to the .cmd file you are attempting to create. I wasn't aware that an unattended install could run multiple manifests; is that possible or are you running the second manifest manually?

You could use conditional <If> tags in the installation manifest if you wanted to perform some verification. You could use <Invoke> to run whatever method you want to confirm that your first manifest was carried out. For example, you could write and import a simple method that leverages $SYSTEM.OBJ.GetClassList to check that your classes exist. If your method isn't able to run that would also be evidence that the first manifest did not succeed.

https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25SYSTEM.OBJ#METHOD_GetClassList

%SYS.Namespace.Exists would confirm whether a namespace exists.

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=ITECHREF_namespace

Alternatively, you could use the <Log> functionality of the installer manifest and then read the log.

Hope that gives you some ideas! I did see that Dan Kutac replied to one of your other posts - it seems like he is working with you on your manifest so I think he would be able to help you with this.

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCI_manifest

Hello Stephen,

That documentation you linked to put you on the right track! If you click on the %SYS.Maint.Bitmap link it will take you to the class reference which contains some examples of how to run the bitmap cleanup:

https://docs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25SYS.Maint.Bitmap

eg.

d ##class(%SYS.Maint.Bitmap).Namespace("Samples",1,1,"2014-01-17 09:00:00")

d ##class(%SYS.Maint.Bitmap).OneClass("BitMap.Test",1,1)

This utility was only added to the product around version 2015, I believe. It should run automatically as part of an Ensemble message purge. If you need to perform this maintenance on an older version, rebuilding the index can be done though this is a more involved process, especially on a live system.

If needed, you can reach out to the WRC who can provide a utility that performs a similar function to %SYS.Maint.Bitmap for older versions.

Hope that helps!

If you see an error message in brackets, this documentation would be a good place to look to find out what it means:

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RERR_system

<FILEFULL> can indicate issues with the actual disk filling up, but you can also run into it if you have configured and reached a maximum database size.

You can check that setting in the management portal at System Administration > Configuration > System Configuration > Local Databases, or you can use the ^DATABASE utility as documented here:

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_chui-mgmt#GCAS_chui-mgmt_database