2 Loading the OracleAS Metadata Repository into an Existing Database

2.3.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 OracleAS Metadata Repository Creation Assistant to do this. The specific steps depend on the storage type used by the Real Application Clusters database:

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

   • Section 2.3.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 Oracle Identity Management components on non-clustered computers.

   You can install all the Oracle Identity Management components on a single computer, or you can distribute them over multiple computers. See the Oracle Application Server 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.3.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.5, "Requirements for the Database".

2. Start up OracleAS Metadata Repository Creation Assistant. See Section 1.7, "Starting OracleAS Metadata Repository Creation Assistant" for details.

3. Follow the screens:

   
   

   Note: The on-screen instructions for the Specify Database Connection Information screen are different from the instructions in this guide. This guide has the correct instructions.

   
   

   Table 2-4 Installing OracleAS Metadata Repository in a Real Application Clusters Database that Uses the Cluster File System

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Oracle Home	Oracle Home: Enter the full path of the Oracle home directory for the database. Be sure you use the conventions of the computer that is running the database (for example, use the proper slashes). Log File Directory: Enter the full path of the directory where you want OracleAS Metadata Repository Creation Assistant to write its log files. This path is on the computer where you are running OracleAS Metadata Repository Creation Assistant. Note that once you click Next to move to the next screen, you cannot change the log file directory. If you click Back to return to this screen, the Log File Directory field becomes read-only. This is to prevent OracleAS Metadata Repository Creation Assistant from writing log files in different directories. Click Next.
   3.	Select Operation	Oracle Home: Enter the full path of the Oracle home directory for the database. Select Load if you want to load the OracleAS Metadata Repository into the database but without registering it with Oracle Internet Directory. Select this option if you do not have an Oracle Internet Directory yet. Select Load and Register if you want to load the OracleAS Metadata Repository into the database and register it with Oracle Internet Directory. Click Next.
   4.	Specify Database Connection Information	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Real Application Clusters Database: Select this option, and complete the fields under it: Hostname and Port: Enter the name of one computer running the Real Application Clusters database and the port number used by the listener. The Real Application Clusters software will automatically replicate the data loaded by OracleAS Metadata Repository Creation Assistant onto all of the nodes. Use the format host:port: hostname1:port1 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: orcl.mydomain.com Click Next.
   5.	Specify Storage Options	Select Regular or Cluster File System.
   6.	Specify Tablespace Information	Enter the information for the tablespaces that OracleAS Metadata Repository Creation Assistant will create in your database. 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 already exists and is writable the directory has enough free space the path to the directory is correct and is consistent with the operating system that is running the database. 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. Ensure that the path to the directory is correct and is consistent with the operating system that is running the database. Example (UNIX): /opt/oracle/dbfiles/ Example (Windows): C:\oracle\dbfiles\ Click Next.
   7.	Warning: Check Disk Space	This warning dialog appears if your SYSTEM and UNDO tablespaces are set to autoextend. Check that the file system that contains the SYSTEM and UNDO tablespaces have enough disk space, as specified in the warning dialog.
   8.	Specify Oracle Internet Directory Connection	This and the next two screens appear only if you selected Load and Register earlier. Internet Directory Hostname: Enter the name of the computer that is running Oracle Internet Directory. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Internet Directory Port: Enter the port number for Oracle Internet Directory. Use SSL to Connect to Oracle Internet Directory for Registration Purposes: Select this option if you want OracleAS Metadata Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. Click Next.
   9.	Specify Login for Oracle Internet Directory	Enter the Username and Password to log in to Oracle Internet Directory. The user must belong to the iAS Admins group. You can use the user's simple name (for example, jdoe) or the user's 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. Note: If you log in as the Oracle Internet Directory superuser (cn=orcladmin), the realm value is not used because the superuser does not belong to any realm. The realm value is used only if you log in using a simple name. Click Next.
   10.	Specify Oracle Context	Specify the location in Oracle Internet Directory where you want to register the OracleAS Metadata Repository. Root Oracle Context (cn=OracleContext): Select this option to register OracleAS Metadata Repository in the root Oracle context. Custom Oracle Context: Select this option to register OracleAS Metadata Repository in a specific realm in Oracle Internet Directory. Enter the DN of the realm in the provided field. Click Next.
   11.	Loading Repository	OracleAS Metadata Repository Creation Assistant creates and populates the tablespaces and schemas.
   12.	Success	Click OK to exit OracleAS Metadata Repository Creation Assistant.

   
   

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

2.3.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.5, "Requirements for the Database".

2. Create raw devices for the OracleAS Metadata Repository.

   See Table 1-12 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. (optional) Create a file to map the tablespaces to the raw devices, and set the DBCA_RAW_CONFIG environment variable to point to this file.

   OracleAS Metadata Repository Creation Assistant 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 OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository in a Real Application Clusters database that uses raw devices. On the Specify Tablespace Information screen, it leaves the fields blank, and you have to enter the data manually.

   The steps in detail:

   1. 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 paths with 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
      B2B_DT1=/dev/vx/rdsk/oracle/mydb_raw_b2b_dt_256m
      B2B_RT1=/dev/vx/rdsk/oracle/mydb_raw_b2b_rt_256m
      B2B_LOB1=/dev/vx/rdsk/oracle/mydb_raw_b2b_lob_256m
      B2B_IDX1=/dev/vx/rdsk/oracle/mydb_raw_b2b_idx_256m
      BAM1=/dev/vx/rdsk/oracle/mydb_raw_bam_175m
      ORABPEL1=/dev/vx/rdsk/oracle/mydb_raw_orapbel_80m
      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.5.13, "Schemas and Tablespaces" for a list of tablespaces and schemas in the OracleAS Metadata Repository.

   2. 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
      
      

4. Start up OracleAS Metadata Repository Creation Assistant. See Section 1.7, "Starting OracleAS Metadata Repository Creation Assistant" for details.

5. Follow the screens:

   
   

   Note: The on-screen instructions for the Specify Database Connection Information screen are different from the instructions in this guide. This guide has the correct instructions.

   
   

   Table 2-5 Installing OracleAS Metadata Repository in a Real Application Clusters Database that Uses Raw Devices

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Oracle Home	Oracle Home: Enter the full path of the Oracle home directory for the database. Be sure you use the conventions of the computer that is running the database (for example, use the proper slashes). Log File Directory: Enter the full path of the directory where you want OracleAS Metadata Repository Creation Assistant to write its log files. This path is on the computer where you are running OracleAS Metadata Repository Creation Assistant. Note that once you click Next to move to the next screen, you cannot change the log file directory. If you click Back to return to this screen, the Log File Directory field becomes read-only. This is to prevent OracleAS Metadata Repository Creation Assistant from writing log files in different directories. Click Next.
   3.	Select Operation	Select Load if you want to load the OracleAS Metadata Repository into the database but without registering it with Oracle Internet Directory. Select this option if you do not have an Oracle Internet Directory yet. Select Load and Register if you want to load the OracleAS Metadata Repository into the database and register it with Oracle Internet Directory. Click Next.
   4.	Specify Database Connection Information	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Real Application Clusters Database: Select this option, and complete the fields under it: Hostname and Port: Enter the name of one computer running the Real Application Clusters database and the port number used by the listener. The Real Application Clusters software will automatically replicate the data loaded by OracleAS Metadata Repository Creation Assistant onto all of the nodes. Use the format host:port: hostname1:port1 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: orcl.mydomain.com Click Next.
   5.	Specify Storage Options	Select Raw File System.
   6.	Specify Tablespace Information	If you created a mapping file and set the DBCA_RAW_CONFIG environment variable to point to this file, this screen displays the values read from the file. See step 3 for details. Correct the values, if necessary, and click Next. If you did not create a mapping file, or if the DBCA_RAW_CONFIG environment variable is unset, you have to enter the information in this screen manually. Click Next.
   7.	Warning: Check Disk Space	This warning dialog appears if your SYSTEM and UNDO tablespaces are set to autoextend. Check that the file system that contains the SYSTEM and UNDO tablespaces have enough disk space, as specified in the warning dialog.
   8.	Specify Oracle Internet Directory Connect	This and the next two screens appear only if you selected Load and Register earlier. Internet Directory Hostname: Enter the name of the computer that is running Oracle Internet Directory. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Internet Directory Port: Enter the port number for Oracle Internet Directory. Use SSL to Connect to Oracle Internet Directory for Registration Purposes: Select this option if you want OracleAS Metadata Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. Click Next.
   9.	Specify Login for Oracle Internet Directory	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 user's 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. Note: If you log in as the Oracle Internet Directory superuser (cn=orcladmin), the realm value is not used because the superuser does not belong to any realm. The realm value is used only if you log in using a simple name. Click Next.
   10.	Specify Oracle Context	Specify the location in Oracle Internet Directory where you want to register the OracleAS Metadata Repository. Root Oracle Context (cn=OracleContext): Select this option to register OracleAS Metadata Repository in the root Oracle context. Custom Oracle Context: Select this option to register OracleAS Metadata Repository in a specific realm in Oracle Internet Directory. Enter the DN of the realm in the provided field. Click Next.
   11.	Loading Repository	OracleAS Metadata Repository Creation Assistant creates and populates the tablespaces and schemas.
   12.	Success	Click OK to exit OracleAS Metadata Repository Creation Assistant.

   
   

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

2.4.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.4.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.5, "Requirements for the Database".

2. Start up OracleAS Metadata Repository Creation Assistant. See Section 1.7, "Starting OracleAS Metadata Repository Creation Assistant" for details.

3. Follow the screens:

   Table 2-6 Installing OracleAS Metadata Repository on a Disk Group in an ASM Instance

   	Screen	Action
   1.	Welcome	Click Next.
   2.	Specify Oracle Home	Oracle Home: Enter the full path of the Oracle home directory for the database. Be sure you use the conventions of the computer that is running the database (for example, use the proper slashes). Log File Directory: Enter the full path of the directory where you want OracleAS Metadata Repository Creation Assistant to write its log files. This path is on the computer where you are running OracleAS Metadata Repository Creation Assistant. Note that once you click Next to move to the next screen, you cannot change the log file directory. If you click Back to return to this screen, the Log File Directory field becomes read-only. This is to prevent OracleAS Metadata Repository Creation Assistant from writing log files in different directories. Click Next.
   3.	Select Operation	Select Load if you want to load the OracleAS Metadata Repository into the database but without registering it with Oracle Internet Directory. Select this option if you do not have an Oracle Internet Directory yet. Select Load and Register if you want to load the OracleAS Metadata Repository into the database and register it with Oracle Internet Directory. Click Next.
   4.	Specify Database Connection Information	Enter connect information for the existing database. SYS Password: Enter the password for the SYS user. Single node instance: Select this option, and complete the fields under it: Hostname: Enter the name of the computer that is running the database. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Port: Enter the port number for the database. Service Name: Enter the service name of the database. Note that the service name must include the database domain name. Example: orcl.mydomain.com Click Next.
   5.	Specify Storage Options	Select Automatic Storage Management (ASM).
   6.	Select Disk Group	Select the disk group in which you want to install the OracleAS Metadata Repository. Click Next.
   7.	Specify Tablespace Information	This screen displays the tablespaces that OracleAS Metadata 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.
   8.	Warning: Check Disk Space	This warning dialog appears if your SYSTEM and UNDO tablespaces are set to autoextend. Check that the file system that contains the SYSTEM and UNDO tablespaces have enough disk space, as specified in the warning dialog.
   9.	Specify Oracle Internet Directory Connection	This and the next two screens appear only if you selected Load and Register earlier. Internet Directory Hostname: Enter the name of the computer that is running Oracle Internet Directory. If your middle tier instances are located in a different domain, you need to append the domain name to the hostname. Internet Directory Port: Enter the port number for Oracle Internet Directory. Use SSL to Connect to Oracle Internet Directory for Registration Purposes: Select this option if you want OracleAS Metadata Repository Creation Assistant to connect to Oracle Internet Directory using SSL when performing the registration. Click Next.
   10.	Specify Login for Oracle Internet Directory	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 user's 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. Note: If you log in as the Oracle Internet Directory superuser (cn=orcladmin), the realm value is not used because the superuser does not belong to any realm. The realm value is used only if you log in using a simple name. Click Next.
   11.	Specify Oracle Context	Specify the location in Oracle Internet Directory where you want to register the OracleAS Metadata Repository. Root Oracle Context (cn=OracleContext): Select this option to register OracleAS Metadata Repository in the root Oracle context. Custom Oracle Context: Select this option to register OracleAS Metadata Repository in a specific realm in Oracle Internet Directory. Enter the DN of the realm in the provided field. Click Next.
   12.	Loading Repository	OracleAS Metadata Repository Creation Assistant creates and populates the tablespaces and schemas.
   13.	Success	Click OK to exit OracleAS Metadata Repository Creation Assistant.

   
   

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

2.4.2 Installing on Regular Files

The procedure for installing the OracleAS Metadata Repository on regular files in an ASM instance is the same as the procedure for installing on regular files on a non-ASM database. See Section 2.1, "Installing in a Database that Uses the File System".

2.6.1 SP2-0332 Errors

If the log file shows an SP2-0332 error in the following context, you may ignore it:

ERROR at line 1:
ORA-04043: object OID_METRIC_TYPE does not exist
Type created.
Type created.
Package created.
Package body created.
SP2-0332: Cannot create spool file.
Procedure created.
PL/SQL procedure successfully completed.

You may also ignore an SP2-0332 error in the following context:

SQL> Connected.
SQL>
PL/SQL procedure successfully completed.
SP2-0332: Cannot create spool file.
DROP USER odscommon CASCADE
ERROR at line 1:
ORA-01918: user 'ODSCOMMON' does not exist
Package body created.
SP2-0332: Cannot create spool file.
Procedure created

2.6.2 SP2-0606 Errors

If the log file shows an SP2-0606 error in the following context, you may ignore it:

ERROR at line 1:
ORA-04043: object OID_METRIC_TYPE does not exist
Type created.
Type created.
Package created.
Package body created.
SP2-0606: Cannot create SPOOL file "LOGS/oidimeta.log"
Procedure created.
PL/SQL procedure successfully completed.

2.7.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.7.2 Copy ldap.ora File to the Database Oracle Home

This procedure is applicable only if you loaded and registered the OracleAS Metadata Repository with Oracle Internet Directory. If you only loaded the OracleAS Metadata Repository without registering it with Oracle Internet Directory, then you can skip this step.

• If your database is version 9.2.0.6 (or higher in the 9.2.x series), copy the file Repository_Creation_Assistant_OH/network/admin/ldap.ora to Database_OH/network/admin/ldap.ora.

  Repository_Creation_Assistant_OH is the Oracle home for the OracleAS Metadata Repository Creation Assistant.

  Database_OH is the Oracle home for your database.

• If your database is version 10.1.0.4 (or higher in the 10.1.x series), copy the file Repository_Creation_Assistant_OH/network/admin/ldap.ora to Database_OH/ldap/admin/ldap.ora.

  Repository_Creation_Assistant_OH is the Oracle home for the OracleAS Metadata Repository Creation Assistant.

  Database_OH is the Oracle home for your database.

2.7.3 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.

2.7.4 Create Instance for Oracle Ultra Search

Oracle Application Server uses the Oracle Ultra Search that comes with the database. If you loaded the OracleAS Metadata Repository in a 9.2.0.6 database, the Oracle Ultra Search that comes with this version of the database does not include a default instance. This means that you will have to create an Oracle Ultra Search instance. For details on how to create an instance, see the section "Creating an Instance" in the chapter "Understanding the Oracle Ultra Search Administration Tool" in the Oracle Ultra Search Administrator's Guide.

If you do not create an Oracle Ultra Search instance, you will get an error when you try the following:

1. Log in to OracleAS Portal.

2. Navigate to the Oracle Ultra Search Administration page. You will get the following error:

   "Error: No Ultra Search instances have been assigned to user "ORCLADMIN" for administration. Contact the Ultra Search administrator for your organization."