RE: changing bad location for root chunk

Peter There are ways but I dont think any are supported, or if you have problems IBM may not cover fixing it under support... 1. Link /dev/root_chunk to your character device (/dev/rroot_chunk) and start your engine. Beware that you may break this later should you maintain this device under smit at a later date. 2. Change the root chunk link in $ONCONFIG to point to the correct and already initialised character device and start your engine. Be careful and run either on a test/play instance first. MW > -----Original Message----- > From: owner-informix-list@iiug.org > [mailto:owner-informix-list@iiug.org]On Behalf Of Peter Link > Sent: Tuesday, 13 May 2003 7:48 a.m. > To: informix-list@iiug.org > Subject: changing bad location for root chunk > > > I've inherited an IDS 7.31 UD4 database running on AIX 4.3.3 ML10, > which unfortunately was set up 6 years ago with chunks pointing > directly (no symlinks) to the block devices instead of the > character-special devices. This includes the root chunk. > > We are working with our application vendor's DBA to move our > badly-interleaved tables to separate dbspaces that are correctly > defined with symlinks, raw disk, properly-sized extents, etc. > > My question is: is there a safe way to get the root chunk re-defined > to point to the character-special device instead of the block device, > and better yet, with a symlink? > > A secondary question: is it worth the bother to change it now? > > > Below are a few lines from onstat -d: > Chunks > > address chk/dbs offset size free bpages flags pathname > > 60052210 1 1 125 62500 48881 PO- > /dev/root_chunk > > > Peter Link > University of Michigan Health System > Ann Arbor, MI USA