Oct 29

Tivoli Storage Manager DB2 ODBC user ID configuration

DB2, SQL, TSM Server 6 Comments Off on Tivoli Storage Manager DB2 ODBC user ID configuration

Problem(Abstract)

To access the Tivoli Storage Manager DB2 instance via an ODBC connection, a user ID must have the necessary permissions.

Resolving the problem

The user ID and password that is configured for ODBC access must be a valid UNIX user that has authority to the Tivoli Storage Manager database. For example, you can use the Tivoli Storage Manager server instance user ID and password. The user ID does not need to be part of a special UNIX group but it must have authority to the DB2 database. The user must also be allowed to log on.

You can grant authority to a separate user ID, other than the Tivoli Storage Manager server instance user ID, to access the database for ODBC query. This document provides two examples to grant authority to the user ID named db2odbc.
Example 1 :
To give the db2odbc user ID access to all tables for the Tivoli Storage Manager database, log on with the Tivoli Storage Manager server instance user ID and run the following DB2 commands:

  1. db2 connect to TSMDB1
  2. db2 grant DATAACCESS, CONNECT on database to db2odbc
  3. db2 grant usage on workload SYSDEFAULTUSERWORKLOAD to user db2odbc
  4. db2 grant execute on package nullid.syssh200 to public

This series of commands grants less authority to the db2odbc user ID than what the Tivoli Storage Manager server instance user ID has. To grant even less authority, use example 2, which gives the user ID only select authority.
Example 2 :
To give the db2odbc user ID select authority only to a specific table, log on with the Tivoli Storage Manager server instance user ID and run the following DB2 commands:

  1. db2 connect to TSMDB1
  2. db2 grant CONNECT on database to db2odbc
  3. db2 grant usage on workload SYSDEFAULTUSERWORKLOAD to user db2odbc
  4. db2 grant execute on package nullid.syssh200 to public
  5. db2 grant select on syscat.tables to user db2odbc
  6. db2 grant select on TSMDB1.BACKUP_OBJECTS to user db2odbc

In this example, the db2odbc user ID is granted authority to run select statements only against the BACKUP_OBJECTS table. For each table for which you want the db2odbc user ID to have select authority, repeat the grant select command with that table name.
To view the available Tivoli Storage Manager tables, run the following command: db2 connect to TSMDB1 db2 "select tabname from syscat.tables where tabschema='TSMDB1' and tabname not like '%(TEMP)'"
Example 3 :
To grant the db2odbc user ID select authority to all tables of a Tivoli Storage Manager running on AIX, log on with the Tivoli Storage Manager server instance user ID and run the following DB2 commands:

  1. db2 connect to TSMDB1
  2. db2 grant CONNECT on database to db2odbc
  3. db2 grant usage on workload SYSDEFAULTUSERWORKLOAD to user db2odbc
  4. db2 grant execute on package nullid.syssh200 to public
  5. db2 grant select on syscat.tables to user db2odbc
  6. for tablename in $(db2 -x "select tabname from syscat.tables where tabschema='TSMDB1' and tabname not like '%(TEMP)'") ; do db2 grant select on TSMDB1.${tablename} to user db2odbc ; done

Example 4 :
To grant the db2odbc user ID select authority to all tables of a Tivoli Storage Manager running on Windows, logon with the Windows account that runs the Tivoli Storage Manager server instance. Open a windows command prompt and enter “db2cmd”. This will open a new Windows command prompt. From the new command prompt, run the following db2 commands :

  1. db2 connect to TSMDB1
  2. db2 grant CONNECT on database to db2odbc
  3. db2 grant usage on workload SYSDEFAULTUSERWORKLOAD to user db2odbc
  4. db2 grant execute on package nullid.syssh200 to public
  5. db2 grant select on syscat.tables to user db2odbc
  6. db2 -x "select tabname from syscat.tables where tabschema='TSMDB1' and tabname not like '%(TEMP)'" > c:\temp\tsmtb.list
  7. for /F %N in (c:\temp\tsmtb.list) do db2 grant select on TSMDB1.%N to user db2odbc

In step 6, a file name, c:\temp\tsmtb.list, is used to write the output of the command. You can select any appropriate file to write this output into. This same file name must then be specified in step 7.

written by Bosse

Dec 27

FBSS7523E & FBSS7519E repository has dirty bit

Server Comments Off on FBSS7523E & FBSS7519E repository has dirty bit

(Abstract)

The Repository has a Sanity Problem.

Symptom

Fastback Server is in limited mode and there is error on the repository.

Cause

The repository filesystem may be corrupt.

Diagnosing the problem

The clog010.sf may contain the following errors:

FBSS7523E The Repository in path <volume> has a Dirty BIT problem (Run chkdsk as described in the user manual). FBSS7519E The repository sanity check ended.The Repository has a Sanity Problem.

Resolving the problem

To resolve the issue, follow the steps below:

1) Run CHKNTFS on the volume and check what it returns (volume dirty or not dirty) CHKNTFS <volume> Example: CHKNTFS H:
If the message returned indicates that the disk has any dirty bits, this means that Microsoft defines the disk as bad.
2) Next, stop the FastBack Server service 3) Run CHKDSK /F <volume> Example: CHKDSK /F H: 4) Run CHKNTFS again on the volume 5) If there is no dirty bits found (they have all been corrected), start the FastBack Server service. If any dirty bits still remain, it is a disk issue, not a Fastback issue.
After running the CHKDSK and CHKNTFS, check the Windows Event Viewer -> System; verify if there are any problems or other messages regarding the disk. Also, check if anti virus software is running. If yes, verify that the FastBack server directory is in the Exclusion list (as it should be).

written by Bosse

Jul 16

IC65242: DOMINO SERVER MAY NOT RESTART AFTER A FASTBACK BACKUP

Domino, Fatsback, Info Comments Off on IC65242: DOMINO SERVER MAY NOT RESTART AFTER A FASTBACK BACKUP

Error description

  • When backing up a Domino Database using one of the scripts
    provided with the SW, FastBack will wait for the Domino server
    to notify it that the database is stopped.
    In some cases, a delay between the time when the Domino server
    has stopped and the actual change of the data base to a stopped
    state can cause the system to try and restart the Domino
    database prematurely and eventually a failure to restart the
    Domino server will occur.

     

  • Local fix

  • Use updated scripts

     

  • Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users that backup Domino with Fastback *
    * Client *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available (Use *
    * updated scripts). This problem is *
    * currently projected to be fixed in level *
    * 5.5.7 and 6.11. Note that this is subject *
    * to change at the discretion of IBM *
    ****************************************************************
    *

     

  • Problem conclusion

  • Background: When backing up a Domino Database using one of the
    scripts provided with the SW, FastBack will wait for the
    Domino server to notify it that the database is stopped. In
    some cases, a delay between the time when the Domino server
    has stopped and the actual change of the data base to a
    stopped state can cause the system to try and restart the
    Domino database prematurely and eventually a failure to
    restart the Domino server will occur.Fix: The scripts that are responsible for domino server
    restart modified to fix the problem. 

  • Temporary fix

  • Use updated scripts.
    The scripts can be download from
    http://www-01.ibm.com/support/docview.wss?&uid=swg21417993

     

  • written by Bosse

    Jul 16

    IC68650: FASTBACK SERVER MAY REPORT ABORTED SNAPSHOT WHEN THERE IS NOTHING TO CLEAN-UP

    Client, Server Comments Off on IC68650: FASTBACK SERVER MAY REPORT ABORTED SNAPSHOT WHEN THERE IS NOTHING TO CLEAN-UP

    Error description

  • FastBack may sent out a snapshot abort using the external
    notification email for consolidated (cleanup) snapshot although
    there was nothing to cleanup.
    
    In Logs
    
    1 .C:Documents and Settings\All Users\Application
    Data\Tivoli\TSM\FastBack\server\events - EventJobX -
    
    2010/05/07 19:36:42 FBSS7037E  Procedure aborted
    2010/05/07 19:36:42 FBSS1031I  **Consolidated**
    2010/05/07 19:36:42 FBSS1041I  Procedure initiated.
    
    2. C:Documents and Settings\All Users\Application
    Data\Tivoli\TSM\FastBack\server\ - Server logs -
    
    DM_CLEANUP_BuildCleanUpMAP: Nothing to do, No change since last
    cleanup
    DM_CLEANUP_Dispatch: DM_CLEANUP_BuildCleanUpMAP (job [5])
    required abort of job
    JOB_S_AddEvent: [5] 2010/05/07 15:02:42 FBSS1031I
    **Consolidated**

     

  • Local fix

  •  Ignore the failure messages

     

  • Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Fastback Users Running Snapshot Cleanup. *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in level 6.1.1 and 5.5.7. Note that this     *
    *                 is subject to change at the discretion of    *
    *                 IBM.                                         *
    ****************************************************************
  • written by Bosse