Vivek,

Your version of IRIS for Health doesn't have the SMP UI to create a FHIR server. That was added in 2020.2.

https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI.Page.cls?KEY=HXIHRN_new#HXIHRN_new_serverui

I'd suggest you look at the 2019.1 docs for your version's instructions. That being said, IRIS' FHIR support is being actively developed so it is changing frequently. If you can upgrade to the latest version of IRIS for Health, you will get access to the most functionality (and quality of life improvements like the SMP option!)

Hello Muhammad,

Either documentation page explains the difference:

Embedded Language Development > ObjectScript > ObjectScript Reference > ObjectScript Functions > $INCREMENT

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

"$SEQUENCE and $INCREMENT can be used as alternatives, or can be used in combination with each other. $SEQUENCE is intended specifically for integer increment operations involving multiple simultaneous processes. $INCREMENT is a more general increment/decrement function.

$SEQUENCE increments global variables. $INCREMENT increments local variables, global variables, or process-private globals.

$SEQUENCE increments an integer by 1. $INCREMENT increments or decrements any numeric value by any specified numeric value.

$SEQUENCE can allocate a range of increments to a process. $INCREMENT allocates only a single increment.

SET $SEQUENCE can be used to change or undefine (kill) a global. $INCREMENT cannot be used on the left side of the SET command."

Hope that helps!

Note that copying the CACHESYS is not a general recommendation. You may choose to copy that database in specific situations if you are prepared to deal with potential consequences. In general, if you have problems with CACHESYS, using the installer would be the preferred option.

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

This documentation states that "InterSystems does not support moving, replacing, or deleting this database."

Virat,

What exactly do you mean by database tuning? Robert and Vitaly mention how to tune a table for SQL optimization, but what exactly were you hoping to achieve?

I wonder if you meant something like configuring the memory settings for an instance, for which I'd recommend starting by reviewing this page of documentation:

Architecture > Scalability >Scalability Guide > Vertically Scaling InterSystems IRIS

Kevin,

That's pretty worrisome. <DIRECTORY> is not a problem with the command - it means the instance can't locate that directory - this case, the CACHESYS directory. I would be surprised if there aren't errors elsewhere in the Caché logs.

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

"There is no such directory on the target system, no Caché database, the Caché database is not mounted, or the database is locked by another configuration. For further details, refer to $ZERROR."

This might be a configuration issue, permissions issue, etc. Definitely would recommend opening a WRC at this point, if you can't identify the problem.

Kevin,

It sounds like your namespace prompt has been replaced with a directory path in the terminal. The /mgr path is for %SYS (or CACHESYS, technically), but the fact that it is displaying that way seems a little unusual. It sounds like you're entering the implied namespace for some reason.

Nothing immediately comes to mind for what could be causing this. You said "at some point", do you recall when that was and if any changes have been made?

I wonder if login auditing would give useful information on this. Does logging in as a different user or looking at the user you are using's security settings show anything?

May be worth opening a WRC, as that might be easier than troubleshooting through this forum.

Yakov,

I'm not sure I understand your comment. It sounds like the setting is working for the most part - when you add all the IPs (desired and undesired) you can see all messages flow. If you remove certain IPs from the list, you can see those IPs being rejected. There is a disconnect between that last sentence, and the behavior you are explaining where allowing IPs doesn't work.

Can you elaborate on this discrepancy?

Muhammad,

That "missing" class is shipped with the Health side of ISC products (ex. IRIS for Health, HealthShare UCR, Health Connect). The fact that it can't be found is somewhat worrisome, but you can narrow this down into 2 main possibilities.

1. the class actually doesn't exist on your instance. I would recommend finding out how that could have happened.

2. the class does exist, but can't be found by the process, potentially because of a namespace / mapping issue. I would take a look at your mappings to see why this class is not available.

Besides those 2 points, a few questions to ask would be: When did this start happening? What changed? Was this class able to be found before?

Hello Augusto,

I think you're at the right part of the documentation. I'm not sure what specifically you are asking about. The actual "upgrade" on Unix involves running cinstall as if you were installing a fresh instance, and you can target the existing instance. The docs cover what else needs to be done before/after that.

I hope that helps? I would definitely recommend testing the procedure to familiarize yourself.

I agree with Pravin that <STORE> errors generally indicate a lack of process private memory which you can try to address by raising that limit. Documentation on <STORE> errors here: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_vstorage#RCOS_C132257

The other practical side of things though - can you use smaller subfolders rather than one that needs to host so many files? Do you really want your process to have to scan through that many files?

Hello Muhammad,

I would recommend reading this section of the documentation on Assets and Resources.

"Users and applications interact with InterSystems IRIS databases through namespaces. While there are no privileges associated with namespaces, access to a namespace is granted or denied based on the privileges associated with the underlying databases. More specifically, to access a namespace, you must hold the Read privilege on the default globals database associated with that namespace."