New post

Find

Question
· Nov 15, 2023

Issue with accesing Caché database tables with Azure Datafactory

Hello community members!

I am trying to connect to Caché database from Azure data factory using ODBC connection. The aim is to read data from Caché and write it in Azure blob storage using copy activity. The ODBC connection is successful and i can see the Caché  tables, but i'm facing an error while reading the table contents.

I'm getting the below error :

ERROR [HY000] [Cache ODBC][State : S1000][Native Code 400]
[SQLCODE: <-400>:<Es ist ein nicht behebbarer Fehler aufgetreten >]
[Cache Error: <<PROTECT>%0AmBk1^%sqlcq.SYA.cls691.1 ^SB700(""),/database/db4/syb/>]
[Location: <ServerLoop - Query Fetch>]
[%msg: <Unexpected error occurred:  <PROTECT>%0AmBk1^%sqlcq.SYA.cls691.1 ^SB700(""),/database/db4/syb/>]

Can anyone suggest what could be going wrong here and where to look for the issue?

Thanks.


.

5 Comments
Discussion (5)2
Log in or sign up to continue
Article
· Nov 15, 2023 2m read

Java Global Editor

This is the related article to the package in Java Contest. 

I decided to present a CRUD++ Global Editor based on IRIS Native API for Java.
++ because it’s a little bit more than just Create, Read, Update, Delete
Visualization of a global is always important to review results immediately.

  • For this purpose, I have extended the API with a Tree Viewer that mimics  ZWrite and allows also the examination of subtrees.
  • A $Query Style Navigator Forward and Reverse operating for easy finding the Global node of interest.
  • Finally, an option to ZKill to delete the content of a Global Node without deleting the subtree below was added.

This required a small helper class on the server side as an extension to the default API

My strategy was to have a rather modest interface usable from the command line
as on Docker console or terminal and keep it as simple as possible. 
Fancy graphic interfaces just distract from the essential content of the example.

If there is any default or a previous value is displayed at input prompt.

In Docker container, the editor is already ready for use.

  • docker-compose exec iris java gedi

 You first connect to server 

        Welcome to IRIS NativeAPI Global Editor

>>> serverIP [127.0.0.1]:
>>> serverPORT [1972]:
>>> namespace [USER]:
>>> username [_SYSTEM]:
>>> password [SYS]:

        Connected to Namespace USER on Server 127.0.0.1:1972

 

Then you loop in the editor menue

 0 = Select Global
 1 = Select Subscripts
 2 = Query Forward
 3 = Query Reverse
 4 = Show Global Tree
 5 = Update Global Value
 6 = Delete Global Value
 7 = Delete Global Tree
 * = Exit Demo

Select the Global and the Subscript you want to work on . 
Especially Global name and Node Subscripts are kept for simple navigation.

0 Selecting the Global clears all Subscripts 

It can be a fresh nonexistent Global too 

1 The subscript you select is kept until you step to menu 0.

2 Move to the Next node with data.

 

The actual Subscript is updated by the new node

Moving beyond the last node clears Subscripts

3 Move to the Previous Node with data.

moving Reverse from the top node shows the last node

4 The Global tree is shown with the actualSubscript on top

The starting node doesn't need data to be accepted

5 Update or set a value to the Node.

or Update

6 This acts like ZKILL removing data but keeping the subnodes.

7 This is the default KILL destroying data and subnodes.

 * Leaving the editor.

I hope you enjoy it and vote for my demo in the contest.

GitHub

Video

2 Comments
Discussion (2)1
Log in or sign up to continue
Question
· Nov 14, 2023

Cleaning text, removing characters which break XPATH

Hi All

I'm having a problem with cleaning user inputted text from a HealthCare system my HealthConnect system interfaces with.

The input can be anything posted into an RTF box on an app which stored in oracle, and extracted by HealthConnect from oracle via an XML based API.

When the XML is returned, various values are read out of it using %XML.XPATH.Document and it is the presence certain characters entered into the RTF fields cause XPATH to throw an error. For example,

  • ASCII character  8211 (en dash) causes XPATH to give an exception of  ERROR #6901: XSLT XML Transformer Error: invalid character 0x19 in at line n offset nnnnn
  • 8217 (right single quotation mark) -  #6901: XSLT XML Transformer Error: invalid character 0x19 in at line n offset nnnnn

(Note that the character code causing the error is incorrectly identified)

Obviously, I can find and swap out the individual characters using $REPLACE, or even work out which characters break XPATH and write a routine to operate on the XML and clean it. These solutions seem inelegant and clumsy to me, can anyone suggest anything simpler or better?

Cheers

Andy

4 Comments
Discussion (4)2
Log in or sign up to continue
Article
· Nov 10, 2023 2m read

Using NativeAPI Command Line Extension from Java

In my previous articles, I described my Command Line Extension to NativeAPI.
Of course, this is also available for any other NativeAPI package.
So I created this example as a demo for the actual Java Contest.
<--break->
The package contains also an IRIS server in Docker for the demo
It is evident that it also works with any remote IRIS server.
You just have to provide it with my NativeAPI CommandLine Extension.

I think this demo is easy to follow and shows the essential features.

  • First, you install the package and start the container
  • then you start the demo
    docker-compose exec iris java rcc
  • Next, you connect  to your IRIS server defaults refer to the ádde IRIS server in the container
    >>> serverIP [127.0.0.1]:
    >>> serverPORT [1972]:
    >>> namespace [USER]:
    >>> username [_SYSTEM]:
    >>> password [SYS]:
    Connected to Instance IRIS on Server 1C09927CAE60 
  • Now, you get into the demo menu
    Select Demo to exercise 
     0 = free ObjectScript
     1 = $ZV from Server
     2 = Actual Time in Server
     3 = TimeZone Offset of Server
     4 = Server ArchitectureVendorModel
     5 = List Global in ZWRITE style
     * = Terminate demo
    
    And this is the result when you run through all 5 examples
  • 1
     IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2023.2 (Build 227U) Mon Jul 31 2023 18:04:28 EDT 
    
    2
     2023-08-15 07:42:16 
    
    3
     0 
    
    4
     x86_64 * Intel * Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz 
    
    0 
    >>> Your ObjectScript [ quit "?"]: quit $ZTS
     66701,27813.678790226 
    
    0 
    >>> Your ObjectScript [ quit "?"]: quit 17/4
     4.250000000000000000 
    
    0 
    >>> Your ObjectScript [ quit "?"]: quit 17/0
     <DIVIDE> 18 x^%ZX 
    
    5 
    >>> Your Global [^dc.MultiD]:
     ^dc.MultiD = 5
     ^dc.MultiD(1) = $lb("Braam,Ted Q.",51353)
     ^dc.MultiD(1,"mJSON") = "{}"
     ^dc.MultiD(2) = $lb("Klingman,Uma C.",62459)
     ^dc.MultiD(2,2,"Multi","a") = 1
     ^dc.MultiD(2,2,"Multi","rob",1) = "rcc"
     ^dc.MultiD(2,2,"Multi","rob",2) = 2222
     ^dc.MultiD(2,"Multi","a") = 1
     ^dc.MultiD(2,"Multi","rob",1) = "rcc"
     ^dc.MultiD(2,"Multi","rob",2) = 2222
     ^dc.MultiD(2,"mJSON") = "{""A"":""ahahah"",""Rob"":""VIP"",""Rob2"":1111,""Rob3"":true}"
     ^dc.MultiD(3) = $lb("Goldman,Kenny H.",45831)
     ^dc.MultiD(3,"mJSON") = "{}"
     ^dc.MultiD(4) = $lb("","")
     ^dc.MultiD(4,"mJSON") = "{""rcc"":122}"
     ^dc.MultiD(5) = $lb("","")
     ^dc.MultiD(5,"mJSON") = "{}"
     **** done ****
    
    Select Demo to exercise
     0 = free ObjectScript
     1 = $ZV from Server
     2 = Actual Time in Server
     3 = TimeZone Offset of Server
     4 = Server Architecture*Vendor*Model
     5 = List Global in ZWRITE style
     * = Terminate demo
    * >>> exit [OK]: Thank you for trying the demo

Video

GitHub

2 Comments
Discussion (2)1
Log in or sign up to continue
InterSystems Official
· Nov 10, 2023

InterSystems IRIS ミニマムサポート CPU モデル

InterSystems IRIS ミニマムサポート CPU モデル

 

AMD が 1999年に x86-64 を発表したとき、将来サーバ CPU のデファクト・アーキテクチャになる発明だとは知る由もなかったでしょう。しかし、いまや CPU は20年前の製品とは大きく異なります。最新 CPU には AVX (Advanced Vector Extensions) から VT-d (Hardware-Assisted Virtualization) まですべての拡張機能が含まれています。

InterSystems IRIS では、これらの新しい CPU 拡張機能を、より活用していきたいと考えています。弊社コンパイラは、多くの状況では最適化されたコードを生成するようスマートに動作しますが、命令セットを持たないプロセッサでは、いくつかの最適化については動作しないため、非サポートにせざるを得ません。また、古い CPU モデルのテストがますます難しくなっています。

 

IRIS 2024.1 から、すべての Intel ベースおよび AMD ベースのサーバに対して、ミニマムサポート CPU マイクロアーキテクチャを設定する予定です。これは、Windows、Red Hat、Ubuntu、SUSE、Oracle Linux および MacOS を含むすべての x86-64 オペレーティング・システムに適用されます。 次の表は、サポートされる CPU マイクロアーキテクチャの一覧です。

 

メーカー

サポート対象マイクロアーキテクチャ

Intel

Haswell (Broadwell), Skylake (Kaby LakeAmber LakeWhiskey LakeSkylake-XCoffee LakeCascade LakeComet LakeCooper Lake), Palm Cove (Cannon Lake), Sunny Cove (Ice LakeLakefield, Ice Lake-SP), Cypress Cove (Rocket Lake), Willow Cove (Tiger Lake), Golden Cove (Alder LakeSapphire Rapids), Raptor Cove (Raptor Lake), およびそれ以降

AMD

Bulldozer (PiledriverSteamrollerExcavator)Zen (Zen+Zen 2Zen 3Zen 4Zen 5), およびそれ以降

 

この6年ほどで新しいマシンを購入された場合は、お使いのプロセッサーは上記に含まれていると思います。 お手数ですが、ご自身のサーバーがこれらの新しいサポート基準を満たすかどうか、数分かけて確認し、この方針があなたのビジネスに重大な影響を及ぼすかどうかお知らせください。表内の各リンク先に詳細な情報が記されています。
 

それ以外の CPU アーキテクチャのサポートについては変化ありません。

  • AIX における IBM POWER 8 とそれ以降の CPU はサポートされます。
  • Red Hat Enterprise Linux と Ubuntu における ARM64v8 とそれ以降の CPU はサポートされます。

 

AWS、Azure または GCP で稼働しているお客様は、現在サポート対象の CPU モデルをご利用いただけます。ご安心ください。

 

上記のサポートリストは、毎年見直される予定です。

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