Hi all,
The problem is this: Oracle table with NUMBER datatype is migrated into DB2 as DECIMAL. No problem.
BUT
The Java application that processes the data using Eclipse or WebLogic is expecting an integer value and receives a decimal datatype instead. This causes the application malfunction.
Is there a way (if any) to workaround this problem, so that the Java application receives from DB2 an integer that can process the way it has been doing all along with Oracle?
EXAMPLE
=======
SELECT IN ORACLE
=============== =============== =============== ===
SQL> select id_parametro from gims.tm_paramet ro;
ID_PARAMETRO
1
2
3
4
6
SQL>
SAME SELECT IN DB2
=============== =============== =============== ===
$ db2 select id_parametro from gims.tm_paramet ro
ID_PARAMETRO
1.
2.
3.
4.
6.
But the java application expects integer values such as 1 2 3 4 5 not decimals like 1. or 1.0 etcetera
How can we fix this ??
Thanks in advance,
Raul Baron
The problem is this: Oracle table with NUMBER datatype is migrated into DB2 as DECIMAL. No problem.
BUT
The Java application that processes the data using Eclipse or WebLogic is expecting an integer value and receives a decimal datatype instead. This causes the application malfunction.
Is there a way (if any) to workaround this problem, so that the Java application receives from DB2 an integer that can process the way it has been doing all along with Oracle?
EXAMPLE
=======
SELECT IN ORACLE
=============== =============== =============== ===
SQL> select id_parametro from gims.tm_paramet ro;
ID_PARAMETRO
1
2
3
4
6
SQL>
SAME SELECT IN DB2
=============== =============== =============== ===
$ db2 select id_parametro from gims.tm_paramet ro
ID_PARAMETRO
1.
2.
3.
4.
6.
But the java application expects integer values such as 1 2 3 4 5 not decimals like 1. or 1.0 etcetera
How can we fix this ??
Thanks in advance,
Raul Baron