Sysmaster Funny ?
Paul Watson reported that in IDS 11.10.FC2 the sysmaster sysextents table still lists extents for tables after they are dropped — in one real case, an entire database remained visible there after a DROP DATABASE — whereas the same test script showed no leftover rows under IDS 10. One reply suggested the issue might be an artifact of running the whole script in a single dbaccess run and recommended splitting it into three separate runs, but Paul said that made no difference: the stale entries persisted even after dropping the database, restarting the engine and running onchecks. Another poster only acknowledged it looked like a genuine problem. No fix or workaround is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Under V10 the following code shows no entries in sysextents at the end
of the run. Under V11.10FC2 I have entries left in sysextents. In fact
on the real system I have an entire database left in sysextents after I
execute a 'drop database' statement.
database oninit;
create table eric
(
col1 serial,
col2 char(200),
primary key(col1)
) extent size 20000 next size 20000 lock mode row;
database sysmaster;
select tabname, sum(size), count(*)
from sysextents
where dbsname = "oninit"
and tabname = "eric"
group by 1;
database oninit;
drop table eric;
database sysmaster;
select tabname, sum(size), count(*)
from sysextents
where dbsname = "oninit"
and tabname = "eric"
group by 1;
Cheers
Paul
Paul Watson
Tel: +1 913-400-2620
Mob: +1 913-387-7529
Web: www.oninit.com
Failure is not as frightening as regret.
If you want to improve, be content to be thought foolish and stupid.
Paul Watson (Oninit) wrote:
> Under V10 the following code shows no entries in sysextents at the end
> of the run. Under V11.10FC2 I have entries left in sysextents. In fact
> on the real system I have an entire database left in sysextents after I
> execute a 'drop database' statement.
>
> database oninit;>
> create table eric
> (
> col1 serial,
> col2 char(200),
> primary key(col1)
> ) extent size 20000 next size 20000 lock mode row;>
> database sysmaster;
> select tabname, sum(size), count(*)
> from sysextents
> where dbsname = "oninit"
> and tabname = "eric"
> group by 1;>
> database oninit;
> drop table eric;>
> database sysmaster;
> select tabname, sum(size), count(*)
> from sysextents
> where dbsname = "oninit"
> and tabname = "eric"
> group by 1;>
> Cheers
> Paul
>
>
> Paul Watson
> Tel: +1 913-400-2620
> Mob: +1 913-387-7529
> Web: www.oninit.com
>
> Failure is not as frightening as regret.
> If you want to improve, be content to be thought foolish and stupid.
>
>
How are you running this? Straight through "dbaccess - oninit.sql" where
oninit.sql is the whole of the sql??
Try doing it in 3 separate runs.
TBP wrote:
> Paul Watson (Oninit) wrote:
>> Under V10 the following code shows no entries in sysextents at the end
>> of the run. Under V11.10FC2 I have entries left in sysextents. In fact
>> on the real system I have an entire database left in sysextents after
>> I execute a 'drop database' statement.
>>
>> database oninit;>>
>> create table eric
>> (
>> col1 serial,
>> col2 char(200),
>> primary key(col1)
>> ) extent size 20000 next size 20000 lock mode row;>>
>> database sysmaster;
>> select tabname, sum(size), count(*)
>> from sysextents
>> where dbsname = "oninit"
>> and tabname = "eric"
>> group by 1;>>
>> database oninit;
>> drop table eric;>>
>> database sysmaster;
>> select tabname, sum(size), count(*)
>> from sysextents
>> where dbsname = "oninit"
>> and tabname = "eric"
>> group by 1;>>
>> Cheers
>> Paul
>>
>>
>> Paul Watson
>> Tel: +1 913-400-2620
>> Mob: +1 913-387-7529
>> Web: www.oninit.com
>>
>> Failure is not as frightening as regret.
>> If you want to improve, be content to be thought foolish and stupid.
>>
>>
>
> How are you running this? Straight through "dbaccess - oninit.sql" where
> oninit.sql is the whole of the sql??
>
> Try doing it in 3 separate runs.
Makes no difference. Even after dropping the database and restarting the
engine, running onchecks etc the tables that 'used' to be the database
are still in sysextents
Cheers
Paul
Paul Watson (Oninit) wrote:
OK, I'm not awake yet, you did say V10 Paul. Hmm, doesn't look good.
Art
> Under V10 the following code shows no entries in sysextents at the end
> of the run. Under V11.10FC2 I have entries left in sysextents. In fact
> on the real system I have an entire database left in sysextents after I
> execute a 'drop database' statement.
>
> database oninit;>
> create table eric
> (
> col1 serial,
> col2 char(200),
> primary key(col1)
> ) extent size 20000 next size 20000 lock mode row;>
> database sysmaster;
> select tabname, sum(size), count(*)
> from sysextents
> where dbsname = "oninit"
> and tabname = "eric"
> group by 1;>
> database oninit;
> drop table eric;>
> database sysmaster;
> select tabname, sum(size), count(*)
> from sysextents
> where dbsname = "oninit"
> and tabname = "eric"
> group by 1;>
> Cheers
> Paul
>
>
> Paul Watson
> Tel: +1 913-400-2620
> Mob: +1 913-387-7529
> Web: www.oninit.com
>
> Failure is not as frightening as regret.
> If you want to improve, be content to be thought foolish and stupid.
>
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
> ===========================================================================================
> Please access the attached hyperlink for an important electronic communications disclaimer:
>
> http://www.oninit.com/home/disclaimer.php
>
> ===========================================================================================
>
>
>
===========================================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.oninit.com/home/disclaimer.php
===========================================================================================