We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
REPAIR CATALOG TABLESPACE command for xml table space
We are working with OBJECT_CREATE_FORMAT=EXTENDED and with UTILITY_OBJECT_CONVERSION=NOBASIC for a long time without any problem.
In the last time we began to work with these parameters in other DB2's that include many tables with XML columns. The REORG of the entire auxiliary tablespace(as it must done) increase the length of START_TS and END_TS columns in the xml table. We understand it done because of the extend of the RBA. The REORG also upgrade the CURRENT_VERSION of the xml auxiliary tablespace. We believe it done because of the increase of the length of START_TS and END_TS columns.
Until here, there isn't any problem for us.
We are using utilities "like" DSN1COPY for copy the tables including the xml tables. We know how to deal with the DOCID and SYSXMLRELS table. When we try to copy base table with xml column and it's corresponding xml table from source db2 to target db2, we have problem when there is difference between the CURRENT_VERSION of the xml auxiliary tablespace. in regular tables, we are using REPAIR CATALOG TABLESPACE command, but for xml auxiliary tablespace, we get message DSNU068I. This situation can happen when the table in the source was created with OBJECT_CREATE_FORMAT=EXTENDED and the table in the target was created with OBJECT_CREATE_FORMAT=BASIC and was converted to EXTNDED RBA by REORG. Of course, the opposite situation is also problematic.
The solution of create the tables with BASIC and the convert them to extended is not applicable for us, because we always create new xml tables and want to copy form an old xml table with CURRENT_VERSION=1 and the changes of OBJECT_CREATE_FORMAT from EXTENDED to BASIC all the time is not good and risky.
The option to use UNLOAD/LOAD is not a good solution also because o:
1) We copy tha data many time per a month.
2) We have many xml tables.
3)In general, the width of xml is big, so unload load take a lot of time.
So, as we understand the options, the only good solution is to allow REPAIR CATALOG TABLESPACE command for xml auxiliary tablespace.
REPAIR CATALOG TABLESPACE command for xml table space RFE 130710
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=130710 We are working with OBJECT_CREATE_FORMAT=EXTENDED and with UTILITY_OBJECT_CONVERSION=NOBASIC for a long time without any problem. In the last time we began to work wit...
over 3 years ago
in Db2 for z/OS
Functionality already exists
Do not place IBM confidential, company confidential, or personal information into any field.