I have tested patch P12814 for Solaris and Ingres 2.6. It has a fix for
bug 101117:
"Failures during usermod can lead to non-persistent objects being
dropped without warning."
Also look out for a pending fix for bugs 120485:
"If a usermod fails because of a lock timeout the tem****ary files (in
II_TEM****ARY) are removed."
and 14901:
"The Ingres terminal monitor does not return a non-zero OS status on
error when /nocontinue is specified, making it more difficult to build
tm commands into automated scripts."
And I have an outstanding do***entation request to make sure the manual
and online help are enhanced to cover issues about locking, restarts,
user permissions, tem****ary sort space, etc. And also to include a
section in the DBA guide.
Paul
________________________________
From: info-ingres-bounces@[EMAIL PROTECTED]
On Behalf Of Paul
White
Sent: Tuesday, 22 July 2008 8:31 AM
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Question on usermod command
The 2.6 do***entation 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
-----Original Message-----
From: info-ingres-bounces@[EMAIL PROTECTED]
Behalf Of
Wallen, Alan - ES/EW
Sent: Tuesday, 22 July 2008 4:20 AM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Question on usermod command
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 Cor****ation. 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.
|
