Very smart people within IBM have confirmed this is NOT a database problem, never was. So if you have DB 16 and are running you are NOT sitting on a powder keg. You are good.

The issue is in fact an install issue. If you were 'current enough' when you installed DB group 16 you were good. If you were 'far enough back' then you were not good. Very much a binary situation.

If you got it, great. If you do not, then get DB Group 17 instead and install that.

And just a reminder to check the CUME if you are installing that as well because the third disk on that set might contain DB group 16. You can find that by looking in the image catalog at that disk. Look into the README directory at the file ORDLIST.TXT and look for PTF SF99703. If it says "Group 16" then delete that disk from the image catalog.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/2/2019 9:56 AM, Andrew Lopez (SXS US) wrote:
FYI This one is bad. Can actually require re-installing the O/S!!

We somehow dodged the bullet here. We're on Level 17 (installed yesterday), but Level 16 shows as having been installed as well. Does anyone know what would cause some servers to not have a problem, and others to experience this?

More details on the issue can be found at https://www.itjungle.com/2019/12/02/db2-for-ibm-i-7-3-hits-a-bad-patch/, but it doesn't get into the details of why some systems can run Level 16 without a problem.


_____________________________________________________________________
Spirax-Sarco Engineering Plc. This e-mail has been scanned for viruses by Cisco Cloud Email Security.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.