Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2010
    Location
    Singapore
    Posts
    197

    Red face Unanswered: Unable to grant SYSMON Authority

    Hi, I wanted to grant a user to SYSMON Authority,

    So i have added the group which user belongs to the SYSMON group

    [db2inst1@WESSSTDW01 ~]$ db2 get dbm cfg |grep SYS
    SYSADM group name (SYSADM_GROUP) = DB2IADM1
    SYSCTRL group name (SYSCTRL_GROUP) =
    SYSMAINT group name (SYSMAINT_GROUP) =
    SYSMON group name (SYSMON_GROUP) = NAGIOS
    Priority of agents (AGENTPRI) = SYSTEM
    [db2inst1@WESSSTDW01 ~]$

    Then refreshed the instance (stop/start)

    when i try to execute a command to assign permission to that user, i ended in this error

    [db2inst1@WESSSTDW01 ~]$ db2 grant select,update on table SYSTOOLS.POLICY to NAGIOS
    DB21034E The command was processed as an SQL statement because it was not a
    valid Command Line Processor command. During SQL processing it returned:
    SQL0569N Authorization ID "NAGIOS" does not uniquely identify a user, a group
    or a role in the system. SQLSTATE=56092
    [db2inst1@WESSSTDW01 ~]$


    when i can check for authorizations i see

    [db2inst1@WESSSTDW01 ~]$ db2 get authorizations

    Administrative Authorizations for Current User

    Direct SYSADM authority = NO
    Direct SYSCTRL authority = NO
    Direct SYSMAINT authority = NO
    Direct DBADM authority = YES
    Direct CREATETAB authority = NO
    Direct BINDADD authority = NO
    Direct CONNECT authority = NO
    Direct CREATE_NOT_FENC authority = NO
    Direct IMPLICIT_SCHEMA authority = NO
    Direct LOAD authority = NO
    Direct QUIESCE_CONNECT authority = NO
    Direct CREATE_EXTERNAL_ROUTINE authority = NO
    Direct SYSMON authority = NO

    Indirect SYSADM authority = YES
    Indirect SYSCTRL authority = NO
    Indirect SYSMAINT authority = NO
    Indirect DBADM authority = NO
    Indirect CREATETAB authority = YES
    Indirect BINDADD authority = YES
    Indirect CONNECT authority = YES
    Indirect CREATE_NOT_FENC authority = NO
    Indirect IMPLICIT_SCHEMA authority = YES
    Indirect LOAD authority = NO
    Indirect QUIESCE_CONNECT authority = NO
    Indirect CREATE_EXTERNAL_ROUTINE authority = NO
    Indirect SYSMON authority = NO

    [db2inst1@WESSSTDW01 ~]$


    I see direct/indirect SYSMON authority is NO, Is that the reason i am unable to assign that group to SYSMON,

    Pl. suggest

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    The entry for SYSMON_GROUP, etc in dbm cfg must be groups, not user accounts. The group and user account in that group must be defined to the operating system.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    If you have both user and group named nagios , you can use

    Code:
    db2 grant select,update on table SYSTOOLS.POLICY to user NAGIOS
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  4. #4
    Join Date
    Aug 2010
    Location
    Singapore
    Posts
    197
    Marcus,

    both my user and group are same NAGIOS

    Sathya,
    Thanks it worked,

    This will confirm that the user/group is assigned SYSMON Authority.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •