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.
A user accidentally overwrote the raw device behind a temporary dbspace (IDS 11.50.FC9IE); the dbspace/chunk is flagged Down and 'onspaces -d' fails with "DBspace is not empty". Restarting the instance (with ONDBSPACEDOWN set) didn't clear the down flag. Art Kagel suggested contacting IBM support, who can mark the chunk/dbspace back online and drop it. No simple self-service fix (e.g. editing sysdbspaces/syschktab) was offered; the poster concluded he'd dbexport all databases, reinitialize the instance and dbimport, which Art endorsed.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
I accidentally overwritten raw device used for dbspace with some data. It
marked as disabled now. This dbspace is not really needed now, we used it for
as temporary space. So i just need to drop it:
informix@...:~$ onstat -d
Dbspaces
address number flags fchunk nchunks pgsize flags
...
4c3fc028 4 0x60005 4 1 2048 ND B informix temp_dbs01
Chunks
address chunk/dbs offset size free bpages
...
4c3fca68 4 4 0 524288 0 PD-B- /dev/ifx/ifx_temp01
informix@...:~$ onspaces -d temp_dbs01 -y
WARNING! The dbspace you wish to drop has been disabled. There
may be database catalog entries for tables or indices which contain
data in this dbspace. If you complete the drop they will be unusable.
Cannot drop the Space.
ISAM error: DBspace is not empty
Any ideas, how to remove this not used dbpsace?
↪ replying to SERGIY ANIKEYEV
KARL OLIVER — — source: IIUG Forums & Mailing Lists
what version informix you using ?
Is disabled the same as down ?.
Should be able to drop down space . I have done it before
Karl,
IBM Informix Dynamic Server Version 11.50.FC9IE
From online.log:
00:46:36 Bad Primary Chunk '/dev/ifx/ifx_temp01'.
Corrupted temp_dbs01 (physical path /dev/ifx/ifx_temp01) has flags [ND B] from
onstat -d output = (N)Not mirrored, (D)Down, (B)Has large chunks greater than2 GB
↪ replying to SERGIY ANIKEYEV
KARL OLIVER — — source: IIUG Forums & Mailing Lists
have you restarted this instance since space was maked down ?
Last time I dropped a corrupt space it was after I had restarted instance.
I had ONDBSPACEDOWN 2 set in onconfig file.
If you have IBM support call them, they can mark the chunk and dbspace back
online and drop it for you if you can give them access to your system.
(Even if you don't have support, it's work asking them if they can help.)
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Wed, Feb 15, 2012 at 8:57 PM, SERGIY ANIKEYEV <sergo@protoka.kiev.ua>wrote:
> Of course i restarted instance many times with no luck, it still uppears
> with
> "ND B" flags.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--e89a8f3ba42935f7cb04b90b3a4c
I can solve this problem just with dbexport all databases -> reinitialize
instance -> dbimport all databases (unfortunally i do not have level 0
archive).
But i was sure that there is a much easier way like delete 2 records from
sysdpspaces/syschktab or something similar, if you know it please advice :)
I'm very surprised there is no simple way to just drop corrupted dbspace.
In any case thanks for your help.
Absolutely! If you can safely dbexport your databases and start from
scratch, go for it!
Art
On Feb 15, 2012 9:29 PM, "SERGIY ANIKEYEV" <sergo@protoka.kiev.ua> wrote:
> I can solve this problem just with dbexport all databases -> reinitialize
> instance -> dbimport all databases (unfortunally i do not have level 0
> archive).
>
> But i was sure that there is a much easier way like delete 2 records from
> sysdpspaces/syschktab or something similar, if you know it please advice :)
>
> I'm very surprised there is no simple way to just drop corrupted dbspace.
>
> In any case thanks for your help.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--bcaec51a76fafd93c304b90bd25a
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.