This content has been marked as final. Show 7 replies
to follow up the root cause of ORA-02270 it would be good to get the DB2 table definition as the table is defined in the Oracle database.
For the other issue with the trigger, please have a look at:
=> it lists which objects the migration supports as:
Supported Migration Objects
=> so no triggers.
Have a look at this example:
create table klaus (col1 char(15), col2 integer, col3 varchar(20));
insert into klaus values ('Hello World',1,'Hello World!');
repeating the following step a couple of times:
insert into klaus select * from klaus;
The select count(*) from klaus; reports now about 16000 records.
Using SQL Dev 3.0 captured the table and creates it as
Using the Online and Offline migration transfers all the rows.
Ok I understand that failure to assign a primary key the performance will be very slow to load data.
but we are talking about a migration not a reengineering and can not tell the client to make a redesign of its database.
We have to migrate as it is even with its flaws and SQL Developer does not permit.
The situation then is that SQL Developer can not perform this migration?
I'm a little bit confused as I didn't ask to change the source model at all.
The error you get might be an issue with a foreign key constraint - but without the source data I'm not able to reproduce nor to verify the root cause. If you don't want to publish the source table information, please file a service request and provide us the offline source model files.
I've converted the SAMPLE database based on DB2 LUW 9.7 using SQL Developer 3.0 and the database was migrated successfully. Afterwards I've used the ONLINE data migration method and it finished also without reporting the ORA-02270.
So please provide more diagnostic information (including a step by step instruction) where you get the error and what object(s) are involved.