When we clone tablespaces from a production to a test Db2 system we would like to suppress all authorizations on the target objects (e.g. tables, views), because users don't possess the same privileges in these two environments. At this time cloning tool generates and executes the grant statements, which leads to wrong privileges in the target Db2 system.
|Who would benefit from this IDEA?||Cloning tool customers doing tablespace clones into different environments.|
How should it work?
We would like a new parameter (for example: SUPPRESS-GRANTS( Y | N )) on the PROCESS-DDL command to suppress the grants in the target db2 system, when we run the source job.
Today we need to revoke all privileges manual after the cloning process.
|Priority Justification||Make the tool more efficient and agil|
|Customer Name||Martin Oberholzer, Zuercher Kantonalbank|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions