Creating an Oracle database

Create an Oracle database before installing Application Engine.

About this task

Tip: If you need to know which database versions are supported for your installation, use this IBM® Support External link opens a new window or tab page to generate a software compatibility report.

Procedure

  1. Connect to your local or remote database server by running the following command:
    sqlplus oracle_user_ID/oracle_password@oracle_instance_name as sysdba
  2. To create the Application Engine database, run the following command on your local or remote database server:
    -- create a new user
    CREATE USER @APP_ENGINE_DB_USER_NAME@ IDENTIFIED BY @APP_ENGINE_DB_PASSWORD@;
    
    -- grant privileges to system and objects
    grant create session to @APP_ENGINE_DB_USER_NAME@;
    grant alter session to @APP_ENGINE_DB_USER_NAME@;
    grant create table to @APP_ENGINE_DB_USER_NAME@;
    -- Note:
    -- 1. @DB_DIR@ is a folder in the PV.
    -- 2. You must specify the DATAFILE or TEMPFILE clause unless you have enabled Oracle Managed Files by setting a value for the DB_CREATE_FILE_DEST initialization parameter. 
    CREATE TABLESPACE @APP_ENGINE_DB_TBLSPACE@
       DATAFILE '@DB_DIR@/@APP_ENGINE_DB_USER_NAME@/@APP_ENGINE_DB_TBLSPACE@.dbf' SIZE 200M REUSE
       AUTOEXTEND ON NEXT 20M
       EXTENT MANAGEMENT LOCAL
       SEGMENT SPACE MANAGEMENT AUTO
       ONLINE
       PERMANENT
     ;
    CREATE TEMPORARY TABLESPACE @APP_ENGINE_DB_TBLSPACE@_TEMP
       TEMPFILE '@DB_DIR@/@APP_ENGINE_DB_USER_NAME@/@APP_ENGINE_DB_TBLSPACE@_TEMP.dbf' SIZE 200M REUSE
       AUTOEXTEND ON NEXT 20M
       EXTENT MANAGEMENT LOCAL
    ;
    
    ALTER USER @APP_ENGINE_DB_USER_NAME@ QUOTA UNLIMITED ON @APP_ENGINE_DB_TBLSPACE@;
     
    ALTER USER @APP_ENGINE_DB_USER_NAME@ DEFAULT TABLESPACE @APP_ENGINE_DB_TBLSPACE@ TEMPORARY TABLESPACE @APP_ENGINE_DB_TBLSPACE@_TEMP;
    
    grant select any table to @APP_ENGINE_DB_USER_NAME@;
    grant update any table to @APP_ENGINE_DB_USER_NAME@;
    grant insert any table to @APP_ENGINE_DB_USER_NAME@;
    grant drop any table to @APP_ENGINE_DB_USER_NAME@; 
    where
    • @APP_ENGINE_DB_USER_NAME@ is the username that the Application Engine uses to connect to the database.
    • @APP_ENGINE_DB_PASSWORD@ is the password that the Application Engine uses to connect to the database.
  3. If Business Automation Application data persistence is enabled, it needs one object store from IBM FileNet® Content Manager. You can either reuse the existing one and specify it for the object_store_name parameter or create one named something like AEOS, which stands for application engine object store.
    • To create the databases for IBM FileNet Content Manager, create a database for the Content Platform Engine Global Configuration Database (GCD) and one database for the content stores. For more information, see Preparing the databases.
    • To create one object store for Business Automation Application data persistence but not reuse the existing one, you must create one database, such as one named AEOSDB. For more information, see Create Oracle table spaces for a Content Platform Engine object store External link opens a new window or tab.
  4. Optional: To use your own JDBC driver, complete the following steps.
    1. Package your JDBC files into a compressed file and use the sc_drivers_url configuration parameter to download them from an accessible web server. Follow the steps in Optional: Preparing customized versions of JDBC drivers and ICCSAP libraries.
    2. Add the customized JDBC driver information to the configuration parameters. Set application_engine_configuration.use_custom_jdbc_drivers to true in the configuration parameters. See Application Engine configuration parameters.

What to do next

To protect the configuration data you are going to enter, see Creating secrets to protect sensitive configuration data.