not enough detail, there's more than 1 way to store XML in the db, can you share your table DDL
also, thick or thin client connection - the XML features can behave different when doing jdbc vs OCI
Hi, Thnx for the update:
Basically an table with an xmltype column and two default value fields and a set of text fields for extra info.
CREATE TABLE "OWNER_DWA"."DSEXPORT_XML"
( "OS_FILENAME" VARCHAR2(255 BYTE),
"XML_DATA" "SYS"."XMLTYPE" ,
"LOAD_DATE" DATE DEFAULT sysdate NOT NULL ENABLE,
"AUDIT_ID" NUMBER GENERATED BY DEFAULT ON NULL AS IDENTITY MINVALUE 1 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE NOT NULL ENABLE,
"COMMENTS" VARCHAR2(400 BYTE)
CREATE INDEX "OWNER_DWA"."IDX_DSEXPORT_XML1" ON "OWNER_DWA"."DSEXPORT_XML" ("XML_DATA") INDEXTYPE IS "XDB"."XMLINDEX" ;
CREATE UNIQUE INDEX "OWNER_DWA"."IDX_DSEXPORT_XML_XML3" ON "OWNER_DWA"."DSEXPORT_XML" ("AUDIT_ID") ;
No oracle client installed just using SQLDeveloper.
I figured it out: java throws an illegal character error on the logging page sort of in the background.
My file is on a network share and although the gui allows you to select the file, the java code that does the actual upload barfs at paths with illegal character in it.
Illegal character in path at index 18: file:/Z:/xxx.xml
The path is deleted here by me but contains both & ,spaces and - in it. One or all causes it to barf.
The bug is then twofold:
The client should display the error to the user in some kind of dialog telling him what went wrong.
And ofcourse that java upload code can not handle filenames with special characters in it.
Thnx for testing it.
if you'd like to file bugs, please send them to My Oracle Support
How do i do that ?