Configuring Datasource for Oracle 10g JDBC drivers

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

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.

Refer to the Connecting JIRA to Oracle documentation for details on how to specify this property in JIRA's dbconfig.xml file.

Resolving Connection Closure Issues

If you experiencing problems with connections closing, you may be able to resolve them by configuring the Commons Database Connection Pool (DBCP) to detect broken connections and create replacement connections. Please read Surviving Connection Closures for instructions on how to do this.

According to the latest documentation, this property is no longer used or needed in Oracle 11+ driver, see http://docs.oracle.com/cd/E11882_01/java.112/e16548/oralob.htm#JJDBC28538:

"The SetBigStringTryClob connection property of Oracle Database 10g Release 1 (10.1) is no longer used or needed."

Last modified on Apr 19, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.