suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38859 Status: Closed

DB2MOVE COPY FAILS WITH "INVALID OBJECT TYPE SPECIFIED"

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
If a db2move COPY operation is performed on a remotely cataloged
database which resides on a client at version 11.5.6.0 or
11.5.7.0, and the remote database server is at version older
than 11.5.6.0, then it may fail with error message "Invalid
object type specified".

Example:
Suppose a database "localDB" resides on a database server
running 11.5.4.0, and it is cataloged on a remote client as
"remoteDB" running version 11.5.6.0.

$  db2move remoteDB COPY -sn remoteschema -co TARGET_DB localDB
SCHEMA_MAP "((remoteschema ,localschema)" -u usserid -p



The db2move will fail with error like so:

Application code page not determined, using ANSI codepage 1208
*****  DB2MOVE  *****
Action:  COPY
Start time:  Mon Oct 25 11:29:14 2021

All schema names matching:  REMOTESCHEMA;
Connecting to database REMOTEDB ... successful!  Server : DB2
Common Server V11.1.4
Copy schema REMOTESCHEMA to LOCALSCHEMA on the target database
LOCALDATABASE
Create DMT :
Rolled back all changes from the create phase (debuginfo:120).

Error Message : Invalid object type specified
db2move failed with -1 (debuginfo:50).

db2diag.log on local server will contain a message like this

XXXXXXXXXXXXXXXX           LEVEL: Severe
PID     : 73058    TID : 140439345940256 PROC :
db2move
INSTANCE: instance             NODE : 000            DB   :
LOCALDB
APPID   : xxxxxxxxxxxxx
HOSTNAME: hostname
FUNCTION: , , , probe:1006
MESSAGE : ZRC=0xFFFFFFFF=-1
DATA #1 : String, 29 bytes
Generate dependency tree call
DATA #2 : Hexdump, 136 bytes
0x00007FFD1D109F50 : 5351 4C43 4120 2020 8800 0000 45FE FFFF
SQLCA   ....E...
0x00007FFD1D109F60 : 4100 4144 4D49 4E5F 4745 545F 4445 5054
A.ADMIN_GET_DEPT
0x00007FFD1D109F70 : 5245 45FF 4144 4D49 4E5F 4745 545F 4445
REE.ADMIN_GET_DE
0x00007FFD1D109F80 : 5054 5245 45FF 496E 7661 6C69 6420 6F62
PTREE.Invalid ob
0x00007FFD1D109F90 : 6A65 6374 2074 7970 6520 7370 6563 6966
ject type specif
0x00007FFD1D109FA0 : 6965 6420 2020 2020 5351 4C45 5246 5250
ied     SQLERFRP
0x00007FFD1D109FB0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007FFD1D109FC0 : 0000 0000 0000 0000 2020 2020 2020 2020
........
0x00007FFD1D109FD0 : 2020 2033 3830 3030
38000
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to	db2_v115m7fp1                                     *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to	db2_v115m7fp1                                     *
****************************************************************
Comment
Upgrade to	db2_v115m7fp1
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.10.2021
09.03.2022
09.03.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)