go to post Alexander Pettitt · Oct 25, 2021 Looks like you can set charset to UTF-8 using the docs here. You might need the full version to do that.
go to post Alexander Pettitt · Oct 20, 2021 What charset do you want to use? That may be the issue. I use putty too.
go to post Alexander Pettitt · Oct 5, 2021 Intersystems has worked hard but encryption is not free. Do you have something like batch processing? You would notice an impact more there then on a 1 second query. I would worry more about key security and recovery. Encryption also has a serious impact on the ability of modern SAN storage to dedup and compress which could result in higher than expected storage costs.
go to post Alexander Pettitt · Sep 28, 2021 You might look at this tool combination for the last journal file. Convert Journal Files Using ^JCONVERT and ^%JREAD
go to post Alexander Pettitt · Sep 7, 2021 If you have not already, migrate to solid state disks. It is weird that the page Vic recommends does not mention that.
go to post Alexander Pettitt · Sep 2, 2021 I don't know a way that you can do that. You can run ^%GSIZE against a specific CACHE.DAT
go to post Alexander Pettitt · Sep 1, 2021 Here is a link to the Cache document - https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCDI_journal#GCDI_journal_view
go to post Alexander Pettitt · Sep 1, 2021 Many things could be happening. How do you cleanup journal files? Purge after so many backups? Are your backup working? You could look in a journal file and see what global data is causing the expansion. If you have the system management portal you can look at journal data there too. You might need to go to the application vendor to tell what data a global holds.
go to post Alexander Pettitt · Aug 9, 2021 Roger is correct. I wonder if the error is controllable though through the cpf. The rules on global names - linked to the temporary doc location - http://dreamymclean.intersystems.skytapdns.com:52773/csp/docbook/Doc.View.cls?KEY=GGBL_structure
go to post Alexander Pettitt · Jun 9, 2021 You could try to compact and truncate. Dmitry's idea will also work and be faster.
go to post Alexander Pettitt · Jun 2, 2021 I think the WRC would be the only ones who could tell you what could be moved into CACHETEMP unless you found someone else who they had told already. If you just don't want to store so many journals you could just backup multiple times a day and do a journal purge. Congratulations on using Ensemble to the point you have this problem.
go to post Alexander Pettitt · May 26, 2021 I have 21 instances of Cache running on a single server. There are a lot of pluses: simpler cpf, database snapshots, easier downtime negotiations I would manually specify memory since you likely have very few simultaneous users. Here is a link Sizing System Memory for Caché
go to post Alexander Pettitt · May 11, 2021 If your session is text you might make a look at a tool like screen that is available for Unix based systems.
go to post Alexander Pettitt · Apr 9, 2021 Death to extents :) I work in Unix where LVM and mount points would make this easy but it looks like Windows has mount points. Windows mount point
go to post Alexander Pettitt · Apr 9, 2021 You can compact and truncate the database while IRIS is up. Compacting a Database Truncating is the next section