IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > Upgrade from IBM Tivoli Monitoring V6.1 or V6.2 > Linux and UNIX: Upgrading a portal server running as a non-root process

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Step 1: Verify the DB2 Database for Linux, UNIX, and Windows authorizations


Before you begin

Both Linux and AIX sites must complete this step.


About this task

In the following example the portal server database is called TEPS, the DB2 for Linux, UNIX, and Windows userid is itmuser, and the DB2 administrative userid is db2inst1.


Procedure

  1. Log in as the DB2 administrator: 

      su - db2inst1

  2. Connect to the portal server database using the portal server's DB2 userid: 

      db2 connect to TEPS user itmuser using TEPSpw

    where TEPSpw is the password for userid itmuser.

  3. Get the authorizations for the portal server's DB2 userid: 

      db2 get authorizations

    Example output: 

       Administrative Authorizations for Current User

 Direct SYSADM authority                    = NO
 Direct SYSCTRL authority                   = NO
 Direct SYSMAINT authority                  = NO
 Direct DBADM authority                     = NO
 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                  = NO
 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

  4. Ensure the settings listed below are set to YES, as shown. 

       Direct DBADM authority                     = YES
 Direct CREATETAB authority                 = YES
 Direct BINDADD authority                   = YES
 Direct CONNECT authority                   = YES
 Direct CREATE_NOT_FENC authority           = YES
 Direct IMPLICIT_SCHEMA authority           = YES
 Direct LOAD authority                      = YES
 Direct QUIESCE_CONNECT authority           = YES
 Direct CREATE_EXTERNAL_ROUTINE authority   = YES

    If they are all set to YES, you are finished. Otherwise continue with steps 5 through 7

  5. Connect to the Tivoli Enterprise Portal Server database as the DB2 administrator: 

      db2 connect to TEPS user db2inst1 using db2pw

    where db2pw is the password for userid db2inst1.

  6. Grant the appropriate authorizations to the portal server's DB2 userid: 

      db2 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,     CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON DATABASE to user itmuser

  7. Reconnect to the portal server database using the portal server's DB2 userid, and recheck its authorizations: 

      db2 connect to TEPS user itmuser using TEPSpw
 Database Connection Information

 Database server        = DB2/LINUX 8.2.8
 SQL authorization ID   = ITMUSER
 Local database alias   = TEPS

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                 = YES
 Direct BINDADD authority                   = YES
 Direct CONNECT authority                   = YES
 Direct CREATE_NOT_FENC authority           = YES
 Direct IMPLICIT_SCHEMA authority           = YES
 Direct LOAD authority                      = YES
 Direct QUIESCE_CONNECT authority           = YES
 Direct CREATE_EXTERNAL_ROUTINE authority   = YES
 Direct SYSMON authority                    = NO

 Indirect SYSADM authority                  = NO
 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

    You should now see the authorizations for the following items set to YES: 

       Direct DBADM authority                     = YES
 Direct CREATETAB authority                 = YES
 Direct BINDADD authority                   = YES
 Direct CONNECT authority                   = YES
 Direct CREATE_NOT_FENC authority           = YES
 Direct IMPLICIT_SCHEMA authority           = YES
 Direct LOAD authority                      = YES
 Direct QUIESCE_CONNECT authority           = YES
 Direct CREATE_EXTERNAL_ROUTINE authority   = YES


Parent topic:

Linux and UNIX: Upgrading a portal server running as a non-root process

+

Search Tips   |   Advanced Search