DB2 - Problem description
Problem IT33826 | Status: Closed |
LIST STORAGE ACCESS command gives 0 entries even if the catalog storage access completed successfully | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Steps to reproduce the behavior: 1. any Db2 v11.5 system - deploy dashdb 2. su db2inst1 3. db2 list storage access: $ db2 list storage access Node Directory Number of entries in the directory = 0 DB20000I The LIST STORAGE ACCESS command completed successfully. 4.if step 3 does not have alias, then create one in the following command: db2 "catalog storage access alias S3 vendor S3 server s3.private.us.cloud-object-storage.appdomain.cloud user password container db2whoc-flex-us-dev dbuser db2inst1" DB20000I The CATALOG STORAGE ACCESS command completed successfully. 5. list storage access alias again, but it's not there: $ db2 "list storage access" Node Directory Number of entries in the directory = 0 DB20000I The LIST STORAGE ACCESS command completed successfully. Expected behavior: We should be able to create a storage access alias like the following. $ db2 "list storage access" Node Directory Node 1 entry: ALIAS=S3 VENDOR=S3 SERVER=s3.private.us.cloud-object-storage.appdomain.cloud USERID= CONTAINER=db2whoc-flex-us-dev OBJECT= DBUSER=db2inst1 DBGROUP= Number of entries in the directory = 1 DB20000I The LIST STORAGE ACCESS command completed successfully. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.08.2020 20.11.2020 20.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |