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 IT17291 Status: Closed

TRANSFER OWNERSHIP OF STORED PROCEDURE RETURNS SQL0901N RC=5 WHEN A
SYSTEM-PERIOD TEMPORAL TABLE IS INVOLVED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If you have defined a system-period temporal table and a stored 
procedure (SP) that reference this table, the transfer ownership 
of the tables works fine but the transfer ownership of the SP 
fails with the error : 
 
db2 "transfer ownership of specific procedure user2.sp1 to user 
user2 preserve privileges" 
 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "Unknown dependent object type: 5".) 
SQLSTATE=58004 
 
 
You can see such messages logged in db2diag and db2 traces: 
 
 
444132    data DB2 UDB catalog services 
sqlrlTransferVerifyNewOwnerPrivileges fnc (3.3.108.1318.0.65) 
    pid 46980 tid 67668 cpid 62140 node 0 probe 65 
    bytes 607 
 
    Data1     (PD_TYPE_DIAG_LOG_REC,599) Diagnostic log record: 
 
    2016-07-29-10.59.07.882000+120 I36044463F597        LEVEL: 
Info 
    PID     : 46980                TID : 67668          PROC : 
db2syscs.exe 
    INSTANCE: DB2_12               NODE : 000           DB   : 
MAM 
    APPHDL  : 0-767                APPID: 
*LOCAL.DB2_12.160729085633 
    AUTHID  : USERTMP              HOSTNAME: IBM-MAM 
    EDUID   : 67668                EDUNAME: db2agent (MAM) 0 
    FUNCTION: DB2 UDB, catalog services, 
sqlrlTransferVerifyNewOwnerPrivileges, probe:65 
    DATA #1 : <preformatted> 
    depSchemaName: USER2   , depSchemaLen: 8, depObjectName: 
POLICY_INFO, depObjectLen: 11, depObjectType: 5 35 
 
 
 
444368    entry DB2 UDB global services sqlzeSqlCode cei 
(1.3.26.45.2) 
    pid 46980 tid 67668 cpid 62140 node 0 
    eduid 67668 eduname db2agent 
    bytes 50 
 
    Data1     (PD_TYPE_ECFID,4) Function: 
    DB2 UDB, catalog services, 
sqlrlCheckNonTABAUTHDepObjectPrivileges 
    Data2     (PD_TYPE_SINT,4) signed integer: 
    -901 
    Data3     (PD_TYPE_UINT,8) unsigned integer: 
    90 
    Data4     (PD_TYPE_UINT,2) unsigned integer: 
    1 
 
 
461137    data DB2 UDB relation data serv sqlrr_dump_ffdc fnc 
(3.3.18.18.0.250) 
    pid 46980 tid 67668 cpid 62140 node 0 probe 250 
    bytes 915 
 
    Data1     (PD_TYPE_DIAG_LOG_REC,907) Diagnostic log record: 
 
    2016-07-29-10.59.07.900000+120 I36046485F905        LEVEL: 
Severe 
    PID     : 46980                TID : 67668          PROC : 
db2syscs.exe 
    INSTANCE: DB2_12               NODE : 000           DB   : 
MAM 
    APPHDL  : 0-767                APPID: 
*LOCAL.DB2_12.160729085633 
    AUTHID  : USERTMP              HOSTNAME: IBM-MAM 
    EDUID   : 67668                EDUNAME: db2agent (MAM) 0 
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901 
sqlerrml: 32 
     sqlerrmc: Unknown dependent object type: 5 
     sqlerrp : SQLRL524 
     sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
               (4) 0x00000000      (5) 0xFFFFFFA6      (6) 
0x00000000 
     sqlwarn : (1)      (2)      (3)      (4)        (5) 
(6) 
               (7)      (8)      (9)      (1)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)