When you try to import an existing project into workspace in Eclipse or Spring Tool Suite, and cannot import because of this error,
Some projects cannot be imported because they already exist in the workspace
then you can try the following.
Open the ".project" file from the project directory and change the project name in the <name> tag. That's it. And try to import again.
Wednesday, June 29, 2016
Friday, June 17, 2016
Turning on Oracle Compatibility Mode in DB2
Both full DB2 and DB2 Express C shipped with the Oracle Compatibility Mode, which can be turned on.
Launch the DB2 Administrator command window and issue the following commands.
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES
Then, restart the database.
db2stop
db2start
Then create a new database and that database is already compatible with Oracle.
db2 CREATE DATABASE DB_Name
Thursday, June 9, 2016
Oracle to DB2 Migration - NULL Unique Constraint
Oracle allows columns of the unique constraint to be NULL.
CREATE TABLE MYTABLE
(
ID VARCHAR2(9),
CD VARCHAR2(6),
UNIQUE (ID, CD)
);
This is OK in Oracle. But if you run the same script in DB2, you will have an error with the error code, SQLCODE=-542. The reason is you must explicitly declare all the columns of the unique constraint as NOT NULL in DB2. So only the following script will work.
CREATE TABLE MYTABLE
(
ID VARCHAR2(9) Not NULL,
CD VARCHAR2(6) Not NULL,
UNIQUE (ID, CD)
);
But with the above script, if you are migrating the existing data from Oracle to DB2, the migration will fail with the error code SQLCODE=-407 if the existing data includes NULL in one of those columns because both columns of the above script do not allow NULL values.
The good news is that starting with the DB2 10.5, EXCLUDE NULL KEYS on unique index is introduced. So the problem can be solved by creating a UNIQUE INDEX separately as the following.
CREATE TABLE MYTABLE
(
ID VARCHAR2(9),
CD VARCHAR2(6)
);
CREATE UNIQUE INDEX MYTABLE_U01 ON MYTABLE (ID, CD) EXCLUDE NULL KEYS;
Subscribe to:
Posts (Atom)