Case# 00594925:
We had identified few limitations with the options on the tablespaces in DB2 LUW area in Aqua Data Studio 18.0 version. Here are the highlights.
1. The storage manager is not showing the Automatic tablespaces information. It only shows whether it is SMS or DMS. Also there is no provision to create automatic tablespaces thru the storage manager.
2. When creating the DDL for the tables, the tablespaces information is not captured. Also the DDL generated is mostly following SQL Server syntax by using the GO statements.
|
53 KB
![]() |
2 KB
|
40 KB
|
93 KB
![]() |
2 KB
|
131 KB
|
154 KB
|
154 KB
|
121 KB
|
38 KB
|
90 KB
|
138 KB
|
130 KB
|
95 KB
|
99 KB
|
97 KB
|
115 KB
|
177 KB
Hi Tom,
I have a concern:
we create tablespace using command - CREATE TABLESPACE TS13 MANAGED BY AUTOMATIC STORAGE(see screenshot).
Here I created Tablespace T13 which is managed by Automatic Stoarage , but still its TABLESPACETYPE is "D" (see Screenshot)
And "D" means it is managed by Database
"S" means managed by system.
So I need to know
Is there anything in the code which stores the Table Space Type by using initials of "Managed By type"?
Thanks,
Bhagyashree
Hi Tom,
I have a concern:
we create tablespace using command - CREATE TABLESPACE TS13 MANAGED BY AUTOMATIC STORAGE(see screenshot).
Here I created Tablespace T13 which is managed by Automatic Stoarage , but still its TABLESPACETYPE is "D" (see Screenshot)
And "D" means it is managed by Database
"S" means managed by system.
So I need to know
Is there anything in the code which stores the Table Space Type by using initials of "Managed By type"?
Thanks,
Bhagyashree
Hi Bhagyashree,
I looked through the catalog tables and could not find a place that made the distinction between DMS and Auto. They really are similar. That said, please add a radio button in the create tablespace gui to let the user create the tablespace with Auto. Change the underlying generated ddl to add the MANAGED BY AUTOMATIC STORAGE clause.
When doing an alter tablespace or displaying tablespace properties, do not display the radio button for Auto since we can only display DMS or SMS.
Does that make sense?
Thanks, Tom
Hi Bhagyashree,
I looked through the catalog tables and could not find a place that made the distinction between DMS and Auto. They really are similar. That said, please add a radio button in the create tablespace gui to let the user create the tablespace with Auto. Change the underlying generated ddl to add the MANAGED BY AUTOMATIC STORAGE clause.
When doing an alter tablespace or displaying tablespace properties, do not display the radio button for Auto since we can only display DMS or SMS.
Does that make sense?
Thanks, Tom
Hi Tom,
When doing an alter tablespace or displaying tablespace properties, do not display the radio button for Auto since we can only display DMS or SMS-- so in this case both the(DMS and SMS) radio buttons should be unchecked right?
CREATE TABLESPACE TS2 MANAGED BY AUTOMATIC STORAGE-- and what should happen on this statement?
Thanks,
Bhagyashree
Hi Tom,
When doing an alter tablespace or displaying tablespace properties, do not display the radio button for Auto since we can only display DMS or SMS-- so in this case both the(DMS and SMS) radio buttons should be unchecked right?
CREATE TABLESPACE TS2 MANAGED BY AUTOMATIC STORAGE-- and what should happen on this statement?
Thanks,
Bhagyashree
Hi Bhagyashree,
When doing an alter tablespace or displaying tablespace properties, use the current value for setting the radio button as we can only have DMS or SMS for a value. Do not display the radio button for auto storage.
When using the create gui, add a button to select automatic storage. The underlying code should change to use the MANAGED BY AUTOMATIC STORAGE clause when building the create statement.
Thanks, Tom
Hi Bhagyashree,
When doing an alter tablespace or displaying tablespace properties, use the current value for setting the radio button as we can only have DMS or SMS for a value. Do not display the radio button for auto storage.
When using the create gui, add a button to select automatic storage. The underlying code should change to use the MANAGED BY AUTOMATIC STORAGE clause when building the create statement.
Thanks, Tom
Unit Test -
Unit Test -
Hi Bhagyashree,
In your ExtractTablespace extract change, what will happen to the following line if one of the older queries are executed? You added a column to the top query but didn't change the two under it. Please have a look.
boolean autoStorage = rs.getBoolean(19);
Also, in the create tablespace gui, would you please change the automatic storage radio button to the first position and make it the default when the menu displays.
Thanks, Tom
Hi Bhagyashree,
In your ExtractTablespace extract change, what will happen to the following line if one of the older queries are executed? You added a column to the top query but didn't change the two under it. Please have a look.
boolean autoStorage = rs.getBoolean(19);
Also, in the create tablespace gui, would you please change the automatic storage radio button to the first position and make it the default when the menu displays.
Thanks, Tom
Hi Tom,
In the create tablespace gui, would you please change the automatic storage radio button to the first position and make it the default when the menu displays -- Done
Also made changes in ExtractTablespace class.
Thanks, Bhagyashree
Hi Tom,
In the create tablespace gui, would you please change the automatic storage radio button to the first position and make it the default when the menu displays -- Done
Also made changes in ExtractTablespace class.
Thanks, Bhagyashree
Hi Bhagyashree,
Based on the comment here, shouldn't you be setting the radio button for alter or properties to "Database managed space" for tablespaces created with automatic storage? You are doing this because the system tables have either D or S. There is nothing to identify that it was created by automatic storage.
Thanks, Tom
Hi Bhagyashree,
Based on the comment here, shouldn't you be setting the radio button for alter or properties to "Database managed space" for tablespaces created with automatic storage? You are doing this because the system tables have either D or S. There is nothing to identify that it was created by automatic storage.
Thanks, Tom
Hi Tom,
Fixed the issue.
Thanks,
Bhagyashree
Hi Tom,
Fixed the issue.
Thanks,
Bhagyashree
Hi Bhagyashree,
1. As per the Tom's comment, In the create tablespace gui, would you please change the automatic storage radio button the default when the menu displays. Currently, the "Database-managed space(High performance)" radio button is checked by default.
2. While creating script, MANAGE BY AUTOMATIC STORAGE should display in blue color the same way it display for MANAGE BY SYSTEM and MANAGE BY DATABASE
Hi Bhagyashree,
1. As per the Tom's comment, In the create tablespace gui, would you please change the automatic storage radio button the default when the menu displays. Currently, the "Database-managed space(High performance)" radio button is checked by default.
2. While creating script, MANAGE BY AUTOMATIC STORAGE should display in blue color the same way it display for MANAGE BY SYSTEM and MANAGE BY DATABASE
Hi Juhi,
1. As per the Tom's comment, In the create tablespace gui, would you please change the automatic storage radio button the default when the menu displays. Currently, the "Database-managed space(High performance)" radio button is checked by default. -- FIxed
2. While creating script, MANAGE BY AUTOMATIC STORAGE should display in blue color the same way it display for MANAGE BY SYSTEM and MANAGE BY DATABASE -- Fixed
Thanks,
Bhagyashree
Hi Juhi,
1. As per the Tom's comment, In the create tablespace gui, would you please change the automatic storage radio button the default when the menu displays. Currently, the "Database-managed space(High performance)" radio button is checked by default. -- FIxed
2. While creating script, MANAGE BY AUTOMATIC STORAGE should display in blue color the same way it display for MANAGE BY SYSTEM and MANAGE BY DATABASE -- Fixed
Thanks,
Bhagyashree
@Tom, Please validate the below scenario.
Steps:
1. Create tablespace with Automatic storage radio button checked
2. Select "System Temporary" or "User Temporary" as tablespace type and create the tablespace
3. Do rightclick the created tablespace -->Script object to window as --> CREATE
Observation: Its creating script which shows MANAGE BY SYSTEM instead of MANAGE BY AUTOMATIC STORAGE.
Note: Its working fine for Regular and Large tablespace type.
@Tom, Please validate the below scenario.
Steps:
1. Create tablespace with Automatic storage radio button checked
2. Select "System Temporary" or "User Temporary" as tablespace type and create the tablespace
3. Do rightclick the created tablespace -->Script object to window as --> CREATE
Observation: Its creating script which shows MANAGE BY SYSTEM instead of MANAGE BY AUTOMATIC STORAGE.
Note: Its working fine for Regular and Large tablespace type.
Hi Juhi,
Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager. That said, we should be consistent in generating the script and use manage by automatic storage if we can. Please have Bhagyashree look into this.
Thanks, Tom
Hi Juhi,
Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager. That said, we should be consistent in generating the script and use manage by automatic storage if we can. Please have Bhagyashree look into this.
Thanks, Tom
Hi Tom,
Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager. That said, we should be consistent in generating the script and use manage by automatic storage. -- Fixed
Thanks,
Bhagyashree
Hi Tom,
Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager. That said, we should be consistent in generating the script and use manage by automatic storage. -- Fixed
Thanks,
Bhagyashree
Hi Tom,
Working fine: Now script is generating with MANAGE BY AUTOMATIC STORAGE for system temporary and user temporary type.
As per you comment "Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager.". so for below scenario, please let us know what should be expected.
Scenario:
1. Create tablespace using "Automatic storage" as space management and "system temporary" as its type. see here
2. Do right-click on created tablespace and select tablespace properties
Observation: Currently, it is showing "database managed space" radio button selected see here for system temporary and user temporary.
Is it expected?
Thanks, Juhi
Hi Tom,
Working fine: Now script is generating with MANAGE BY AUTOMATIC STORAGE for system temporary and user temporary type.
As per you comment "Temporary tablespaces are always managed by the system where permanent tablespaces are managed by the database manager.". so for below scenario, please let us know what should be expected.
Scenario:
1. Create tablespace using "Automatic storage" as space management and "system temporary" as its type. see here
2. Do right-click on created tablespace and select tablespace properties
Observation: Currently, it is showing "database managed space" radio button selected see here for system temporary and user temporary.
Is it expected?
Thanks, Juhi
Hi Juhi,
You are correct... There seems to be a problem when displaying the managed radio button in the gui. I created one of each of the different types - LARGE, REGULAR, SYSTEM TEMPORARY, or USER TEMPORARY using automatic storage. You can see here that two(SYSTEM TEMPORARY, USER TEMPORARY) are managed by S. The other two(LARGE, REGULAR) are managed by D. You can use that query to test what the gui output should be.
Please have Bhagyashree take a look at this.
Thanks, Tom
Hi Juhi,
You are correct... There seems to be a problem when displaying the managed radio button in the gui. I created one of each of the different types - LARGE, REGULAR, SYSTEM TEMPORARY, or USER TEMPORARY using automatic storage. You can see here that two(SYSTEM TEMPORARY, USER TEMPORARY) are managed by S. The other two(LARGE, REGULAR) are managed by D. You can use that query to test what the gui output should be.
Please have Bhagyashree take a look at this.
Thanks, Tom
Its working fine now. Hence, marking it verified.
Its working fine now. Hence, marking it verified.
Issue #15470 |
Verified |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build ADS19.5.0-dev-39 |
No time estimate |