Rechercher

Question
· Mai 2, 2024

Compact & Truncate

Hi Guys,

 

I never ran a Compact & truncate process before and we do have a 4.6TB database with 1.9TB free space available that I would like to recover 

 

 

but when trying to compact first it did ask me to target in MBs and not sure what this is, does it mean that I need enough space to move all my 4.6TB database to ? and given that system is running live does the Compact or Truncate process stop or affect our system from been used from our clients and any idea how long such process would take to finish (minutes or hours) ?  

 

 

 

Thanks

8 Comments
Discussion (8)2
Connectez-vous ou inscrivez-vous pour continuer
Article
· Mai 2, 2024 3m de lecture

LinuxでODBC接続を行う方法

こちらの記事では、LinuxでODBC接続の設定を行う方法をご紹介します。


はじめに、Linuxのバージョンを確認します。

$ cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="9.4 (Plow)"
:


1. yumパッケージのアップデートを行います

$ sudo yum update


2. unixODBCをインストールします

$ sudo yum install unixODBC

確認します

$ which odbcinst
/usr/bin/odbcinst
$ which isql
/usr/bin/isql
$ odbcinst -j
unixODBC 2.3.9
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /home/ec2-user/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8


3. IRISクライアントをインストールします

※Linuxのバージョンにあったインストーラを使用してください。

$ cd IRIS-2024.1.0.262.0-lnxrh9x64

$ sudo ./irisinstall_client
Your system type is 'Red Hat Enterprise Linux 9 (x64)'.
Enter a destination directory for client components.
Directory: /intersystems/iris
Directory '/intersystems/iris' does not exist.
Do you want to create it <Yes>?
Installation completed successfully


4. 構成ファイルの作成をします

※SYSTEM DATA SOURCES: /etc/odbc.ini に以下を追加します

[ODBC Data Sources]
InterSystemsODBC6435 = InterSystemsODBC6435

[InterSystemsODBC6435]
Description=InterSystems ODBC
Driver = /intersystems/iris/bin/libirisodbcur6435.so
Setup = /intersystems/iris/bin/libirisodbcur6435.so
Unicode SQLTypes = 1
Host=***.***.***.***
Namespace=USER
UID=_SYSTEM
Password=SYS
Port=1972
$ sudo vi /etc/odbc.ini 


5. 環境変数:ODBCINIの登録をします 

※すべてのユーザで使用できるよう、環境変数を永続化させます。

$ sudo vi /etc/profile

# ---- 以下を追加
export ODBCINI=/etc/odbc.ini

(設定を反映させるために、一度ログアウトして再度ログインします)

$ echo $ODBCINI
/etc/odbc.ini

※ご参考:初期化ファイルの名前と場所


6. IRISへのODBC接続確認をします

$ isql -v InterSystemsODBC6435
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> SELECT count(*) FROM INFORMATION_SCHEMA.TABLES
+---------------------+
| Aggregate_1         |
+---------------------+
| 429                 |
+---------------------+
SQLRowCount returns 1
1 rows fetched
SQL>

 

今回は、IRISクライアントインストールで試しましたが、ODBCドライバ単体のインストールも可能です。
詳細は以下のドキュメントをご覧ください。
UNIX® システムでの ODBC のインストールと検証


ODBCデータソースの定義についての詳細は、以下のドキュメントをご覧ください。
UNIX® での ODBC データ・ソースの定義
 

enlightened【ご参考】
PyODBC経由でIRISに接続するAWS Lambda関数を作成するまでの流れ
LinuxでJDBC接続を行う方法

Discussion (0)0
Connectez-vous ou inscrivez-vous pour continuer
InterSystems officiel
· Avr 30, 2024

Alert: SQL Query using “NOT %INLIST” fails to return results

Alert: SQL Query using “NOT %INLIST” fails to return results

InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results.  See below for the specifics on impacted queries.

This issue exists in the listed versions of the following products:

  • InterSystems IRIS® data platform
  • InterSystems IRIS for Health
  • HealthShare® Health Connect

As well as:

  • Other InterSystems products based on the above products.

Impacted versions:

  • 2021.1.3, 2021.1.4
  • 2022.1.3, 2022.1.4
  • 2023.1.0, 2023.1.1, 2023.1.2, 2023.1.3
  • 2024.1.0

 

Only queries with the following conditions could return wrong results:

  • The WHERE clause contains a NOT %INLIST
  • There is a NULL value in the list

 

The correction for this defect is identified as DP-430793 and will be included in all future product releases beginning with:  2022.1.5, 2023.1.4, 2024.1.0.267.2, and 2024.1.1.  It is also available via Ad hoc distribution. 

If you have any questions regarding this alert, please contact the Worldwide Response Center.

NOTE:  Edited 5/16 to reflect that this defect has been corrected in the newly released 2024.1.0.267.2 patch.

Discussion (0)2
Connectez-vous ou inscrivez-vous pour continuer
Article
· Avr 30, 2024 2m de lecture

Monitoring InterSystems IRIS environments with Red Hat Insights

InterSystems worked closely with the Red Hat Insights team to implement a curated set of recommendations for system administrators to ensure the best experience running InterSystems IRIS on Red Hat Enterprise Linux (RHEL). Included with all RHEL subscriptions, the Insights service proactively identifies potential issues with monitored platforms and applications running on RHEL. Through our joint collaboration, Insights now watches for common scenarios that decrease the performance of IRIS in most cases and offers an InterSystems-approved recommendation for consideration.  

Ten recommendations are currently implemented and can be found under the “InterSystems” topic within the Insights Advisor service.  Advisor recommendations help in areas including:

  1. Performance Tuning Guidance. We provide best practices for configuring HugePages, Transparent HugePages (THP), swappiness, shmmax kernel parameters, and more.
  2. Product Compatibility. Insights highlights which versions of InterSystems products are encouraged to be used to provide the best experience.
  3. Journaling and High-availability Configuration Suggestions, like Write Image Journaling (WIJ) drive mapping, identifying an arbiter to support automatic failure, or enabling FreezeOnError for better integrity and recoverability of InterSystems IRIS database.

Every recommendation contains details about the detected RHEL version, InterSystems IRIS instance information, and system-specific step-by-step instructions to remediate the detected issue.  Links to the InterSystems documentation are also provided for further reference.

Enable Insights with InterSystems today.

Registering your systems with Red Hat Insights is very straightforward and typically requires only a single command to be executed. Alternatively, the Red Hat registration assistant application can be used to complete the necessary steps based on your setup. Analysis of InterSystems IRIS workloads does not require additional steps and is enabled once systems are registered with Insights. Specific recommendations can easily be turned off if they are not applicable to your environment.  

Head to Red Hat Insights to learn more about the service and get started with the registration assistant.

Talk with Red Hat experts at InterSystems Global Summit 2024.

Red Hat will be exhibiting at InterSystems Global Summit June 9-12 and available to discuss Insights and other Red Hat capabilities.

2 Comments
Discussion (2)3
Connectez-vous ou inscrivez-vous pour continuer
Question
· Avr 29, 2024

Export a Production class where the Xdata block items are consistently sorted?

When using something like BeyondCompare when working with production class exports, the XData block "items" content very rarely if ever wind up in the same order making Beyond compare a total mess.

Is there a way of either sorting it on the export, or would I have to find (or write) some XSLT-based tool to go into the exported class and sort all the items? Does anyone know of a tool like that available?

Thanks!

Discussion (0)1
Connectez-vous ou inscrivez-vous pour continuer