Hello,
We use DevArt Oracle ExecuteArray function to insert a collection of data, when there are more than 1 error occurrs during insertion ( e.g. PK violation), an OracleException will be thrown with an Error collection contains all error details. However, since we are using a bridge to pass the OracleException object, we found the Errors collection is not serialized and deserialized correctly, the Error collection only contains 1 error rows and all error details are lost.
Could you please look into the issue? We use version 8.5.464.0.
Thanks!
Search found 7 matches
- Fri 28 Oct 2016 21:06
- Forum: dotConnect for Oracle
- Topic: OracleException.Errors collection is not serialized
- Replies: 2
- Views: 1590
- Fri 15 Aug 2014 23:43
- Forum: dotConnect for Oracle
- Topic: ArrayExecute insertion to varchar column with double value
- Replies: 3
- Views: 1143
ArrayExecute insertion to varchar column with double value
When I trying to do a executeArray insertion with single column varchar(50), the parameter value list contains both double and string. I will got “Input string was not in a correct format.” Exception. Why cant you convert double to string?
- Tue 14 Jun 2011 21:55
- Forum: dotConnect for Oracle
- Topic: Number was not inserted correctly by using ArrayInsertion
- Replies: 2
- Views: 1289
Number was not inserted correctly by using ArrayInsertion
Hello,
I found some number was not inserted correctly by using ArrayInsertion into a Float column. And this is only happens on 10g server but not 920.
Here's the table DDL
CREATE TABLE "NUMBERTEST"
(
"AKEY" NUMBER(*,0),
"AINT" NUMBER(*,0),
"ASIGNED" NUMBER(*,0),
"AFLOAT" NUMBER(*,0),
"ADOUBLE" FLOAT(126), "ADECIM" NUMBER(*,0),
"ADATE" TIMESTAMP (6),
"ACODE" NVARCHAR2(50),
"ANAME" NVARCHAR2(50),
"AADDRESS" NVARCHAR2(50) )
and here's data we are trying to insert ( first line is column header)
"AKEY","AINT","ASIGNED","AFLOAT","ADOUBLE","ADECIM","ADATE","ACODE","ANAME","AADDRESS"
59,968696870,193,-217171717,979797980,979797980,"1945-03-23 00:00:00","DhcSrGLl3Z","Xj:BmJUwN705kUt:KNyx","suikaSdgo"
You will find that 979797980 is turned into 979797952 when inserted by array insertion. If you use regular insert statement. it works fine.
Is this a bug in DevArt?
I found some number was not inserted correctly by using ArrayInsertion into a Float column. And this is only happens on 10g server but not 920.
Here's the table DDL
CREATE TABLE "NUMBERTEST"
(
"AKEY" NUMBER(*,0),
"AINT" NUMBER(*,0),
"ASIGNED" NUMBER(*,0),
"AFLOAT" NUMBER(*,0),
"ADOUBLE" FLOAT(126), "ADECIM" NUMBER(*,0),
"ADATE" TIMESTAMP (6),
"ACODE" NVARCHAR2(50),
"ANAME" NVARCHAR2(50),
"AADDRESS" NVARCHAR2(50) )
and here's data we are trying to insert ( first line is column header)
"AKEY","AINT","ASIGNED","AFLOAT","ADOUBLE","ADECIM","ADATE","ACODE","ANAME","AADDRESS"
59,968696870,193,-217171717,979797980,979797980,"1945-03-23 00:00:00","DhcSrGLl3Z","Xj:BmJUwN705kUt:KNyx","suikaSdgo"
You will find that 979797980 is turned into 979797952 when inserted by array insertion. If you use regular insert statement. it works fine.
Is this a bug in DevArt?
- Wed 20 Apr 2011 22:36
- Forum: dotConnect for Oracle
- Topic: OracleTimeStamp.Parse does not work
- Replies: 4
- Views: 3208
- Tue 19 Apr 2011 23:25
- Forum: dotConnect for Oracle
- Topic: OracleTimeStamp.Parse does not work
- Replies: 4
- Views: 3208
OracleTimeStamp.Parse does not work
I was trying to parse a string to OracleTimeStamp. I found if I use the format string "MM/DD/YYYY HH:MI:SS.FF", it always show PM
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 AM", "MM/DD/YYYY HH:MI:SS.FF", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 PM", "MM/DD/YYYY HH:MI:SS.FF", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
If I use "MM/DD/YYYY HH:MI:SS.FF AM", it flips AM to PM and PM to AM.
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 PM", "MM/DD/YYYY HH:MI:SS.FF AM", OracleDbType.TimeStamp)
12/23/2011 12:01:38 AM
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 AM", "MM/DD/YYYY HH:MI:SS.FF AM", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
It looks a bug to me. Or anyone can suggest a correct format string to make it work?
Thanks!
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 AM", "MM/DD/YYYY HH:MI:SS.FF", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 PM", "MM/DD/YYYY HH:MI:SS.FF", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
If I use "MM/DD/YYYY HH:MI:SS.FF AM", it flips AM to PM and PM to AM.
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 PM", "MM/DD/YYYY HH:MI:SS.FF AM", OracleDbType.TimeStamp)
12/23/2011 12:01:38 AM
OracleTimeStamp.Parse("12/23/2011 12:01:38.99 AM", "MM/DD/YYYY HH:MI:SS.FF AM", OracleDbType.TimeStamp)
12/23/2011 12:01:38 PM
It looks a bug to me. Or anyone can suggest a correct format string to make it work?
Thanks!
- Mon 04 Apr 2011 20:07
- Forum: dotConnect for Oracle
- Topic: OutOfMemoryException when retrieving rows from a large table
- Replies: 2
- Views: 4439
- Wed 23 Mar 2011 21:50
- Forum: dotConnect for Oracle
- Topic: OutOfMemoryException when retrieving rows from a large table
- Replies: 2
- Views: 4439
OutOfMemoryException when retrieving rows from a large table
Hello,
We are retrieving data from a large table by using DevArt.Oracle connector.
We got the OutOfMemoryException when retrieving more than 1000 rows from the table. We are wondering if there's a buffer limit to check to avoid such issue. Do you have any suggestion?
System.OutOfMemoryException
Exception of type 'System.OutOfMemoryException' was thrown.
Stack Trace:
at Devart.Data.Oracle.OracleDataReader.a()
at Devart.Data.Oracle.OracleDataReader.Read()
Here's the table DDL:
CREATE TABLE "SCALABILTY"."COLUMNS_113"
(
"WBIMP_ID" NUMBER(*,0) NOT NULL ENABLE,
"WBITRAN_ID" NUMBER(*,0) NOT NULL ENABLE,
"WBIMP_STATUS" VARCHAR2(40),
"WBIMP_MSG" VARCHAR2(4000),
"WBIMP_PROC_DATE" DATE,
"WBITRAN_FILENAME" VARCHAR2(256),
"WBITYP_NAME" VARCHAR2(40) NOT NULL ENABLE,
"WBIMP_RECNUM" NUMBER(*,0) NOT NULL ENABLE,
"A" VARCHAR2(1000),
"B" VARCHAR2(1000),
"C" VARCHAR2(1000),
"D" VARCHAR2(1000),
"E" VARCHAR2(1000),
"F" VARCHAR2(1000),
"G" VARCHAR2(1000),
"H" VARCHAR2(1000),
"I" VARCHAR2(1000),
"J" VARCHAR2(1000),
"K" VARCHAR2(1000),
"L" VARCHAR2(1000),
"M" VARCHAR2(1000),
"N" VARCHAR2(1000),
"O" VARCHAR2(1000),
"P" VARCHAR2(1000),
"Q" VARCHAR2(1000),
"R" VARCHAR2(1000),
"S" VARCHAR2(1000),
"T" VARCHAR2(1000),
"U" VARCHAR2(1000),
"V" VARCHAR2(1000),
"W" VARCHAR2(1000),
"X" VARCHAR2(1000),
"Y" VARCHAR2(1000),
"Z" VARCHAR2(1000),
"AA" VARCHAR2(1000),
"AB" VARCHAR2(1000),
"AC" VARCHAR2(1000),
"AD" VARCHAR2(1000),
"AE" VARCHAR2(1000),
"AF" VARCHAR2(1000),
"AG" VARCHAR2(1000),
"AH" VARCHAR2(1000),
"AI" VARCHAR2(1000),
"AJ" VARCHAR2(1000),
"AK" VARCHAR2(1000),
"AL" VARCHAR2(1000),
"AM" VARCHAR2(1000),
"AN" VARCHAR2(1000),
"AO" VARCHAR2(1000),
"AP" VARCHAR2(1000),
"AQ" VARCHAR2(1000),
"AR" VARCHAR2(1000),
"as" VARCHAR2(1000),
"AT" VARCHAR2(1000),
"AU" VARCHAR2(1000),
"AV" VARCHAR2(1000),
"AW" VARCHAR2(1000),
"AX" VARCHAR2(1000),
"AY" VARCHAR2(1000),
"AZ" VARCHAR2(1000),
"BA" VARCHAR2(1000),
"BB" VARCHAR2(1000),
"BC" VARCHAR2(1000),
"BD" VARCHAR2(1000),
"BE" VARCHAR2(1000),
"BF" VARCHAR2(1000),
"BG" VARCHAR2(1000),
"BH" VARCHAR2(1000),
"BI" VARCHAR2(1000),
"BJ" VARCHAR2(1000),
"BK" VARCHAR2(1000),
"BL" VARCHAR2(1000),
"BM" VARCHAR2(1000),
"BN" VARCHAR2(1000),
"BO" VARCHAR2(1000),
"BP" VARCHAR2(1000),
"BQ" VARCHAR2(1000),
"BR" VARCHAR2(1000),
"BS" VARCHAR2(1000),
"BT" VARCHAR2(1000),
"BU" VARCHAR2(1000),
"BV" VARCHAR2(1000),
"BW" VARCHAR2(1000),
"BX" VARCHAR2(1000),
"by" VARCHAR2(1000),
"BZ" VARCHAR2(1000),
"CA" VARCHAR2(1000),
"CB" VARCHAR2(1000),
"CC" VARCHAR2(1000),
"CD" VARCHAR2(1000),
"CE" VARCHAR2(1000),
"CF" VARCHAR2(1000),
"CG" VARCHAR2(1000),
"CH" VARCHAR2(1000),
"CI" VARCHAR2(1000),
"CJ" VARCHAR2(1000),
"CK" VARCHAR2(1000),
"CL" VARCHAR2(1000),
"CM" VARCHAR2(1000),
"CN" VARCHAR2(1000),
"CO" VARCHAR2(1000),
"CP" VARCHAR2(1000),
"CQ" VARCHAR2(1000),
"CR" VARCHAR2(1000),
"CS" VARCHAR2(1000),
"CT" VARCHAR2(1000),
"CU" VARCHAR2(1000),
"CV" VARCHAR2(1000),
"CW" VARCHAR2(1000),
"CX" VARCHAR2(1000),
"CY" VARCHAR2(1000),
"CZ" VARCHAR2(1000),
"CLIENT_ID" NUMBER(*,0)
DEFAULT -1 NOT NULL ENABLE,
PRIMARY KEY ("WBIMP_ID"))
Thanks!
We are retrieving data from a large table by using DevArt.Oracle connector.
We got the OutOfMemoryException when retrieving more than 1000 rows from the table. We are wondering if there's a buffer limit to check to avoid such issue. Do you have any suggestion?
System.OutOfMemoryException
Exception of type 'System.OutOfMemoryException' was thrown.
Stack Trace:
at Devart.Data.Oracle.OracleDataReader.a()
at Devart.Data.Oracle.OracleDataReader.Read()
Here's the table DDL:
CREATE TABLE "SCALABILTY"."COLUMNS_113"
(
"WBIMP_ID" NUMBER(*,0) NOT NULL ENABLE,
"WBITRAN_ID" NUMBER(*,0) NOT NULL ENABLE,
"WBIMP_STATUS" VARCHAR2(40),
"WBIMP_MSG" VARCHAR2(4000),
"WBIMP_PROC_DATE" DATE,
"WBITRAN_FILENAME" VARCHAR2(256),
"WBITYP_NAME" VARCHAR2(40) NOT NULL ENABLE,
"WBIMP_RECNUM" NUMBER(*,0) NOT NULL ENABLE,
"A" VARCHAR2(1000),
"B" VARCHAR2(1000),
"C" VARCHAR2(1000),
"D" VARCHAR2(1000),
"E" VARCHAR2(1000),
"F" VARCHAR2(1000),
"G" VARCHAR2(1000),
"H" VARCHAR2(1000),
"I" VARCHAR2(1000),
"J" VARCHAR2(1000),
"K" VARCHAR2(1000),
"L" VARCHAR2(1000),
"M" VARCHAR2(1000),
"N" VARCHAR2(1000),
"O" VARCHAR2(1000),
"P" VARCHAR2(1000),
"Q" VARCHAR2(1000),
"R" VARCHAR2(1000),
"S" VARCHAR2(1000),
"T" VARCHAR2(1000),
"U" VARCHAR2(1000),
"V" VARCHAR2(1000),
"W" VARCHAR2(1000),
"X" VARCHAR2(1000),
"Y" VARCHAR2(1000),
"Z" VARCHAR2(1000),
"AA" VARCHAR2(1000),
"AB" VARCHAR2(1000),
"AC" VARCHAR2(1000),
"AD" VARCHAR2(1000),
"AE" VARCHAR2(1000),
"AF" VARCHAR2(1000),
"AG" VARCHAR2(1000),
"AH" VARCHAR2(1000),
"AI" VARCHAR2(1000),
"AJ" VARCHAR2(1000),
"AK" VARCHAR2(1000),
"AL" VARCHAR2(1000),
"AM" VARCHAR2(1000),
"AN" VARCHAR2(1000),
"AO" VARCHAR2(1000),
"AP" VARCHAR2(1000),
"AQ" VARCHAR2(1000),
"AR" VARCHAR2(1000),
"as" VARCHAR2(1000),
"AT" VARCHAR2(1000),
"AU" VARCHAR2(1000),
"AV" VARCHAR2(1000),
"AW" VARCHAR2(1000),
"AX" VARCHAR2(1000),
"AY" VARCHAR2(1000),
"AZ" VARCHAR2(1000),
"BA" VARCHAR2(1000),
"BB" VARCHAR2(1000),
"BC" VARCHAR2(1000),
"BD" VARCHAR2(1000),
"BE" VARCHAR2(1000),
"BF" VARCHAR2(1000),
"BG" VARCHAR2(1000),
"BH" VARCHAR2(1000),
"BI" VARCHAR2(1000),
"BJ" VARCHAR2(1000),
"BK" VARCHAR2(1000),
"BL" VARCHAR2(1000),
"BM" VARCHAR2(1000),
"BN" VARCHAR2(1000),
"BO" VARCHAR2(1000),
"BP" VARCHAR2(1000),
"BQ" VARCHAR2(1000),
"BR" VARCHAR2(1000),
"BS" VARCHAR2(1000),
"BT" VARCHAR2(1000),
"BU" VARCHAR2(1000),
"BV" VARCHAR2(1000),
"BW" VARCHAR2(1000),
"BX" VARCHAR2(1000),
"by" VARCHAR2(1000),
"BZ" VARCHAR2(1000),
"CA" VARCHAR2(1000),
"CB" VARCHAR2(1000),
"CC" VARCHAR2(1000),
"CD" VARCHAR2(1000),
"CE" VARCHAR2(1000),
"CF" VARCHAR2(1000),
"CG" VARCHAR2(1000),
"CH" VARCHAR2(1000),
"CI" VARCHAR2(1000),
"CJ" VARCHAR2(1000),
"CK" VARCHAR2(1000),
"CL" VARCHAR2(1000),
"CM" VARCHAR2(1000),
"CN" VARCHAR2(1000),
"CO" VARCHAR2(1000),
"CP" VARCHAR2(1000),
"CQ" VARCHAR2(1000),
"CR" VARCHAR2(1000),
"CS" VARCHAR2(1000),
"CT" VARCHAR2(1000),
"CU" VARCHAR2(1000),
"CV" VARCHAR2(1000),
"CW" VARCHAR2(1000),
"CX" VARCHAR2(1000),
"CY" VARCHAR2(1000),
"CZ" VARCHAR2(1000),
"CLIENT_ID" NUMBER(*,0)
DEFAULT -1 NOT NULL ENABLE,
PRIMARY KEY ("WBIMP_ID"))
Thanks!