2 Running Oracle Application Server Repository Creation Assistant

2.1.1 Running Oracle Application Server Repository Creation Assistant from CD-ROM or DVD

To run Oracle Application Server Repository Creation Assistant from CD-ROM or DVD:

1. You run Oracle Application Server Repository Creation Assistant on the computer where the database is installed. The tool needs to access the binaries in the database's Oracle home.

   Ensure the listener for the existing database and the database itself are up and running before you start Oracle Application Server Repository Creation Assistant.

2. If your computer does not mount CD-ROMs or DVDs automatically, you need to set the mount point manually.

3. Insert the "Oracle Application Server Metadata Repository Creation Assistant and Utilities" CD-ROM into the CD-ROM drive, or insert the DVD into the DVD drive.

4. Start up Oracle Application Server Repository Creation Assistant from the CD-ROM or DVD:

   CD-ROM: prompt> mount_point/repCA/runRepca [parameters]
   DVD:    prompt> mount_point/repca_utilities/runRepca [parameters]
   
   

   The runRepca command accepts the following parameters.

   Table 2-1 Parameters for the runRepca Command

   Parameter	Required or Optional	Description
   -OH oracle_home	Required	Specifies the full path to the Oracle home directory of the database where you want to install the metadata repository. If you do not specify this parameter, Oracle Application Server Repository Creation Assistant prompts you to enter it.
   -LOGDIR logdir	Optional	Specifies the full path to the directory where Oracle Application Server Repository Creation Assistant can write log files. If not specified, Oracle Application Server Repository Creation Assistant writes the log files to the ORACLE_HOME/assistants/repca/log directory. Be sure you have write permission for the log directory.
   -REGNREALM realm	Optional	Specifies the realm in Oracle Internet Directory under which the OracleAS Metadata Repository is to be registered. You specify the realm using the realm's simple name. If this parameter is not specified, Oracle Application Server Repository Creation Assistant registers the OracleAS Metadata Repository under the root oracle context ("cn=oraclecontext"). In Oracle Database 10g, the Enterprise User Security feature requires databases to be registered under the oraclecontext of a realm in order to work with Oracle Delegated Administration Services and OracleAS Single Sign-On. To learn more about Enterprise User Security, see the Oracle Advanced Security Administrator's Guide in the Oracle Database 10g documentation library.
   -REGISTER	Optional	Specifies that Oracle Application Server Repository Creation Assistant should only register the metadata repository with Oracle Internet Directory. It will not install schemas into the database.
   -RAW	Optional	Specifies that the database uses raw devices for its database files.
   -RAC	Optional	Specifies that this is a Real Application Clusters database.
   -HELP	Optional	Displays help for the parameters.

   
   

   Example:

   runRepca -OH /opt/oracle/oradb -LOGDIR /opt/oracle/repca/logs
   
   

When to Use the -RAW and -RAC Parameters

You need to specify these parameters only if you are installing the OracleAS Metadata Repository in a database that uses raw devices or in a Real Application Clusters database.

Table 2-2 shows the possible scenarios, and the correct parameters to use in each scenario.

2.1.2 Running Oracle Application Server Repository Creation Assistant from a Hard Drive

To run Oracle Application Server Repository Creation Assistant from a hard drive:

1. Copy the Oracle Application Server Repository Creation Assistant files to your hard drive. Ensure that you can access the hard drive from the computer where the database is installed. Oracle Application Server Repository Creation Assistant needs to access the binaries in the database's Oracle home.

   Files you need to copy to your hard drive:

   • CD-ROM: copy the contents of the "Oracle Application Server Metadata Repository Creation Assistant and Utilities" CD-ROM to your hard drive.

   • DVD: copy the contents of the repca_utilities directory to your hard drive.

2. Ensure the listener for the existing database and the database itself are up and running before you start Oracle Application Server Repository Creation Assistant.

3. Start up Oracle Application Server Repository Creation Assistant from the hard drive:

   prompt> /path/to/hard/drive/repCA/runRepca [parameters]
   
   

   See Table 2-1 for a description of parameters.

2.5.1 Installation Overview

To create this environment, install Oracle Application Server as follows:

1. Install OracleAS Metadata Repository in your existing Real Application Clusters database.

   You use Oracle Application Server Repository Creation Assistant to do this. The specific steps depend on the storage type used by the Real Application Clusters database:

   • Section 2.5.2, "Installation Steps for Real Application Clusters Databases that Use a Cluster File System or Volume Manager"

   • Section 2.5.3, "Installation Steps for Real Application Clusters Databases that Use Raw Devices"

   
   

   Note: Do not register the OracleAS Metadata Repository with Oracle Internet Directory, because you have not installed Oracle Internet Directory yet.

   
   

2. Install the Identity Management components on non-clustered computers.

   You can install all the Identity Management components on a single computer, or you can distribute them over multiple computers. See the Oracle Application Server 10g Installation Guide for details.

   When the installer prompts for the database hostname in the "Specify Metadata Repository Login and Connect Information" screen, enter all the node names in the Real Application Clusters, plus the port numbers for each node. Use the format node:port. Separate the pairs with a comma character.

   For example, if you have three nodes (named node1, node2, and node3) in the cluster, and the listener listens on port 1521 for all nodes, then you would enter:

   node1:1521, node2:1521, node3:1521
   
   

3. Install Oracle Application Server middle tiers.

2.5.2 Installation Steps for Real Application Clusters Databases that Use a Cluster File System or Volume Manager

To install the OracleAS Metadata Repository in an existing Real Application Clusters database that uses a cluster file system (such as Oracle Cluster File System) or volume manager (such as Veritas or EMC), perform these steps:

1. Ensure that the database meets the requirements listed in Section 1.4, "Database Requirements".

2. Start up Oracle Application Server Repository Creation Assistant on the computer where the database is installed. See Section 2.1, "Starting Oracle Application Server Repository Creation Assistant". The parameters that you need in this case are -OH, -RAC, -LOGDIR if you want to specify a different log directory, and -REGNREALM if you want to register the OracleAS Metadata Repository in a specific realm. For example:

   runRepca -OH /opt/oracle/oradb -RAC -LOGDIR /opt/oracle/repca/logs -REGNREALM abcRealm
   
   

3. Follow the screens:

   Table 2-7 Steps for Installing OracleAS Metadata Repository in a Database that Uses Cluster File System or Volume Manager

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Database Connect	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Hostname and Port: Enter the names of the computers running the Real Application Clusters database and the port numbers used by the listener. Use the format host:port, and separate each host:port with a comma character: hostname1:port1, hostname2:port2, hostname3:port3, ... If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Example 1 (same domain): myhost:1521, myhost2:1521 Example 2 (different domain): myhost.mydomain.com:1521, myhost2.mydomain:1521 Service Name: Enter the service name of the database. The service name must include the database domain name. The service name must be the same for all instances in the cluster. Example: asdb.mydomain.com Click Next.
   3.	Warning: Check swap space	This screen informs you that you need at least 512 MB of free swap space. Click OK to continue, or click Cancel to exit Oracle Application Server Repository Creation Assistant.
   4.	Specify Tablespace Information	Use Same Directory for All Tablespaces: Select this option if you want to place all the files for all the tablespaces in the same directory. Specify the directory in the field below this option. Ensure that the directory has enough free space. Use Individual Directories for Each Tablespace: Select this option if you want to place the files for the tablespaces in different directories. Tablespaces: Expand the tree to view the tablespaces for each component. Select a tablespace to view or edit its associated datafile or size. Size: Select the largest size for a tablespace if you have applications that use the component heavily. If not, select the smallest size. Filename: Enter the file name for the database file. Example: portal.dbf Directory: Enter the directory where you want to put the database file for the tablespace. You can click the "..." button to browse your file system. Example (UNIX): /opt/oracle/dbfiles/ Example (Windows): C:\oracle\dbfiles\ Click Next.
   5.	Register with Oracle Internet Directory	If you already have an Oracle Internet Directory and know its connect information, select Register Now and enter the name of the computer where Oracle Internet Directory is running and the port number. Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. If you do not have an Oracle Internet Directory, or do not know its connect information, select Skip Registration. Click Next.
   6.	Specify Login for Oracle Internet Directory	This screen appears if you selected Register Now in the previous screen. Enter the Username and Password to log in to Oracle Internet Directory. The user must belong to the iASAdmins group. You can use the user's simple name (for example, jdoe) or the DN (for example, cn=orcladmin). If your Oracle Internet Directory contains more than one realm, you need to enter the realm that contains the specified user. Click Next.
   7.	Loading Repository	Oracle Application Server Repository Creation Assistant creates and populates the tablespaces and schemas.
   8.	Success	Click OK to exit Oracle Application Server Repository Creation Assistant.

   
   

4. Perform post-installation steps. See Section 2.9, "Post-Installation Steps".

2.5.3 Installation Steps for Real Application Clusters Databases that Use Raw Devices

To install the OracleAS Metadata Repository in a Real Application Clusters database:

1. Ensure that the database meets the requirements listed in Section 1.4, "Database Requirements".

2. Create raw devices for the OracleAS Metadata Repository.

   See Table 1-10 for a list of tablespaces for which you have to create raw devices, and their minimum sizes.

   The command to create raw devices is specific to the volume manager you are using. For example, if you using VERITAS Volume Manager, the command is vxassist.

3. Create a file to map the tablespaces to your raw devices.

   Each line in the file has the following format:

   tablespace_name=raw_device_file_path
   
   

   You can use the following sample file, replacing the raw device file pathswith your values. Append a "1" to the tablespace names, as shown in the sample file below.

   PORTAL1=/dev/vx/rdsk/oracle/mydb_raw_portal_128m
   PORTAL_DOC1=/dev/vx/rdsk/oracle/mydb_raw_portal_doc_64m
   PORTAL_IDX1=/dev/vx/rdsk/oracle/mydb_raw_portal_idx_64m
   PORTAL_LOG1=/dev/vx/rdsk/oracle/mydb_raw_portal_log_64m
   IAS_META1=/dev/vx/rdsk/oracle/mydb_raw_ias_meta_256m
   DISCO_PTM5_META1=/dev/vx/rdsk/oracle/mydb_raw_disco_meta_64m
   DISCO_PTM5_CACHE1=/dev/vx/rdsk/oracle/mydb_raw_disco_cache_64m
   DCM1=/dev/vx/rdsk/oracle/mydb_raw_dcm_256m
   DSGATEWAY_TAB1=/dev/vx/rdsk/oracle/mydb_raw_synd_64m
   WCRSYS_TS1=/dev/vx/rdsk/oracle/mydb_raw_clip_64m
   IP_DT1=/dev/vx/rdsk/oracle/mydb_raw_ip_dt_128m
   IP_RT1=/dev/vx/rdsk/oracle/mydb_raw_ip_rt_128m
   IP_LOB1=/dev/vx/rdsk/oracle/mydb_raw_ip_lob_128m
   IP_IDX1=/dev/vx/rdsk/oracle/mydb_raw_ip_idx_128m
   OCATS1=/dev/vx/rdsk/oracle/mydb_raw_oca_64m
   UDDISYS_TS1=/dev/vx/rdsk/oracle/mydb_raw_uddi_64m
   OLTS_ATTRSTORE1=/dev/vx/rdsk/oracle/mydb_raw_olts_attr_128m
   OLTS_BATTRSTORE1=/dev/vx/rdsk/oracle/mydb_raw_olts_battr_64m
   OLTS_CT_STORE1=/dev/vx/rdsk/oracle/mydb_raw_olts_ct_store_256m
   OLTS_DEFAULT1=/dev/vx/rdsk/oracle/mydb_raw_olts_default_128m
   OLTS_SVRMGSTORE1=/dev/vx/rdsk/oracle/mydb_raw_olts_svrmgstore_64m
   
   

   See Section 1.4.10, "Schemas and Tablespaces" for a list of tablespaces and schemas in the OracleAS Metadata Repository.

   When you run Oracle Application Server Repository Creation Assistant, it reads this file and populates the Specify Tablespace Information screen with the data. You just need to confirm the data on that screen.

   If you do not create this file, you can still run Oracle Application Server Repository Creation Assistant to install the OracleAS Metadata Repository in a Real Application Clusters database. On the screen where Oracle Application Server Repository Creation Assistant would have displayed the data read from the file, it leaves the fields blank, and you need to enter the data manually.

4. Set the DBCA_RAW_CONFIG environment variable to the full path of the file.

   For example, if you saved the file as /opt/oracle/repca/tablespace_map.txt, then you would set the environment variable as follows:

   setenv DBCA_RAW_CONFIG /opt/oracle/repca/tablespace_map.txt
   
   

5. Start up Oracle Application Server Repository Creation Assistant on the computer where the database is installed. See Section 2.1, "Starting Oracle Application Server Repository Creation Assistant". The parameters that you need in this case are -OH, -RAC, -RAW, -LOGDIR if you want to specify a different log directory, and -REGNREALM if you want to register the OracleAS Metadata Repository in a specific realm. For example:

   runRepca -OH /opt/oracle/oradb -RAC -RAW -LOGDIR /opt/oracle/repca/logs -REGNREALM abcRealm
   
   

6. Follow the screens:

   Table 2-8 Steps for Installing OracleAS Metadata Repository in a Database that Uses Raw Devices

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Database Connect	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Hostname and Port: Enter the names of the computers running the Real Application Clusters database and the port numbers used by the listener. Use the format host:port, and separate each host:port with a comma character: hostname1:port1, hostname2:port2, hostname3:port3, ... If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Example 1 (same domain): myhost:1521, myhost2:1521 Example 2 (different domain): myhost.mydomain.com:1521, myhost2.mydomain:1521 Service Name: Enter the service name of the database. The service name must include the database domain name, and the service name must be the same for all instances in the cluster. Example: asdb.mydomain.com Click Next.
   3.	Warning: Check swap space	This screen informs you that you need at least 512 MB of free swap space. Click OK to continue, or click Cancel to exit Oracle Application Server Repository Creation Assistant.
   4.	Specify Tablespace Information	This screen displays values read from the file pointed to by the DBCA_RAW_CONFIG environment variable. Correct the values, if necessary, and click Next.
   5.	Register with Oracle Internet Directory	If you already have an Oracle Internet Directory and know its connect information, select Register Now and enter the name of the computer where Oracle Internet Directory is running and the port number. Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. If you do not have an Oracle Internet Directory, or do not know its connect information, or plan to use the OracleAS Metadata Repository only for OracleAS Cluster, select Skip Registration. Click Next.
   6.	Specify Login for Oracle Internet Directory	This screen appears if you selected Register Now in the previous screen. Enter the Username and Password to log in to Oracle Internet Directory. The user must belong to the iASAdmins group. You can use the user's simple name (for example, jdoe) or the DN (for example, cn=orcladmin). If your Oracle Internet Directory contains more than one realm, you need to enter the realm that contains the specified user. Click Next.
   7.	Loading Repository	Oracle Application Server Repository Creation Assistant creates and populates the tablespaces and schemas.
   8.	Success	Click OK to exit Oracle Application Server Repository Creation Assistant.

   
   

7. Perform post-installation steps. See Section 2.9, "Post-Installation Steps".

2.6.1 Installing on a Disk Group

This section describes how to install the OracleAS Metadata Repository on a disk group in an ASM instance.

If you want to install OracleAS Metadata Repository in an ASM instance but you want to install on regular files instead of on a disk group, see Section 2.6.2, "Installing on Regular Files".

To install the OracleAS Metadata Repository on a disk group in an ASM instance, perform these steps:

1. Ensure that the database meets the requirements listed in Section 1.4, "Database Requirements".

2. Start up Oracle Application Server Repository Creation Assistant on the computer where the database is installed. See Section 2.1, "Starting Oracle Application Server Repository Creation Assistant". The parameters that you need in this case are -OH, -LOGDIR if you want to specify a different log directory, and -REGNREALM if you want to register the OracleAS Metadata Repository in a specific realm. For example:

   runRepca -OH /opt/oracle/oradb -LOGDIR /opt/oracle/repca/logs -REGNREALM abcRealm
   
   

3. Enter N if Oracle Application Server Repository Creation Assistant asks you if you will be creating the tablespaces on raw file systems.

   Will you be creating the Application Server tablespaces on raw filesystems [Y | N]? N
   
   

4. Enter N if Oracle Application Server Repository Creation Assistant asks you if you are loading OracleAS Metadata Repository in a Real Application Clusters database.

   Do you plan to use a Real Application Clusters database for your Metadata Repository [Y | N]? N
   
   

5. Follow the screens:

   Table 2-9 Steps for Installing OracleAS Metadata Repository on a Disk Group in an ASM Instance

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Database Connect	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Hostname and Port: Enter the name of the computer and the port number for the database. Use the format hostname:port. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Example 1 (same domain): myhost:1521 Example 2 (different domain): myhost.mydomain.com:1521 Service Name: Enter the service name of the database. Note that the service name must include the database domain name. Example: asdb.mydomain.com Click Next.
   3.	Warning: Check swap space	This screen informs you that you need at least 512 MB of free swap space. Click OK to continue, or click Cancel to exit Oracle Application Server Repository Creation Assistant.
   4.	Specify Tablespace Creation Storage Mechanism	Select Create tablespaces managed by Automatic Storage Management (ASM). Click Next.
   5.	Select Disk Group	If your database has multiple disk groups, you will see a screen that enables you to select the disk group in which you want to install the OracleAS Metadata Repository. If your database has only one disk group, you will see a screen displaying the name of that disk group. Click Next.
   6.	Specify Tablespace Information	This screens displays the tablespaces that Oracle Application Server Repository Creation Assistant needs to create. In the Size column, select the appropriate size for the tablespaces. Select the largest size for a tablespace if you have applications that use the component heavily. If not, select the smallest size. Click Next.
   7.	Register with Oracle Internet Directory	If you already have an Oracle Internet Directory and know its connect information, select Register Now and enter the name of the computer where Oracle Internet Directory is running and the port number. Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. If you do not have an Oracle Internet Directory, or do not know its connect information, select Skip Registration. Click Next.
   8.	Specify Login for Oracle Internet Directory	This screen appears if you selected Register Now in the previous screen. Enter the Username and Password to log in to Oracle Internet Directory. The user must belong to the iASAdmins group. You can use the user's simple name (for example, jdoe) or the DN (for example, cn=orcladmin). If your Oracle Internet Directory contains more than one realm, you need to enter the realm that contains the specified user. Click Next.
   9.	Loading Repository	Oracle Application Server Repository Creation Assistant creates and populates the tablespaces and schemas.
   10.	Success	Click OK to exit Oracle Application Server Repository Creation Assistant.

   
   

6. Perform post-installation steps. See Section 2.9, "Post-Installation Steps".

2.6.2 Installing on Regular Files

This section describes how to install the OracleAS Metadata Repository on regular files in an ASM instance.

If you want to install in an ASM instance but you want to install the OracleAS Metadata Repository on a disk group, see Section 2.6.1, "Installing on a Disk Group".

To install the OracleAS Metadata Repository on regular files in an ASM instance, perform these steps:

1. Ensure that the database meets the requirements listed in Section 1.4, "Database Requirements".

2. Start up Oracle Application Server Repository Creation Assistant on the computer where the database is installed. See Section 2.1, "Starting Oracle Application Server Repository Creation Assistant". The parameters that you need in this case are -OH, -LOGDIR if you want to specify a different log directory, and -REGNREALM if you want to register the OracleAS Metadata Repository in a specific realm. For example:

   runRepca -OH /opt/oracle/oradb -LOGDIR /opt/oracle/repca/logs -REGNREALM abcRealm
   
   

3. Enter N if Oracle Application Server Repository Creation Assistant asks you if you will be creating the tablespaces on raw file systems.

   Will you be creating the Application Server tablespaces on raw filesystems [Y | N]? N
   
   

4. Enter N if Oracle Application Server Repository Creation Assistant asks you if you are loading OracleAS Metadata Repository in a Real Application Clusters database.

   Do you plan to use a Real Application Clusters database for your Metadata Repository [Y | N]? N
   
   

5. Follow the screens:

   Table 2-10 Steps for Installing OracleAS Metadata Repository on Regular Files in an ASM Instance

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Database Connect	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Hostname and Port: Enter the name of the computer and the port number for the database. Use the format hostname:port. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Example 1 (same domain): myhost:1521 Example 2 (different domain): myhost.mydomain.com:1521 Service Name: Enter the service name of the database. Note that the service name must include the database domain name. Example: asdb.mydomain.com Click Next.
   3.	Warning: Check swap space	This screen informs you that you need at least 512 MB of free swap space. Click OK to continue, or click Cancel to exit Oracle Application Server Repository Creation Assistant.
   4.	Specify Tablespace Creation Storage Mechanism	Select Create tablespaces managed by the file system or as Oracle-managed files. Click Next.
   5.	Specify Tablespace Creation File System	Select Regular file system. Click Next.
   6.	Specify Tablespace Information	Use Same Directory for All Tablespaces: Select this option if you want to place all the files for all the tablespaces in the same directory. Specify the directory in the field below this option. Ensure that the directory has enough free space. Use Individual Directories for Each Tablespace: Select this option if you want to place the files for the tablespaces in different directories. Tablespaces: Expand the tree to view the tablespaces for each component. Select a tablespace to view or edit its associated datafile or size. Size: Select the largest size for a tablespace if you have applications that use the component heavily. If not, select the smallest size. Filename: Enter the file name for the database file. Example: portal.dbf Directory: Enter the directory where you want to put the database file for the tablespace. You can click the "..." button to browse your file system. Example (UNIX): /opt/oracle/dbfiles/ Example (Windows): C:\oracle\dbfiles\ Click Next.
   7.	Register with Oracle Internet Directory	If you already have an Oracle Internet Directory and know its connect information, select Register Now and enter the name of the computer where Oracle Internet Directory is running and the port number. Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. If you do not have an Oracle Internet Directory, or do not know its connect information, select Skip Registration. Click Next.
   8.	Specify Login for Oracle Internet Directory	This screen appears if you selected Register Now in the previous screen. Enter the Username and Password to log in to Oracle Internet Directory. The user must belong to the iASAdmins group. You can use the user's simple name (for example, jdoe) or the DN (for example, cn=orcladmin). If your Oracle Internet Directory contains more than one realm, you need to enter the realm that contains the specified user. Click Next.
   9.	Loading Repository	Oracle Application Server Repository Creation Assistant creates and populates the tablespaces and schemas.
   10.	Success	Click OK to exit Oracle Application Server Repository Creation Assistant.

   
   

6. Perform post-installation steps. See Section 2.9, "Post-Installation Steps".

2.9.1 Update sqlnet.ora File

Configure SQL*Net settings so that the ORASSO_PS schema in the OracleAS Metadata Repository can be contacted. To do this, update the ORACLE_HOME/network/admin/sqlnet.ora file (ORACLE_HOME specifies the database home where you installed the OracleAS Metadata Repository) by adding LDAP to the NAMES.DIRECTORY_PATH entry as follows:

NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, ONAMES, HOSTNAME)

If you do not perform this configuration, errors are displayed in OracleAS Portal when using the OracleAS Single Sign-On administration portlet. The error is caused by the DB link used by OracleAS Portal to connect to the ORASSO_PS schema for external application functionality. The DB link is resolved using the SQL*Net settings configured in the database home where the OracleAS Metadata Repository resides.

2.9.2 Unlock the DCM Schema and Set Its Password

Unlock the dcm schema and set its password. This step is required only if (1) you want to use the metadata repository only for database clustering of "J2EE and Web Cache" middle tier instances and (2) you did not register the metadata repository with Oracle Internet Directory.

1. Set the ORACLE_HOME environment variable to point to the full path of the directory where the database is installed.

2. Set the ORACLE_SID environment variable to the database's SID.

3. Unlock the dcm schema and set its password using SQL*Plus.

   The following alter user command sets the password to "welcome1", but you can set it to any value.

   prompt> $ORACLE_HOME/bin/sqlplus "sys/password as sysdba"
   SQL> alter user dcm identified by welcome1 account unlock;