The Problem
My coworker and I were installing a fresh setup of DSpace on an existing Oracle 10g installation. First of all, deploying the application via the Oracle Application Server was not working at all. Eventually we decided to make an exception for DSpace (from our normal deployment procedures in my office). We set up Apache Tomcat on RedHat Enterprise Linux 5 and the application finally deployed.
We started testing the application and things looked fine. Very soon we realized that when we tried to add content to DSpace, the content creation process was not functioning properly. Null values were being passed through the content creation process, and content could not be saved to the database due to Null Pointer Exceptions.
We searced all of DSpace's documentation, Googled, re-Googled, and Googled the terms again looking for what could be throwing the error.
The Solution
After about a week of searching, my coworker stumbled upon a Sourceforge mailing list thread which caught our attention. Our existing database was set up using a different character encoding (ISO-8859-1, I believe) and our DBA's were unwilling/unable to set up the dspace tables as utf-8.
If the database is not set up utf-8 there are major problems saving to the database. My coworker and I were unable to get around these issues. We fixed the problem by setting up a fresh PostreSQL database for DSpace using utf-8. It works like a charm now.
I've been working on two articles in the DSpace wiki to better document the problem that it seemed a lot of people out there had, no one ever left a solution for it though.
So hopefully if others are having this problem this post and the wiki could help them. Pleae comment if it helps you. Thanks!
Good morning. Sorrow was like the wind. It came in gusts. Help me! Can not find sites on the: Botox for excessive sweating. I found only this - stop excessive facial Sweating. Excessive sweating is also known as the hyperhidrosis in the medical terms, is the medical condition during which body parts of the human body sweats more than basic needs in the human body. If you have an excessive sweating problem, you. THX ;-), Keturah from Zaire.
Thank you very much Mr.oreo_masta for your article.Any kind of problem of
database make very harm of the database users.I think it will be very
helpful for oracle database users and also all dba.
I was able to duplicate this bug exactly. It occurs when a line such as:
/*!50020 DEFINER=`user`@`%`*/
when "user" is NOT a valid user. This happens when you export a stored procedure from one
db and move it to another with different users.
Removing the offending DEFINER lines from the creates of the stored procedures fixes it.