Código de erro 610 ao fazer backup do DB2 no TSM

1

Estou tentando fazer backup de um banco de dados DB2 usando o Tivoli Storage Manager (TSM), mas está causando erros.

Agora estou recebendo esta mensagem de erro:

[db2inst1@hostname ~]$ export DSMI_CONFIG=/etc/adsm/dsm.opt
[db2inst1@hostname ~]$ export DSMI_LOG=/home/db2inst1
[db2inst1@hostname ~]$ export DSMI_DIR=/opt/tivoli/tsm/client/api/bin64

[db2inst1@hostname ~]$ db2 BACKUP DB foo ONLINE USE TSM OPTIONS @/etc/adsm/dsm.opt
SQL2033N  An error occurred while accessing TSM during the processing of a
database utility.  TSM reason code: "610".

[db2inst1@hostname ~]$ db2 BACKUP DB foo ONLINE USE TSM
SQL2033N  An error occurred while accessing TSM during the processing of a
database utility.  TSM reason code: "610"

Fazer backup do banco de dados para um arquivo normal funciona.

De acordo com o dsmrc.h, este é o código de erro 610:

#define DSM_RC_NLS_CANT_OPEN_TXT   610 /* error trying to open msg txt file  */

Eu não sei por que seria capaz de encontrar as mensagens txt.

Este é o meu arquivo /etc/adsm/dsm.sys:

* Servername corresponds with value given in dsm.opt
    SERVERname         TSM_SERVER

* Note: if you previously had a windows node, you cannot reuse the
* same node name and must apply for a new one for your linux backups
    NODENAME           foo-db
    TCPServeraddress   some.tsm.server.com
    TCPPort            1500
    QUERYSCHEDPERIOD   3
    COMMmethod         TCPIP

    PASSWORDAccess     Generate
    SCHEDMode          Polling
    SCHEDLOGName       /var/log/tsm/dsmsched.log
    SCHEDLOGRetention  7 D
    ERRORLOGName       /var/log/tsm/dsmerror.log
    ERRORLOGRetention  7 D
    INCLEXCL          /opt/tivoli/tsm/client/ba/bin/inclexcl
    COMPRESSION        No
    ManagedService     schedule

* Space separated list of users requiring TSM access (case sensitive).
    USERS              root db2inst1

* Virtualmountpoints allow you to specifiy a path as a domain to be backed up
* in dsm.opt, without it being on its own filesystem.
* If any of these paths are on their own filesystem remove the entry here.
    VIRTUALMOUNTPoint  /home
    VIRTUALMOUNTPoint  /root
    VIRTUALMOUNTPoint  /etc
    VIRTUALMOUNTPoint  /var/www

Aqui está meu arquivo /etc/adsm/dsm.opt:

  SERVERNAME      TSM_SERVER
  COMPRESSAlways  No
  DATEformat      3
  LANGuage        AMENG

* Add domains (filesystems) eligible for backup.
* If you want to specifiy a domain that isn't on its own filesystem
* you will need to add a virtualmountpoint entry for it in dsm.sys

  DOMAIN "/home"
  DOMAIN "/root"
  DOMAIN "/etc"
  DOMAIN "/var/www"

Veja algumas informações de diagnóstico:

[db2inst1@hostname db2dump]$ db2level
DB21085I  Instance "db2inst1" uses "64" bits and DB2 code release "SQL10010"
with level identifier "0201010E".
Informational tokens are "DB2 v10.1.0.0", "s120211", "LINUXAMD64101", and Fix
Pack "0".
Product is installed at "/opt/ibm/db2/V10.1".

[db2inst1@hostname db2dump]$ db2licm -l
Product name:                     "DB2 Enterprise Server Edition"
License type:                     "CPU Option"
Expiry date:                      "Permanent"
Product identifier:               "db2ese"
Version information:              "10.1"
Enforcement policy:               "Soft Stop"
Features:
DB2 Performance Optimization ESE: "Not licensed"
DB2 Storage Optimization:         "Not licensed"
DB2 Advanced Access Control:      "Not licensed"
DB2 Geodetic Data Management:     "Not licensed"
IBM Homogeneous Replication ESE:  "Not licensed"
DB2 pureCluster:                  "Not licensed"



[db2inst1@hostname db2dump]$ uname -a
Linux hostname 2.6.32-279.2.1.el6.x86_64 #1 SMP Thu Jul 5 21:08:58 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

[db2inst1@hostname db2dump]$ cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.3 (Santiago)

[root@hostname bin64]# ls -la /opt/tivoli/tsm/client/api/bin64
total 165988
drwxr-xr-x 4 root bin       4096 Mar 22 12:41 .
drwxr-xr-x 5 root bin       4096 Mar 22 11:05 ..
drwxr-xr-x 5 root bin       4096 Mar 22 11:05 cit
-r--r--r-- 1 root bin        782 Jan  9 03:46 dsm.opt.smp
-r--r--r-- 1 root bin        971 Jan  9 03:46 dsm.sys.smp
-rwsr-xr-x 1 root bin    7060424 Jan  9 03:46 dsmtca
lrwxrwxrwx 1 root root        16 Mar 22 11:05 EN_US -> ../../lang/EN_US
-r-xr-xr-x 1 root bin    8805328 Jan  9 03:46 libApiTSM64.so
-r-xr-xr-x 1 root bin    1555256 Jan  9 03:46 libcrypto.so.0.9.8
-r-xr-xr-x 1 root bin      36404 Jan  9 03:46 libdmapi.so
-r-xr-xr-x 1 root bin      50183 Jan  9 03:46 libgpfs.so
-r-xr-xr-x 1 root bin     325912 Jan  9 03:46 libssl.so.0.9.8
lrwxrwxrwx 1 root bin         14 Mar 22 11:05 libTsmViSdkAPI.so -> libTsmViSdk.so
-r-xr-xr-x 1 root bin  148796471 Jan  9 03:46 libTsmViSdk.so
lrwxrwxrwx 1 root bin         18 Mar 22 11:05 libVMcrypto.so -> libcrypto.so.0.9.8
lrwxrwxrwx 1 root bin         15 Mar 22 11:05 libVMssl.so -> libssl.so.0.9.8
-r-xr-xr-x 1 root bin    2984648 Jan  9 03:46 libxerces-c1_6_0.so
-r-xr-xr-x 1 root bin     117659 Jan  9 03:46 libxmlutil-6.4.0.0.so
lrwxrwxrwx 1 root root        16 Mar 22 11:05 RU_RU -> ../../lang/RU_RU
drwxr-xr-x 2 root bin       4096 Mar 22 11:05 sample

Alguma idéia de como eu poderia contornar o erro código de razão SQL2033N 610? Todos os recursos online parecem me dizer para apontar o DSMI_DIR para outro lugar, mas não sei para onde apontar. Apontá-lo no diretório EN_US não ajudou.

    
por Leons 22.03.2013 / 17:48

0 respostas

Tags