@Tom Your SQL looks OK at a quick glance.

The documentation subtask of this issue links to this page:
http://confluence.atlassian.com/display/JIRA/JIRA+4.0+Database+Schema+Changes+for+MySQL+and+Oracle

Which contains SQL to manually update your DB which looks like this:

ALTER TABLE PROPERTYTEXT ADD TEMPVALUE CLOB;
UPDATE PROPERTYTEXT SET TEMPVALUE = PROPERTYVALUE;
ALTER TABLE PROPERTYTEXT DROP COLUMN PROPERTYVALUE;
ALTER TABLE PROPERTYTEXT RENAME COLUMN TEMPVALUE TO PROPERTYVALUE;

Great!

On that note Tom, since you are on Oracle and I know you have some issues with GH performance, you should have a look at: GHS-1398.

Cheers,
JC

Working with 3.13.5

Used following statement

CREATE TABLE JIRA.PROPERTYTEXT_TMP AS
SELECT * FROM JIRA.PROPERTYTEXT
/

COMMIT
/

DROP TABLE JIRA.PROPERTYTEXT CASCADE CONSTRAINTS
/

CREATE TABLE JIRA.PROPERTYTEXT (
ID Number(18) NOT NULL,
PROPERTYVALUE CLOB,
CONSTRAINT PK_PROPERTYTEXT PRIMARY KEY (
ID
)
)
/

INSERT INTO JIRA.PROPERTYTEXT
SELECT * FROM JIRA.PROPERTYTEXT_TMP
/

COMMIT
/

and modified the EntryModel.xml appropriately, and all is working fine. Going into production tomorrow morning with it.

Yes, that's the right item.

The database will not be updated automatically. JIRA will simply complain in the logs if the existing database column is of different type than the one it expects (i.e. the one defined in entitymodel.xml and the relevant fieldtype file).

Cheers,
Anton

Is this the item I need to fix?

<entity entity-name="OSPropertyText" table-name="propertytext" package-name="">
<field name="id" type="numeric"/>
<field name="value" col-name="propertyvalue" type="very-long"/>
<prim-key field="id"/>
</entity>

Second, do I have to manually update a column in the database? Will it update automatically. I am about to migrate from 3.12 to 3.13, so I thought it would be a good time to make this change and see how it goes.

Thanks, I will try that, but something like this needs to be handled sooner then later.

Is this likely to get fixed in 3.1x of something. If not, I think it is time for us to start looking for a replacement. We need at least project management lite and Green hopper gives us this. This isn't that hard of a fix to make. Lot's of testing, but easy fix.

This is a BLOCKER for anyone using greenhopper and Oracle.

I am dead in the water as far as Green Hopper is concerned. This is a BLOCKER for me!!!!