JIRA 4.3 : Configuring Datasource for Oracle 10g JDBC drivers
This page last changed on Apr 26, 2010 by rosie@atlassian.com.
When using JIRA with Oracle, the Oracle 10g JDBC driver needs to have the SetBigStringTryClob property set to true to store text of unlimited size in the database. If this property is not set, you will have problems modifying JIRA workflows and storing large (over 32k) text strings. The SetBigStringTryClob property needs to be set in the application server, where the database connection is defined (the 'datasource' definition). The definition depends on the application server that you are using. Please refer to one of the sections below that is applicable to your application server to determine what to add to the datasource definition. The same thing applies to I-Net's JDBC driver, except the property is called streamstolob. Tomcat 5.5 and 6.0 (JIRA Standalone)
Modify the section where JIRA is configured, usually conf/Catalina/localhost/jira.xml or conf/server.xml (in JIRA Standalone): <Context path="/jira" docBase="path/to/atlassian-jira-3.11.war"> <Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource" username="...." password="...." driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@<database host machine>:<port>:<SID>" connectionProperties="SetBigStringTryClob=true" /> <Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction" factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/> <Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/> </Context> |
![]() |
Document generated by Confluence on Mar 27, 2011 18:52 |