Search

In the Windows Ressource Manager I can observe multiple parallel processes coming from cache.exe with read operations to journaling files. All except one of these processes have the

Following my previous post, some urged me to get to the point – ok, so I found my "star" journaling globals, the ones that take up the most space – but how do I avoid this? How do I

Hi, We are using CACHE 2017.2.1, I would like to retrieve data from Journal for killed global. Let say we have global name ^ EMP(123) with data and also have some child nodes and it

Hi,I am placing Cache instance in backup mode by using the command: csession <INST> -U%SYS "##Class(Backup.General).ExternalFreeze()"and I see in the console log a message

I'm creating a new namespace by the installation manifest XML and in the "database" tag configuration I don't see attribute to configure if I what jounal globals or not to this database.In

I have several 1GB journals from a LIVE server that I would like to inspect (eg: check which globals have been updated over the time). Is there a simple way to view those journals

My fantasy didn't go beyond periodically running %SYS.Journal.System:Progress() class query, while I'd prefer to use an event handler of some kind. Any ideas? Hi Alexey. I'm not

In System Administration | Configuration | System Configuration | Journal Settings there is a check box for Freeze on error. From reading the documentation, it sounds like the choice

I'm working on a task where I need to apply journal file records to another database. I can't use Journal.Restore class methods as I need to perform some data transformation, therefore

InterSystems has corrected a defect that causes invalid database and journal records to be introduced when using a specific $LIST syntax. The likelihood of encountering this defect

InterSystems FAQ rubric If the system does not stop for 24 hours, old journal files will be deleted at 0:30 according to the "Journal file deletion settings". A possible cause of

Sounds odd - but I encountered it - twice now. Cache was restarted. in that period the primary journal directory was full and it was writing to the secondary journal directory. So upon

InterSystems has corrected several critical defects that can result in data integrity issues. These defects were identified and corrected within a short time, so InterSystems has simplified

Virtual Summit 21 is only a week away, and our Experience Labs are filling up fast. Register today (for the summit, then for the labs).