Re: Problem saving to a BLOB field after switching to ORACLE 11g driver
Re: Problem saving to a BLOB field after switching to ORACLE 11g driver
- Subject: Re: Problem saving to a BLOB field after switching to ORACLE 11g driver
- From: Chuck Hill <email@hidden>
- Date: Tue, 11 May 2010 10:34:17 -0700
On May 11, 2010, at 8:57 AM, Ricardo J. Parada wrote:
We upgraded ORACLE to 11g and so I switched to the 11g driver. But
now we started getting these exceptions:
[2010-05-11 07:31:24,579] ERROR
com.webobjects.eoaccess.EOGeneralAdaptorException: Invalid
argument(s) in call
at
com
.webobjects
.eoaccess
.EODatabaseContext
._exceptionWithDatabaseContextInformationAdded
(EODatabaseContext.java:4504)
at
com
.webobjects
.eoaccess.EODatabaseContext.performChanges(EODatabaseContext.java:
6216)
at
com
.webobjects
.eocontrol
.EOObjectStoreCoordinator
.saveChangesInEditingContext(EOObjectStoreCoordinator.java:376)
at
com
.webobjects
.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3192)
at er.extensions.eof.ERXEC._saveChanges(ERXEC.java:1085)
at er.extensions.eof.ERXEC.saveChanges(ERXEC.java:1007)
...
I suspect it is related to BLOB fields because it happens right
after EOF issues SQL to insert into a table with a BLOB field. The
SQL looks something like this:
INSERT INTO MIME_CONTENT(DEFAULT_DOWNLOAD_FILE_NAME, MIME_TYPE,
CREATION_DATE, MIME_CONTENT, MIME_CONTENT_ID) VALUES (?, ?, ?,
EMPTY_BLOB(), ?)" withBindings:
1:"BasicAdHocReport.csv"(defaultDownloadFileName), 2:"text/comma-
separated-values"(mimeType), 3:2010-05-11 11:17:00(creationDate),
4:496737(mimeContentID)
SELECT t0.MIME_CONTENT FROM MIME_CONTENT t0 WHERE t0.MIME_CONTENT_ID
= ? FOR UPDATE" withBindings: 1:496737(mimeContentID)
SELECT ... FOR UPDATE usually means that WO has gotten totally
confused. It should probably be doing something like
UPDATE MIME_CONTENT SET MIME_CONTENT = .... where MIME_CONTENT_ID =
496737
See http://www.google.ca/search?q=SELECT+"FOR+UPDATE"+webobjects&;
Often this indicates a difference between your prototypes and the
name / case of the data type that the JDBC driver is returning.
Chuck
Switching to the old driver makes the exception go away. Any wild
guess if this is an EOF problem or a driver problem?
For reference, the version of the oracle jdbc driver is 11.2.0.1.0.
Thanks for any help,
Ricardo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden