FAQ about using Caché Monitor with InterSystems Caché

This is a list of the questions users asked most frequently about Caché Monitor with InterSystems Caché. The answers were written for Caché Monitor, but the causes (default namespace, port handling, %SYS rights) apply to any JDBC client connecting to Caché or IRIS.

001: Error when selecting the Namespaces node

Question

I am using Caché 2009.1. Apparently the application connects to the server, but when I click on the Namespaces node the following error appears:

PROBLEM: com.intersys.objects.CacheException

Caché Monitor version 0.57
Java version 1.6.0_15, 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.<init>(CacheClassMetadataImpl.java:87)
  at com.intersys.cache.metadata.CacheClassMetadataImpl.<init>(CacheClassMetadataImpl.java:122)
  at com.intersys.cache.metadata.AbstractCacheClass.<init>(AbstractCacheClass.java:47)
  at com.intersys.cache.jbind.JBindCacheClassNew.<init>(JBindCacheClassNew.java:35)
  at com.intersys.cache.jbind.JBindDatabase.getCacheClass(JBindDatabase.java:414)
  at com.intersys.objects.CacheQuery.<init>(CacheQuery.java:26)

Answer

Fix this behaviour by changing the default namespace of the server registration. Open the server properties (right-click the server node, then Properties) and change the default namespace from %CACHELIB to a regular namespace, for example SAMPLES or USER.

002: Caché Monitor does not start properly

Question

When I launch Caché Monitor a splash screen is shown, but then nothing else happens. The process monitor shows that CacheMonitor.exe is running, but there are no other windows.

Answer

This happens if you have not extracted the entire ZIP file. Caché Monitor is missing important files and cannot start properly. The ZIP file contains a folder called lib, and this folder is missing in your installation folder. Extract all files and folders from the ZIP file into your installation folder and start Caché Monitor again. See also the installation instructions.

003: Communication link failure

Question

I cannot connect to my Caché server. I always get a Communication link failure.

Answer

When 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, check the port first. Open the Server properties dialog:

Some information about port handling in Caché:

• Caché 2007.1 and above choose the default ports at installation differently from previous releases. The 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 uses 1972 or the first available subsequent number.

The port actually configured is shown in the Caché ODBC data source dialog and in the Management Portal (superserver port). See how to read the values from the ODBC dialog.

004: User is not allowed to query for namespaces

Question

My account is not allowed to use the %SYS namespace. What can I do?

Answer

Caché Monitor reads the list of namespaces from the %SYS database. If your account does not have the right to access %SYS, disable the namespace query: open the server properties and select the option Don't query for Caché namespace list (called "Don't use %SYS namespace" before version 2.92). Then enter the namespace you want to work with manually on the Details tab of the connection.

006: How can I transfer a single computer licence to another computer?

Question

I wish to transfer my Caché Monitor single computer licence to a new PC. Are there instructions on how to deactivate the licence on the existing PC?

Answer

This cannot be done by the user. Contact support with detailed licence information so that the previous activation can be removed. After that you can activate on another machine. Today, write to sales@sqldatalens.com; see also the licensing page for how Caché Monitor licences carry over to SQL DATA LENS.