Thinking Out Loud

March 6, 2016

RANT PSU Naming

Filed under: oracle — mdinh @ 11:12 pm

Do you know what PSU there are?

oracle@arrow:db12c:/media/sf_working/12c/psu
$ ll *.zip
-rwxrwx---. 1 root vboxsf 147028181 Mar  4 20:00 p21948354_121020_Linux-x86-64.zip
-rwxrwx---. 1 root vboxsf 101720296 Mar  4 19:58 p22139226_121020_Linux-x86-64.zip

Let me give you a hint – (12.1.0.1.160119)
Now do you know what they are?

Let me give you another hint.
21948354 (12.1.0.1.160119) – 12.1.0.1 JAN2016 PSU (Database assumed here)
22139226 (12.1.0.2.160119) – OJVM PSU Patches

160119 – what date format is this?

opatch lsinventory

Patch  22139226     : applied on Wed Feb 03 11:07:55 CST 2016
Unique Patch ID:  19729684
Patch description:  "Database PSU 12.1.0.2.160119, Oracle JavaVM Component (Jan2016)"
   Created on 4 Jan 2016, 01:41:46 hrs PST8PDT
   Bugs fixed:
     19699946, 19176885, 19623450, 22139226, 19909862, 21811517, 19223010
     21068507, 19895326, 19877336, 22118835, 22118851, 21566993, 19153980
     20408829, 21047766, 19231857, 19895362, 19855285, 20415564, 21555660
     19245191, 21047803, 20408866, 21566944

Patch  21948354     : applied on Wed Feb 03 11:03:24 CST 2016
Unique Patch ID:  19553095

Looks like the whole numbering system is screwed up now.

Patch description:  "Database Patch Set Update : 12.1.0.2.160119 (21948354)"
   Created on 20 Dec 2015, 23:39:33 hrs PST8PDT
Sub-patch  21359755; "Database Patch Set Update : 12.1.0.2.5 (21359755)"
Sub-patch  20831110; "Database Patch Set Update : 12.1.0.2.4 (20831110)"
Sub-patch  20299023; "Database Patch Set Update : 12.1.0.2.3 (20299023)"
Sub-patch  19769480; "Database Patch Set Update : 12.1.0.2.2 (19769480)"
Advertisements

2 Comments »

  1. 2-digit year. Reminds me of Y2K.
    The “created date” and the PSU date are different. Then, of course, the “applied” date is later. So your documentation must capture all three dates ?

    Comment by Hemant K Chitale — March 10, 2016 @ 3:31 am | Reply

    • 2-digit year. Reminds me of Y2K. – Yes and different country will interpreted date format differently.

      Not sure if there new format was a push from clients.

      I know there are companies with mandate patches must be applied n days after release and this would be useful for auditing purposes.

      Personally, I don’t think created date has any value as this is when Oracle created the patch.

      The following information for when the patch was applied would be good to keep track off.

      Patch 22139226 : applied on Sun Mar 06 15:46:50 PST 2016
      Patch description: “Database PSU 12.1.0.2.160119, Oracle JavaVM Component (Jan2016)”

      Patch 21948354 : applied on Sun Mar 06 15:35:02 PST 2016
      Patch description: “Database Patch Set Update : 12.1.0.2.160119 (21948354)”

      Comment by mdinh — March 13, 2016 @ 3:47 am | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: