Informix Error -827

Reasons / Common Causes

-827 is the interactive-tool-context counterpart to -329: per the official guidance, this error's own documentation simply points to -329's discussion, so the same underlying causes apply here — a misspelled name, the database living on a different server, a missing/incorrect DBPATH on Informix SE, the database genuinely not existing, or (on a secondary server) the database being unlogged.

1. A misspelled database name — the simplest and most common cause, per -329's discussion.
2. The database on a different server/site, needing an explicit @server qualifier.
3. On Informix SE, an incorrect or missing DBPATH.
4. The database genuinely not existing under that name.
5. On a secondary (HDR/RSS) server, an unlogged database not visible there.

Solutions / Resolution

1. Follow -329's documented resolution steps — verify spelling, specify the server explicitly if the database is remote, check DBPATH on SE, confirm existence via sysdatabases on Dynamic Server, and check logging status on a secondary server.
2. Confirm DBPATH's current setting, since this error's own text emphasizes it directly:

   echo "$DBPATH"
   

Examples

Checking DBPATH

$ echo "$DBPATH"

Confirming the database exists

SELECT name FROM sysdatabases WHERE name = 'target_db';

(run against sysmaster via dbaccess, per -329's documented check)

Diagnostic Checks

1. Follow the same diagnostic checks as -329: spelling, server topology, DBPATH (on SE), and logging status (on secondaries).

Related Errors / Related Topics

• -329 — "Database not found or no system permission." The general form of this same condition — this error's own official text points directly to -329's discussion for the full detail.

Same underlying causes as -329 — this error's own documentation points there directly.