Page 1 of 1

ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Mon 23 Nov 2015 12:23
by StefanAim
We have probles with our existing product switching from Oracle 11 to Oracle 12:
The CodeFirst Migrations don't work anymore for following statement:

CreateTable("A_Table_Name ", c => new { ..., Myfield = c.String(nullable: false; maxLength: 6000), ... })...

For Oracle 11, dotConnect translated this into a CLOB field, with Oracle 12 it creates an
varchar2(6000) which results obviously in an ORA-00910 (length too large for data type) exception

We have OracleMaxStringSize.Standard set and we are using DevArt Version 8.5.464
Comment: We and our customers use standard Oracle settings.

Re: ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Tue 24 Nov 2015 10:09
by Shalex
Thank you for your report. We have reproduced the issue and will notify you when it is fixed.

Re: ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Thu 26 Nov 2015 12:59
by StefanAim
Hy,

do you know when you can provide a fix? We are currently finalizing our release (two weeks to go) and we
have to know if we should wait and add a new devart version or have to think about a workaround.

Re: ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Fri 27 Nov 2015 16:25
by Shalex
As a temporary workaround, please use

Code: Select all

CreateTable("A_Table_Name ", c => new { ..., Myfield = c.String(nullable: false; storeType: "clob"), ... })...
instead of

Code: Select all

CreateTable("A_Table_Name ", c => new { ..., Myfield = c.String(nullable: false; maxLength: 6000), ... })...

Re: ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Mon 30 Nov 2015 11:18
by StefanAim
Thanks! We confirmate that the Workaround is working. Please notify us, when the fix is done.

Re: ORA-00910 for EF Code First Migrations with Oracle 12

Posted: Thu 07 Jul 2016 17:30
by Shalex
The bug with generating size of the VARCHAR2 and NVARCHAR2 columns in Oracle 12c using the Code-First/Code-First Migrations functionality is fixed in the newest (9.1.55) build of dotConnect for Oracle.