Db2 authorizations for plans, packages, and collections
The High-speed Apply Engine creates plans, packages, and collections. Depending on the privileges that you are willing to grant to the user ID that runs High-speed Apply Engine, you can grant the Db2 authorizations and privileges for these activities using one of the methods described in this section.
The following table defines the variables that appear in all of the GRANT examples in this section.
Variable name | Description |
---|---|
aptPlan | Name of High-speed Apply Engine plan that is specified during installation For more information, see PlanName-parameter. |
collectionIDs | Names of collections to which High-speed Apply Engine dynamically binds packages during processing This name can be:
For more information, see CollectionID. |
databaseName | Target database being changed by the apply request |
tableNames | Target tables being changed by the apply request |
userid01 | Authorization ID of the user running the apply request You can specify PUBLIC or a specific authorization ID. For more information, see AuthID. |
userid02 | Authorization ID (different than userid01) with authority to bind plans, bind packages, and administer collections This authorization ID can be a secondary authorization ID. The privileges that are granted to this authorization ID vary, depending on how you enable High-speed Apply Engine bind processing. For more information, see AuthID. |
userPlan01 | Name of a pre-bound plan that is bound by using special bind options (optional, when BindAction parameter is Use) For more information, see PlanName. |
This section contains the following topics: