RE: bad primary chunk?
hi again, i noticed that when i do a onstat -d, it showed there are 10
active dbspace
Dbspaces
address number flags fchunk nchunks flags owner name
33710108 1 1 1 1 N informix wdps_root
33710d20 2 1 2 1 N informix wdps_dbspace
33710d98 3 1 3 1 N informix wdps_blob
33710e10 4 2001 9 1 N T informix wdps_temp
33710e88 5 1 5 2 N informix wdps_dbspace2
33710f00 6 1 6 1 N informix wdps_dbspace3
33710f78 7 8000 7 1 N S informix mysblobs
33710ff0 8 1 8 1 N informix wdpsdbs4
33711068 9 2001 10 1 N T informix tempdbs1
337110e0 10 2001 11 1 N T informix
wdps_temp_tc00
10 active, 2047 maximum
Chunks
address chk/dbs offset size free bpages flags pathname
33710180 1 1 0 100000 27968 PO-
/informix/dbspace_link/rootdbs
337104b0 2 2 0 500000 407188 PO-
/informix/dbspace_link/wdpsdbs
33710588 3 3 0 250000 249947 PO-
/informix/dbspace_link/blobdbs
33710660 4 5 0 102400 11645 PO- /s6/wdpsdbs2_02
33710738 5 5 0 100000 34781 PO- /s6/wdpsdbs2
33710810 6 6 0 100000 90763 PD- /s7/wdpsdbs3
337108e8 7 7 0 5000 -1 -1 PDS
/informix/mysblobs
337109c0 8 8 0 100000 90763 PO- /s7/wdpsdbs4
33710a98 9 4 0 50000 49947 PO- /s6/tempdbs
33710b70 10 9 0 100000 99947 PO-
/tc10/wdps/tempdbs
33710c48 11 10 0 100000 99697 PO-
/tc00/tempdbs_tc00
11 active, 2047 maximum
However, when i check onmonitor dbapaces -> info, the dbspace no.7
(mysblobs) is not there. Why is it so? What could have happened to cause
this ?
what does this indicate? what is the diff between the onstat -d & the
onmonitor dbapaces -> info ?
rgds,
YFWoi
-----Original Message-----
From: Dirk Moolman [mailto:dirkm@reach.co.za]
Sent: 22 November 2000 22:38
To: Woi Yew Fong
Subject: RE: bad primary chunk?
Hi, the only way you will know which device was linked to which dbspace, is
if you kept a copy somewhere of your links and database layout.
I have a script on my system that creates all my links, and I also print
out the database layout (onstat -d) everytime I make a backup.
With this information you will be able to recover your links. I don't think
you will be able to do it otherwise.
Dirk
-----Original Message-----
From: owner-informix-list@iiug.iiug.org
[mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Woi Yew Fong
Sent: Wednesday, November 22, 2000 12:24 PM
To: informix-list@iiug.org; 'Neil Truby'
Subject: RE: bad primary chunk?
How can re-establish the link back?
How to know the bad chunk is link(assigned) to which dbspace previously ?
Btw, I'm using IUS 9.14 on IRIX 6.5.
-----Original Message-----
From: Neil Truby [mailto:ntruby@netcomuk.co.uk]
Sent: 22 November 2000 13:48
To: informix-list@iiug.org
Subject: Re: bad primary chunk?
What could cause it? A failed disk or controller. Someone removed the
link. Someone wrote directly to the disk area and corrupted it.
If it's one of the non-fatal problems, like the link had been removed and
you've now re-established it, then onspaces will allow you to bring it back
online. Otherwise a restore from archive is necessary.
Woi Yew Fong <yfwoi@tpl.com.sg> wrote in message
news:8vfbvj$n6d$1@news.xmission.com...
>
> I keep encounter this message "Bad primary chunk /s7/mysblobs" when i do a
> onmonitor mode -> startup or oninit -s. I also noticed
> that the bad chunk (/s7/mysblobs) is offline. What could cause a chunk to
> offline? How do i bring the chunk up/online?
>
> YFWoi