Oninit
Talk to an expert →

Informix Error -330

-330 Cannot create or rename the database.

Possibly you tried to create a database with the same name as one that already exists or rename a database to a name that already exists; if so, choose a different name. Otherwise, check the accompanying ISAM error code for more detailed information on the cause. Possibly a shortage of disk space or a problem with file permissions exists.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-330 covers a mix of straightforward and infrastructure-level failures on CREATE DATABASE or renaming a database: most commonly a name collision, but potentially disk space or filesystem permission problems underneath.

  1. A CREATE DATABASE statement using a name that already exists on the server — the most common cause.
  2. Renaming a database to a name that's already taken by another database.
  3. Insufficient disk space on the filesystem/dbspace where the new database's system catalog would need to be created.
  4. File permission issues preventing the server process from creating the underlying files.
Solutions / Resolution
  1. Choose a different, genuinely unique database name, per the official guidance, if the cause is a name collision.
  2. Check the accompanying ISAM error code for the specific underlying condition if the name is confirmed to be free.
  3. Check available disk space on the target dbspace/filesystem if the name isn't the issue.
  4. Check filesystem-level permissions for the Informix server process on the relevant directories.
Examples
Confirming the name is actually free before retrying
SELECT name FROM sysmaster:sysdatabases WHERE name = 'sales2';
-- if found, the name is already taken — choose a different one
CREATE DATABASE sales2;
Checking disk space when the name is confirmed free
onstat -d
-- confirm the target dbspace has sufficient free space
-- for the new database's system catalog
Diagnostic Checks
  1. Query sysmaster:sysdatabases to confirm whether the target name is genuinely already in use.
  2. Read the accompanying ISAM error code if the name is confirmed available.
  3. Check disk space and filesystem permissions on the target dbspace.
Related Errors / Related Topics
  • -329 — "Database not found or no system permission." The lookup-side counterpart — this error occurs when a database can't be found rather than can't be created.
  • -310 — "Table table-name already exists in database." A conceptually similar already-exists restriction, at the table level instead of the database level.

Confirm the name is genuinely free first; if it is, the ISAM error code and disk-space/permission checks are the real next diagnostic step.