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.
Currently we need to use the XMLQUERY in our LEFT OUTER JOINS during view creation. The views are created with no error, While querying the view it fails with below error. An ON clause associated with a JOIN operator or in a MERGE statement is not valid.. SQLCODE=-338, SQLSTATE=42972, DRIVER=4.18.60
Sample View created Create OR REPLACE view JV_FSG1_ENTITLEMENT#NAU as ( SELECT a.RECID, a.XMLRECORD "THE_RECORD" , a.RECID "ENTITLEMENT_ID" ,XMLCAST(XMLQUERY('$d/row/c171[position()=1]' passing a.XMLRECORD as "d") as VARCHAR(4000)) "AUDIT_DATE_TIME" FROM "FSG1_ENTITLEMENT#NAU" a LEFT OUTER JOIN "FBNK_SEC_ACC_MASTER" b ON b.RECID = XMLCAST(XMLQUERY('$d/row/c1[position()=1]' passing a.XMLRECORD as "d") as VARCHAR(4000)) );
Our product is written to cater all the major databases and Oracle supports XMLQUERY function in the views. We donot see any other solutions but to use CTE as a workaround. To fix it on our side is a monstrous task and it simply might not be possible. It means regutting all of our view logic just for their database. This will mean that We need to DISQUALIFY DB2 as a product Temenos supports until this is fixed. Please help us rectify this in the earliest.
Do not place IBM confidential, company confidential, or personal information into any field.