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.
We don't have IMM console in IIAS like in Netezza.
Every time the IIAS server is unreachable,
SSR must visit data center
connect to the system with his laptop to SCP ports
share screen with IBM engineer
IIAS "Need to support the multiple path directories for schema level backup
Right now in the version 0.15 we have schema level backup but it allows only one backup path .
We need to address this schema level backup to support multiple backup paths so that we can avoid the performance issue.
After insert on capture side on table with autonumber column, data is inserted, but sequence is not replicated on apply side.
You can follow the following steps to recreate the scenario.
CREATE LARGE TABLESPACE "TSD_DBA_TEST" IN DATABASE PARTITI...
We have an audit requirement to revoke Database and Platform user's access if they are inactive (hasn't been used) for 90 days.To satisfy above condition, we need to identify who has access to Platform and Database revoke if inactive for 90 days.
A user should ONLY be able to view objects of a schema that has explicit privileges (unless the owner).
Eg. If we say 'grant schemaadm on schema abc to role xyz' then any user in that role should be able to view the tables in schema abc. (like...
Do not place IBM confidential, company confidential, or personal information into any field.