![]() You can't revoke a privilege on an object from a user, if this user hasn't been granted this permission explicitly (you get SQL0556N on such a revoke statement). DB2 stores permissions on objects, not restrictions. You can enable the 'TIMESTAMP' monitoring switch by the following commands: update dbm cfg using dftmontimestamp on Privileges grant select on SYSIBMADM. User in DB2 can have privileges granted via user's groups and roles as well. db2instx) for connecting to the database, or if you can su/sudo to the instance-owner on the Db2-server, then that instance owner account can grant other users the dbadm (and some other) database rights, and the user with SECADM role can grant additional permissions. Best practice is to keep the version of the jdbc driver the same between the WAS and the Db2-server, so keep those versions maintained. For complete Database Visibility functionality, the following monitoring switches of the DB2 server need to be enabled: 'TIMESTAMP'. If you know the password for the instance-owner (e.g. Best advice is to deploy the current most recent fixpack to the Db2-server, so get your DBA to do this first on your development/test environments before deploying to production.Īdditionally consider ensuring to maintain the Db2 jdbc driver version on your WAS server, instead of continuing to use the (usually old version) that comes with WAS. Your question mentions v11.1.0.0 (this is fixpack 0 of Version 11.1 ). ![]() There are always too many silly bugs that have long since been fixed by subseqent cumulative fixpacks. DB2 10.5 LUW I was thinking along the lines of: db2 'revoke all on database from user IN (select grantee from syscat. These files should have root as owner and must have permission -r-s-x-xĬhange the permission of the files to -r-s-x-xĪpart from the above, it is always unwise to use any "fixpack 0" of any Db2 product to production environments on linux/unix/windows. IBM DB2 Connect 10.5 DB2 Connect Installing and Configuring DB2 Connect Servers SC27-5517-00 IBM DB2 Connect 10.5 DB2 Connect Installing and Configuring DB2 Connect Servers SC27-5517-00 Note Before using this information and the product it supports, read the general information under Appendix B, Notices, on page 107. This is caused by incorrect permissions and ownership of the following security files in ~/sqllib/security directory The advice given there, in case of broken links, is: Cause The sqlode -1639 is caused by incorrect permissions on files on the Db2-server.
0 Comments
Leave a Reply. |