The resource manager DBCA template predefines an Oracle
configuration for the Content Manager EE resource
manager.
The AdvSetup/Oracle/ICM_Resource_Manager.dbt template
helps you to create a new Content Manager EE resource
manager database.
By default, this template predefines the following
configurations:
- Sets Oracle initialization parameters to the minimum required
settings for the resource manager.
- Creates standard Content Manager EE resource
manager 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, then make sure that you 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 resource manager administrator user's default table
space is OBJPARTS and temporary table space is TEMP.
- Creates all database files in standard Oracle directories in ORACLE_HOME
and ORACLE_BASE.
- Runs the icmrmschema.sql script to create
the Oracle resource manager administrative database user with all
required privileges. If the user already exists, then the script assigns
the required privileges to it. The script also sets the user's 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 noted in this section.
Important: If you change any default table space names in the
DBCA template, then remember to properly set the values for ICM_RM_DEFAULT_TBLSPC
and ICM_RM_TEMP_TBLSPC in the Oracle DBCA File Location
Variables window.
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 EE resource manager
database using the DBCA template for guidance:
- Copy the DBCA templates from the Content Manager EE 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.
- 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 icmrmschema.sql file (for example, ORACLE_HOME/assistants/dbca/templates).
- In the Operations window, select Create
a Database.
- In the Database Templates window, select
the ICM Resource Manager template (ICM_Resource_Manager*.dbt). This template will populate the rest of the DBCA pages with
recommended default values.
- In the Database Identification window, type
a Global Database Name (for example, icmrm.us.ibm.com)
and write it in your Oracle worksheet as the resource manager's Oracle
service name.
- 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.
- In the Database File Locations window, click File
Location Variables and change your password for the resource
manager administrative user (rmadmin). Write the password in your
Oracle configuration worksheet. If you change the name
of the rmadmin user, write the new name in your Oracle configuration
worksheet.
- In the Database Content window, clear the
features that you do not need.
- In the Initialization Parameters window,
the template sets the init.ora file parameters to the minimum requirements
for the resource manager. 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 EE applications, then you might
need to increase these settings. By default, the template is configured
to use Oracle automatic SGA memory management.
- If you created a new dedicated listener, then verify that your
listener alias matches the one in the tsnames.ora file
by completing the following steps in the Initialization
Parameters window:
- Click All Initialization Parameters.
- Click Show Advanced Parameters.
- In the LOCAL_LISTENER field,
verify that the value matches the listener alias that you defined
in your tsnames.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 EE 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 tsnames.ora file,
then the Oracle PMON process will fail to register the instance with
the Oracle listener, and Content Manager EE will
fail to connect to the database.
- In the Initialization Parameters window,
the database character set specified on the Character sets page
must be set to Unicode.
- 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.
- In the DBCA Password Management window,
make sure that all Content Manager EE users
are unlocked.
During the Content Manager EE installation,
you will be 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.
