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.
CDC for Oracle(version 11.4) does not work with longer identifiers than 30 bytes.
Use cases for the system: updates source data. System: continous mirroring
Scenario: ・prepare oracle12c with definition 30 bytes over identifier. ・and implements CDC for oracle. ・update some data on source database. ・check to flat file. There is nothing primary key.
We already have source database for Oracle10g with Japanese identifiers, and currently utilize CDC 10.2. It has a multi-byte character-set, and currently identifier is defined a full-character.
However, we have a migration plan to Oracle12c with UTF8, and doing this will extend identifier size by 1.5 times.(Japanese character with shift-jis needs 2 bytes, on the other hands with UTF-8 needs 3 bytes.) We have decided to utilize CDC v11.4, because your sales agent proposed us this product.
But CDC for Oracle does not work only when updates. This identifier limit should be extended to 31-128 bytes.
Do not place IBM confidential, company confidential, or personal information into any field.