I did something similar last week but for a new journal location (ii_journal_2).

I did the same steps as you except for the extenddb part. (defined in accessdb/locations, then relocatedb -new_journal_location).

Looks like extenddb just 'added' your new work location to the existing one.

________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin Bowes
Sent: May 27, 2009 10:36 AM
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] relocating a work location



Hi All,



I've defined an alternate work location (ii_work_2).



I'd like to alter a database to use just that work location and not the standard under II_WORK.



So having defined the work location to the installation, I thought a simple relocatedb would work...

relocatedb bowtest -new_work_location=ii_work_2

Wed May 27 15:26:27 2009 E_DM1503_RELOC_NEWLOC_NOTFOUND New location not found.

Wed May 27 15:26:27 2009 E_DM1507_RELOC_ERR Error occurred while processing the WORK relocation request.



So...

extenddb bowtest -Uwork -lii_work_2

relocatedb bowtest -new_work_location=ii_work_2



Which works without error, but when I check with infodb the database has both work locations defined.



Am I doing something wrong, or have I misinterpretted what relocatedb -new_work_location does?



Ingres Version is: II 9.0.4 (a64.lnx/105)NPTL + p12707



Martin Bowes

Marty,

There may be a doc issue there. My understanding was that -new_work_location
was only used when using relocatedb to create a new database.

I have not tried this but you may be able to use unextenddb to remove the
old work location. Failing that you could make it an Auxillary Work location
for that database in accessdb so that it is not used by default.

Peter Gale
Ingres Corp.

2009/5/27 Martin Bowes <martin.bowes (AT) ctsu (DOT) ox.ac.uk>


--
Peter Gale
pgale61 (AT) gmail (DOT) com

Marty,

I know for certain it will bitch when the small location fills up. The trick
is to map multiple locations (in different sub dirs) to the larger file
system so that in effect you have several locations all the same size. e.g
if the small one is 100mb and the large one is 300mb then map 3 locations to
the large one.

Peter Gale


2009/5/27 Martin Bowes <martin.bowes (AT) ctsu (DOT) ox.ac.uk>



--
Peter Gale
pgale61 (AT) gmail (DOT) com

Yes it will.

Your total work space = the smallest location X the number of locations. The modify will fail when the smallest work location fills up.

Andre

________________________________

From: Martin Bowes [mailto:martin.bowes (AT) ctsu (DOT) ox.ac.uk]
Sent: May 27, 2009 10:59 AM
To: Ingres and related product discussion forum
Cc: Peter Gale; Laframboise, André
Subject: RE: [Info-Ingres] relocating a work location



Hi Guys,



I was just about to try unextendb and see what happens...and it does the trick without any need to use relocatedb...



So there is probably a doc bug...maybe.



Also when I have more than one work location for a database and they are of radically different sizes. And then I try to modify a large table. Will the system work in both locations simultaneously and not bitch when it fills the first location up?



I might have to try that to find out for sure.



Marty



From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Peter Gale
Sent: 27 May 2009 15:49
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] relocating a work location



Marty,

There may be a doc issue there. My understanding was that -new_work_location was only used when using relocatedb to create a new database.

I have not tried this but you may be able to use unextenddb to remove the old work location. Failing that you could make it an Auxillary Work location for that database in accessdb so that it is not used by default.

Peter Gale
Ingres Corp.

2009/5/27 Martin Bowes <martin.bowes (AT) ctsu (DOT) ox.ac.uk>

Hi All,



I've defined an alternate work location (ii_work_2).



I'd like to alter a database to use just that work location and not the standard under II_WORK.



So having defined the work location to the installation, I thought a simple relocatedb would work...

relocatedb bowtest -new_work_location=ii_work_2

Wed May 27 15:26:27 2009 E_DM1503_RELOC_NEWLOC_NOTFOUND New location not found.

Wed May 27 15:26:27 2009 E_DM1507_RELOC_ERR Error occurred while processing the WORK relocation request.



So...

extenddb bowtest -Uwork -lii_work_2

relocatedb bowtest -new_work_location=ii_work_2



Which works without error, but when I check with infodb the database has both work locations defined.



Am I doing something wrong, or have I misinterpretted what relocatedb -new_work_location does?



Ingres Version is: II 9.0.4 (a64.lnx/105)NPTL + p12707



Martin Bowes


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres




--
Peter Gale
pgale61 (AT) gmail (DOT) com