Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Db2
Created by Guest
Created on Apr 21, 2023

When setting 'DB2_COMPATIBILITY_VECTOR=ORA' in non-ora DB, the resulting string length is different.

when it's going to setup "db2set DB2_COMPATIBILITY_VECTOR=ORA"~

$ db2set DB2_COMPATIBILITY_VECTOR=ORA
$ db2stop force
03/27/2023 18:05:52     0   0   SQL1064N  DB2STOP processing was successful.
SQL1064N  DB2STOP processing was successful.
$ db2start
03/27/2023 18:06:00     0   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.
$ db2 connect to sample1

  Database Connection Information

Database server        = DB2/LINUXX8664 11.5.5.0 <----
SQL authorization ID   = DB2INST1
Local database alias   = SAMPLE1

$ db2set -all
[i] DB2_COMPATIBILITY_VECTOR=ORA <-----
[i] DB2TRC_DEF_BUFFSIZE=1024M
[i] DB2COMM=TCPIP


$ db2 get db cfg for sample1

      Database Configuration for Database sample1

Database configuration release level                    = 0x1500
Database release level                                  = 0x1500

.....

Number compatibility                                    = OFF
Varchar2 compatibility                                  = OFF
Date compatibility                                      = OFF

$ db2 -tvf tab2
SELECT CASE WHEN SUBSTR(U.COL1,1,1)='F' THEN 'OUT' ELSE 'IN' END AS USER_TYPE, LENGTH(CASE WHEN SUBSTR(U.COL1,1,1)='F' THEN 'OUT' ELSE 'IN' END) AS VARCHAR_LENGTH, CASE WHEN SUBSTR(U.COL2,1,1)='F' THEN 'OUT' ELSE 'IN' END AS USER_TYPE, LENGTH(CASE WHEN SUBSTR(U.COL2,1,1)='F' THEN 'OUT' ELSE 'IN' END) AS CHAR_LENGTH FROM TESTTAB2 U WITH ur

USER_TYPE VARCHAR_LENGTH USER_TYPE CHAR_LENGTH
--------- -------------- --------- -----------
IN                     3 IN                  3 <-----
OUT                    3 OUT                 3

 2 record(s) selected.

Needed By Quarter
  • Guest
    Reply
    |
    May 9, 2023

    I think there should be a warning in the output if you try to enable 'Character literals' while being a non-ora db.

    In our case, this has been a big issue in our project and is still listed as a potential issue.

    Should I open a new idea to put a warning in the output?

    1 reply
  • Admin
    Ned Whelan
    Reply
    |
    May 8, 2023

    After reviewing this Idea, it is working as expected. With DB2_COMPATIBILITY_VECTOR=ORA, "Character literals" is enabled:

    https://www.ibm.com/docs/en/db2/11.5?topic=oracle-implicit-casting-character-graphic-constants

    In this mode, the string literals 'OUT' and 'IN' are CHAR(3) and CHAR(2) respectively. The result type for the CASE expression is thus CHAR(3) and therefore the length is always 3.

    1 reply