This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Archecker table level restore utility does not compatible of handling Informix engine complex table schema clauses
Individual Table restoration 'archecker' utility only support simple schema definition contents as the schema file. However, Informix engine support complex clauses when setting up a table.
E.g. When fragmenting a table based on interval based fragmentation to store each year data in a separate fragment, 'Archecker' table level restoration utility is not intelligent enough to apply the following fragment clause straight away during the table restoration attempt:
Fragment by range( ) Interval(NUMTOYMINTERVAL(1,'YEAR')) store in()
Luckily, there is a painful work around solution IBM suggests us to follow-up the steps as follows:
1) Create an additional table level restore (tlr) table with the required schema using the required fragmentation clause. 2) Even if we need to restore on the same dbspace through 'Archecker', setup the 'Archecker' script with the source/target details *without* the fragment/partition details. 3) Execute the normal 'Archecker' command. 4) drop the original table name and rename the tlr table (in step 1) back to the original table name .
This will obviously be a big challenge to any non-DBA person to restore such a table easily and fast manner during an emergency situation. Even for an experience person , it takes considerable time to setup the initial schema file manually as required.
So, the suggestion will be either to extend the 'Archecker' functionality to support such complex table clauses those are support by Informix engine or provide an individual table level restoration functionality through Ontape/OnBar mechanisms to avoid the above complexity to end user.
Do not place IBM confidential, company confidential, or personal information into any field.