[
https://issues.apache.org/jira/browse/DERBY-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-4298.
-------------------------------------
Resolution: Duplicate
This looks like a duplicate of DERBY-2068. Closing as such.
> Derby should give clearer error message (not Database not found) or succeed
> if user attempts to shutdown a database that is not booted
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4298
> URL: https://issues.apache.org/jira/browse/DERBY-4298
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1,
> 10.6.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If a Derby database is not booted and a user attempts to shut it down, they
> will get a Database not found message which can be misleading. We should have
> a better error message at least or perhaps just boot the database and then
> shutdown. I think the later would be preferable but don't know if there is
> some reason against it.
> [C:/test5] java org.apache.derby.tools.ij
> ij version 10.6
> ij> connect 'jdbc:derby:wombat;create=true';
> ij> exit;
> [C:/test5] java org.apache.derby.tools.ij
> ij version 10.6
> ij> connect 'jdbc:derby:wombat;shutdown=true';
> ERROR XJ004: Database 'wombat' not found.
> To workaround the issue, you can first make a connection to the database and
> then shutdown.
> ij> connect 'jdbc:derby:wombat';
> ij> connect 'jdbc:derby:wombat;shutdown=true';
> ERROR 08006: Database 'wombat' shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
