IBM Support

DB2_COMPATIBLITY_VECTOR yields unexpected results if turned on/off after the database is created

Troubleshooting


Problem

DB2_COMPATIBLITY_VECTOR changes SQL behaviors and enables compatibility features that DB2 does not normally use. The registry variable set to DB2_COMPATIBLITY_VECTOR=ORA allows the user to take full advantage of the DB2 compatibility features for Oracle applications.

Symptom

When the DB2_COMPATIBLITY_VECTOR variable is unset after the database is created with DB2_COMPATIBLITY_VECTOR=ORA, it might yield unexpected results.

The same can be said for vice versa: when the database is created with the default DB2_COMPATIBLITY_VECTOR unset, and it is set to ORA afterwards.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Instance","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
30 April 2025

UID

swg21983296