Db2 Basics: Using FTPS to get a Fixpack Directly to a Db2 Server

You may also like...

6 Responses

  1. Larry Sokoloski says:

    Hi Ember, I just noticed the FTPS option yesterday while downloading a CDC fixpack, but I never tried it before. I think I will next time – thanks!

  2. Erwin Hattingh says:

    Is there a real use case for this ? Not likely any Db2 server can download directly from the internet , definitely not ftp/ftps ?
    Moreover, even then: Download binaries only ONCE, from any supplier, to internal distribution vault. Then quality control and testing (distribute that one image to test / development / acceptance / production)
    I have seen IBM publishing the exact same fixpack (name on website and zip/tar filename after downloading) that was NOT the same build … One reason I never download a fixpack the first week(s) after it is published …

    • Ember Crooks says:

      Many Db2 servers do actually allow downloads directly from the internet. Even if it’s not to the Db2 server, though, this method can be useful for getting the fix pack to a jump server or other server that is on the same network as the Db2 server. Agreed that an internal location for code is a better solution. And a good point on not downloading a fix pack the first week. I, too, always wait a week after a fix pack before starting to use it.

  3. Philip Nelson says:

    Ember,

    Thanks for the info. For years I’ve always downloaded fixpacks using wget (as per your older post) and this has always worked flawlessly for me. I find that HTTP(S) tends to be more often available in corporate sites than FTP(S). You just have to use the URL you capture within a reasonable timeframe (it expires fairly quickly).

    Just one more comment. I’d always take the Server, rather than Universal, Fixpack. This is because the Server Fixpack is a full install image (apart from the license key) and can be used to lay down a fresh installation of Db2. I always lay down the new fixpack beside the original install and then use db2iupdt to switch the instance over to the new code level. You can also use db2iupdt with the “-f ” option (or the deprecated “-D” option) to move back down again if you find any issues. Only when I know I’m not wanting to fall back do I then remove the old code install. I find separating out the code install from the instance migration in this way takes a lot of pressure off during fixpack applications. You just have to remember to reapply the license key after the upgrade.

  4. Erwin Hattingh says:

    I agree with Phil: I also always take the “Server”, not the “Universal” Fixpack (and usually also ‘lay down the new fixpack beside the original install’, as fallback if there are issues)

Leave a Reply

Your email address will not be published. Required fields are marked *