go to post Vic Sun · Mar 31, 2020 Happy to help! For what it's worth, best practice to initiate a failover would be to simply cleanly shut down the primary.
go to post Vic Sun · Mar 31, 2020 Hi Laura, There are some tables covering schemas that might be of use to you as documented here: Exporting a Production "Export the underlying Caché global that contains the schema and then import this on the target system. To export a global, select System Explorer > Globals, select the desired globals and then select Export. The X12 schemas are stored in the EnsEDI.Description, EnsEDI.Schema, EnsEDI.X12.Description, and EnsEDI.X12.Schema globals. The XML schemas are stored in the EnsEDI.XML.Schema global. See “Exporting Globals” in the Using Caché Globals guide for details on exporting globals."
go to post Vic Sun · Mar 31, 2020 Hello Dan, I am struggling to understand the scenario that you are testing/planning for. Do you have an arbiter? I would read through the mirroring docs which discuss the various options available to you and the various automatic responses that mirroring can take (including some diagrams). https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GHA_mirror https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GHA_mirror#GHA_mirror_set_autofail_outages If you want to simulate network isolation, I think you'd need to actually network isolate. If you force the backup to become primary, Caché will try to force down the original primary to prevent split brain.
go to post Vic Sun · Mar 30, 2020 If you can't identify a permissions issue I would recommend opening a WRC case to investigate as it will probably take some looking around at your system to resolve, and that isn't easily done via a forum. Worth considering is if this works in other environments and if so what the difference in permissions might be, and if you can try the freeze or journal switch directly in Caché terminal (taking the OS terminal out of the equation).
go to post Vic Sun · Mar 30, 2020 Hello Augusto, If you're on Unix error 13 is permission denied so I would definitely suspect that this is a permissions issue. Do you have any other journaling issues (maybe other messages in cconsole.log)? Can you try running your commands straight in the Caché terminal and see if they work?
go to post Vic Sun · Mar 2, 2020 Hi Joe, If you haven't seen it already, our Printers documentation could be useful for you. You could try printing some things from terminal just to test and then see if you can implement it into your production. Eduard's question is relevant as well to see what you can actually do.
go to post Vic Sun · Feb 18, 2020 Hi Hansel, For a mirroring issue usually the full context of all mirror members is usually important to understand a problem, whereas a singular message may not paint the whole picture. This error in particular (you included an excerpt, but I have seen it before) indicates that this instance is unable to take over the VIP, so you may want to check if the VIP is available or if it may be assigned to a different machine as the rest of the error message would indicate.
go to post Vic Sun · Feb 17, 2020 Are you using an Archive Path or Work Path? When you look at the Visual Trace does it give you any more ideas for where issues could be cropping up? Can you elaborate on this: "It appears like the same file gets picked up by a later session but we have no way of knowing if it is the same doc or not." Do you mean that the file is sometimes picked up but with a reported filesize of 0kb? What business process is attempting to move the file to a working directory? What were the errors that you had previously? If Ensemble is having trouble picking up the file it may be a fileshare availability issue. This is likely not going to be easy to troubleshoot through this forum, I'd recommend reaching out to the WRC to investigate.
go to post Vic Sun · Feb 5, 2020 Wish I could be of more help, but I think there is no longer a freely available trial version of Caché, and if you are looking for a download you would need to go through your company. You may want to reach out to your ISC sales team to see if something can be arranged.
go to post Vic Sun · Feb 4, 2020 Hi Christopher, I'm not sure where you're seeing Download Caché Evaluation, all links show IRIS instead for me. IRIS is the product of the future for InterSystems so it's what is being presented for evaluation. Is there a particular reason that you need Caché? If you are a supported customer you can still get access to Caché through the WRC but if you are looking to try an InterSystems product then IRIS has Caché's capabilities and then some. https://www.intersystems.com/try-intersystems-iris-for-free/
go to post Vic Sun · Feb 4, 2020 The $job documentation put me on the path to look deeper into %SYS.ProcessQuery. The class documentation recommends using SQL to avoid the overhead of opening the object. It also recommends looking for a property that doesn't require sending a mailbox message to the process. %SYS.ProcessQuery For example: SELECT CommandsExecuted FROM %SYS.ProcessQuery where pid=5812 If the pid exists the query will return a row, otherwise it will return nothing. Hope that helps.
go to post Vic Sun · Feb 4, 2020 I'd have to think a bit on what the "best" way to do this would be, but the following seems to work: %SYSTEM.Process.JobType() In my admittedly quick testing, it will return 0 for a process that doesn't exist.
go to post Vic Sun · Jan 9, 2020 Your user may have permissions to write a file to the output directory, but that doesn't mean you will have access to all the utilities that pButtons will try to run, including Windows Perfmon. There should definitely be more than 1 log file is a pButtons is running normally. I wonder if the Buttons report was able to collect its cstats as that also requires elevated permissions. You can check that section within the html report to see if it exists. I would definitely recommend opening an Administrator Windows command prompt and then navigating to \cacheinstalldir\bin, where you can use "ccontrol console <instancename>" to access the terminal. From there try to run a test pButtons.
go to post Vic Sun · Jan 9, 2020 What's in the log file? Prior to collection in the html there should be multiple log files containing various pieces of information, so tracking down what is/isn't collecting could be useful. I suspect OS permissions, can you open a terminal making sure you have administrator privileges so that you can run the proper performance monitoring utilities? You can just run a test 5 minute run to check if things are running properly.
go to post Vic Sun · Dec 5, 2019 Hello Paul, I'm not sure about DTLs specifically, but I'm seeing the latest community edition as 2019.4 which has the new SMP design. I tried my 2019.3 community edition which also has the new SMP. https://hub.docker.com/_/intersystems-iris-data-platform What version are you looking at?
go to post Vic Sun · Dec 2, 2019 You can find Studio-only installations in the Components section of the WRC distributions page, which includes versions compatible with IRIS 2019.2.
go to post Vic Sun · Nov 26, 2019 Hello Duncan, Please see the following documentation. Defining and Calling Methods. Some examples: do ##class(Package.Class).Method(Args) set myval= ##class(Package.Class).Method(Args) write ##class(Package.Class).Method(Args) You may find some of the courses on learning.intersystems.com (linked in the top bar of the developer community as well) useful such as the Caché Objects Introduction.
go to post Vic Sun · Nov 26, 2019 Hi Tamara, The following developer community article may be of use to you: https://community.intersystems.com/post/how-make-phone-calls-using-cach%C3%A9-objectscript-and-twilio For text/SMS alerts though you can see the following sample from the developer community: https://community.intersystems.com/post/simple-text-messaging-alert-using-sms-gateway There is also an online course Setting Up Alerts to try the text code out.
go to post Vic Sun · Nov 22, 2019 16384 was the default a long time ago back in Caché 2011, and upgrades would not automatically change this value. It is a good idea to review your memory settings periodically to make sure they still make sense for your application and usage. This value having never been tweaked from its default may be a sign that other memory values were never thoughtfully adjusted, so the following article may be of use to you (or your team): https://community.intersystems.com/post/intersystems-data-platforms-and-performance-part-4-looking-memory
