Hello Joss,

use this document to copy one backup image (or one tablespace) from
one machine to another:

    Symptom
     You want to perform a database copy. You want to back up the database
     using ADSM.
     How can the database backed up on host A by user db2xxx be restored on
     host B by user db2yyy?
     The following note applies to TSM witout changes.
     Additional key words
     DB6, Clone, DBClone, DBcopy, ADSM, TSM
     Cause and preconditions
     We analyze the source system
       Host name:   A
       DB name:     XXX
       ADSM nodes:  NODE_A

     and the target system
       Host name:   B
       DB name:     YYY
       ADSM nodes:  NODE_B

     Note:
     The users db2xxx and db2yyy are used in this description. If you back
up
     and restore the database using other users, substitute them for db2xxx
     and db2yyy.
     Example:
     Under Windows NT backups are usually performed by the user <sid>adm.
In
     this case, db2xxx and db2yyy have to be replaced by xxxadm and yyyadm.

     Solution

     1. Perform an offline backup into ADSM in the source system

     2. NT: Change file dsm.opt on the target host. Environment variable
        DSMI_CONFIG points to this file.

     3. UNIX: Change file dsm.sys on the target host. The file is in the
        directory that the environment variable DSMI_DIR points to.

        a) Deactivate the lines
                    PASSWORDACCESS    GENERATE
                    NODENAME          NODE_B
            with asterisks (asterisk is *)

        b) Add the lines
                    PASSWORDACCESS    PROMPT
                    NODENAME          NODE_A


     4. Adjust the DB2 configuration on the target host.

        To do this, you require the ADSM password of NODE_A. If you do not
        know this, reset it using ADSM tools.

        The actions described below must be performed by user db2yyy.

        a) Under DB2 UDB (V5 and higher) the ADSM parameters are maintained
           as part of the database configuration. This is only possible if
           one already existed. If this is not the case, execute the
command:
                db2 create database yyy

           This creates a database that can be used for the purpose. Make
the
           following adjustments:
                db2 update db cfg for yyy using adsm_nodename NODE_A
                db2 update db cfg for yyy using adsm_owner db2xxx
                db2 update db cfg for yyy using adsm_password <pw of
NODE_A>

           If, in addition, a different management class is set as default
in
           ADSM, the parameter ADSM_MGMTCLASS must additionally be adjusted
           to the name of the class. The adjustment is analogous to those
           shown above.

        b) Under DB2 V2, the ADSM settings are made in the Database Manager
           Configuration. Execute the following commands:
                db2 update dbm cfg using ADSM_NODENAME NODE_A
                db2 update dbm cfg using ADSM_OWNER db2xxx
                db2 update dbm cfg using ADSM_PASSWORD <password of NODE_A>

        The display of the backups of DB2 then fails as well as the display
        via the tool db2adutl (RC=137) but the restore works via db2cc,
        db2dd, the brdb6-tools or the command line.

     5. Now the database copy can be made according to the corresponding
        Notes (see below).

     CAUTION:
     Remember that the above-mentioned changes must be reversed after you
     copy the database so that the backup of the new system also works
     correctly and can be carried out under the correct nodes, users and so
     on.
     This means that

     1. the parameters ADSM_NODENAME, ADSM_OWNER and ADSM_PASSWORD are set
        again to BLANK with, for example, for DB2 UDB
             db2 update dbm cfg for yyy using adsm_nodename "''"

        or for DB2 V2
               db2 update dbm cfg using adsm_nodename "''"

     2. in the file dsm.sys (NT) or dsm.sys (UNIX) the original values for
        PASSWORDACCESS and NODENAME are set again.

best regards, Joachim Mueller

Datenbanken
DOUGLAS Informatik & Service GmbH
Kabeler Straße 4
D-58099 Hagen

Tel.:+49-2331-690-249
Fax:+49-2331-690-78-249
Mobile: +49-170-2221-249

mailto:[EMAIL PROTECTED]
http://www.douglas-informatik.de





(Embedded image moved to file: pic28145.pcx)

Von:  [EMAIL PROTECTED]@lists1.ba.best.com am 02.04.2001 18:38 ZE2



Bitte antworten an [EMAIL PROTECTED]

Gesendet von:  [EMAIL PROTECTED]


An:    [EMAIL PROTECTED]
Kopie:
Thema: DB2EUG: How to restore a tablespace to a different db on a
       differente machine ?



Hello  everybody,

How to restore a tablespace to a different db on a differente machine
using ADSM ?

My environment is DB2v5.2/Aix4.3.3.

I've to test the performance of a big table's reorganization.
So I need to restore the tablespace the way it is on the original
machine, and launch the reorg process.

But the difficulty to me, is to restore the tablespace using
ADSM to a different database of a différent machine.

The tablespace is about 40Go.

Do I've to create a database remote and a node directory pointing
to the original database before to proceed of the restore using ADSM ?

Did anybody had to do such an acrobatic operation ?
If so, could I have a help, even an advice ?

Thanks a in advance.

Best regards, Joss.


oO°OoO°OoO°OoO°OoO°Oo
   Jocelyn GIZOLME
   SDDC-PSR
   Tel : 7-4989
oO°OoO°OoO°OoO°OoO°Oo

__________________________________
     Your mouse has moved.
Windows has to reboot for change to take effect.
           [OK]

=:o)



=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see
http://people.mn.mediaone.net/scottrmcleod


Paintbrush

Reply via email to