to the Connection Properties dialog in Caché Monitor:

1. Host \ IP Address
   Specifies the IP address in dotted decimal such as “127.0.0.1” or just the server name

2. Host Port Number
   Specifies the port for connecting to the DSN. The default for Caché is 1972.

3. User Name
   Specifies the username for logging into the DSN. By default, this is “_SYSTEM” and is not case sensitive.

4. Password
   Specifies the password for the account specified by the UID entry. For the SYSTEM username, the password is “SYS” and is case sensitive.

5. Caché Namespace
   Specifies the namespace for the DSN. For Caché Monitor this information is not required cause Caché Monitor shows all Namespaces from Server for easy navigation. A User Name with the enough rights to query this information from SYS database is required. If the selected User hasen’t the required rights, on the Details tab a namespace can be selected (entered).

The post Get Intersystems Caché ODBC settings to use with Caché Monitor (JDBC) appeared first on Tools for InterSystems Caché and Intersystems IRIS.

The post Import Caché Connections appeared first on Tools for InterSystems Caché and Intersystems IRIS.

There are two configuration options enabled by default to let Caché Monitor work better with network proxies. Please disable these options and try again.

To do that open the config.properties file (you find it in the Caché Monitor install folder) and change two lines from:

system.java.net.useSystemProxies=true
system.java.net.preferIPv4Stack=true

into this

#system.java.net.useSystemProxies=true
#system.java.net.preferIPv4Stack=true

Alternatively you can also remove the lines

After doing this restart Caché Monitor please. Now the error message should be gone.

The post communication link failure: Malformed reply from SOCKS server appeared first on Tools for InterSystems Caché and Intersystems IRIS.

The Query Cloud is like a virtual database. Within this virtual database you can query and use data from different databases, combine them with SQL as if they are in the same database. The jTDS database driver is an free driver for Microsoft SQL Server (6.5, 7, 2000, 2005, 2008 and 2012) and Sybase Adaptive Server Enterprise (10, 11, 12 and 15). Read this to get details about register the jTDS driver within Caché Monitor.

If you want to add a table to Caché Monitors Query Cloud to combine them with other tables (data) from another datasources there exists a limitation that need to be respected: To adding tables from a jTDS datasource to the Query Cloud we recommed to create a seperate connection within Caché Monitor for the source database.

For example: If you want to add tables from the AdvatureWorks2014 database, the connection information (connection url) should contain the database:

In the Server Navigator you can view tables from any database on the specific server. But only tables from the database that are specified in the connection url e.g. AdventureWorks2014 should be added to the Query Cloud!

The post How to use the jTDS database driver with Caché Monitors – Query Cloud appeared first on Tools for InterSystems Caché and Intersystems IRIS.

This database driver is an open source driver for MS SQL Server & Sybase Adaptive Server. jTDS is 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL Server (6.5, 7, 2000, 2005, 2008 and 2012) and Sybase Adaptive Server Enterprise (10, 11, 12 and 15). jTDS is free software and released under the terms of the GNU LGPL.

The next steps are not required if you use Cache Monitor 2.81 or later because the driver and the configuration are already included!

To use this driver within Caché Monitor follow the next steps, please:

1. Download the driver and copy to the Caché Monitor folder
   Download the jTDS Driver from here https://sourceforge.net/projects/jtds/files/
   Navigate to the Caché Monitor installation folder, e.g. C:\Program Files (x86)\CacheMonitor and open the folder called “libs”. Create a new folder called “jtds” and copy the database driver into that folder. You find the driver file in the zip file you’ve downloaded before. The Driver file called like “jtds-1.3.1.jar”.
2. Register the driver file
   Navigate to the Caché Monitor installation folder, e.g. C:\Program Files (x86)\CacheMonitor and open the file “config.properties” with an editor and insert this lines:jdbc.jtds.drivername=jTDS for MS SQL Server & Sybase Adaptive Server
   jdbc.jtds.driverclass=net.sourceforge.jtds.jdbc.Driver
   jdbc.jtds.driverlib=lib/jtds/jtds-1.3.1.jar
   jdbc.jtds.sampleurl=jdbc:jtds:<server_type>://<server>[:<port>][/<database>][;<property>=<value>[;…]]
3. Select the driver and connect

Use the driver’s integrated security, which automatically absorbs the *current OS user’s* identity to verify with the DBMS at runtime.

The post How to use the jTDS databse driver for MS SQL Server & Sybase Adaptive Server with Caché Monitor appeared first on Tools for InterSystems Caché and Intersystems IRIS.

The post Support appeared first on Tools for InterSystems Caché and Intersystems IRIS.

001 – Error by select the Namespaces node

Question: I’am using Cache 2009.1, apparently the application connects to the server however, when I try to click on the Namespaces node, the following error appears:

PROBLEM: com.intersys.objects.CacheException

ERROR DISPLAYED:
Caché Monitor-Version 0.57
Java Version 1.6.0_15
VM Name Java HotSpot(TM)
Client VM Driver Version:2009.1.1.504

com.intersys.objects.CacheException at com.intersys.cache.jbind.ReadOnlyDatabase.parseStatus(ReadOnlyDatabase.java:1640) at com.intersys.classes.CPPStoredProc.getJavaClassDef(CPPStoredProc.java:1774) at com.intersys.cache.metadata.CacheClassMetadataImpl. (CacheClassMetadataImpl.java:87) at com.intersys.cache.metadata.CacheClassMetadataImpl. (CacheClassMetadataImpl.java:122) at com.intersys.cache.metadata.AbstractCacheClass. (AbstractCacheClass.java:47) at com.intersys.cache.jbind.JBindCacheClassNew. (JBindCacheClassNew.java:35) at com.intersys.cache.jbind.JBindDatabase.getCacheClass(JBindDatabase.java:414) at com.intersys.objects.CacheQuery. (CacheQuery.java:26)

Answer:
Fix this behavior by changing the default namespace of the Server registration. Go to the Server Properties (right click on server node -> properties) and change the default namspace from %CACHELIB to e.g. SAMPLES. You find more details about this topic: here

002 – Caché Monitor didn’t start properly:

Question:When I launch Caché Monitor, a splash screen is projected, but then nothing else occurs. If I check the process monitor on my XP machine, I see that CacheMonitor.exe is running, but nothing happens and there are no other screens.
A:
This behavior occurs if you haven’t extract the entire zip file from Caché Monitor. Caché Monitor are missing important files and can’t start properly.
In the zip file is a folder called “lib” this folder is mssing in your installation folder.

Extract all files and folders from the zip file into you installation folder and start Caché Monitor again.

003 – Communication link failure

Q:
I can’t connect to my Caché Server, i always get an “Communication link failure”
A:

If you register a new server in Caché Monitor the default Port is 1972. This can be the wrong port! If you get a “Communication link failure”, please check the port first. You can do that by open the “Server properties” dialog:

Here are some Information about the port handling in Caché:

Caché 2007.1 and above chooses the default ports for installation differently from previous releases. The new algorithm is:  If port 1972 is unused, choose it. Otherwise, choose the first available port number equal to or greater than 56773.

Caché 5.2 does it in this way:  Use 1972 or the first available subsequent number.

004 – User are not allowd to query for namespaces

Question: My connection is not allowd to use the %SYS namespace. What can i do?

Answer:  If your account haven’t the right to access the %SYS namespace wich is the needed for the namespace list you can disable the query for namespaces.

006 – How can I transfer a single computer license to another computer

Question: I wish to transfer my Caché Monitor Single Computer license to a new PC. Are there any instructions on how to deactivate the license from the existing PC?

Answer: This can’t be done by a Caché Monitor User itself. You have to contact support with detailed license information, so they can remove a previous activations. After this you can activate on another machine.

The post FAQ about using Cache Monitor with InterSystems Cache appeared first on Tools for InterSystems Caché and Intersystems IRIS.

How to: using the editor

How to: register server from local known Caché servers

How to: working with script manager

How to: Write sql queries across databases

Show how Caché Monitor helps to query and bring together tables from different sources. Writing sql query across namespaces; databases and jdbc sources like MS SQL Server is very easy with Caché Monitor. All this is done without any installation\configuration on Server Side!

How to: Working with CSV files like database tables

Join (Merge, Combine) multiple CSV Files via SQL. Analyse and Filter your csv files like any onther database table.

How to: Connect to MySQL on Amazon Web Service

This video shows how to Connect to a MySQL database on Amazon Web Service with Caché Monitor. You see how to identify and config the JDBC connection string to connect.

How to: query data from three servers in one SQL

This video shows how to query data from a MS SQL Server and two InterSystems Caché Servers in ONE sql statement. The example statement JOINs five tables: three tables from the Adventure Works database and one table on each Caché Server. This is done via Microsoft SQL Server Linked Server feature.

The post How to Videos of Caché Monitor appeared first on Tools for InterSystems Caché and Intersystems IRIS.

The post Requirements running Caché Monitor appeared first on Tools for InterSystems Caché and Intersystems IRIS.

Pressing CTRL+O open also a new Query Analyzer but you must choose server and namespace.
Find Cached Queries that are expensive to execute

The post First steps with Caché Monitor appeared first on Tools for InterSystems Caché and Intersystems IRIS.