Oracle Security Alerts for July 2019 got published

Tim says:

Hi Mike,

Do you know why AIX downloads were released for .190716 and then retracted <24h later?
19.3.0/19.3.1 deja vu all over again

Specifically:
29699079, 29699097, 29699168 for AIX

Arun Gupta says:

Mike,
I was patching 18.1 DB_HOME with the July 2019 patch and ran into a couple of issues.
a) The datapatch failed to load OJVM files into PDBs which were plugged into the CDBs from non-CDBs. MOS search revealed Doc ID 2488247.1. I applied the easy fix (without unplug/re-plug of PDB) and it worked. ,
b) For some reason, the patching script takes it upon itself to compile every invalid object in the database.

SQL> begin
2 for invalid_object in
3 (select object_id
4 from dba_objects
5 where status = ‘INVALID’
6 order by object_id)
7 loop
8 dbms_utility.validate(invalid_object.object_id);
9 end loop;
10 end;
11 /

Now, if my database has invalid application objects because of any reason whatsoever, the datapatch throws an error:

Validating logfiles…done
Patch 29757256 apply: WITH ERRORS

Although the patch is applied successfully, the DBA_REGISTRY_SQLPATCH keeps showing WITH ERRORS in status. I had to use:

datapatch -verbose -ignorable_errors=ORA-04045,ORA-04052,ORA-02019,ORA-00604,ORA-06512

The list of ignorable_errors has to include every ORA error thrown by every invalid object and only then I get a clean log and SUCCESS in DBA_REGISTRY_SQLPATCH.

Validating logfiles…done
Patch 29757256 apply: SUCCESS

Patching script never used to compile every invalid object, but I guess something has changed.

Thanks,
Arun