Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

These instructions will help you connect Bamboo to an Oracle 11g database. Oracle 10g is no longer a supported database for use with Bamboo and the 11.2.x drivers from Oracle do not support 9i.

Bamboo provides two ways to connect to an Oracle database — using JDBC or using a datasource. JDBC is generally simpler and is the recommended method.

このページの内容

重要

  • For JDBC or JNDI connections, please ensure that the user connecting to the database will have total permissions over it. This includes DBMS_LOB package and other resources available.
  • Note that the JDBC driver for Oracle 11g (Oracle 11.2.0.1.0) is bundled with Bamboo. You do not have to download and install the driver.

Configuring Oracle

  1. Ensure that you have a database instance available for Bamboo (either create a new one or use an existing one).
  2. Within that database instance, create a user which Bamboo will connect as (e.g. bamboo-user). (tick) Remember this database user name, as it will be used to configure Bamboo's connection to this database.
    (info) When you create a user in Oracle, Oracle will create a 'schema' automatically.

    create user bamboo-user identified by password;
    
  3. ユーザーが次の権限を持つことを確認します :

    grant connect, resource, create table to bamboo-user;
    

Connecting using JBDC

To connect Bamboo to a Oracle database, using JDBC:

  1. Run the Setup Wizard and choose the Custom Installation method.
  2. At the 'Choose a Database Configuration' step, choose External Database > Oracle 11g. The 'Select Database Connection' screen will appear.
  3. Select Direct JDBC connection. The 'Setup JDBC Connection' screen will appear as shown in the screenshot below.

    設定説明
    Driver Class NameType: oracle.jdbc.driver.OracleDriver
    データベース URLType the URL where Bamboo will access your database, e.g. jdbc:oracle:thin:@localhost:1521:SID. For syntax, please see the Oracle documentation.
    ユーザ名Type the username that Bamboo will use to access your database.
    パスワードType the password that Bamboo will use to access your database.
  4. Select Overwrite existing data if you wish Bamboo to overwrite any tables that already exist in the database.
  5. Click Continue.

Screenshot: Setup JDBC Connection (Oracle)

Connecting using a datasource

To connect Bamboo to a Oracle database, using a datasource:

  1. Configure a datasource in your application server (consult your application server documentation for details). For the syntax of the JDBC URL to use, please see the Oracle documentation.
  2. Run the Setup Wizard and choose the Custom Installation method.
  3. At the 'Choose a Database Configuration' step, choose External Database > Oracle 11g.
  4. Select Connect using a datasource (configured in the application server). The 'Setup Datasource Connection' screen will appear as shown in the screenshot below.
  5. In the JNDI name field, type the JNDI name of your datasource, as configured in your application server.
    (warning)If java:comp/env/jdbc/DataSourceName doesn't work, try jdbc/DataSourceName (and vice versa).
  6. Select Overwrite existing data if you wish Bamboo to overwrite any tables that already exist in the database.
  7. 続行をクリックします。

Screenshot Setup Datasource Connection

  • ラベルなし

5 Comments

  1. Anonymous

    what size do i need for std. installation?

    1. Anonymous

      File a support ticket.  We did, and they looked at us like deers in the headlights.

      The more tickets we get in to Atlassian, the more they're likely to start improving this stuff.

  2. Anonymous

    Seems that the Oracle jdbc drivers are not included if you use the WAR installation method.

  3. Anonymous

    Is there any way to create the database using DDL scripts?  I'm at a loss for how to create a large set of build server farm databases without going through this painful process every single time (of course, I could build one and do an export, and reimport for every additional database I want to build, but that strikes me as ghetto).

    1. Anonymous

      Unfortunately, there's not.  We faced the same challenge, and raised the issue with support for those EXACT same concerns.  The best thing they could do, they said, was to file it as an enhancement request.

      What we've ended up doing is what you suggested - creating the database on a test instance, exporting out the DDL as the "gold master", and reimporting it in every future buildout we needed.  Frankly, this is one of the great short-sighted visions of this product.  Large-scale, enterprise installations.