Results 1 to 12 of 12
  1. #1
    Join Date
    Aug 2016
    Posts
    19

    Unanswered: db2adutl cross node - on restore client db2adult show not all backupimages

    Hello,

    we have to systems. One production and one test system.
    We enabled cross node recovery to restore a prod database in the test environment.
    This was successfully.
    But now with the db2adult command we only see the prod backup images to 01.12.2016.
    We can't see newer images, but when we run the db2adult command on the prod server we can see all images.
    We haven't changed anything at the configuration.

    Can anyone help us and tell use why we cannot see newer images of the prod database at the test environment?

    Thanks.

  2. #2
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Not enough detail in your post.

    On Test, are you correctly switching between two dsm.opt files, one for Prod other for Test , or are you using alternative-command lines to specify what you want?

    Post the full command-line from test of the db2adutl query full db.... when querying cross-node for production, and the relevant entries that result in the TSM-client error log file and db2diag on test.

  3. #3
    Join Date
    Aug 2016
    Posts
    19
    DB2adult from the Testmachine:

    Query for database APPL


    Retrieving FULL DATABASE BACKUP information.
    1 Time: 20161201210002 Oldest log: S0830799.LOG DB Partition Number: 0 Sessions: 2
    2 Time: 20161130210002 Oldest log: S0830643.LOG DB Partition Number: 0 Sessions: 2
    3 Time: 20161129210003 Oldest log: S0830476.LOG DB Partition Number: 0 Sessions: 2
    4 Time: 20161128210003 Oldest log: S0830306.LOG DB Partition Number: 0 Sessions: 2
    5 Time: 20161127210002 Oldest log: S0830027.LOG DB Partition Number: 0 Sessions: 2
    6 Time: 20161126210002 Oldest log: S0829801.LOG DB Partition Number: 0 Sessions: 2
    7 Time: 20161125210002 Oldest log: S0829558.LOG DB Partition Number: 0 Sessions: 2
    8 Time: 20161124210002 Oldest log: S0829280.LOG DB Partition Number: 0 Sessions: 2


    Retrieving INCREMENTAL DATABASE BACKUP information.
    No INCREMENTAL DATABASE BACKUP images found for APPL


    Retrieving DELTA DATABASE BACKUP information.
    No DELTA DATABASE BACKUP images found for APPL


    DB2adult from the Prodmachine:

    Retrieving FULL DATABASE BACKUP information.
    1 Time: 20161228210003 Oldest log: S0835251.LOG DB Partition Number: 0 Sessions: 2
    2 Time: 20161227210002 Oldest log: S0835093.LOG DB Partition Number: 0 Sessions: 2
    3 Time: 20161226210002 Oldest log: S0834920.LOG DB Partition Number: 0 Sessions: 2
    4 Time: 20161225210003 Oldest log: S0834808.LOG DB Partition Number: 0 Sessions: 2
    5 Time: 20161224210003 Oldest log: S0834716.LOG DB Partition Number: 0 Sessions: 2
    6 Time: 20161223210002 Oldest log: S0834603.LOG DB Partition Number: 0 Sessions: 2
    7 Time: 20161222210003 Oldest log: S0834464.LOG DB Partition Number: 0 Sessions: 2
    8 Time: 20161221210002 Oldest log: S0834337.LOG DB Partition Number: 0 Sessions: 2
    9 Time: 20161220210002 Oldest log: S0834199.LOG DB Partition Number: 0 Sessions: 2
    10 Time: 20161219210002 Oldest log: S0834029.LOG DB Partition Number: 0 Sessions: 2
    11 Time: 20161218210003 Oldest log: S0833783.LOG DB Partition Number: 0 Sessions: 2
    12 Time: 20161217210002 Oldest log: S0833691.LOG DB Partition Number: 0 Sessions: 2
    13 Time: 20161216210003 Oldest log: S0833510.LOG DB Partition Number: 0 Sessions: 2
    14 Time: 20161215210003 Oldest log: S0833243.LOG DB Partition Number: 0 Sessions: 2
    15 Time: 20161214210002 Oldest log: S0832995.LOG DB Partition Number: 0 Sessions: 2
    16 Time: 20161213210003 Oldest log: S0832778.LOG DB Partition Number: 0 Sessions: 2
    17 Time: 20161212210002 Oldest log: S0832553.LOG DB Partition Number: 0 Sessions: 2
    18 Time: 20161211210002 Oldest log: S0832289.LOG DB Partition Number: 0 Sessions: 2
    19 Time: 20161209210002 Oldest log: S0832058.LOG DB Partition Number: 0 Sessions: 2
    20 Time: 20161208210002 Oldest log: S0831863.LOG DB Partition Number: 0 Sessions: 2
    21 Time: 20161207210003 Oldest log: S0831664.LOG DB Partition Number: 0 Sessions: 2
    22 Time: 20161206210003 Oldest log: S0831488.LOG DB Partition Number: 0 Sessions: 2
    23 Time: 20161205210002 Oldest log: S0831315.LOG DB Partition Number: 0 Sessions: 2
    24 Time: 20161204210003 Oldest log: S0831141.LOG DB Partition Number: 0 Sessions: 2
    25 Time: 20161203210002 Oldest log: S0831061.LOG DB Partition Number: 0 Sessions: 2
    26 Time: 20161202210003 Oldest log: S0830939.LOG DB Partition Number: 0 Sessions: 2
    27 Time: 20161201210002 Oldest log: S0830799.LOG DB Partition Number: 0 Sessions: 2
    28 Time: 20161130210002 Oldest log: S0830643.LOG DB Partition Number: 0 Sessions: 2
    29 Time: 20161129210003 Oldest log: S0830476.LOG DB Partition Number: 0 Sessions: 2
    30 Time: 20161128210003 Oldest log: S0830306.LOG DB Partition Number: 0 Sessions: 2
    31 Time: 20161127210002 Oldest log: S0830027.LOG DB Partition Number: 0 Sessions: 2
    32 Time: 20161126210002 Oldest log: S0829801.LOG DB Partition Number: 0 Sessions: 2
    33 Time: 20161125210002 Oldest log: S0829558.LOG DB Partition Number: 0 Sessions: 2
    34 Time: 20161124210002 Oldest log: S0829280.LOG DB Partition Number: 0 Sessions: 2


    TSM Client Log:

    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE '*:\Users\...\AppData\Local\Temp\...\*'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE '*:\...\dsmsched.log'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE '*:\...\*.zzzzz'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.3gp'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.3g2'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.ace'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.arc'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.ark'' received from the TSM server client options set.
    12/29/2016 15:42:33 ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.
    12/29/2016 15:42:33 ANS2038W Invalid option 'EXCLUDE.COMPRESSION '*:\...\*.arj'' received from the TSM server client options set.




    Diaglog:



    PID : 15582 TID : 140025962424064PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : DBPEPTST
    APPHDL : 0-26 APPID: *LOCAL.DB2.161221081614
    AUTHID : APPPEPV
    EDUID : 83 EDUNAME: db2stmm (DBPEPTST)
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
    MESSAGE : Unable to find donor to satisfy minSize constraint

    2016-12-29-15.36.18.703598+060 I280840487E491 LEVEL: Warning
    PID : 15582 TID : 140025962424064PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : DBPEPTST
    APPHDL : 0-26 APPID: *LOCAL.DB2.161221081614
    AUTHID : APPPEPV
    EDUID : 83 EDUNAME: db2stmm (DBPEPTST)
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
    MESSAGE : Unable to find donor to satisfy minSize constraint

    2016-12-29-15.39.18.732523+060 I280840979E491 LEVEL: Warning
    PID : 15582 TID : 140025962424064PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : DBPEPTST
    APPHDL : 0-26 APPID: *LOCAL.DB2.161221081614
    AUTHID : APPPEPV
    EDUID : 83 EDUNAME: db2stmm (DBPEPTST)
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
    MESSAGE : Unable to find donor to satisfy minSize constraint

    2016-12-29-15.42.18.761509+060 I280841471E491 LEVEL: Warning
    PID : 15582 TID : 140025962424064PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : DBPEPTST
    APPHDL : 0-26 APPID: *LOCAL.DB2.161221081614
    AUTHID : APPPEPV
    EDUID : 83 EDUNAME: db2stmm (DBPEPTST)
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
    MESSAGE : Unable to find donor to satisfy minSize constraint

    2016-12-29-15.45.18.790583+060 I280841963E491 LEVEL: Warning
    PID : 15582 TID : 140025962424064PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : DBPEPTST
    APPHDL : 0-26 APPID: *LOCAL.DB2.161221081614
    AUTHID : APPPEPV
    EDUID : 83 EDUNAME: db2stmm (DBPEPTST)
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
    MESSAGE : Unable to find donor to satisfy minSize constraint



    In the diaglog i couldn't find errors about the tsm problems that we are facing.

  4. #4
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    please answer the questions correctly in full.

    On Test, are you correctly switching between two dsm.opt files, one for Prod other for Test , or are you using alternative-command lines to specify what you want?

    Post the full command-line from test... (you showed only the output, not the *command-lines* )

    Is the db-name APPL identical on test and prod ?

  5. #5
    Join Date
    Aug 2016
    Posts
    19
    Hello,

    the dsm.opt is located here:
    /opt/tivoli/tsm/client/api/bin64/dsm_db2.opt
    and there is a second one "dsm.opt.smp" there.

    The Servername is Server1.
    Test and Prod are using these server.

    Here is the output with command line (sv-126 is the prod node):
    db2adutl query full db appl nodename SV-126 owner db2inst1
    --- ERROR! Database not found in system directory! ---

    Query for database APPL


    Retrieving FULL DATABASE BACKUP information.
    1 Time: 20161201210002 Oldest log: S0830799.LOG DB Partition Number: 0 Sessions: 2
    2 Time: 20161130210002 Oldest log: S0830643.LOG DB Partition Number: 0 Sessions: 2
    3 Time: 20161129210003 Oldest log: S0830476.LOG DB Partition Number: 0 Sessions: 2
    4 Time: 20161128210003 Oldest log: S0830306.LOG DB Partition Number: 0 Sessions: 2
    5 Time: 20161127210002 Oldest log: S0830027.LOG DB Partition Number: 0 Sessions: 2
    6 Time: 20161126210002 Oldest log: S0829801.LOG DB Partition Number: 0 Sessions: 2
    7 Time: 20161125210002 Oldest log: S0829558.LOG DB Partition Number: 0 Sessions: 2
    8 Time: 20161124210002 Oldest log: S0829280.LOG DB Partition Number: 0 Sessions: 2
    9 Time: 20161123210002 Oldest log: S0829020.LOG DB Partition Number: 0 Sessions: 2
    10 Time: 20161122210002 Oldest log: S0828770.LOG DB Partition Number: 0 Sessions: 2
    11 Time: 20161121210002 Oldest log: S0828508.LOG DB Partition Number: 0 Sessions: 2
    12 Time: 20161120210002 Oldest log: S0828214.LOG DB Partition Number: 0 Sessions: 2


    Retrieving INCREMENTAL DATABASE BACKUP information.
    No INCREMENTAL DATABASE BACKUP images found for APPL


    Retrieving DELTA DATABASE BACKUP information.
    No DELTA DATABASE BACKUP images found for APPL


    And no, on test database called DBPEPTST and on prod APPL.
    Before restoring we drop the DBPEPTST and then we are restroring it as DBPEPTST.


    On Prod we are executing only following command:

    [db2inst1@sv-126 ~]$ db2adutl query

    Query for database APPL


    Retrieving FULL DATABASE BACKUP information.
    1 Time: 20161228210003 Oldest log: S0835251.LOG DB Partition Number: 0 Sessions: 2
    2 Time: 20161227210002 Oldest log: S0835093.LOG DB Partition Number: 0 Sessions: 2
    3 Time: 20161226210002 Oldest log: S0834920.LOG DB Partition Number: 0 Sessions: 2
    4 Time: 20161225210003 Oldest log: S0834808.LOG DB Partition Number: 0 Sessions: 2
    5 Time: 20161224210003 Oldest log: S0834716.LOG DB Partition Number: 0 Sessions: 2
    6 Time: 20161223210002 Oldest log: S0834603.LOG DB Partition Number: 0 Sessions: 2
    7 Time: 20161222210003 Oldest log: S0834464.LOG DB Partition Number: 0 Sessions: 2
    8 Time: 20161221210002 Oldest log: S0834337.LOG DB Partition Number: 0 Sessions: 2
    9 Time: 20161220210002 Oldest log: S0834199.LOG DB Partition Number: 0 Sessions: 2
    10 Time: 20161219210002 Oldest log: S0834029.LOG DB Partition Number: 0 Sessions: 2
    11 Time: 20161218210003 Oldest log: S0833783.LOG DB Partition Number: 0 Sessions: 2
    12 Time: 20161217210002 Oldest log: S0833691.LOG DB Partition Number: 0 Sessions: 2
    13 Time: 20161216210003 Oldest log: S0833510.LOG DB Partition Number: 0 Sessions: 2
    14 Time: 20161215210003 Oldest log: S0833243.LOG DB Partition Number: 0 Sessions: 2
    15 Time: 20161214210002 Oldest log: S0832995.LOG DB Partition Number: 0 Sessions: 2
    ...
    ...
    ...

    Quote Originally Posted by db2mor View Post
    please answer the questions correctly in full.

    On Test, are you correctly switching between two dsm.opt files, one for Prod other for Test , or are you using alternative-command lines to specify what you want?

    Post the full command-line from test... (you showed only the output, not the *command-lines* )

    Is the db-name APPL identical on test and prod ?

  6. #6
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    On the test environment, for the db2adutl query full db command-line, try using the additional -options "fromnode=SV-126 -fromowner=db2inst1" and
    use the same values used for the fromnode and fromowner as used during the successful cross-node restore from prod .

    Also on the Prod enviornment ensure that the TEST DB2-instance-owner has access to all of the TSM-objects of PROD (use db2adutl queryaccess on prod to verify).

    The behaviour suggests that the tsm-node name (nodename) is not correct when referenced from the tsm-client, or is unknown (double check your tsm-client dsm.sys on test).
    Last edited by db2mor; 12-29-16 at 14:16.

  7. #7
    Join Date
    Aug 2016
    Posts
    19
    When I try with the "fromnode=SV-126 -fromowner=db2inst1" clauses at the db2adutl command, i get syntax errors. I checked the syntax and there is no way to use this at the db2adutl command.
    It is used only at the restore command.
    In past the normal db2adutl command was sufficient to get the prod backups and now it is possible to, only we can't see newer backup images.


    Quote Originally Posted by db2mor View Post
    On the test environment, for the db2adutl query full db command-line, try using the additional -options "fromnode=SV-126 -fromowner=db2inst1" and
    use the same values used for the fromnode and fromowner as used during the successful cross-node restore from prod .

    Also on the Prod enviornment ensure that the TEST DB2-instance-owner has access to all of the TSM-objects of PROD (use db2adutl queryaccess on prod to verify).

    The behaviour suggests that the tsm-node name (nodename) is not correct when referenced from the tsm-client, or is unknown (double check your tsm-client dsm.sys on test).

  8. #8
    Join Date
    Aug 2016
    Posts
    19
    Here are the "queryaccess" outputs of the two systems:

    on Test:

    [db2inst1@tbwvl-appep01 work]$ db2adutl queryaccess

    Node Username Database Name Type
    --------------------------------------------------------------
    --------------------------------------------------------------
    Access Types: B - backup images L - logs A - both



    on Prod:
    [db2inst1@sv-126 ~]$ db2adutl queryaccess

    Node Username Database Name Type
    --------------------------------------------------------------
    SV-126 db2inst1 APPL A
    T-PEP01 db2inst1 APPL A
    TBWVL-APPEP01 db2inst1 APPL A
    --------------------------------------------------------------
    Access Types: B - backup images L - logs A - both

  9. #9
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Post the db2level output on Prod and Test
    Post the dsm.sys (not dsm.opt) of Prod and Test

  10. #10
    Join Date
    Aug 2016
    Posts
    19
    Prod db2level:
    DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09074"
    with level identifier "08050107".
    Informational tokens are "DB2 v9.7.0.4", "s110330", "IP23243", and Fix Pack
    "4".
    Product is installed at "/opt/ibm/db2/v97".


    Prod dsm.sys:
    *** The following replication server connection information is automatically updated
    *** These options should not be changed manually
    REPLSERVERNAME TSMPRD01
    REPLTCPSERVERADDRESS 10.100.37.15
    REPLTCPPORT 1500
    REPLSERVERGUID 31.e3.4f.70.ed.98.11.e4.96.bf.42.f2.e9.af.53.77

    *** end of automatically updated options
    ************************************************** **********************
    * Tivoli Storage Manager *
    * *
    * Sample Client System Options file for UNIX (dsm.sys.smp) *
    ************************************************** **********************

    * This file contains the minimum options required to get started
    * using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
    * enter the appropriate values for each option listed below and
    * remove the leading asterisk (*) for each one.

    * If your client node communicates with multiple TSM servers, be
    * sure to add a stanza, beginning with the SERVERNAME option, for
    * each additional server.

    ************************************************** **********************

    SErvername Server1
    *** The MYREPLICATIONServer and MYPRIMARYServername options are automatically updated and should not be changed manually
    MYREPLICATIONServer TSMPRD01
    MYPRIMARYServername TSMPRD02
    COMMMethod TCPip
    TCPPort 1500
    TCPServeraddress tsmprd02.intern.company.de
    NODename sv-126
    PASSWORDACCESS generate


    RESOURceutilization 4
    include /data/log/active/.../* DB2ARCH
    include /data/log/archive/.../* DB2ARCH


    Test db2level:

    [db2inst1@tbwvl-appep01 ~]$ db2level
    DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09072"
    with level identifier "08030107".
    Informational tokens are "DB2 v9.7.0.2", "s100514", "IP23089", and Fix Pack
    "2".
    Product is installed at "/opt/ibm/db2/V9.7.2".


    Test dsm.sys:
    ************************************************** **********************
    * Tivoli Storage Manager *
    * *
    * Sample Client System Options file for UNIX (dsm.sys.smp) *
    ************************************************** **********************

    * This file contains the minimum options required to get started
    * using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
    * enter the appropriate values for each option listed below and
    * remove the leading asterisk (*) for each one.

    * If your client node communicates with multiple TSM servers, be
    * sure to add a stanza, beginning with the SERVERNAME option, for
    * each additional server.

    ************************************************** **********************

    SErvername Server1
    COMMMethod TCPip
    TCPPort 1500
    TCPServeraddress tsmprd02.intern.company.de
    NODename tbwvl-appep01
    PASSWORDACCESS generate




    RESOURceutilization 4





    Quote Originally Posted by db2mor View Post
    Post the db2level output on Prod and Test
    Post the dsm.sys (not dsm.opt) of Prod and Test

  11. #11
    Join Date
    Aug 2016
    Posts
    19
    When I'm using "root" in the db2adutl query... owner root... command instead of "db2inst1", I can see all the images?
    But in the past I used the true owner "db2inst1"? What is happened and what should I do?

  12. #12
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Is the TSM-server triggering the DB2-backup?
    You can get your TSM admin to help - the metadata for TSM actions is usually in a DB2 database on the TSM-server and you can run SQL against it to compare the attributes of the backups before and after your restore-action.

Posting Permissions

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