This is the documentation for Bamboo 5.5. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

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.

 

Important

  • 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 no longer bundled since Bamboo 5.1. You need to download and install the driver from the Oracle website yourself.

On this page:

Related pages:

Troubleshooting Databases

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. Ensure that the user has the following permissions:

    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.

    SettingDescription
    Driver Class NameType: oracle.jdbc.driver.OracleDriver
    Database URLType the URL where Bamboo will access your database, e.g. jdbc:oracle:thin:@localhost:1521:SID. For syntax, please see the Oracle documentation.
    UsernameType the username that Bamboo will use to access your database.
    PasswordType 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. Click Continue.

Screenshot Setup Datasource Connection

  • No labels

4 Comments

  1. What happens when the Oracle schema password is updated? I can't see a way to change this within the Bamboo configuration pages.

  2. Hi Paul,

    I've since re-installed Bamboo using the integrated database but will check once I switch back to Oracle. One thing though, I wouldn't have thought the password would be in a config file in bare text.

    Going forward, I think it's up to the user (i.e. me) to ensure that whatever database I use for Bamboo reinstates the same password after it expires.

    Cheers!

    Lee

    1. Hi Lee, that sounds like you have it sorted. I agree about the password in plaintext... I'll investigate that.