Last PSU

[big]

Hi,

I wanted to know the highest PSU on my DB (11.2.0.4).
 
Then I ran:

$ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed | egrep -i 'DATABASE PSU|DATABASE PATCH SET UPDATE'

That gave me back two rows:

19852360   26027154  Sat Sep 23 10:30:07 CEST 2017  ORACLE JAVAVM COMPONENT 11.2.0.4.1 DATABASE PSU -
19769489   19769489  Tue Feb 02 17:17:14 CET 2016   DATABASE PATCH SET UPDATE 11.2.0.4.5 (INCLUDES CPU

Which is my highest PSU? Is my commande line correct for finding the PSU?

Any other way to find last PSU?

Thanks.

[ErmanArslansOracleBlog]

Yours seems like Jan 2015 PSU.
This one -> Bug 19769489 - 11.2.0.4.5 (Jan 2015) Database Patch Set Update (DB PSU)

For 11G; check with the query below;

SELECT TO_CHAR(action_time, 'DD-MON-YYYY HH24:MI:SS') AS action_time,
       action,
       namespace,
       version,
       id,
       comments,
       bundle_series
FROM   sys.registry$history
ORDER by action_time;

The following might also help;

SELECT comments, version, action, TO_CHAR(action_time, 'DD-MON-YYYY HH24:MI:SS') AS action_time
FROM   sys.registry$history
WHERE  comments LIKE '%PSU%'
AND    action = 'APPLY';

[ErmanArslansOracleBlog]

You should consider applying an up-to-date PSU, the latest one ->

Patch 31537677: DATABASE PATCH SET UPDATE 11.2.0.4.201020
 

[big]

Thanks Erman.

[raiq1]

Dear Erman sir,

i have applied the last available psu in my production environment today, make sure we have ebs12.1.3 with 11.2.0.4 database.

Followed by the Readme file and applied both PSU & OJVM patch.

Before applied the psu patches, i count the invalid objects and found that it was 9 invalid objects in the database and after  psu patches bef-psu-patch.xlsaft-psu-patch.xls16 invalid objects.

i have utlrp.sql to compile the invalid objects but dont understand why the invalid objects are increased.

i am attaching both invalid objects list, before and after psu patches, kindly check the attachments and advice.

Regards,
Raiq

[ErmanArslansOracleBlog]

Invalid objects differ..
Normally, they should be checked one by one.. I mean you should check the errors they have, the errors preventing them to be compiled..

However, your invalid objects are mainy on FPA*

These may be related with the lack of PFA license.

Check -> FPA Objects Are Invalid After Upgrade to 12.2.x (Doc ID 2689793.1)

Check the symptomps.. I know your are on 12.1.3 , but still this may be related with  the license for FPA and need to enable OLAP.
If the issue is similar, if it is the license and if Project Portfolio has not been implemented, the invalids can be ignored as per doc id:400964.1