Creating a Content Manager Enterprise Edition library server database with the Oracle DBCA template

Edit online

The library server DBCA template predefines an Oracle configuration for the Content Manager Enterprise Edition library server.

About this task

The AdvSetup/Oracle/ICM_Library_Server*.dbt template helps create a new Content Manager Enterprise Edition library server database.

By default, this template predefines the following configurations:
  • Sets Oracle initialization parameters to the minimum required settings for the library server.
  • Creates standard Content Manager Enterprise Edition library server 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, 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 administrator user's default table space is ICMLFQ32 and temporary table space is TEMP.
  • Creates all database files in standard Oracle directories in ORACLE_HOME and ORACLE_BASE.
  • Enables Oracle Text. If you never plan to use the text search feature, you can disable the text search feature, reduce the job_queue_processes init.ora parameter by 1, and remove the ICMLSTXT table space that is dedicated for Oracle Text.
  • Enables Oracle XML DB. Make sure not to deselect Oracle XML DB in the DBCA template. Starting with Oracle 11gR2, a new security model governs a database user's ability to access hosts that are external to the Oracle database server by using the UTL* packages. Therefore, the security model now requires an Oracle XML DB installation and additional new privileges (CONNECT and RESOLVE) for the library server schema owner.
  • Runs the icmlsschemas.sql script to create the Oracle library server administrative database user and the library server connection database user 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 space, default temporary table space, and a default password of password.
You can modify the sample DBCA templates if you maintain the requirements and considerations that are noted in this section.
Important: If you change any default table space names in the DBCA template, remember to properly set the values for ICM_LS_DEFAULT_TBLSPC and ICM_LS_TEMP_TBLSPC in the Oracle DBCA File Location Variables window.

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

Procedure

The following steps walk you through the creation of a Content Manager Enterprise Edition library server database by using the DBCA template for guidance:

  1. Copy the DBCA templates from the Content Manager Enterprise Edition directory AdvSetup/Oracle to the ORACLE_HOME/assistants/dbca/templates directory.
    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 icmlsschemas.sql file (for example, to the ORACLE_HOME/assistants/dbca/templates directory path).
  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 the library server.
    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) and the library server connection user (icmconct). Write the passwords in your Oracle configuration worksheet.
    If you change the name of the icmadmin or icmconct 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 file from the Custom Scripts page. The library server template requires the icmlsschemas.sql script to create the library server schemas with the proper database privileges.
  9. In the Initialization Parameters window, the template sets the init.ora file parameters to the minimum requirements for the library server. 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 fails to register the instance with the Oracle listener, and Content Manager Enterprise Edition fails to connect to the database.
  11. In the Initialization Parameters page, if you plan to share the Content Manager Enterprise Edition library server database with the resource manager or any IBM® Records Manager repositories, then click the Character sets tab and set the database character set to Unicode.
    Note that Unicode is required for any database besides a stand-alone library server.
  12. 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.
  13. 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 the library server administrator password.

What to do next

During the Content Manager Enterprise Edition installation, you are prompted for a specific number of table space names. If you created fewer than this specific number, then you must repeat the use of a table space name.

If you plan to create the resource manager database on a separate machine, you must run DBCA on that machine by using the resource manager database template.