DB2 - Problembeschreibung
Problem IT17143 | Status: Geschlossen |
MEMBER SUBSET IS NOT DROPPED AFTER HOST DATABASE IS DROPPED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
After creating the member subset by using ?SYSPROC.WLM_CREATE_MEMBER_SUBSET?, even though the host database is dropped, there is a case that member subset is NOT dropped and remained in ?db2 list db directory?. This fix will delete member subsets when the host database is dropped. I attached a reproduction result here to help your understanding. ------------------------------------- $ db2 connect to sample $ db2 "CALL SYSPROC.WLM_CREATE_MEMBER_SUBSET('CA1_SUBSET','<databaseAlias>DU IP_CA1</databaseAlias>', '(0)')" $ db2 connect reset $ db2 list db directory ... Database 2 entry: Database alias = DUIP_CA1 Database name = SAMPLE Local database directory = /home/jhhyun2 Database release level = 14.00 Comment = CA1_SUBSET Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number = ... Database 4 entry: Database alias = SAMPLE Database name = SAMPLE Local database directory = /home/jhhyun2 Database release level = 14.00 Comment = Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number = $ db2 drop db sample DB20000I The DROP DATABASE command completed successfully. $ db2 list db directory ... Database 2 entry: Database alias = DUIP_CA1 Database name = SAMPLE Local database directory = /home/jhhyun2 Database release level = 14.00 Comment = CA1_SUBSET Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number = ... ------------------------------------- | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in DB2 11.1 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.09.2016 09.05.2017 09.05.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
11.1.1.1 |