Creating a database by using the shared Oracle DBCA template

Edit online

The shared DBCA template configures Oracle for all Content Manager Enterprise Edition schemas (library server and resource manager) and the IBM® Records Manager schema in one database. This template also predefines a merged table environment by creating the Content Manager Enterprise Edition, IBM Records Manager, and Content Manager Enterprise Edition Records Enabler schemas.

About this task

The AdvSetup/Oracle/ICM_shared_database*.dbt template helps you to create a shared database. Use this DBCA template in the following scenarios:

  • A merged table environment that will use IBM Records Manager and Content Manager Enterprise Edition Records Enabler for security.
  • All Content Manager Enterprise Edition schemas (library server and resource manager) in one database on one Oracle server.
By default, this template predefines the following configurations:
  • Sets Oracle initialization parameters to the minimum required settings for all databases.
  • Creates standard table spaces with default sizes and reusable data files that can grow unbounded. By default, the table spaces are locally managed with automatic segment space management. The templates also configure automatic undo management. If you reduce the number of table spaces to four or fewer, make sure to increase the size of other table spaces to compensate. Never eliminate the SYSTEM, SYSAUX, TEMP, or UNDOTBS1 table spaces, and never decrease any table space sizes. By default, the library server and Content Manager Enterprise Edition Records Enabler administrator users' default table space is ICMLFQ32. The default table space for the resource manager is OBJPARTS. The default table space for IBM Records Manager is USERS, and cannot be modified. The USERS table space cannot be renamed. For all users, the default temporary table space is TEMP.
  • Creates all database files in standard Oracle directories under ORACLE_HOME and ORACLE_BASE.
  • Enables Oracle Text.
  • Runs the icmlsschemas.sql (library server), icmrmschema.sql (resource manager), irmschema.sql (IBM Records Manager), and cmreschema.sql (Content Manager Enterprise Edition Records Enabler) scripts to create all users with all required privileges. If the users already exist, the script assigns the required privileges to them. The script also sets the users' default table spaces, default temporary table spaces, and default passwords of password.
You can modify the sample DBCA templates if you maintain the requirements and considerations noted in this section.
Important: If you change any default table space names in the DBCA template, then remember to properly set the following values in the Oracle DBCA File Location Variables window:
  • ICM_LS_DEFAULT_TBLSPC
  • ICM_LS_TEMP_TBLSPC
  • ICM_RM_DEFAULT_TBLSPC
  • ICM_RM_TEMP_TBLSPC
  • IRM_TEMP_TBLSPC
  • CMRE_DEFAULT_TBLSPC
  • CMRE_TEMP_TBLSPC
Note that IBM Records Manager always requires the USERS table space to be the default table space.

For information about using DBCA, see the Oracle Database 2 Day DBA from docs.oracle.com.

The following steps walk you through the creation of an Content Manager Enterprise Edition shared database using the DBCA template for guidance:

Procedure

  1. Copy the DBCA templates from the Content Manager Enterprise Edition directory AdvSetup/Oracle to ORACLE_HOME/assistants/dbca/templates.
    Recommendation: Copy the SQL scripts to the same directory. Otherwise, you must specify their location in the DBCA File Location Variables window for DBCA_TEMPLATE_PATH.
  2. Start the Oracle DBCA from the ORACLE_HOME/bin directory. If you must start DBCA from any other directory, modify the DBCA file location variable, CM_SCRIPTS_PATH, to the new relative path where you copied the SQL scripts (for example, ORACLE_HOME/assistants/dbca/templates).
  3. In the Operations window, select Create a Database.
  4. In the Select Database Deployment Type window, select the ICM Library Server template (ICM_Library_Server*).
    This template will populate the rest of the DBCA pages with recommended default values.
  5. In the Database Identification window:
    1. Type a Global Database Name (for example, icmnlsdb.us.ibm.com), and then write it in your Oracle worksheet as the Oracle service name for both the library server and the resource manager.
    2. Clear Create as Container database.
  6. In the Management Options window, if you plan to use additional features, for example, if you select Configure the Database with Enterprise Manager (EM), then make sure to increase the job_queue_processes initialization parameter from the default setting of 1.
    Otherwise, database creation can fail. See your Oracle documentation for more information on Oracle database features requirements. The EM increases the table space sizes and requires more memory, processor, and disk space overhead.
  7. In the Database File Locations window, click File Location Variables and change your passwords for the library server administrative user (icmadmin), the library server connection user (icmconct), and the resource manager administrative user (rmadmin). Write the passwords in your Oracle configuration worksheet.
    If you change the name of the icmadmin, icmconct, or rmadmin user, write the new name in your Oracle configuration worksheet.
  8. In the Database Content window, clear the features that you do not need.
    Important: Do not remove the icmlsschemas.sql, icmrmschemas.sql, irmschema.sql, or cmreschema.sql file from the Custom Scripts page. The shared database template requires these scripts to create each schema with the proper database privileges.
  9. In the Initialization Parameters page, the template sets the initialization parameters to the minimum requirements for each schema. You can increase values for these parameters but should not decrease them. If you enable additional Oracle database features or plan to use the database with non-Content Manager Enterprise Edition applications, then you might need to increase these settings. By default, the template is configured to use Oracle automatic SGA memory management.
  10. If you created a new dedicated listener, then verify that your listener alias matches the one in the tnsnames.ora file by completing the following steps in the Initialization Parameters window:
    1. Click All Initialization Parameters.
    2. Click Show Advanced Parameters.
    3. In the LOCAL_LISTENER field, verify that the value matches the listener alias that you defined in your tnsnames.ora file. If you created a dedicated listener, then specify that listener here. This alias should also correspond to the listener port for the Content Manager Enterprise Edition database, for example: 
      LISTENER_ECM =
   (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT =  1522 ))
    If your LOCAL_LISTENER value does not match the alias in the tnsnames.ora file, then the Oracle PMON process will fail to register the instance with the Oracle listener, and Content Manager Enterprise Edition will fail to connect to the database.
  11. In the Initialization Parameters window, the database character set specified on the Character sets tab must be set to Unicode.
  12. Click the Memory tab. For Shared Memory Management, click Automatic. Alternatively, customize the Java Pool size to at least 120 MB.
  13. In the Database Storage window, do not rename the USERS or INDX table spaces. Otherwise, the Content Manager Enterprise Edition installation can fail.
  14. Confirm your options and click Finish to create the library server database.
    If you receive the following error, then verify that you set the COMPATIBLE parameter to the correct Oracle version in your init.ora/spfile file: ORA-12916: Cannot use default permanent table space with this release.
  15. In the DBCA Password Management window, make sure that all Content Manager Enterprise Edition users are unlocked, including the Oracle Text user CTXSYS. Make sure that the CTXSYS password is unique from all other administrator passwords.

Results

The shared database template is configured to assume the following configuration:
  • Standard Content Manager Enterprise Edition configuration with IBM Records Manager and Content Manager Enterprise Edition Records Enabler in table-merge mode with the library server.
However, the shared database template also supports the scenario where you run Content Manager Enterprise Edition products in stand-alone mode. In this configuration, set ICM_LS_ADMINID, ICM_RM_ADMINID and IRM_ADMINID to unique values. In such a configuration, Content Manager Enterprise Edition Records Enabler is not relevant because it requires a table-merge environment. All other requirements and guidelines still apply.