Hi Richard,

at the version of Cache you are using there is no terminal via web browser. Not even sure if the community webterminal is working with this old version of Cache.

Only recent IRIS versions have introduced a terminal service via web technologies to be used with VSCode.

Hi Scott,

my first thought here was use ^GBLOCKCOPY.

GBLOCKCOPY can copy all globals from one database into a new database or namespace.
So in your case create a new namespace with the correct mappings and new default databases. then use ^GBLOCKCOPY to copy all globals into this namespace. The copy to namespace follows the mapping definition for the namespace and should split Global(data) and Routine(also in globals) into the respective default databases.
This new databases can also created mirrored and then would be populated on all nodes respectively.

A caveat though i would test this first as i am a bit unsure if it really gets all globals located in a database(including system), although i am pretty sure it does.

Hi Jingesh,

have a look at this older dev community article: Synchronize data with DSTIME | InterSystems Developer Community |

Hope it helps.

very quick and dirty test, probably only works on small streams, also needs to actually read the whole stream for compare.
 

# test compare - streams are same
set stream1=##class(%Stream.TmpCharacter).%New()
set stream2=##class(%Stream.TmpCharacter).%New()
do stream1.WriteLine("ABC123")
do stream2.WriteLine("ABC123")
do stream1.Rewind()
do stream2.Rewind()
w (stream1.Read() = stream2.Read())

1

# test compare - stream are different
set stream1=##class(%Stream.TmpCharacter).%New()
set stream2=##class(%Stream.TmpCharacter).%New()
do stream1.WriteLine("ABC123")
do stream2.WriteLine("DEF456")
do stream1.Rewind()
do stream2.Rewind()
w (stream1.Read() = stream2.Read())

0

Hi Fred,

on the AWS instance what does the command "iris list" return?
Also you can have a look at the messages.log file located at the <installDir>/mgr/messages.log

This should give you an idea of what the issue is.

pure objectscript way no functions needed, we just use the IRIS type conversion behavior:
 

set number1="123123"set number3="123123123 Not a pure number"if ((+number1=number1) && (+number2=number2) && (number1>=number2)) {
    set div=number1-number2
} else {
    w !,"Conditions not met"
}

1. create a wrapper class with classmethods mapping to your routine(s)

or better

2. convert your routines to classes

then use $CLASSMETHOD | Caché ObjectScript Reference | Caché & Ensemble 2018.1.4 – 2018.1.9
to call these dynamically.

This also addresses the issue that xecute is highly risky from a security point of view, it can easily be targeted with injection attacks.

The beauty of the IRIS technology stack is that code and data is withing the same instance.

To separate code from data ISC uses the idea of code and data databases, which can be configured on a namespace level, this combined with global, package and routine mappings results in very versatile environment that should satisfy every need. If you want to actually separate compute from data storage, this is also possiple using the ECP protocol with dedicated app servers. 

Hi,

I guess you have written a custom extension using superclass %SYS.Monitor.SAM.Abstract?
If so the method you are looking for is SetSensorLabels see doc here

Where you install IRIS depends on your use case. E.g. if you are "only" developing, no real user load the disc layout you would use is markedly different to a production system with 1000s concurrent connections.

so just a couple of thoughts on disk layout:

Install IRIS and every of its components in a dedicated folder e.g. /iris . Reasoning behind this is a single folder is easier to be excluded from any e.g. AntiMalware scanner that could wreak havoc on a database backend. 

In that subfolder separate data, file store, journals and executables.

Reasoning: For a high-performance system each of above has a different i/o workload and a different performance profile. e.g. while journals are nearly 100% sequential writes, database executable are a mix of read and writes.  Database files are also a mix of read and writes but usually much bigger block sizes. Also different filesystems have different performance profiles.

So taking above in account also following best practises for mounts and i/o workload separation:

root (/)
/{instancename}/iris -> instance installation folder
/{instancename}/journalPrimary
/{instancename}/journalSecondary
/{instancename}/database
/{instancename}/filestore
/{instancename}/webfiles

Based on above you can mount volumes depending on workload sitting on different physical disks/lvms also for high performance environment you might want to separate the disc on multiple scsi controllers. So each controller only served a specific i/o profile.

Also to note IRIS2021 changed the default disc i/o behaviour from use OS file cache to direct unbuffered i/o. Which again means separate IRIS workloads from any OS workload.

Hi,

not sure about Veeam installing stuff etc.

But i know some customers only backup the backup mirror, never the primary mirror as even with snapshot taking only a couple of seconds, QoS detection get triggered due to a slight performance degradation during the backup. If the backup is running against the Primary mirror, this then results in a forced failover being triggered.

There is a setting in vscode for the objectscript extension, that allows you to modify the compile flags used.

My current settings, which also triggers compilation of embedded SQL vs default behaviour to not compile embedded SQL.

"objectscript.compileFlags": "cbk/compileembedded=1"

Hi Phillip,

if IRIS is frozen/hung only way to see is via messages.log

The freeze and thaw is recorded there.

Hi So looking at those errors:

First we have a process with an active transaction, that process crashed. So now the system is trying to rollback those transactions.
Then the process conducting the rollback (pid: 10800) ran out of process memory (STORE error) 

Although i think the clean demon in the end was able to rollback the open transaction.

Hi Jim,

you should probably let us know what you are trying to achieve.

I had the same error. I manually created that folder, which did not help. Then after i put SELinux into permissive mode (internal test container) , the error went away so i guess its SELinux tags that are wrong also.

Option 2 is not totally correct.
The parameter [Startup] MaxIRISTempSizeAtStart=5000 will clear the IRISTemp database and shrink it to the size specified it will not prevent IRISTemp from growing further.
So you set the parameter and restart IRIS and the runaway IRISTemp database will be reset to 5000MB (per example)
To ensure IRISTemp is not taking over all your available space either relocate the DB to a dedicated volume or set the maximum DB size in SMP for the database. But this all has its own risk.

Just as a FYI this is not working if using server side editing with no local source code.