Search the JIRA 5.0.x Beta and RCs Documentation:

Index
Downloads (PDF, HTML & XML formats)
Other versions

This documentation relates to JIRA 5.0.x Beta and RCs only.
The latest official version is JIRA 4.4.x
If you are using JIRA 4.4.x either view this page in the JIRA 4.4.x documentation or visit the JIRA 4.4.x documentation home page.
Skip to end of metadata
Comment: Corrected links that should have been relative instead of absolute.
Go to start of metadata

This page has general notes on connecting JIRA to Oracle. It supplements the official Oracle installation documentation.

Labels:
None
Edit Labels

6 Comments

Hide/Show Comments

  1. Apr 15, 2008

    Kirill Frolov

    I've used ojdbc14.jar from Oracle 10.2.0.3 client.

    The problem I've experienced is that it didn't wont to connect falling out with exception of "Locale not supported".

    It turned out that Regional Setting applet must use English on BOTH Regional Options AND Advanced tabs.

    Agter that change everything is quite ok.

  2. Oct 01, 2008

    Grunthos The Flatulent

    Here's an idea. Instead of putting this on your web page:

    We thus strongly recommend avoiding Oracle if you have any choice in the matter, for the benefit of all concerned. 

    How about coding a product that works properly with Oracle?

    This app has the issue working with Oracle .

    1. Oct 02, 2008

      Andrew Lui [Atlassian Technical Writer]

      Hi Grunthos,

      Thanks for your feedback on the documentation. Given the past experiences of our customers who have used Oracle, we must continue to strongly support this recommendation. However, you are quite correct in saying that this warning has been badly worded and can definitely be improved.

      I will update the page accordingly.

      Kind Regards,
      Andrew

  3. Sep 04, 2009

    Anonymous

    Does anybody know whether the Oracle password can be encrypted in the server.xml file ?

    1. Sep 04, 2009

      Pierre-Philippe Bastin

      This is required by most infrastructure or security managers. They don't like clear passwords in flat files ...

      If there is no other solution, could you give some arguments that help convince them ...

      Thanks

      1. Mar 25, 2010

        Mark Lassau

        The Tomcat server needs a clear text password in order to make the DB connection.
        In theory, it could use two-way encryption to allow an encrypted password to be in server.xml, which it
        could decrypt in order to make the encryption.
        However, anyone with half a brain could also decrypt the password, so you just be led into a false sense of security.
        It is better to admit that the server.xml is a sensitive file, and make it clear that it needs to be protected.

        For more discussion see (eg) http://stackoverflow.com/questions/129160/how-to-avoid-storing-passwords-in-the-clear-for-tomcats-server-xml-resource-defi