Skip to main content
Host, port, username, password. The plugin speaks the DM8 wire protocol itself, so no part of the DM client stack has to be on your Mac and no DM8 version is ruled out.
A CLOB or BLOB that DM8 stored outside the row reads as an empty cell. Nothing marks it as truncated, so it looks exactly like an empty column. Cast CLOB values to VARCHAR, or wrap binary columns in RAWTOHEX, when you need the contents.
Dameng DM8 connection form

The Dameng DM8 connection form

The driver is not in the app. Picking in the Choose a Database sheet offers the download before the form opens, and opening a saved connection installs it without asking. Settings > Plugins > Browse > installs it up front. See Plugins.

Quick setup

Click Create Connection…, choose Dameng DM8, fill in host, port, and credentials, and click Save & Connect.

Connection settings

One DM8 instance holds one database, so there is nothing to switch between; use the schema picker instead, which switches without reconnecting. SYS, SYSDBA, SYSAUDITOR, SYSSSO, and CTISYS are marked system schemas. An open tab stays on the schema it started with. See Tabs.

Connection URL

The path is a schema, not a database. See Connection URL Reference.

SSL/TLS

None. Native DM8 TLS is not implemented, the SSL pane is hidden, and the connection is unencrypted. Reach a server outside a private network through an SSH tunnel, SOCKS proxy, or Cloudflare tunnel.

Limitations

  • Stopping a query drops its connection. The driver reconnects on your next query, back on the schema you were using: a read reruns, an open transaction is gone, and a write is reported rather than retried. Check whether the write landed before running it again. A query timeout does the same.
  • The server finishes the statement you stopped. A heavy query keeps running there, and a stop can take a few seconds to show up.
  • A view definition longer than 8188 bytes is refused. The DDL tab reports the length instead of showing truncated text you could save back. Read the full definition on the server.
  • Username and password are the only authentication, and there is no trigger editor. Write trigger DDL in the SQL editor.

Troubleshooting

The Dameng connection is closed.: The server, a tunnel, or the network dropped the connection. The driver rebuilds it on the next query; rerun the statement. The Dameng connection was lost, so the open transaction was rolled back.: Nothing in that transaction committed. Run its statements again. Dameng did not switch to the requested schema.: The schema does not exist or your user cannot reach it. List the schemas visible to your user with SELECT OBJECT_NAME FROM ALL_OBJECTS WHERE OBJECT_TYPE = 'SCH'. Switch away from a schema before dropping it.: A schema cannot drop itself out from under the session. Move to another one first. If a server value fails to decode, include the DM8 version and the column type in a GitHub issue.