WebSphere Commerce Instance Creation Doesn’t Like DB2 9.7 FixPack 5

You may also like...

3 Responses

  1. Sathy Sannasi says:

    Could this be because db2inst1 did not have DATAACESS privilege on the database?

    GRANT DBADM (including the implicit grant for the db creator) by default provides DATAACCESS privileges. That’s how it was till Fixpak 4 atleast.
    If the default has changed in FP5, it is either a bug or an undocumented change.

    Of course, I do not find a document supporting my theory 😉

    Thanks

    • Ember Crooks says:

      That’s the other workaround, I suppose, to just grant dbadm and and secadm to db2inst1. But if the database is created by the proper user, we wouldn’t have to do that. We didn’t have to in FixPack 3 and before, and we didn’t have to when we did the workaround of doing instance creation on DB2 9.7 FixPack 4 instead of DB2 9.7 FixPack 5. You’d also have to revoke permissions from whatever id you’re using to run the Commerce Instance creation.

  1. December 13, 2016

    […] WebSphere Commerce Instance Creation Doesn’t Like DB2 9.7 FixPack 5 […]

Leave a Reply

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