bad primary chunk?
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
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
the most direct way to bring a chunk back online is by using the onspaces
command. Type onspaces at the command line and it will feed you a host of
parameters to include with this command. Also check your logs to find out
what Informix says about the down chunk. When you try to bring it up, if it
fails, an error message will be associated with the process. Type finderr
<error #> where error # is the corresponding number of the error message you
get.
Woi Yew Fong wrote:
> 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
--
Phillip Tien
Database Administrator
Whole Foods Market, Inc.
It's not gonna be an orgy...it's a toga party.