DB2 - Problembeschreibung
Problem IT02746 | Status: Geschlossen |
TRANSFER OWNERSHIP COMMAND FAILED WITH SQL0607N ERROR FOR TABLESPACES SYSTOOLSPACE AND SYSTOOLSTMPSPACE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
Attempting to transfer ownership of tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE may fail with SQL0607N error. For example, below are these two tablespaces which have ownership as of the db2 instance owner db2inst1, db2 "select substr(owner,1,30) owner, substr(tbspace,1,30) tbspace, ownertype from syscat.tablespaces where tbspace like 'SYSTOOL%'" OWNER TBSPACE OWNERTYPE ------------------------------ ------------------------------ --------- DB2INST1 SYSTOOLSPACE U DB2INST1 SYSTOOLSTMPSPACE U however attempting to transfer their ownership to the other user db2inst2 would fail with SQL0607N error stating they are system objects. db2 "TRANSFER OWNERSHIP OF tablespace SYSTOOLSPACE TO USER DB2INST2 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: SQL0607N "TRANSFER OWNERSHIP" is not defined for system objects. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL USERS * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 5 or newer * **************************************************************** | |
Local-Fix: | |
If possible, drop and recreate these two tablespaces via the new user. | |
Lösung | |
Problem was first fixed in Version 10.5 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.06.2014 13.03.2015 13.03.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |