Undocumented oncheck features
Posted in 2003
Topics: Storage & Space Management, Cloud, Docker & Containers
After reading the posting from HITEN .S.BHAWSAR regarding Problem
Determination Tutorials, I followed the links and found some useful
information - you're never too old to learn :-) One interesting option was
to use oncheck -me (after exporting RASHELP=1) to merge extents. Has anyone
used this undocumented (until now !!) feature? I assume it just merges
adjacent extents. What locking does it do, typically how long will it run
for, say, a 500,000 row table with 30 extents which could be merged into 4?
How supported is it should it go wrong.
Keith
**********************************************************************************
This message is sent in strict confidence for the addressee only. It may
contain legally privileged information. The contents are not to be disclosed
to anyone other than the addressee. Unauthorised recipients are requested
to preserve this confidentiality and to advise the sender immediately of any
error in transmission.
This footnote also confirms that this email message has been swept for the
presence of computer viruses, however we cannot guarantee that this message
is free from such problems.
**********************************************************************************
sending to informix-list
Keith,
If it isn't documented, it isn't supported.
M.P.
"Simmons, Keith" <keith.simmons@office2office.biz> wrote in message
news:bn30si$jd6$1@terabinaries.xmission.com...
>
> After reading the posting from HITEN .S.BHAWSAR regarding Problem
> Determination Tutorials, I followed the links and found some useful
> information - you're never too old to learn :-) One interesting option was
> to use oncheck -me (after exporting RASHELP=1) to merge extents. Has
anyone
> used this undocumented (until now !!) feature? I assume it just merges
> adjacent extents. What locking does it do, typically how long will it run
> for, say, a 500,000 row table with 30 extents which could be merged into
4?
> How supported is it should it go wrong.
>
> Keith
>
>
****************************************************************************
******
> This message is sent in strict confidence for the addressee only. It may
> contain legally privileged information. The contents are not to be
disclosed
> to anyone other than the addressee. Unauthorised recipients are requested
> to preserve this confidentiality and to advise the sender immediately of
any
> error in transmission.
> This footnote also confirms that this email message has been swept for the
> presence of computer viruses, however we cannot guarantee that this
message
> is free from such problems.
>
****************************************************************************
******
> sending to informix-list