Install Ingres patch p13036 on pitblade

From PTAGISWiki

Background

I found it impossible to select on a timestamp value. The fix for me was to learn from Ingres support that I could use a syntax like this:

select start_time from wqb_query_details where start_time=timestamp '2008-09-24 14:09:47.724'\g

But they also expected this syntax to work:

select start_time from wqb_query_details where start_time={ts '2008-09-24 14:09:47.724'}\g

Currently, that second format returns this:

* select start_time from wqb_query_details where start_time={ts '2008-09-24 14:09:47.724'}\g
Executing . . .

E_US09C5 line 1, Syntax error on '{'.  The correct syntax is: 
    SELECT [ALL|DISTINCT] target_list 
      FROM table(s) 
      [WHERE search_cond] 
      [GROUP BY col(s)] 
      [HAVING search_cond] 
 [UNION subselect] 
 [ORDER BY col(s)]
    (Tue Sep 30 10:27:24 2008)

1. Using timestamp literal:   WORKS!!!
 update table set c1='updated' where col2=timestamp '2008-08-15 12:11:42.12'
2. using JDBC escape sequence:  DOES NOT WORK!!!
 update table set c1='updated' where col2={ts '2008-08-15 12:11:42.12' } 

This patch is supposed to change that behavior so that the JDBC escape code syntax works.

Installation procedure

• graceful stop of weblogic via the web admin console
• ingstop
• copied p13036.tar to pitblade:$II_SYSTEM/ingres
• untarred the file
• cd into the newly created patch13036 directory
• run ./utility/iiinstaller

bash-2.05$ ./utility/iiinstaller 
Initializing ...

Determining the target installation's version ...

Patch and target installation versions match.
Version:  9.1.1 (su9.us5/103)

Please be sure to read the release notes for the following bugs as 
they require additional steps for remediation over and above applying 
the patch:

118405
119428
119632
119712
119826
119961

If there are no bugs listed above, please ignore this section.

For sites using the Spatial Object Libraries a separate SOL patch may be 
required in order to maintain installation consistency. 
This will only be required if a SOL patch exists for this patch level.

A SOL patch does not exist for this patch level.

If required, installation instructions are exactly the same as described 
below with the only difference being that the string p13036 is replaced 
with p13036_SOL and patch13036 is replaced with patch13036_SOL.

Do you wish to Continue or Quit install program [C,(Q)]: c

Performing patch install.


------------------------------------------------------------

Initial validation of patch and installation env. complete.
Starting the install program at:  30-Sep-2008 09:45:08

Install log:     /dsk1/ing2006r2/ingII/ingres/files/install_p13036.log
User command:    ./utility/iiinstaller 
Executed from:   /dsk1/ing2006r2/ingII/ingres/patch13036



Generating list of currently installed deliverables ...

Computing disk space requirements ...

Please confirm backup location:
    Current default:  [/dsk1/ing2006r2/ingII/ingres/install/backup]
                      (II_PATCH_BACKUP)
    Free space info (in kbytes):
          Available:  19634855
      Amount needed:  96037
    Press "return" to accept current default, or
    input new location:  


Computing check sums for files under patch directory ...

Check sums for files under patch directory look OK.

Creating a backup of currently installed deliverables.

Backup completed; verifying using check sums ...

Verification of backup complete.

Backup of installation completed successfully.

Installing patch ...

Patch install completed; verifying using check sums ...

Verification of patch install complete.

Finishing up ...


Patch install completed successfully.

The install program completed successfully.


Ending at:  30-Sep-2008 09:48:59

• edit version.rel

bash-2.05$ cat version.rel
II 9.1.1 (su9.us5/103) 12964 13036

• ingstart

bash-2.05$ ingstart

Ingres 2006 Release 2/ingstart

Checking host "pitblade" for system resources required to run Ingres 2006 Release 2...

Your system has sufficient resources to run Ingres 2006 Release 2.

Starting your Ingres 2006 Release 2 installation...

Starting the Name Server...
WARNING!!! The recommended file descriptor hard limit for the NET Server to service 64 inbound, and 64 outbound connections is 261. The current file descriptor hard limit is set to 256.
Starting Net Server (default)...
GCC Server = 61174
    TCP_IP port = II (21064)

Starting Data Access Server (default)...



Ingres 2006 Release 2 installation successfully started.

• restart weblogic

Results

It doesn't appear that the patch solved the problem. Selecting on a timestamp literal still works, but using the JDBC escape sequence still does not work:

pitblade:II:rday: > sql -upittag ptagis3
INGRES TERMINAL MONITOR Copyright 2007 Ingres Corporation
Ingres 2006 Release 2 SPARC SOLARIS Version II 9.1.1 (su9.us5/103) login
Tue Sep 30 10:57:01 2008

continue
* select start_time from wqb_query_details where start_time=timestamp '2008-09-24 14:09:47.724'\g
Executing . . .


┌───────────────────────────────────────┐
│start_time                             │
├───────────────────────────────────────┤
│2008-09-24 14:09:47.724000             │
└───────────────────────────────────────┘
(1 row)
continue
* select start_time from wqb_query_details where start_time={ts '2008-09-24 14:09:47.724'}\g
Executing . . .

E_US09C5 line 1, Syntax error on '{'.  The correct syntax is: 
    SELECT [ALL|DISTINCT] target_list 
      FROM table(s) 
      [WHERE search_cond] 
      [GROUP BY col(s)] 
      [HAVING search_cond] 
 [UNION subselect] 
 [ORDER BY col(s)]
    (Tue Sep 30 10:57:16 2008)

continue

Oops, the JDBC escape syntax is not valid for use in the terminal monitor. So that syntax error is no indication of whether the patch worked or not.

I ran the test select statement with the JDBC escape codes in the Eclipse data base debugging tool and got no results and no errors. So that would indicate that the patch did not work.