HPL loader question
Posted in 2004
Topics: Server Administration
When HPL loads into a table with indexes it can disable/re-enable the
indexes. When
the indexes are re-enabled how does HPL determine how many threads to use?
Does the onconfig parameter ON_RECVRY_THREADS affect this?
What about when oncheck rebuilds indexes single threadedly. Would
this parameter affect things?
"David Williams" <djw@smooth1.fsnet.co.uk> wrote in message
news:c4stah$60j$1@newsg4.svr.pol.co.uk...
>
> When HPL loads into a table with indexes it can disable/re-enable the
> indexes. When
> the indexes are re-enabled how does HPL determine how many threads to use?
>
> Does the onconfig parameter ON_RECVRY_THREADS affect this?
>
> What about when oncheck rebuilds indexes single threadedly. Would
> this parameter affect things?
I've always assumed that "re-anablement" is simply re-building. Certainly
the "re-enabled" have characteristics of newly-built indexes such as
greatly-reduced space usage etc. Assuming this is correct (and I don;t know
it to be true), wouldn't the parallel sort parms from the session starting
ipload be the key influencers?