New post

Find

Article
· Jan 14 2m read

messages.log に出力される SuperServer failed to start slave server のエラーメッセージについて

#System Administration #Tips & Tricks #Caché #Ensemble #InterSystems IRIS #InterSystems IRIS for Health

これは InterSystems FAQ サイトの記事です。
 

09/04/24-14:37:47:260 (2575554) 2 [Utility.Event] ISCLOG: SuperServer Super Server job slave failure ns=%SYS rtn=%SYS.SERVER
09/04/24-14:37:47:260 (2575554) 2 [Utility.Event] SuperServer failed to start slave server

メッセージログ（cconsole.log/messages.log）の上記のようなログは、スーパーサーバ／SuperServer（既定：1972ポート）に対して外部からリクエストがあったが、リクエストに対応する子プロセスの起動に失敗した場合に記録されます。

スーパーサーバへの新規接続に対してスーパーサーバがJOBコマンド(タイムアウトあり)を実行したが、タイムアウト時間内にJOBコマンドが完了しなかったケースなどが考えられます。


通常こちらは 、システムの負荷が非常に高くJOBコマンドによる子プロセスの生成に時間を要してしまったような、OS レベルの問題である可能性が高いです。

運用に支障がないようであれば、そのような状況は一時的であったと考えられます。

子プロセス生成失敗の、さらに詳細な原因は、メモリ上の SYSLOG に残っている可能性があります。


以下の手順で %SYS 上で SYSLOG を実行し、ログを確認することが可能です。

%SYS>do ^SYSLOG
Device: C:\temp\a.log        <-- ログファイルフルパス

Parameters? "WNS" =>         <-- リターン

Show detail? No => Y


SYSLOGのログの内容については、SYSLOGログおよびメッセージログ (cconsole.log/messages.log) を用意して頂き、弊社サポートセンターまでお気軽にお問い合わせください。


もし、このようなシステム高負荷が継続して発生し、このサーバに接続しているアプリケーションにも影響がある場合、Jobサーバを構成することであらかじめJOBコマンド用の待機プロセスを用意して、JOBコマンドの負荷を減らすことでエラーを抑制できる可能性があります。

※JOB サーバについて
JobServers
[システム管理] > [構成] > [追加設定] > [開始] にある [JobServers] 

Discussion (0)0
Log in or sign up to continue
Article
· Jan 14 1m read

Connecting IRIS to SQL Server using ODBC connection

#Authentication #Management Portal #ODBC #SQL #System Administration #Tutorial #InterSystems IRIS

In this tutorial, I will discuss how can you connect your IRIS data platform to sql server db  .

 

Prereq: 

Step 1: Run ODBC data sources  

Step 2: Go to System DSN tab and click add:

 

Step 3: Select "ODBC Driver for SQL Server" and click finish

Step 4: Then fill in the server details:

 

Step 5: 

 

 

 

Step 6: Then click next

 

Step 7: Then click finish

 

You can verify the connection by this window

 

 

Now open IRIS management portal:

Go to: System administration -> Configuration -> Connectivity -> SQL Gateway Connections

Click create new connection

Step 8:  Fill in the details: and test the connection

 

Note if you cant see the DSN: Make sure you selected the correct driver in step 3, and at System DSN level. 

 

And now you have established the connection! 

2 Comments
Discussion (2)2
Log in or sign up to continue
Article
· Jan 14 2m read

第七十三章 管理设备和助记词空间 - 设备的解释级别

#InterSystems IRIS for Health

第七十三章 管理设备和助记词空间 - 设备的解释级别

与 ^%IS 或 OPEN 命令一起使用的设备标识符最多要经过三个级别的解释。因此，如果在 ^%ISDevice： 提示符处输入助记词 47，则使用的最终设备 ID 可能会有所不同。下面介绍了这三个级别。

级别 1：%IS 实用工具级别

如果使用 ^%IS 实用程序选择设备，则使用第一级。^%IS 全局中的助记词可以与设备编号相关联。然后，^%IS 实用程序向该设备编号发出 OPEN 命令。

级别 2：OPEN 命令级别

在 OPEN 命令中，IRIS 会检查此数字是否存在于 Device panel 表的 Alias 列中。如果是这样，它会将其转换为该设备的实际设备号或名称。

Discussion (0)1
Log in or sign up to continue
InterSystems Official
· Jan 14

Alert: Invalid Data Introduced to Database and Journal files with Specific $LIST Operations

#Journaling #ObjectScript #HealthShare #InterSystems IRIS #InterSystems IRIS for Health #TrakCare #Documentation #Health Connect #InterSystems Official

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 is very low but the operational impacts can be significant.

Products Affected

  • InterSystems IRIS® data platform: Versions 2023.3, 2024.1.0, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • InterSystems IRIS® for Health: Versions 2023.3, 2024.1.0, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • HealthShare® Health Connect: Versions 2023.3.0, 2024.1, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • HealthShare® Unified Care Record and Suite: Version 2024.2
  • All offerings based on the above products

 

The issue only affects Unicode installations.

The issue arises when appending a new element to a list in a global using the following syntax:

SET $LIST(<global reference>, *+1) = value.

When the resulting list from this call exceeds the maximum string length, the correct behavior is to return a <MAXSTRING> error.  This is what occurred prior to InterSystems IRIS, InterSystems IRIS for Health, and Health Connect version 2023.3. In 2023.3 and subsequent versions, the invalid value is saved to the database instead of generating a <MAXSTRING> error.

Any subsequent attempt to reference the global node results in a <MAXSTRING> error. 

The global update also results in a journal record (assuming updates to this global are normally journaled).  Any operation that attempts to apply the resulting journal record – including recovery at startup, journal restore, and mirror operations – will fail with a <MAXSTRING> error and halt further processing of the journal file.

If you experience the impact of this defect, contact the Worldwide Response Center (WRC) for assistance.

The correction for this defect is identified as DP-437169. It will be included in all future releases beginning with InterSystems IRIS, InterSystems IRIS for Health and Health Connect 2024.1.3 and 2025.1.0. It is also available via Ad Hoc distribution. The correction will be included in HealthShare Unified Care Record version 2025.1 and suite of products when they are released, but will not be included in maintenance releases of previous releases. If you have any questions regarding this alert, please contact the Worldwide Response Center.

Discussion (0)3
Log in or sign up to continue
Article
· Jan 14 1m read
Open Exchange

Testando FOREIGN SERVER e FOREIGN TABLE

#Docker #JDBC #Namespace #SQL #Testing #InterSystems IRIS

Olá! Eu expandi meu repositório de demonstração, andreas5588/demo-dbs-iris,para facilitar o teste dos recursosFOREIGN SERVER e FOREIGN TABLE no IRIS.

Para alcançar isso, criei um namespace chamado FEDERATION. A ideia é a seguinte:

  1. Configurar conexões JDBC para cada namespace.
  2. Criar um FOREIGN SERVER dentro do namespace FEDERATION para cada conexão.
  3. Definir umaFOREIGN TABLE pelo menos para uma tabela com base em cada servidor externo.

O Script:  demo-dbs-iris/src/sql/02_create_foreign_server.sql

O IRIS não suporta a execução de instruções SQL que combinam tabelas de diferentes namespaces. Para solucionar essa limitação, esse namespace federado aproveita o conceito de criação de servidores externos para incluir outros namespaces. Ao definir tabelas externas, torna-se possível combinar tabelas perfeitamente entre namespaces, permitindo que os usuários escrevam instruções SQL que unifiquem dados em uma única consulta. Esse namespace é usado para explorar esse recurso, serve como uma demonstração prática dessa capacidade, mostrando como explorá-la e utilizá-la.

Execute este contêiner de demonstração diretamente via:

docker pull andreasschneiderixdbde/demo-dbs-iris:latest

Depois disso, você pode fazer consultas como essa:

Divirta-se testando e melhorando a demonstração

 

Andreas

Discussion (0)1
Log in or sign up to continue