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

Reporting patch levels

6 views
Skip to first unread message

Roy Hann

unread,
Jun 23, 1999, 3:00:00 AM6/23/99
to
If the thought of raspberry squirrels is not enough to keep you awake
nights, perhaps you can help out with this one:

I need to determine the patch level of an OI 1.2 installation on NT. I told
someone I couldn't think of any way to do it. Please show me I am wrong.

Roy Hann
BKB Client/Server (UK) Ltd.

Bill Hoelzer

unread,
Jun 23, 1999, 3:00:00 AM6/23/99
to

On 06/23/99 02:52:15 PM Roy Hann wrote:

>I need to determine the patch level of an OI 1.2 installation on
NT. I told
>someone I couldn't think of any way to do it. Please show me I
am wrong.

Roy,

Here is the answer I received from CA Tech. Support when I asked
this question:

There are two ways of determining what patches have been
installed on NT. The first is to simply check the files in the
ingres directories. Any files replaced by a patch will have
the original file backed up with a .pxxxx extension, where
xxxx is the patch number. For instance, if patch 5307 replaces
iiabf.exe with a newer version (which it does), the original
executable will be copied to a file called iiabf.exe.p5307,
and the new iiabf.exe will take it's place. Just check for a
bunch of files in the %II_SYSTEM%\ingres\bin directory with a
.pxxxx extension. The other way is to check the registry.
Whenever a patch is installed, a notation is made in
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates International
Inc.\OpenIngres

When connecting to the server via SQL, and issuing the select
_version()
command the following is displayed:

OI 2.0/9712 (int.wnt/00)

However, when accessing the registry on the server, the
following is found:

[HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates International
Inc.\OpenIngres]
"RegisteredOwner"="MDS"
"RegisteredOrganization"="SCT"
"OIVersion"="OI 1.2/01 (int.wnt/02)"

The upgrade from OpenIngres 1.2 to OpenIngres 2.0 did not update
the registry correctly. The version of OpenIngres 2.0 running on
the server did not have any patches applied.

It looks like the most reliable way to check for patches is to
check the ..\bin directory for files with a .pxxxx extension.
__________
Bill Hoelzer
SCT Manufacturing & Distribution Systems

deLucio, Felipe

unread,
Jun 23, 1999, 3:00:00 AM6/23/99
to

Take a look at the regestry in HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\OpenIngres.
This may help you.
Felipe.

    If the thought of raspberry squirrels is not enough to keep you awake
    nights, perhaps you can help out with this one:

    I need to determine the patch level of an OI 1.2 installation on NT.  I told

    someone I couldn't think of any way to do it.  Please show me I am wrong.

    Roy Hann
    BKB Client/Server (UK) Ltd.

Karl & Betty Schendel

unread,
Jun 24, 1999, 3:00:00 AM6/24/99
to
Roy Hann wrote:

>If the thought of raspberry squirrels is not enough to keep you awake
>nights, perhaps you can help out with this one:
>
>I need to determine the patch level of an OI 1.2 installation on NT. I told
>someone I couldn't think of any way to do it. Please show me I am wrong.

If the patch directory is still there you can tell from it. If the patch.doc
is there you can look at it. If the installation has been all cleaned up,
the best you can do is guess from the create dates of iimerge etc. I don't
know any guaranteed way to tell the patch level.
(Sometimes a patch leaves a version.rel file with the patch level in it,
but not always it seems. If the version.rel date looks close to the exe
dates it might be ok.)

Although we did explore the subject of fruited small game animals, my
recollection is that the whole thing started with raspberry squirrel CAKE.


Karl R. Schendel, Jr.
K/B Computer Associates sche...@kbcomputer.com
Ingres and Unix Expertise

President, North American Ingres Users Association
pres...@naiua.org

Roy Hann

unread,
Jun 24, 1999, 3:00:00 AM6/24/99
to
>It looks like the most reliable way to check for patches is to
>check the ..\bin directory for files with a .pxxxx extension.


Thanks Bill, I will check this out.

Bill Hoelzer

unread,
Jun 24, 1999, 3:00:00 AM6/24/99
to

On 06/24/99 08:31:48 AM Roy Hann wrote:

>>It looks like the most reliable way to check for patches is to
>>check the ..\bin directory for files with a .pxxxx extension.
>


On November 12, 1998, I opened the following issue with CA Tech.
Support. Because of the many clients and systems that we
support, it would be very helpful if we could programatically
determine the patch level of all CA products; Ingres II,
OpenROAD, Enterprise Access (Gateways), and Ingres/Net. The only
answer that I have received so far is that this issue has been
transferred to the DAR group.


Issue 6604253
Definition:
II 2.0/9808 (int.wnt/00)


We would like our software to be able to check the patch level
of the
Ingres DBMS server in addition to the version level.


The dbmsinfo('_version') function returns the Ingres version
string.
It would be helpful if there was also a dbmsinfo('_patch')
function as well.

Or, always update the Ingres version string when a new 'patch'
is sent out.
For example, increment the /00 number for each patch between
major releases.

Resolution:
Transferring to the Dar Group.

0 new messages