Wednesday, 30 June 2010
Enabling Oracle compatibility on DB2
Enabling the Oracle Compatibility on DB2 made easy with DB2 9.7! The key registry variable for this is DB2_COMPATIBILITY_VECTOR
To enable all the compatibility features set it to ORA
If the DB2_COMPATIBILITY_VECTOR registry variable is set to ORA, and the DB2_DEFERRED_PREPARE_SEMANTICS registry variable is not set, a default value of YES is used. However, it is recommended that the DB2_DEFERRED_PREPARE_SEMANTICS registry variable be explicitly set to YES.
Make sure you issue a db2stop/db2start in order for the changes to take effect.
To enable all the compatibility features set it to ORA
db2set DB2_COMPATIBILITY_VECTOR=ORA
If the DB2_COMPATIBILITY_VECTOR registry variable is set to ORA, and the DB2_DEFERRED_PREPARE_SEMANTICS registry variable is not set, a default value of YES is used. However, it is recommended that the DB2_DEFERRED_PREPARE_SEMANTICS registry variable be explicitly set to YES.
db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES
Make sure you issue a db2stop/db2start in order for the changes to take effect.
db2stop force
db2start
Some of the great DB2 9.7 features
Now migration from Oracle to DB2 made easy.
As of DB2 9.7, you can deploy PL/SQL code to DB2.
Also, problems occurring previously due to differences in locking mechanism between Oracle and DB2 should be easy to fix now with the new Isolation level "Currently Committed"
As of DB2 9.7, you can deploy PL/SQL code to DB2.
Also, problems occurring previously due to differences in locking mechanism between Oracle and DB2 should be easy to fix now with the new Isolation level "Currently Committed"
Subscribe to:
Comments (Atom)