RE: Sysmaster Funny ?

'Works' under V10, nothing in sysextents. Under V11 the tables still 'exist' in sysextents even after a restart 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. > -----Original Message----- > From: Art S. Kagel (Oninit) [mailto:art@oninit.com] > Sent: 09 March 2008 08:43 > To: paul@oninit.com > Cc: informix-list@iiug.org > Subject: Re: Sysmaster Funny ? > > 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 > > ======================================================================= > ==================== =========================================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ===========================================================================================

Got to the bottom of it - the same disk (dbspace) was being used by a dev instance and a HDR Secondary. Once that was fixed everything is fine. Chers Paul Paul Watson wrote: > 'Works' under V10, nothing in sysextents. > > Under V11 the tables still 'exist' in sysextents even after a restart > > 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. > > >> -----Original Message----- >> From: Art S. Kagel (Oninit) [mailto:art@oninit.com] >> Sent: 09 March 2008 08:43 >> To: paul@oninit.com >> Cc: informix-list@iiug.org >> Subject: Re: Sysmaster Funny ? >> >> 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.