Requirements for db connect id need to be more specific
The authorization requirements for the connection id specified in the teamserver.properties file need to be documented with more detail. Beyond just being able to create an manipulate tables and perform dbm updates, this id also requires SYSCTRL authorization to be able to create the CONTENTTS tablespace. Basically, I had to grant dbadm on the database to the connection id as well as SYSCTRL group authority to create tablespaces and even monitors. If this auth was NOT granted, the createTables failed (or the routine leaves the user assuming they were not successfully created. This is with DB2 9.1.5.
One answer
I filed task Document required db2 permissions (59464) to track this.
--
Ritchie Schacher
Jazz Server Development
"thloeber" <thloeber> wrote in message
news:g771t7$su2$1@localhost.localdomain...
--
Ritchie Schacher
Jazz Server Development
"thloeber" <thloeber> wrote in message
news:g771t7$su2$1@localhost.localdomain...
The authorization requirements for the connection id specified in the
teamserver.properties file need to be documented with more detail.
Beyond just being able to create an manipulate tables and perform dbm
updates, this id also requires SYSCTRL authorization to be able to
create the CONTENTTS tablespace. Basically, I had to grant dbadm on
the database to the connection id as well as SYSCTRL group authority
to create tablespaces and even monitors. If this auth was NOT
granted, the createTables failed (or the routine leaves the user
assuming they were not successfully created. This is with DB2 9.1.5.