Troubleshooting InterSystems IRIS Cloud Services

Privileged operations

A number of InterSystems SQL commands and procedures available in InterSystems IRIS data platform require privileges that are not available in Cloud SQL and may result in the following error message when executed in the cloud portal or through a programmatic connection:

Error executing statement: User SQLAdmin is not privileged for the operation

These are typically procedures that make use of lower-level platform capabilities, are relevant to non-SQL application development, or both. 

Timeouts and truncated results

When using the SQL Query Tools page of the cloud portal to execute SQL, complex queries on large datasets or queries that return result sets including long text or binary fields may time out, return truncated results, or both. The SQL editor in the cloud portal is intended to support schema and table creation and browsing, data loading, and exploratory queries, and is subject to some architectural constraints on web applications. InterSystems recommends using client-side applications or tools to make programmatic JDBC, ODBC, ADO.NET or DB-API connections to your Cloud SQL deployment for more substantial SQL work involving larger data sets..

Is your deployment running?

In the cloud portal, select Deployments in the left navigation pane and identify the tile for the one you are trying to connect to. If it says Status: Stopped, click the tile to display the deployment’s Overview page, and click the Start button at the top of the Deployment Details section.

If the deployment is not running within a minute or two, please open a ticket with the iService helpdeskOpens in a new tab.

Review and modify the connection settings and parameters

To prepare to make a programmatic connection to your deployment, you must do the following:

• Enable external connections, either when creating the deployment or later.

• Add the originating IP address of the connection to the list of allowed address ranges, or allow all IP addresses by removing the listed ranges if any.

• Determine the correct hostname, port number, namespace, and credentials by consulting the Connection details section of the Overview page.

• Use the Get X.509 certificate button to download a self-signed certificate from the deployment. (You cannot download a certificate when external connections are disabled or when the deployment is not running.

• Review your connection code, including the required TLS encryption, for the DB-APIOpens in a new tab, JDBCOpens in a new tab, ADO.NETOpens in a new tab, or ODBCOpens in a new tab driver (as appropriate) and update your code including TLS configuration as needed.

If one of these is not correct, you may see errors such as the following; each is preceded by a client driver identifier such as [InterSystems IRIS JDBC]):

• Communication link failure: host-string.elb.us-east-1.amazonaws.com

  External connections are not enabled.

  Hostname is incorrect.

  Important:

  If external connections are disabled and then enabled again, a new hostname is generated. Check your hostname value against that displayed in the Connection details section of the Overview page

• Communication link failure: Connection timed out: connect

  IP address at which the connection is originates is not within any of the allowed address ranges.

  Connection is not encrypted using TLS as required.

  Port number is incorrect.

• Communication link failure: Access Denied

  Namespace, credentials, or both are incorrect.

• Communication link failure: Socket is closed / Communication link failure: Cannot find the file specified /path/SSLConfig.properties

  The TLS configuration is incorrect.

  The correct certificate is not specified.

  Important:

  If you download a self-signed certificate from the deployment using the Get X.509 certificate button while external connections are enabled, then disable external connections and later reenable them, you must download a new certificate; the previous certificate will not work.

To make any required settings changes and verify the needed information, open the cloud portal, select Deployments in the left navigation pane, and click the tile for the one you want to connect to. On the Overview page, scroll down to External Connections.