Please make sure the version you are on is safe to run compaction. See Pete Greskoff's 3 links in this developer community post:

https://community.intersystems.com/post/how-reduce-size-intersystems-cach%C3%A9-database-file-cachedat

In InterSystems IRIS as of 2019.1.0, you have the option to monitor and cancel database tasks such as compaction:

Using Character-based Security Management Routines

^DATABASE

option 15. Show background database tasks
"Displays a list of background tasks that are running or that have run since startup. You can also use this option to re-enter the monitor screen, where you can cancel a currently running task as well as purge the history of completed tasks. (Note that the tasks listed here are not the same as those listed as scheduled tasks in the Task Manager.)"

Hello Pandian,

This should be a larger discussion with your InterSystems sales rep. I would highly recommend reaching out to them.

Hello James,

This documentation should contain the answers you seek: Displaying Free Space Information.

You can use the System Management Portal's Databases page, or ^%FREECNT.

Hope that helps!

Hello Rick,

You might need to explain more about your criteria. The Business Service should be checking if filename and time modified match to determine if the file is the same. You may be able to just change the timestamp when you want to recheck.

Alternatively, you may be able to code some logic to have the files be moved to an archive path and then brought back over into the file path when you want to retry.

Settings for the File Inbound Adapter

There might be a way to modify the "already processed" status of a file, but I'm not sure if that's a great idea and you may want to discuss it with your InterSystems representative.

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 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.

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

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 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

For reference, the documentation on that command can be found at the bottom of this page:

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

Hello Rueben,

Please review your Caché user permissions. I suspect you may be running into an issue with the secure debug shell as documented here:

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

I hope that is helpful to you but if you are still troubleshooting I would recommend reaching out to the WRC to investigate.