Worldwide Response Center (WRC) - is InterSystems support service.We provide expert technical assistance to our customers 24 hours a day, every day. We maintain support advisors in 15 countries around the world and have specialists fluent in English, Spanish, Portuguese, Italian, Welsh, Arabic, Hindi, Chinese, Thai, Swedish, Korean, Japanese, Finnish, Russian, French, German, Hebrew, and Hungarian. Every one of our clients immediately gets help from a highly qualified support specialist who really cares about client success.
Date range queries going too slow for you? SQL Performance got you down? I have one weird trick that might just help you out! (SQL Developers hate this!)*
If you have a class that records timestamps when the data is added, then that data will be in sequence with your IDKEY values - that is, TimeStamp1 < TimeStamp2 if and only if ID1 < ID2 for all IDs and TimeStamp values in table - then you can use this knowledge to increase performance for queries against TimeStamp ranges. Consider the following table:
(This article was reviewed in February 2021. It is still relevant to Caché-based installations and similarly applies to IRIS-based installations.)
This article discusses the Windows write caching setting which can leave systems vulnerable to data loss or corruption in the event of power loss or operating system crash. The setting is on by default in some Windows configurations.
While Studio and Atelier are useful development interfaces, there are occasionally situations where a quick edit needs to be made to code and only terminal access is available. A useful set of tools to do this are the zload, zprint, zinsert, zremove, and zsave commands. These are abbreviated to zl, zp, zi, zr, and zs respectively. While each of these commands has its own page in documentation, this article will synthesize that information with examples to provide instruction for their combined use.
It has been noticed that some customers running JAVA programs (for example, FOP) on AIX would see the server eventually running low then out of memory. Customer would notice the system pages heavily and user experience becomes bad. And the server would crash when out of memory.
When the problem happens, we can see in ipcs a lot of shared memory segment marked for deletion (Capital D at the beginning of MODE section). This means they will not disappear until the last process attached to the segment detaches it.
I'm very proud of the Worldwide Response Center - an excellent group of men and women - and I am interested to hear from you about your experience using the WRC. There are always better ways for us to serve you.
I'm also very excited about the Developer Community which we're bringing to you to give you an opportunity to connect with groups and individuals in the InterSystems community. Let us know what you think and how we can improve it in order to serve you better.
June 16, 2021 - Advisory: Discontinued Technologies and Features
Note: A previous version of this advisory listed Caché Server Pages as a deprecated technology. Caché Server Pages is not deprecated and is fully supported.
InterSystems has corrected an issue that can cause InterSystems IRIS® and Caché to not take advantage of large pages for shared memory on Windows, even though these products report that large pages are allocated. This can have detrimental effects on system performance.
Presenter: Kyle Baxter Task: Upgrade to a new version of Caché without concerns about slowing existing SQL queries Approach: Use the new Frozen Plans feature in Caché
Content related to this session, including slides, video and additional learning content can be found here.
InterSystems has corrected two defects that affect online backup of very large databases. Backups taken via external methods, such as snapshots or direct file copies, are not affected. These defects exist in all released versions of all InterSystems products.
InterSystems has identified an issue with product distributions containing Certificate Authority certificates that expire at the end of 2020. This issue does not affect system operation or system security in any way, although it does generate alerts about expiring certificates in the cconsole.log or messages.log files.
Following from Brendan's recent post on the new WRC UI (https://community.intersystems.com/post/new-wrc-customer-interface), we have put together a fairly short (9 minute) video that steps you through the different pages of the interface and shows you how to use the various features for sorting, filtering and exporting data.
InterSystems has corrected a defect that can cause a build-up of orphaned processes consuming system resources. In extreme cases, this can cause a system to become unresponsive.
I am currently working on an Upgrade to HealthShare 2019.1.1. As described in the steps once the upgrade was complete to run $system.OBJ.Upgrade(). When I run $system.OBJ.Upgrade() , it is not finding any classes to update. However I am getting an Error 5116 on one of my Productions...
Class dictionary version for '%1' is out of date, please run upgrade utility $system.OBJ.Upgrade()
so if I am running $system.OBJ.upgrade() why isn't it updating this production as it should?
I am validating a v3 document against one xsd and using %XML.SAX.ContentHandler class . My requirment is to find the xpath of the error location. There is no method which does it.
I can find the line and offset using LocatePosition method.
This error is sometimes seen while viewing a listing in InterSystems IRIS Business Intelligence: ERROR #5540: SQLCODE: -99 Message: User <USERNAME> is not privileged for the operation (4)
As the error suggests, this is due to a permission error. To figure out which permissions are missing/needed, we can take a look at the SQL query that is generated. We will use a query from SAMPLES as an example.
I am calling a stored procedure over an ODBC connection and every time I call it there are several warnings written to the log event {Found no Parameter 1 (used as 1) for query}.I seem to be getting this on every query executed and that seems to happen a number of times the query parameters are per query and its filling up my disc.
1) Is there a way to suppress these warnings as the query seems to be executed and data written to the database?
By likes
Open Exchange app