is raised, I sent you a test projectORA-01461: can bind a LONG value only for insert into a LONG column
ORA-01461 during update of CLOB in ASP
ORA-01461 during update of CLOB in ASP
during update of a CLOB column a
Hannes, your letters were blocked by our e-mail system. Sorry for the inconvenience.
1. Please send me also the DDL/DML script for the database objects you are working with via data sources.
2. The exact steps we should follow to reproduce the ORA-01461 error.
3. The version of your Oracle Server.
4. Your current version of dotConnect for Oracle is 5.70.152 (Tools > Oracle > About), and you are using Direct Mode. Is this correct?
1. Please send me also the DDL/DML script for the database objects you are working with via data sources.
2. The exact steps we should follow to reproduce the ORA-01461 error.
3. The version of your Oracle Server.
4. Your current version of dotConnect for Oracle is 5.70.152 (Tools > Oracle > About), and you are using Direct Mode. Is this correct?
1: you can use the connect string in my example, the db in online over internet
2: try edit/update in grid (any value)
3: 11.2
4: 5.70.152
2: try edit/update in grid (any value)
3: 11.2
4: 5.70.152
Shalex wrote:Hannes, your letters were blocked by our e-mail system. Sorry for the inconvenience.
1. Please send me also the DDL/DML script for the database objects you are working with via data sources.
2. The exact steps we should follow to reproduce the ORA-01461 error.
3. The version of your Oracle Server.
4. Your current version of dotConnect for Oracle is 5.70.152 (Tools > Oracle > About), and you are using Direct Mode. Is this correct?
We have just tried to connect to your database using the connection string from your project and received "A connection attempt failed...". Probably, a host with your database is turned off at the moment. Please notify us here or by e-mail (alexsh at devart dot com) when your database is available (tell us the date and the time in the GMT 0 format).
Otherwise, send us the DDL/DML script of your database objects (the REPORT table with its data). This is a better way.
Otherwise, send us the DDL/DML script of your database objects (the REPORT table with its data). This is a better way.
The reason of "ORA-01461: can bind a LONG value only for insert into a LONG column" is that the OracleDataSource parameter of the"String" type is converted to OracleDbType.VarChar in all previous versions of dotConnect for Oracle (VarChar's max size is 4000 symbols). Starting from the next version, OracleDbType for parameter of the "String" type will be determined basing on its length (VarChar < 4000 < Clob).
If your version of dotConnect for Oracle is 5.70.170 or higher, you can use the following workaround: remove the Type attribute (Type="String") in Source Editor for parameter that corresponds to the Clob column in database - this will allow provider to determine the correct OracleDbType itself. This issue was discussed at http://www.devart.com/forums/viewtopic.php?p=58900.
If your version of dotConnect for Oracle is 5.70.170 or higher, you can use the following workaround: remove the Type attribute (Type="String") in Source Editor for parameter that corresponds to the Clob column in database - this will allow provider to determine the correct OracleDbType itself. This issue was discussed at http://www.devart.com/forums/viewtopic.php?p=58900.
New version of dotConnect for Oracle 6.00 is available for download now!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=19624 .
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=19624 .