Ephraim Malane · Dec 5, 2022

%Identifying what is consuming space in the HealthShare Installation (Linux machine reports AWS install Disk Space Utilization reached 80%)

Hi Community,


Can someone assist me to check why HealthShare Iris install disk space increased, I want to know what contributed to Disk space utilization increase as it it now running at 81%. I am running Redhat Linux machine which is hosted on AWS.


Product version: IRIS 2020.2
$ZV: HealthShare 2020.2 [HealthShare Modules: Active Analytics:20.0.8620 + Core:20.0.8620 + Patient Index:20.0.8620] - IRIS for UNIX (Red Hat Enterprise Linux for x86-64) 2020.1 (Build 217_1_20418U) Tue Nov 17 2020 15:48:44 EST
0 113
Discussion (8)2
Log in or sign up to continue

Thanks Tani,

Database and journal filesystems seem to be okay..see below

I suggest you use InterSystems Portal, go to System Operation section, then Databases. Look at which databases lie within the mountpoint which is showing 81% use:

Usually the biggest culprit is IRISTemp database. This data base is essentially used for temporary storage of data during the live of a process and can grow quite big if a process misbehaves. The space can usually be reclaimed by setting configuration parameter and restarting IRIS.

Hi guys,

I have found that the issue is on IRIS.DAT file database on  /hs-exchange/sys/healthshare/mgr/HSAUDIT.

This database only store database logs right? And how do I reduce the space in this db?

This database stores audit information (actions users took during the instance lifetime).

Depending on your specific situation you might have to keep it for a while due to a contract or compliance reasons.

When DB grows unexpectedly these are the general steps:

1. Check that DB is actually full and not over-expanded. To do that go to SMP-> System Operation -> Databases -> HSAudit. Check % Free Space - that is a space allocated to IRIS.DTA but not used. You can reclaim it by truncating the database.

2. Run ^%GSIZE to get global report and see which globals are the largest. In your particular case, however, you can just go into Globals (from the Databases page) and check IRIS.AuditD which presumably consumes all the space (in details you can calculate space consumption).

3. Based on (2) results do something about the largest globals. In your case, if it's indeed IRIS.AuditD check which system events are logged most often and either fix that (if it's a PROTECT error for example), disable auditing for that particular event. Note that usually old audit entries are purged by a task, maybe something is wrong with that.

Thank you so much Eduard,

I just want to check something, I noticed that on the list of databases, we have HSAUDIT AND IRISAUDIT database. I want to confirm if they are all saving audit data