This content has been marked as final. Show 3 replies
Seems like a bug in SQL Developer that it is not picking up the scale. Will notify the appropriate group for a fix. NUMBER(x,y) is a valid representation in Oracle. Can you check to see what the default mapping is in SQL Developer before the conversion process begins?. If it shows up as NUMBER(x) then change it to NUMBER(x,y).
In the meanwhile iyou can fix the DDL before generating the schema in Oracle.
I can only map to DECIMAL or NUMBER but can't specify the precision and scale. If double click on system I could specify precision and scale but it isn't dynamic. Not all the decimal in db2 have the same precision and scale.
Edited by: user13802543 on 21/03/2012 10:16
Unfortunately it appears to be a bug for DB2 databases. So you have to manually update the DDL for affected columns/tables and generate the Oracle schema. If you need the fix for the issue at the earliest but have some time then can open a service request on our my oracle support website (support.oracle.com).