DB2 FOR LUW / DB2FORLUW / 970 - DB2

If database name is not a catalogued alias in the database 
directories, you will get the following message when attempting 
to migrate the database: 
 
migrate db migdb 
SQL30061N  The database alias or database name "MIGDB 
" was not 
found at the remote node.  SQLSTATE=08004 
 
Here's an example of a database directory setup that will 
resultin this problem: 
     list db directory 
 
    System Database Directory 
 
  Number of entries in the directory = 1 
 
Database 1 entry: 
 
Database alias        = MIGDB 
Database name        = WSDBV8 
Local database directory      = /notnfs/mladen2 
Database release level       = c.00 
Comment         = 
Directory entry type       = Indirect 
Catalog database partition number    = 0 
Alternate server hostname      = 
Alternate server port number      = 
 
            The 
db2diag.log will contain entries such as the following: 
 
2009-09-28-11.36.51.610028-240 I1712A271   LEVEL: 
WarningPID     : 635040        TID  : 1   PROC : 
db2bp  INSTANCE: db2inst1       NODE : 000 
      EDUID   : 1 
     FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10 
    MESSAGE : Begin engn migration 
 
  2009-09-28-11.36.51.620240-240 I1984A433     LEVEL: 
Severe PID     : 774502        TID  : 1545  PROC : 
db2syscINSTANCE: db2inst1       NODE : 000  DB   : 
WSDBV8 APPHDL  : 0-8        APPID: 
      *LOCAL.db2inst1.090928153651 
     AUTHID  : DB2INST1 
    EDUID   : 1545     EDUNAME: db2agent (MIGDB) 
   FUNCTION: DB2 UDB, base sys utilities, sqleInitRestrict, 
  probe:100 
 RETCODE : ZRC=0xFFFFFC0B=-1013 
 
The sqleInitRestrict db2diag.log entry is the key eye catcher 
tohelp identify you're hitting this issue.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users attempting to migrate the database                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If database name is not a catalogued alias in the            * 
* databasedirectories, you will get the following message      * 
* whenattempting to migrate the database:migrate db            * 
* migdbSQL30061N  The database alias or database name "MIGDB"  * 
* wasnot found at the remote node.  SQLSTATE=08004             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to version 9.7 Fixpak 2 or later              * 
****************************************************************

Please make sure the database name and the database alias are 
the same before migrating.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem is first fixed in Version 9.7 Fixpak 2

Please make sure the database name and the database alias are 
the same before migrating.

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

01.10.2009
22.06.2010
22.06.2010

9.7.