Re: relinking
Posted in 1999
Topics: Installation, Setup & Upgrades, Storage & Space Management, Platform-Specific Issues
The onstat -d looks like this where the pathname is a symlink to the raw disk......
(abbreviated....)
Chunks
address chk/dbs offset size free bpages flags pathname
c036170 1 1 5 40000 38469 PO- /dev/vx/rdsk/dbdg/db_rootchunk
c036408 2 2 5 250000 236593 PO- /dev/vx/rdsk/dbdg/db_astchunk
c0364e0 3 3 5 250000 179434 PO- /dev/vx/rdsk/dbdg/db_hsrchunk
c0365b8 4 4 5 100000 49947 PO- /dev/vx/rdsk/dbdg/db_llogchunk
c036690 5 5 5 50000 39947 PO- /dev/vx/rdsk/dbdg/db_plogchunk
c036768 6 6 5 900000 622417 PO- /dev/vx/rdsk/dbdg/db_airchunk
c036840 7 7 250005 250000 247012 PO- /dev/vx/rdsk/dbdg/db_astchunk
I created these symlinks when we first installed the system using vm instead of disksuite. I'd
like to change them so that the symlinks reside in a different directory structure - such
as....
/dev/vx/rdsk/dbdg/db_rootchunk - changed to - /dev/dbgroup/db_rootchunk
/dev/vx/rdsk/dbdg/db_astchunk - changed to - /dev/dbgroup/db_astchunk
any ideas? Thanks for your help! maria
Paul watson wrote:
> >>> Maria Wilson <m.l.wilson@larc.nasa.gov> 11/02/99 08:06PM >>>
> >not sure if this is possible or not - here's the scoop -
> >just upgraded to Solaris 7 ( running ods 7.23) and now using disksuite
> >as opposed to vm. Upgrade went fine and restore of database services
> >was easy.... here's the question - Can I change the paths for the
> >symlinks to the raw devices? I know that you can easily relink to a new
> >disk if necessary - but how about doing the opposite and changing the
> >name(path) of the symlink? Really don't want to stay with t.he vm
> >directory structure - if possible.
> >
> >ex - /dev/vx/rdsk/dbdg/rootchunk to /dev/dbgroup/rootchunk
>
> If the vx rootchunk is the path reported via onstat -d then no (ish). This
> is the reason why you use symlinks eg/chunks/rootdbs. You should never use the
> links that the OS uses. If you've got enough disk you can move this link by
> adding/deleting/renaming mirrors devices.
>
> If you are brave then you can tweak the reserve pages but it is not a task to be considered
> lightly
>
> Paul Watson
> WF Software Ltd
> Tel: +44 1436 674729
> Fax: +44 1436 678729
> www.wfsoftware.com/informix
> # If you broke it, hide the evidence
--
----------------------------------------------------------------
Maria L. Wilson 757.766.8265 757.766.2571(fax)
Computer Sciences Corporation
NASA Langley Research Center m.l.wilson@larc.nasa.gov
Hampton, VA 23666 http://www.larc.nasa.gov
----------------------------------------------------------------
Maria Wilson <m.l.wilson@larc.nasa.gov> writes:
> The onstat -d looks like this where the pathname is a symlink to the raw disk......
> (abbreviated....)
> Chunks
> address chk/dbs offset size free bpages flags pathname
> c036170 1 1 5 40000 38469 PO- /dev/vx/rdsk/dbdg/db_rootchunk
> c036408 2 2 5 250000 236593 PO- /dev/vx/rdsk/dbdg/db_astchunk
> c0364e0 3 3 5 250000 179434 PO- /dev/vx/rdsk/dbdg/db_hsrchunk
> c0365b8 4 4 5 100000 49947 PO- /dev/vx/rdsk/dbdg/db_llogchunk
> c036690 5 5 5 50000 39947 PO- /dev/vx/rdsk/dbdg/db_plogchunk
> c036768 6 6 5 900000 622417 PO- /dev/vx/rdsk/dbdg/db_airchunk
> c036840 7 7 250005 250000 247012 PO- /dev/vx/rdsk/dbdg/db_astchunk
>
> I created these symlinks when we first installed the system using vm instead of disksuite. I'd
> like to change them so that the symlinks reside in a different directory structure - such
> as....
> /dev/vx/rdsk/dbdg/db_rootchunk - changed to - /dev/dbgroup/db_rootchunk
> /dev/vx/rdsk/dbdg/db_astchunk - changed to - /dev/dbgroup/db_astchunk
>
> any ideas? Thanks for your help! maria
The whole idea with symlinks is that they don't move -what they point to does:)
I believe you have to rebuild your database with dbschema and other stupid
tools that will make you _extremly_ frustrated...
I've placed the symlinks in $INFORMIXDIR/idb_$INFORMIXSERVER and still believe
thats a good idea 8)
Thomas
Thomas Parsli wrote:
>
> Maria Wilson <m.l.wilson@larc.nasa.gov> writes:
[SNIP]
> The whole idea with symlinks is that they don't move -what they point to does:)
>
> I believe you have to rebuild your database with dbschema and other stupid
> tools that will make you _extremly_ frustrated...
>
> I've placed the symlinks in $INFORMIXDIR/idb_$INFORMIXSERVER and still believe
> thats a good idea 8)
Just let me suggest that using a subdirectory of $INFORMIXDIR for the
chunk links is not as good as idea as it first appears. When you upgrade
you will want to install the new version in a new INFORMIXDIR. There are
three reasons for this. First so you can install the new software in a
clean directory with no old baggage. Second so that you can install the
new software while the engine is ONLINE so the upgrade itself takes only
the time needed to bounce the engine and perhaps for the new engine to
convert disk structures not the time it takes to untar the tapes. The
third reason is so that if there are major problems after the upgrade you
can revert the database and bring up the old version without having to
reinstall. Then latter, perhaps as late as after another upgrade, you can
delete the older INFORMIXDIR structure and recover the space. In this
scenario your chunks directory will still be in the old INFORMIXDIR so you
cannot just 'rm -rf' it, though you might not think about that at the
time... 8-(
Better to go up a level and place the chunk links directory in informix's
HOME directory.
Art S. Kagel
Related threads
- IDS 10 table-level restore
- Informix Development Webinar December 11, 2007
- ontape -p/r with changed ROOTPATH
- Migrate from HP PA-RISC to HP ITANIUM by ontape