Generating SQL schema from EDMX designer using your devart TT, we get the following error:
The SSDL generated by the activity called ‘CsdlToSsdlAndMslActivity’ is not valid and has the following errors:
Precision ‘38’ is not valid. Precision must be between ‘1’ and ‘29’ for ‘decimal’ type.
I set a decimal field type with 38 precision and 19 scale. I have no errors generating SQL schema for SQL Server.
If I try to manually create a table on Oracle using NUMBER(38,19) as type, I have no errors, so I think there is a problem with your field type validation.
Can you help me?
Search found 17 matches
- Fri 26 Aug 2011 08:29
- Forum: Entity Framework support
- Topic: Error generating SQL schema with decimal(38,16)
- Replies: 2
- Views: 1359
- Thu 14 Jul 2011 06:52
- Forum: dotConnect for Oracle
- Topic: Workflow Instance Store bugs
- Replies: 7
- Views: 3267
- Mon 11 Jul 2011 07:25
- Forum: dotConnect for Oracle
- Topic: Workflow Instance Store bugs
- Replies: 7
- Views: 3267
- Mon 13 Jun 2011 12:48
- Forum: dotConnect for Oracle
- Topic: Workflow Instance Store bugs
- Replies: 7
- Views: 3267
I have a new bug for you.
Previous bugs are on Oracle 11.0.2.1.0
Using Oracle 10.2.0.5.0, your Workflow Instance Store is not working. Also a simple workflow persist command thrown an InstancePersistenceCommandException exception:
The execution of the InstancePersistenceCommand named {urn:schemas-microsoft-com:System.Activities.Persistence/command}SaveWorkflow was interrupted by an error
The inner exception is
Inner Exception
---------------
Type : Devart.Data.Oracle.OracleException, Devart.Data.Oracle, Version=6.30.160.0, Culture=neutral, PublicKeyToken=09af7300eec23701
Message : ORA-06550: riga 1, colonna 6:
PLS-00103: Trovato il simbolo "" anziché uno dei seguenti:
begin case
declare exit for goto if loop mod null pragma raise return
select update while with
<< close current delete fetch lock insert
open rollback savepoint set sql execute commit forall merge
pipe
Il simbolo "" è stato ignorato.
ORA-06550: riga 6, colonna 136:
PLS-00103: Trovato il simbolo "" anziché uno dei seg
Source : Devart.Data.Oracle
Help link :
Code : 6550
Offset : 5
Errors :
ErrorCode : -2147467259
Data : System.Collections.ListDictionaryInternal
TargetSite : Void b(Int32)
Stack Trace : at Devart.Data.Oracle.av.b(Int32 A_0)
at Devart.Data.Oracle.bj.a(Int32 A_0, be A_1)
at Devart.Data.Oracle.OracleCommand.InternalExecute(CommandBehavior behavior, IDisposable disposable, Int32 startRecord, Int32 maxRecords, Boolean nonQuery)
at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior, Boolean nonQuery)
at Devart.Data.Oracle.OracleCommand.ExecuteNonQuery()
at Devart.Data.Oracle.DurableInstancing.am.a(Boolean A_0)
at Devart.Data.Oracle.DurableInstancing.c.c()
Thank you.
Previous bugs are on Oracle 11.0.2.1.0
Using Oracle 10.2.0.5.0, your Workflow Instance Store is not working. Also a simple workflow persist command thrown an InstancePersistenceCommandException exception:
The execution of the InstancePersistenceCommand named {urn:schemas-microsoft-com:System.Activities.Persistence/command}SaveWorkflow was interrupted by an error
The inner exception is
Inner Exception
---------------
Type : Devart.Data.Oracle.OracleException, Devart.Data.Oracle, Version=6.30.160.0, Culture=neutral, PublicKeyToken=09af7300eec23701
Message : ORA-06550: riga 1, colonna 6:
PLS-00103: Trovato il simbolo "" anziché uno dei seguenti:
begin case
declare exit for goto if loop mod null pragma raise return
select update while with
<< close current delete fetch lock insert
open rollback savepoint set sql execute commit forall merge
pipe
Il simbolo "" è stato ignorato.
ORA-06550: riga 6, colonna 136:
PLS-00103: Trovato il simbolo "" anziché uno dei seg
Source : Devart.Data.Oracle
Help link :
Code : 6550
Offset : 5
Errors :
ErrorCode : -2147467259
Data : System.Collections.ListDictionaryInternal
TargetSite : Void b(Int32)
Stack Trace : at Devart.Data.Oracle.av.b(Int32 A_0)
at Devart.Data.Oracle.bj.a(Int32 A_0, be A_1)
at Devart.Data.Oracle.OracleCommand.InternalExecute(CommandBehavior behavior, IDisposable disposable, Int32 startRecord, Int32 maxRecords, Boolean nonQuery)
at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior, Boolean nonQuery)
at Devart.Data.Oracle.OracleCommand.ExecuteNonQuery()
at Devart.Data.Oracle.DurableInstancing.am.a(Boolean A_0)
at Devart.Data.Oracle.DurableInstancing.c.c()
Thank you.
- Wed 08 Jun 2011 14:33
- Forum: dotConnect for Oracle
- Topic: Workflow Instance Store bugs
- Replies: 7
- Views: 3267
Workflow Instance Store bugs
Hello,
I have found two issues in your Workflow Instance Store.
The first one is about the GetExpirationTime function. I have an exception InstancePersistenceCommandException (The execution of the InstancePersistenceCommand named {urn:schemas-microsoft-com:System.Activities.Persistence/command}SaveWorkflow was interrupted by an error) with an Oracle error ORA-01841. I think the compute of the expiration date is not correct in the GetExpirationTime function and need to be changed into "return sysdate + offsetInMilliseconds / (24*60*60*1000);"
The second one is an InstanceNotReadyException exception when I call the LoadRunnableInstance on an instance of WorkflowApplication class. The exception message is "No runnable workflow instances were found in the InstanceStore for this WorkflowApplication to load."
I have found no workaround to manage this issue. I think that the problem is not how the workflowapplication instance is configured, because the same code using the SqlWorkflowInstanceStore works without problems. Can you help me?
Kind Regards!
I have found two issues in your Workflow Instance Store.
The first one is about the GetExpirationTime function. I have an exception InstancePersistenceCommandException (The execution of the InstancePersistenceCommand named {urn:schemas-microsoft-com:System.Activities.Persistence/command}SaveWorkflow was interrupted by an error) with an Oracle error ORA-01841. I think the compute of the expiration date is not correct in the GetExpirationTime function and need to be changed into "return sysdate + offsetInMilliseconds / (24*60*60*1000);"
The second one is an InstanceNotReadyException exception when I call the LoadRunnableInstance on an instance of WorkflowApplication class. The exception message is "No runnable workflow instances were found in the InstanceStore for this WorkflowApplication to load."
I have found no workaround to manage this issue. I think that the problem is not how the workflowapplication instance is configured, because the same code using the SqlWorkflowInstanceStore works without problems. Can you help me?
Kind Regards!
- Wed 19 Jan 2011 07:33
- Forum: dotConnect for Oracle
- Topic: ORA-01453 exception
- Replies: 5
- Views: 1368
Thank you StanislavK
Setting the "Validate Connection" connection string parameter to true solved the issue
Please, consider to set this parameter to true as default, because I think that current behaviour is an unexpected one. I think that if a connection become invalid, it should be recycled, and should not be allowed to reuse it.
Where can I find a list of all parameters available for the connection string? I check you documentation, but the OracleConnectionStringBuilder class doesn't have the "Validate Connection" parameter.
Setting the "Validate Connection" connection string parameter to true solved the issue
Please, consider to set this parameter to true as default, because I think that current behaviour is an unexpected one. I think that if a connection become invalid, it should be recycled, and should not be allowed to reuse it.
Where can I find a list of all parameters available for the connection string? I check you documentation, but the OracleConnectionStringBuilder class doesn't have the "Validate Connection" parameter.
- Mon 17 Jan 2011 07:34
- Forum: dotConnect for Oracle
- Topic: ORA-01453 exception
- Replies: 5
- Views: 1368
ORA-01453 exception
The steps to reproduce the issue are
1) Execute an insert statement using classic ADO.NET DbCommand and your provider. This command must fail due to duplicated primary key violation
2) Execute a delete operation using entity framework and your provider
You should obtain an ORA-01453 exception if the connection string has the option "Transaction Scope Local" = true. The issue occurs on Oracle 10.2.0.4.0, not on Oracle 11.2.0.1.0
I send you as attachment an example solution using the support form.
Please send me a feedback asap.
Thank you
1) Execute an insert statement using classic ADO.NET DbCommand and your provider. This command must fail due to duplicated primary key violation
2) Execute a delete operation using entity framework and your provider
You should obtain an ORA-01453 exception if the connection string has the option "Transaction Scope Local" = true. The issue occurs on Oracle 10.2.0.4.0, not on Oracle 11.2.0.1.0
I send you as attachment an example solution using the support form.
Please send me a feedback asap.
Thank you
- Wed 12 Jan 2011 12:39
- Forum: dotConnect for Oracle
- Topic: Visual Studio 2010 issue with toolbox integration enabled
- Replies: 5
- Views: 1363
- Sat 08 Jan 2011 08:42
- Forum: dotConnect for Oracle
- Topic: Visual Studio 2010 issue with toolbox integration enabled
- Replies: 5
- Views: 1363
Visual Studio 2010 issue with toolbox integration enabled
Installing dotConnect for Oracle with the option "Design time assemblies support", I got issues using Silverlight designer in Visual Studio 2010: I cannot no more drag and drop controls from toolbox to the designer.
Can anyone help me ?
I have this problem with 6.00.70 and also previous versions.
Can anyone help me ?
I have this problem with 6.00.70 and also previous versions.
- Sat 08 Jan 2011 08:30
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
- Thu 18 Nov 2010 14:00
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
I have just sent you the test project. Please, let me updated. It's very important for us to resolve this issue because we have invested on your oracle provider to use oracle dbms.AndreyR wrote:We had a similar user request, but I failed to reproduce the problem with pooling.
Could you please send us (support * devart * com, subject "Transaction Pooling Error") a small test project illustrating the issue?
Please note, however, that multi-threaded usage of DbConnection object isn't safe (because each non-static DbConnection instance is not thread-safe).
- Thu 18 Nov 2010 09:34
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
Hi AndreyR, can you update me about the transaction issues? We need a solution because perfomance are really ugly using your provider with connection pooling disabled.AndreyR wrote:Thank you for the report, we have reproduced the situation.
I will let you know as soon as the problem is fixed.
We are investigating the problem with TransactionScope.
I will post here about teh results of our investigation.
- Tue 26 Oct 2010 09:00
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
Thank you very much!AndreyR wrote:We have fixed the problem with the ON DELETE NO ACTION problem.
This fix is available in the latest 5.70.180 build.
You can download a trial version from here or get a non-trial version in Registered Users' Area if you are a registered user.
- Fri 01 Oct 2010 09:30
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
Updating to the version 5.70.170, the ON DELETE CASCADE has been added to the generated script, but when there is no action associated to the ON DELETE, DDT template generates the script "ON DELETE NO ACTION". This is not correct and I get an error ORA-00905 Missing keyword.
When there is not action associated to the DELETE, it should not be specified in the script because it is the default behaviour.
Can you update me about the other problems?
Thank you.
When there is not action associated to the DELETE, it should not be specified in the script because it is the default behaviour.
Can you update me about the other problems?
Thank you.
- Wed 18 Aug 2010 15:06
- Forum: dotConnect for Oracle
- Topic: DELETE CASCADE missing using generate database from model
- Replies: 12
- Views: 2337
I have just tried using the last version 5.70.152 build, but there is the same problem.
The SSDL contains the OnDelete action, but the generated SQL doesn't have the ON DELETE CASCADE ACTION set.
I am using Visual Studio 2010 with Entity Framework 4 and POCO Generation.
I have also another issue to signalize you using transactions.
I have two threads that performs queries. When in one thread there are both operations in a TransactionScope and operations without TransactionScope on the same data, I get an exception ORA-24776.
Performing some debugging I have found that when a transaction is disposed (calling complete or not), sqldeveloper shows that the corresponding session is not closed immediately as I expected. So when the other thread perform some operation, I receive a ORA-24776 exception (cannot start a new transaction).
I suppose the problem is due to connection pooling, so I tried to disable connection pooling in the connection string and it works. Setting Pooling=false, the transactions work as expected. I also tried to open and close the EntityConnection manually and it works also with Pooling=true.
So using both Pooling=true and managing connection automatically, I get the exception ORA-24776.
The issues exists both in Oracle 11.2.0.1 and Oracle 10.2.0.1.
Can I send you a little solution sample that shows the two issues?
The SSDL contains the OnDelete action, but the generated SQL doesn't have the ON DELETE CASCADE ACTION set.
I am using Visual Studio 2010 with Entity Framework 4 and POCO Generation.
I have also another issue to signalize you using transactions.
I have two threads that performs queries. When in one thread there are both operations in a TransactionScope and operations without TransactionScope on the same data, I get an exception ORA-24776.
Performing some debugging I have found that when a transaction is disposed (calling complete or not), sqldeveloper shows that the corresponding session is not closed immediately as I expected. So when the other thread perform some operation, I receive a ORA-24776 exception (cannot start a new transaction).
I suppose the problem is due to connection pooling, so I tried to disable connection pooling in the connection string and it works. Setting Pooling=false, the transactions work as expected. I also tried to open and close the EntityConnection manually and it works also with Pooling=true.
So using both Pooling=true and managing connection automatically, I get the exception ORA-24776.
The issues exists both in Oracle 11.2.0.1 and Oracle 10.2.0.1.
Can I send you a little solution sample that shows the two issues?