Re: [Info-ingres] Re: Unextend a database
- From: Paul Mason <latepaul@xxxxxxxxx>
- Date: Thu, 19 Jan 2006 15:16:41 +0000
On 1/19/06, martin.bowes@xxxxxxxxxxxxx <martin.bowes@xxxxxxxxxxxxx> wrote:
> Hi Herman,
>
> I'd suggest contacting IngresCorp and asking them exactly what this
> function is supposed to do.
>
> I would have thought that in the case of dropping an extent it did the
> necessary sanity check - ie the database in question isnt actually using
> the area and then was capable of removing the empty directory and
> amending the configuration file accordingly.
>
> Clearly it aint doing that.
No it isn't. But extenddb -l{loc_name} -drop isn't dropping an extent
to a location, it's dropping the location completely. It's the
equivalent of delete in the locations screen of accessdb or DROP
LOCATION in SQL of which the SQL-Ref Guide says:
"Note that you can only drop a data or work location if no currently
existing database has been extended to it"
(P 8-166)
So the only way to remove a location extent in 2.6 is to
unload/reload. Once there are no databases using it you can extenddb
-drop or DROP LOCATION, or accessdb to drop the entire location if
that's what you want.
A PITA to be sure, which is probably why we added unextenddb in r3. :)
>
> I'm running with this is a bug.
>
I'm gonna say it's not it's an unfortunate lack of a feature but it's not a bug.
--
Paul Mason
.
- Prev by Date: Re: [Info-ingres] Re: Unextend a database
- Next by Date: Re: [Info-ingres] imadb
- Previous by thread: Re: Unextend a database
- Next by thread: Re: [Info-ingres] imadb
- Index(es):
Relevant Pages
|
