Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Matthew Tan planned to move BaanIV data on IDS 7.30.FC7 to a new disk by creating new dbspaces and using onunload/onload. Neil Truby warned that indexes load back into their original dbspace and the dbspace name may matter, and proposed adding mirrors on the new disk and swapping soft links. Matthew said data and indexes are in separate dbspaces. Neil still doubted it would work with a different name.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Matthew Tan — — source: Usenet: comp.databases.informix
We are about to move our BaanIV data to a newer hard disk (running on
the same Digital server v4.0).
Our Informix version is Informix Dynamic Server Version 7.30.FC7
I am thinking of recreating a new dbspace with new chunks. As shown
below this is our current inf_storage file setup:
#---------------------------------------------------------------------#
S T O R A G E
# Please edit this file with vi
#---------------------------------------------------------------------
*:*:T:group:1:10:INITIAL 16 NEXT 16 LOCK row DBSPACE datadbs
*:*:I::1::DBSPACE idxdbs
These will be the steps I will be doing:
1) Create a new dbspace, baandbs with empty chunks
2) Do a on onunload from the datadbs:
ounnload -t /temp/datadbs.out -b 1024 -s 10000000 datadbs
3) Do a onload to the dbspace baandbs:
onload -t /temp/datadbs.out -b 1024 -s 10000000 baandbs4) Change the DBSPACE datadbs in inf_storage to baandbs
For the index it will be:
1) create a new dbspace, indexdbs with empty chunks
2) Do a onunload from the idxdbs
onunload -t /temp/idxdbs.out -b 1024 -s 10000000 idxdbs3) Do a onload to the dbspace indexdbs
onload -t /temp/idxdbs.out -b 1024 -s 10000000 indexdbs4) Change the DBSPACE idxspace in inf_storage to indexdbs
All the steps above correct?
Thanks in advance!
↪ replying to Matthew Tan
Neil Truby — — source: Usenet: comp.databases.informix
--- Original Message -----
From: "Matthew Tan" <happy236@yahoo.com>
Newsgroups: comp.databases.informix
Sent: Tuesday, October 21, 2003 3:12 AM
Subject: Onunload & onload question
> These will be the steps I will be doing:
> 1) Create a new dbspace, baandbs with empty chunks
> 2) Do a on onunload from the datadbs:
> ounnload -t /temp/datadbs.out -b 1024 -s 10000000 datadbs
> 3) Do a onload to the dbspace baandbs:
> onload -t /temp/datadbs.out -b 1024 -s 10000000 baandbs> 4) Change the DBSPACE datadbs in inf_storage to baandbs
>
> For the index it will be:
> 1) create a new dbspace, indexdbs with empty chunks
> 2) Do a onunload from the idxdbs
> onunload -t /temp/idxdbs.out -b 1024 -s 10000000 idxdbs> 3) Do a onload to the dbspace indexdbs
> onload -t /temp/idxdbs.out -b 1024 -s 10000000 indexdbs> 4) Change the DBSPACE idxspace in inf_storage to indexdbs
Not sure what datadbs and indexdbs are, nor DBSPACE. Some sort of Baan
thing I guess.
IDS likes to load indexes back into the dbspace whence they came, so if
wither datadbs or indexdbs contain any indexes, the above won't work.
How would I do it?:
1. Enable mirroring for my instance, if it isn't already
2. Create mirrors for every chunk on the new disk
3. Stop the database server
4. Switch the links around (you *are* using soft links for chunk names,
aren't you?) so that the primaries are now the mirrors, and vice versa
5. Start the database server
6. Drop the mirrors.
All done!
↪ replying to Neil Truby
Matthew Tan — — source: Usenet: comp.databases.informix
"Neil Truby" <neil.truby@ardenta.com> wrote in message news:<bn2n5l$s6gob$1@ID-162943.news.uni-berlin.de>...
> Not sure what datadbs and indexdbs are, nor DBSPACE. Some sort of Baan
> thing I guess.
There are two dbspaces use primarily by Baan. The datadbs contains the
data ONLY while the indexdbs containts the index only.
> IDS likes to load indexes back into the dbspace whence they came, so if
> wither datadbs or indexdbs contain any indexes, the above won't work.
Since, the indexes are in a separate dbspace, my steps will go through
right?
Thanks for the help!
↪ replying to Matthew Tan
Neil Truby — — source: Usenet: comp.databases.informix
"Matthew Tan" <happy236@yahoo.com> wrote in message
news:77a91b88.0310211819.6953cf5@posting.google.com...
> "Neil Truby" <neil.truby@ardenta.com> wrote in message
news:<bn2n5l$s6gob$1@ID-162943.news.uni-berlin.de>...
>
>
> > Not sure what datadbs and indexdbs are, nor DBSPACE. Some sort of Baan
> > thing I guess.
>
> There are two dbspaces use primarily by Baan. The datadbs contains the
> data ONLY while the indexdbs containts the index only.
>
> > IDS likes to load indexes back into the dbspace whence they came, so if
> > wither datadbs or indexdbs contain any indexes, the above won't work.
>
> Since, the indexes are in a separate dbspace, my steps will go through
> right?
I don't think so, not easily, not if the new dbspace doesn't have the same
name as the old.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.