DB2 - Problembeschreibung
Problem IC63452 | Status: Geschlossen |
MIGRATE DB <DBALIAS> FAILS WITH SQL30061N | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users attemtpting database migration * **************************************************************** * 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.5 Fixpak 6 or latter * **************************************************************** | |
Local-Fix: | |
Please make sure the database name and the database alias are the same before migrating. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem is first fixed in Version 9.5 Fixpack 6 | |
Workaround | |
Please make sure the database name and the database alias are the same before migrating. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC63518 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.09.2009 22.06.2010 22.06.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5., 9.5.FP6 | |
Problem behoben lt. FixList in der Version |