HP3000-L Archives

February 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James Clark,Florida" <[log in to unmask]>
Reply To:
James Clark,Florida
Date:
Thu, 17 Feb 2000 09:52:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (77 lines)
I thought the same thing but I believe that this option would, with a
database full of empty delete slots, to continue to extend the high water
mark. Stephen question is why did the high water mark go down?

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Doug Werth
> Sent: Thursday, February 17, 2000 9:32 AM
> To: [log in to unmask]
> Subject: Re: Unknown Highwater Mark Behavior
>
>
> Stephen Bruno <[log in to unmask]> writes:
>
> <snip>
> >
> > 4    A final batch process was then executed, which performed DBPUTs of
> the
> > records removed
> >      from Step 2 above, back into the dataset.  Again, we would also
> anticipate
> > that the highwater
> >      mark would remain, unchanged, however . . .
> >
> >      Dataset stats:      Capacity  Entries         Highwater Mark
> >                     600,000        201,263         354,071
> >
> > There was no execution of an Adager Repack or a DBGeneral Re-org or a
> complete
> > unload/load on
> > the dataset, but yet the highwater mark was lowered.  What else could
> attribute
> > to this and would this
> > cause any performance degradation?
> >
>
> The behavior you describe is consistent with the HWMPUT feature of Image
> which allows you to add entries to your detail datasets at the high-water
> mark, rather than re-using the delete space chain. You can see the setting
> of this flag in DBUTIL.
>
>
> >>show opsdb.pred flags
>   For database OPSDB.PRED
>
>   Maintenance word is not present.
>
>   Access is enabled.
>   Autodefer is disabled.
>   Dumping is disabled.
>   Rollback recovery is disabled.
>   Recovery is disabled.
>   ILR is disabled.
>   Mustrecover is disabled.
>   Logging is disabled.
>   Prefetch is disabled.
>   Indexing is disabled.
>   HWMPUT is disabled.
> <<<<<<<<<<<-------------------------HWMPUT setting
>   Use of lock table for deadlock detection is enabled.
>   Restart is disabled.
>   Database last stored on WED, FEB  2, 2000, 11:23 AM.
>   Database has not been modified since last store date.
>   Shadowing is disabled.
>   Use of Dependency SEMaphore(DSEM) is disabled.
>   Subsystem access is READ/WRITE.
>
> HTH.
>
> Doug.
>
> Doug Werth                             Beechglen Development Inc.
> [log in to unmask]                               Cincinnati, Ohio
>

ATOM RSS1 RSS2