Re: Expanded chunk capacity mode in 9.40
Posted in 2004
Topics: Storage & Space Management, Server Administration, Triggers, Constraints & Referential Integrity, Logging & Checkpoints, Versions, Editions & End-of-Life
Andrew Hamm wrote:
>
> Richard Kofler wrote:
> >
> > to enable this new feature you must use onmode -BC
> > Take a quick look into 8.40 Admin Ref & Guide
>
> ok - in 9.40 I see trhat onmode reports the existence of -BC flag
>
> but the online PDF admin and reference guide for 9.40 doesn't describe it at
> all. I assume you really meant 8.40 and not 9.40 manuals? If so I don't have
> them immediately to hand.
It is in the 9.40 online docs, as other poster already pointed out.
We do not have any XPS (version 8.xx) running, only IDS: Version 9.21,
9.30, 9.40.UC2 and 9.40FC4W4
>
> > triggers checkpoints more dense than we want to have
> > them (1 hour we want, 50 mins we get)
>
> You mean you want to have a checkpoint only every hour, but you get one
> every 50 minutes? The alternative interpretation is too horrible to consider
hmm - my English is just too bad sometimes, sorry for that :(
We are using CKPTINTVL 3600, but due to the physical log
filling up to 75% in less than 1 hour during busy hours
we do have checkpoints every 50 minutes.
So far we did not find a way to make our physical log
bigger than 2 GB without enabling large chunk support.
(onmode -BC 1)
> :-> Sounds like there's a little bit more write activity going on with large
> chunks.
I did not notice more write activity when we were testing
with large chunks enabled.
The only troubles we ever had was in IDS 9.40.UC2 and are fixed in
version 9.40.F|UC4.
>
> Ahh well - i'll stick to tradition for this job. Thanks for the pointers.
dic_k
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe
Richard Kofler wrote:
>
> It is in the 9.40 online docs, as other poster already pointed out.
yeah, I just can't seem to find any index entries in the online .PDF
manuals. Have I mentioned I hate PDF?
> hmm - my English is just too bad sometimes, sorry for that :(
>
> We are using CKPTINTVL 3600, but due to the physical log
> filling up to 75% in less than 1 hour during busy hours
> we do have checkpoints every 50 minutes.
> So far we did not find a way to make our physical log
> bigger than 2 GB without enabling large chunk support.
> (onmode -BC 1)
Why not have two chunks in it's space and then .... oh wait, the -s
parameter to onparams -p probably doesn't like such a big number without -BC
hey?
Andrew Hamm wrote:
>
> Richard Kofler wrote:
> >
> > It is in the 9.40 online docs, as other poster already pointed out.
>
> yeah, I just can't seem to find any index entries in the online .PDF
> manuals. Have I mentioned I hate PDF?
Well... Using <CTRL>F one can search in a pdf file and
simulate grep by pressing <F3>, which is 'continue to search'
Not fast - but atleast much better than docs scattered
into 100-reds of html files, where I cannot simulate grep
no matter how patient I am.
Actually, if you
a) download all the pdf files
b) edit the funny file names into something
meaningful and modify the index.html accordingly
c) get a decent module from CPAN to process the bunch
you can grep over all docu files or even extract all
warning or hint sections, exclude windows paragraphs
and thus it IS possible to live with it :)
>
> > hmm - my English is just too bad sometimes, sorry for that :(
> >
> > We are using CKPTINTVL 3600, but due to the physical log
> > filling up to 75% in less than 1 hour during busy hours
> > we do have checkpoints every 50 minutes.
> > So far we did not find a way to make our physical log
> > bigger than 2 GB without enabling large chunk support.
> > (onmode -BC 1)
>
> Why not have two chunks in it's space and then .... oh wait, the -s
> parameter to onparams -p probably doesn't like such a big number without -BC
> hey?
We opened a support case to confirm, that the physical log
cannot have more than one chunk in the dbspace. The docs is
mentioning it pretty straight: storage of the physical log
on disk must be continuous -> it has to be a single chunk
dbspace.
dic_k
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe