Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Info-Ingres] Question on usermod command

33 views
Skip to first unread message

Wallen, Alan - ES/EW

unread,
Jul 21, 2008, 2:38:04 PM7/21/08
to Ingres and related product discussion forum
The Ingres 2.6 Command Reference Guide's description for the usermod command states "The usermod command modifies a database's user-defined tables to the most appropriate storage structure for accelerating query processing."

I had thought that usermod simply modified the tables to their defined storage structures which is what I recall seeing in the description for usermod in the Ingres 2006 Command Reference Guide.

Has this command changed between the two versions of Ingres or is the description incorrect in the Ingres 2.6 Command Reference Guide?

We're running Ingres 2.6 and I wouldn't want to suddenly have our database tables changed to unexpected storage structures if I were to run this command.

Thanks,
Alan

________________________________
This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.

Paul White

unread,
Jul 21, 2008, 6:52:41 PM7/21/08
to Ingres and related product discussion forum
The 2.6 documentation was misleading. It was corrected in Ingres2006.

In 2.6 be sure to capture the output of the usermod command (I use tee) so,
after a fail condition, you can restart the rebuild at the correct point.
In case of any fails, dont run usermod a second time otherwise you risk
losing index definitions. It is a good idea to keep a backup copy of the
schema definition just in case.

There has also been some recent enhancements to make the operation safer by
rebuilding the indexes immediately after each table modify instead of at the
very end.
Also the newer version provides more efficient parallel index rebuilds and
is therefore much faster.

I cant remember the patch numbers just now but will post them when I get
into the office.

Paul

0 new messages