IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components Security
Created by Guest
Created on May 16, 2017

DDL creation support thru implicit trusted connection

Trusted context is a very good security mecanism to promote a user from an application server to a specific role.

We face 2 problems:
- DDL issued from Siebel application server, when applying a change, fails for CREATE TABLE
- If user has no direct INSERT privilege for exemple, and wants to create a TRIGGER FOR INSERT, the message is misleading "user doesn't have INSERT privilege". INSERT INTO TAB suceeds (because user had DATAACCESS thru trusted context). The SQL0551 error message should list the case for trusted connections.

All DDL is owned by SIEBEL user. Creating a trigger, a view is valid if user has CONTROL ownership of all tables for example (we used previously SADMIN with no CONTROL priviliege). The only exception that is is annoying is CREATE TABLE statement.