freeing sbspace space
Posted in 2011
Topics: High Availability & Replication, Storage & Space Management, Platform-Specific Issues, Versions, Editions & End-of-Life
I have a table with 3 columns, one is a blob held in a sbspace; the sbspace was filling up so I purged out old records and did a level 0 backup. I was looking at utilization of the spaces and chunks using ServerStudio. The sbspace shows as being allocated even though there were no rows in the table. * IBM Informix Dynamic Server Version 11.50.FC8GE (GE=Growth Edition, we are small) * RHEL Linux x86_64 * The database has logging on but the sbspace was not specifically configured with logging on. * The engine is the primary in an HDR pair. So to the questions... Can someone point in the direction to the query that will show if the space is really used or this is just a problem with AGS reporting? Are the docs correct that the space should have been freed after the delete and L0 backup? What if the table is truncated? Is there a way to free the space other than a reorg of the table? Thanks in advance, John Moore
DOH!
Should have held out just a bit longer before posting.
After poking around I found onspaces -cl <space> which cleaned up the
unreferenced smart objects.
John
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
John Moore
Sent: Tuesday, May 31, 2011 9:22 AM
To: ids@iiug.org
Subject: freeing sbspace space [23882]
I have a table with 3 columns, one is a blob held in a sbspace; the
sbspace was filling up so I purged out old records and did a level 0
backup. I was looking at utilization of the spaces and chunks using
ServerStudio. The sbspace shows as being allocated even though there
were no rows in the table.
* IBM Informix Dynamic Server Version 11.50.FC8GE (GE=Growth Edition, we
are small)
* RHEL Linux x86_64
* The database has logging on but the sbspace was not specifically
configured with logging on.
* The engine is the primary in an HDR pair.
So to the questions...
Can someone point in the direction to the query that will show if the
space is really used or this is just a problem with AGS reporting?
Are the docs correct that the space should have been freed after the
delete and L0 backup?
What if the table is truncated?
Is there a way to free the space other than a reorg of the table?
Thanks in advance,
John Moore
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.