The DB2_COMPATIBILITY_VECTOR registry variable is used to enable one or more DB2® compatibility features introduced since DB2 Version 9.5.
This register key is to enable the DB2 SQL compatibility to other product.
There are 3 major product are supported:
- SYB: for Sybase
- ORA: for Oracle 10FFF
- MYS: for MySQL 3004
We can use db2set to change it and this changes require bounce the db2 instance in order to take effective. The value can be set either by name or the hex value.
Below example is to set the DB2 compatible mode to Oracle , so we can use dual instead of SYSIBM.SYSDUMMY1.
However, the ORA value is not valid in the DB2 Express-C version, if we try to set it to ORA, we would get the DBI1301E Invalid value error.
The work around is to set by individual features, for example, to enable dual dummy table, we have to set it as 2. Hex value ( 10FFF) is still not supported in Express-C.
- DB2_COMPATIBILITY_VECTOR registry variable: http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.apdv.porting.doc/doc/r0052867.html
- DB2 Viper 2 compatibility features: http://www.ibm.com/developerworks/data/library/techarticle/dm-0707rielau/index.html