[vwnc] oracle 10 & oraEXDI errors?

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

I use Oracle a lot and I haven't run into that, but it may be an issue with specific driver and/or database versions. I'd suggest both contacting support and seeing if you can reproduce the problem using the most recent version. There have been a number of changes and fixes to the database code. If they do fix the problem, it may be possible to back-port the current drivers to 7.4.1 without needing to do a full upgrade. I doubt that they would have a lot of dependencies on base image changes.

At 03:37 AM 11/27/2008, Mark Plas wrote:

Content-Language: en-US
Content-Type: multipart/alternative;
         boundary="_000_5044A277360FA74383740D339171BEA2404A84E64Emgxmailbrusse_"

Hi,
 
Since some time our customers have unpredictable crashes when doing queries on Oracle 10 using our VW7.4.1 application. What they all seem to have in common is that the problems started since they shifted from Oracle 9 to Oracle 10.
 
The error they get is ORA-01455: converting column overflows integer datatype.
 
This error msg could however be wrong according to this site: http://www.edhanced.com/ask-mred/?q=node/view/204 which says that the msg might have to be OCI-01455.
 
The problem is the error cannot be reproduced in a predictable way. The users just sometimes crash. In an exceptional case where we could actually see the error happening, we weren’t able to reproduce it, even when we tried to reexecute the exact same SELECT query that caused the crash.
 
The SQL query is not at all complex. It is just something like:
 
      Select col1, col2, col3 from table where primary_key=:1
 
The error does seem to occur typically in situations where a lot of small statements are being executed. A similar error also occurs when trying to insert a single row in a table. The message then is ORA-01401: inserted value too large for column. Again, in this case, simply reexecuting the statement works.
 
I’ve already checked the OracleBuffers on OracleSession to see whether they contain the correct datatypes when transferring data, and they seemed ok. But then again, I’ve only been able to check this once since the problem cannot be reproduced on demand.
 
As I said, all of this started happening when they upgraded from oracle 9 to oracle 10. the oracle clients were also all updated to oracle 10, so that isn’t the problem. (There are definitely problems with oracle 9 clients connecting to oracle 10).
 
Could this be in a way related to the Oracle EXDI support for oracle 10 in VW? From the symptoms I’m inclined to think the problem could have to do with some memory corruption. Perhaps some things changed between the oracle9 and oracle10 drivers that are not covered by the ora EXDI?
 
Is there perhaps a separate Oracle EXDI for oracle 10? We still use the same one as the one they used on oracle 9. I’m not aware that there is another parcel for oracle10 support.
 
All of this is on VW7.4.1.
 
I know some of you also use oracle&VW. Have you had similar problems?
 
Any help is most welcome.
 
Thanks,
Mark
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc