Journaling

Syndicate content 6 

Hi,

We have Mirroring established between NODE 1 & Node 2 . We have set the "cachesys" database enabled for Journalling. But we dont see the User Accounts , Roles, Resources created on Node 1 ( favoured Primary) reflected on Node 2 . Is creating them manually again is the only option for this ? . Is there any way to sync them or would adding %SYS to MIRROR a possible solution. Would it be great if anyone has faced this as we have an issue that during failovers Team is locked out . 

Best Regards,

Arun Madhan

Last answer 19 October 2018 Last comment 22 October 2018
+ 1   1 6
195

views

+ 1

rating

I am still working on a generic task where I need to apply journal file records to another database. Initially I didn't want to use Journal.Restore class methods as I need to perform some data transformation, and it seemed that the clearest way to achieve it was to read journal file record by record using %SYS.Journal.Record API. 

This approach worked (with some help from @Dmitry Maslennikov and @Eduard Lebedyuk), while it turned that the processing speed of %SYS.Journal.Record:List query was very slow, about 1MB of journal data per second on a mid-range server

Last answer 16 June 2018 Last comment 16 June 2018
0   0 2
120

views

0

rating

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 I'm reading journal file record by record using %SYS.Journal.Record API.  

It seems that there are only few journal records that I need to process, namely:

Type TypeName
6    SET
7    KILL
8    KILLdes
9    ZKILL
10   RemoteSET
11   RemoteKILL
12   RemoteZKILL
14   BitSET

No problem, while I'm just curious: which COS command could provide KILLdes record? I've met it only once in the context like this:

KILLdes ^SYS("Task","TaskD",1006,"EmailOnError",1)

I can't imagine that Caché is smart enough to recognize the command series

Last answer 7 June 2018 Last comment 7 June 2018
0   0 3
157

views

0

rating

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 to freeze on error is one of system availability vs system integrity.

Curious to know whether Ensemble users choose to freeze on error or not.

If you have a best practice recommendation based upon your experience or knowledge, that would be helpful information too.

Last answer 5 June 2018 Last comment 4 June 2018
0   0 4
103

views

0

rating

Currently, we are running 2014.1 on two different servers (OpenVMS, RHEL). The plan is to transition from OpenVMS to RHEL, but our Write Daemon is in a Troubled state on both servers.

On the OpenVMS server, we have a WIJ file that's 26G and can grow to 40G (size of database cache). Since it hasn't grown to 40G, we don't believe the size of the WIJ file to be the issue.

What else should we be looking at regarding the performance of the Write Daemon?

Last answer 20 March 2018
0   0 2
0

comments

222

views

0

rating

I am pleased to announce that Release Candidates of Caché and Ensemble 2017.2 are now available.

Many customers have already downloaded the Field Test over the past few months, and we appreciate your feedback.

This release contains significant improvements, including:

  • Parallel dejournaling to improve throughput of mirroring and journal restore.
  • New iFind and iKnow features like co-occurrence search, performance improvements, and more.
  • SQL enhancements in Query Auditing, optional ANSI SQL operator precedence, and Frozen Plan Evolution, along with our normal cast of query optimization improvements.
  • Ensemble updates include DICOM enhancements, XML performance, and XSLT2 activities in BPL.

You can get details of these improvements from the Release Notes, which can be downloaded from the Developer Download page link below

Last comment 10 October 2017
+ 6   0 2
710

views

+ 6

rating

I'm purging a lot of management data from an Ensemble production, which is creating 100s of GBs of journals. Has anybody succeeded in disabling journaling on an Ensemble purge? The user interface doesn't have an option for this, but I'm thinking you might be able to identify the process and externally disable journaling on it.

Last answer 2 August 2017 Last comment 4 August 2017
0   0 4
300

views

0

rating

Hi Everyone,

Link to webinar recording: https://learning.intersystems.com/course/view.php?id=623

Thank you for your interest in this webinar!

Please submit questions about the content of the webinar as comments below this article.

The webinar covers two topics: monitoring message activity and volume and monitoring disk space. I summarize and motivate the topics in the following two sections. The information in this webinar and post applies to the Ensemble, Health Connect, and HealthShare products. For simplicity, I am only going to refer to Ensemble in this post.

1) Monitoring Message Activity and Volume:

Last comment 16 May 2017
+ 3   0 1
332

views

+ 3

rating

Prmoetheus is a really good to combine measures, and export them in graphical dashboards

https://prometheus.io/

http://grafana.org/

 

I would like to write some a caché exporter for Prometheus, that will allow to expose some metrics of the database, or even some metrics of my own

Did anyone already tried ?

Thank for the answer

Last answer 15 May 2017 Last comment 11 October 2016
+ 1   0 3
218

views

+ 1

rating

One of my journal spaces has status "IOER" in MSM MUMPS.

I think this is happend during system freeze.

 

 

I never seeing a journal file status like that.  I did not find anything about it in the intersystems documentation.

I can simply delete the damaged file, but I'd like to know how to prevent this from happening.

Anyone have some idea about it?

My MSM-UNIX Version is 4.4.0.

Thanks

Last answer 21 March 2017 Last comment 21 March 2017
0   0 1
127

views

0

rating

We are finally planning to migrate some ancient Caché applications that are run on Caché 5.0.21 to a new server with Caché 2016.2.0 or so.

I wonder if we could use Shadowing between those to keep the data on the new server up to date?

We would copy the Caché backup from the old environment to the new and do a RESTORE there and then start shadowing.

I know than 5.0.21 is no more officially supported by ISC.

Last answer 26 October 2016 Last comment 28 October 2016
0   0 1
344

views

0

rating

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 minimize the journal's size?

[DISCLAIMER: Some might still be disappointed after this post as well frown but wait till the next one... blush]

Last comment 29 August 2016
+ 5   0 3
574

views

+ 5

rating