User c6388a069b
14-05-2012 12:12:34
Importing as view and then Entity e remote oracle table coming from another schema I receive the following error mesage as attached. Is it due to a particular type of filed that IJChem is not able to recognize? Thanks in advance Fabio
ChemAxon fa971619eb
14-05-2012 12:14:40
Fabio, could you attach the file again? That one seems empty.
Tim
User c6388a069b
14-05-2012 13:28:44
Hi Tim,
here you are as the table was created, do ou see any issue? For me the field "EXPIRATION_DATE" TIMESTAMP (4) is the cause of the failure. Is it?
Many thanks in advance
CREATE TABLE "BIO"."HNAV1_7"
(
"ID" NUMBER(10,0) NOT NULL ENABLE,
"COMPOUND_ID" NVARCHAR2(255),
"BATCH_ID" NVARCHAR2(255),
"PROJECT_ID" NVARCHAR2(255),
"LNB_REF" NVARCHAR2(255),
"ASSAY" NVARCHAR2(255),
"METHOD_ID" NVARCHAR2(255),
"CELL_TYPE" NVARCHAR2(255),
"TECHNOLOGY" NVARCHAR2(255),
"EXPIRATION_DATE" TIMESTAMP (4),
"CELL_ID" NVARCHAR2(255),
"COMMENTS" NVARCHAR2(255),
"REST_1ST_PIC50_MOD" NVARCHAR2(255),
"REST_1ST_PIC50" FLOAT(126),
"REST_1ST_SLOPE" FLOAT(126),
"REST_1ST_CONC_A" FLOAT(126),
"REST_1ST_PERC_A" FLOAT(126),
"REST_1ST_CONC_B" FLOAT(126),
"REST_1ST_PERC_B" FLOAT(126),
"REST_1ST_CONC_C" FLOAT(126),
"REST_1ST_PERC_C" FLOAT(126),
"REST_PIC50_MOD" NVARCHAR2(255),
"REST_PIC50" FLOAT(126),
"REST_SLOPE" FLOAT(126),
"REST_CONC_A" FLOAT(126),
"REST_PERC_A" FLOAT(126),
"REST_CONC_B" FLOAT(126),
"REST_PERC_B" FLOAT(126),
"REST_CONC_C" FLOAT(126),
"REST_PERC_C" FLOAT(126),
"SLOW_PIC50_MOD" NVARCHAR2(255),
"SLOW_PIC50" FLOAT(126),
"SLOW_CONC_A" FLOAT(126),
"SLOW_PERC_A" FLOAT(126),
"SLOW_CONC_B" FLOAT(126),
"SLOW_PERC_B" FLOAT(126),
"SLOW_CONC_C" FLOAT(126),
"SLOW_PERC_C" FLOAT(126),
"RATIO_REST_1ST_OVER_SLOW_MOD" NVARCHAR2(255),
"RATIO_REST_1ST_OVER_SLOW" FLOAT(126),
"RATIO_REST_OVER_SLOW_MOD" NVARCHAR2(255),
"RATIO_REST_OVER_SLOW" FLOAT(126),
PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "BIO_DATA" ENABLE
)
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING STORAGE
(
INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
)
TABLESPACE "BIO_DATA" ;
ChemAxon fa971619eb
16-05-2012 08:57:23
Yes, I think its almsot certainly the TIMESTAMP(4) column type. The Oracle JDBC driver is reporting this as of type 1111, which means OTHER. So IJC is being confused because it doesn't know how to handle the column.
I think TIMSTAMP without any parameters should work OK. Are you able to switch to that column type?
We'll look and see if we can find a workaround for this, but for now I think cahnging the column type is the only solution.
Tim