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,
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.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io
Indeed, it's unfortunate that the standard Oracle connector in CP4D doesn't support anything more than host, sid/service, and port. You can't even specify a DataGuard failover pair for HA.
Could you describe your experience using the custom JDBC connector for connecting with Oracle? How are you specifying the connect string in the parameters, and do you really need to upload an ojdbc driver for each and every connection to Oracle?
If there was support for a tnsnames.ora file and/or LDAP reference, that would also solve any connect string length limit.
There's a limit of something like 10K when you add the connection string into the platform connections section of CPD, but when you then try to use that connection within data discovery... it attempts to create the data connection within the Metadata Import (legacy IMAM) repository. That has a limit of 256 characters for the URL. There is a way to break the URL within the IMAM data connection definition (part then goes into the additional attributes)... but that's only when you have the typical ";" style URL... like "database=GOSALES;encrypted=true;"... this is using an Oracle "thin" client URL which is effectively the TNSNAMES.ORA definition. So not something that can be broken apart in that fashion.
After investigation, we can't identify where the limit is. According to the development team, the size of the URL is not limited. We need more details on how to reproduce this issue. Please provide the detailed steps to reproduce the issue, and we may consider this. You can also contact the IBM support team as there should not be such a limitation currently in Cloud Pak for Data connection forms.
The customer will not be able to move into production this quarter without this capability.