Oninit
Talk to an expert →

Informix Error -359

-359 Cannot drop or rename the current database or any open database.

The database that is currently open cannot be dropped or renamed. First use the CLOSE DATABASE statement or end the applications that access the database; then you can drop it.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-359 is closely related to -358: DROP DATABASE/RENAME DATABASE requires the target database to not be currently open — by the issuing session or by any other session/application, not just the one running the statement.

  1. The current session has the target database open and is attempting to drop or rename it without first issuing CLOSE DATABASE.
  2. A different session or application still has the database open, even though the issuing session itself is disconnected from it.
  3. A connection pool holding idle connections against the target database, keeping it "open" from the server's perspective even without active queries running.
Solutions / Resolution
  1. Close the database in the current session with CLOSE DATABASE before attempting DROP/RENAME, per the official guidance.
  2. Terminate other applications/sessions accessing the database if the block persists after closing it locally — check for other open connections.
  3. For connection-pooled applications, ensure the pool releases connections to the target database before attempting the drop/rename, since idle pooled connections can still count as "open."
Examples
Closing locally before dropping
DATABASE sales;
CLOSE DATABASE;
DROP DATABASE sales;
Checking for other sessions still holding it open
onstat -g ses
-- lists active sessions; check each session's detail
-- (onstat -g ses <sid>) for the database it's currently
-- connected to, then coordinate with or terminate the
-- relevant ones before retrying
Diagnostic Checks
  1. Confirm the current session has closed the database before attempting the drop/rename.
  2. Check onstat -g ses for other sessions still connected to the target database.
  3. Check for connection-pooled applications that may be holding idle connections open against it.
Related Errors / Related Topics
  • -358 — "Must close current database before CREATE, START or ROLLFORWARD." A closely related restriction requiring a database to be closed before a different set of statements.
  • -330 — "Cannot create or rename the database." A related database-lifecycle error, on creation rather than drop/rename.

Check for other sessions, not just your own, still holding the database open — an idle connection-pool member is a common overlooked culprit.