The reference to dba_registry_sqlpatch view is in the patch notes that come
with the Quarterly PSUs.
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
<mailto:Dimensional.dba@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
<http://www.dimensionaldba.com/> www.dimensionaldba.com
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Matthew Parker
Sent: Thursday, July 27, 2017 6:09 PM
To: gogala.mladen@xxxxxxxxx; 'oracle-l' <oracle-l@xxxxxxxxxxxxx>
Subject: RE: No time for DB patch?
For 12c the information is stored in dba_registry_sqlpatch, new functionality
when datapatch runs.
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
<mailto:Dimensional.dba@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
<http://www.dimensionaldba.com/> www.dimensionaldba.com
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mladen Gogala
Sent: Thursday, July 27, 2017 4:04 PM
To: oracle-l <oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: No time for DB patch?
I am patching my database with the latest and the greatest patch sets available
today. All was well, I haven't run into any issues. However, when I want to
check the result, here is what I see:
SQL> select action_time,version,comments from dbA_registry_history order by
1;ACTION_TIME VERSION COMMENTS
05/18/15 12.1.0.2.3OJVMBP RAN jvmpsu.sql
11/06/15 12.1.0.2.5OJVMBP RAN jvmpsu.sql
01/20/16 12.1.0.2.6OJVMBP RAN jvmpsu.sql
07/30/16 12.1.0.2.160719OJVMPSU RAN jvmpsu.sql
11/06/16 12.1.0.2.160719OJVMPSU RAN jvmpsu.sql
01/28/17 12.1.0.2.170117OJVMPSU RAN jvmpsu.sql
05/10/17 12.1.0.2.170418OJVMPSU RAN jvmpsu.sql
07/27/17 12.1.0.2.170718OJVMPSU RAN jvmpsu.sql
12.1.0.2 RDBMS_12.1.0.2.0DBPSU_LINUX.X64_161210
9 rows selected.
Elapsed: 00:00:00.342
The same query gives the following result on my 12.2 instance:
SQL> select action_time,version,comments from dbA_registry_history order by 1;
ACTION_TIME VERSION COMMENTS
12.2.0.1 RDBMS_12.2.0.1.0_LINUX.X64_170125
Elapsed: 00:00:00.003
In both cases, the action time for the DB PSU is missing. The time for the
JavaVM PSU is shown without a problem, but there is no time for DB PSU. On the
other hand, version 11 works as advertised:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter session set nls_timestamp_format='MM/DD/YY';
Session altered.
Elapsed: 00:00:00.004
SQL> set sqlformat ansiconsole
SQL> select action_time,version,comments from dbA_registry_history order by 1;
ACTION_TIME VERSION COMMENTS
08/24/13 11.2.0.4 Patchset 11.2.0.2.0
02/17/17 11.2.0.4.170117OJVMPSU RAN jvmpsu.sql
02/17/17 11.2.0.4 PSU 11.2.0.4.161018
05/10/17 11.2.0.4.170418OJVMPSU RAN jvmpsu.sql
05/10/17 11.2.0.4 PSU 11.2.0.4.170418
05/10/17 11.2.0.4.170418OJVMPSU OJVM PSU post-install
05/10/17 Patch 25434033 applied
07/27/17 11.2.0.4.170718OJVMPSU RAN jvmpsu.sql
07/27/17 11.2.0.4 PSU 11.2.0.4.170718
07/27/17 11.2.0.4.170718OJVMPSU OJVM PSU post-install
07/27/17 Patch 26027154 applied
11 rows selected.
Elapsed: 00:00:00.326
Is it just a simple omission or there is some kind of motivation behind this?
Also, there is no Java VM PSU for 12.2? Did Oracle Corp. finally come to the
sensible conclusion that Java is no good and decided to adopt Perl everywhere?
