10 Installing the OracleAS Metadata Repository in an Existing Database

10.2.1 Database Version

You can install the OracleAS Metadata Repository in the following database versions:

To check the release of your database, query the PRODUCT_COMPONENT_VERSION view:

prompt> sqlplus "sys/password as sysdba"
SQL> select version from product_component_version
 where product like ’Oracle%i%’;

password specifies the password for the SYS user.

prompt> sqlplus "sys/password as sysdba"
SQL> select version from sys.patch$;

prompt> sqlplus "sys/password as sysdba"
SQL> select comp_name, version, status from dba_registry
 where comp_id = ’CATPROC’;

COMP_NAME                     VERSION     STATUS
----------------------------- ----------- --------
Oracle9i Packages and Types   9.2.0.4.0   Valid

10.2.2 Standard Edition Databases: Additional Requirement

If you are using the Standard Edition database, Release 1 (9.0.1.x) or Release 2 (9.2.0.x), you will not be able to use Oracle Internet Directory’s multimaster replication feature (because this feature relies on ASR, which is available only on the Enterprise Edition database).

As an alternative, you can use the fan-out replication feature. See the Oracle Internet Directory Administrator's Guide for details.

10.2.3 Initialization Parameters

During installation, the database must have its initialization parameters set to the values specified in Table 10-2.

After installation, you can change the values of most of these parameters to optimize performance, if necessary.

To check the values of the initialization parameters using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"
SQL> show parameters parameter_name

password specifies the password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"
SQL> select name,value from v$parameter;

The method that you use to change a parameter’s value depends on whether the parameter is static or dynamic, and on whether your database uses a parameter file or a server parameter file.

See the Oracle9i Database Administrator’s Guide for details on parameter files, server parameter files, and how to change parameter values.

If your database uses a parameter file, you can change the parameter values using two different methods:

• You can edit the parameter file and restart the database. This method works for both static and dynamic parameters.

• To change the values of dynamic parameters, you can use the alter system command, but the new values persist only until the database is shut down. For example:

  prompt> sqlplus "sys/password as sysdba"
  SQL> alter system set aq_tm_processes=9;
  
  

If your database uses a server parameter file, use the alter system command to change the parameter values. For static parameters, set the scope to spfile. You have to restart the database for the new value to take effect. For dynamic parameters, you can set the scope to spfile, memory, or both. For the values to persist, set the scope to spfile or both. For example:

prompt> sqlplus "sys/password as sysdba"
SQL> alter system set aq_tm_processes=9 scope=both;

10.2.4 Database Options

The database must have the following database options enabled:

prompt> sqlplus "sys/password as sysdba"
SQL> select * from v$option;

prompt> sqlplus "sys/password as sysdba"
SQL> select count(*) from dba_objects where object_type like
 ’JAVA%’  and owner = ’SYS’ and status = ’VALID’;

prompt> sqlplus "sys/password as sysdba"
SQL> select count(name) from sys.props$
 where name = ’EXPORT_VIEWS_VERSION’;

10.2.5 PL/SQL Packages

The database must have the following PL/SQL packages installed:

prompt> sqlplus "sys/password as sysdba"
SQL> select count(object_name) from all_objects where object_name like
 ’DBMS_DDL%’ and status = ’VALID’;

prompt> sqlplus "sys/password as sysdba"
SQL> select count(*) from dba_views where owner = ’CTXSYS’ and view_name = ’CTX_VERSION’;

10.2.6 DBMS_LDAP Package

Check that your database contains the DBMS_LDAP package, and that the package is valid. You need to reinstall the package if it is not valid.

1. Check that the version of the DBMS_LDAP package is 2. The following SQL command must return 0.

   prompt> sqlplus "sys/password as sysdba"
   SQL> select dbms_ldap_utl.check_interface_version(’2’) from dual;
   
   DBMS_LDAP_UTL.CHECK_INTERFACE_VERSION('2')
   ------------------------------------------
                                            0
   
   

   If the command returns a different value, or if it returns an error such as:

   The DBMS_LDAP package supplied with this database doesn't support the
   version 2 interface used by 904 components.
   
   

   you need to reload the package. Go to "Reloading the DBMS_LDAP Package" at the end of this section.

2. Check that the DBMS_LDAP package is valid. The following SQL command must return 9.

   1. Create a file containing the following lines. You can name the file anything you like (for example, test_ldap.sql).

      select count(*) from dba_objects where
      ( object_name = 'DBMS_LDAP' and 
      object_type = 'PACKAGE' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP' and 
      object_type = 'PACKAGE BODY' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP_UTL' and 
      object_type = 'PACKAGE' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP_UTL' and 
      object_type = 'PACKAGE BODY' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP' and 
      object_type = 'SYNONYM' and 
      status = 'VALID' and owner = 'PUBLIC' 
      ) OR 
      ( object_name = 'DBMS_LDAP_UTL' and 
      object_type = 'SYNONYM' and 
      status = 'VALID' and owner = 'PUBLIC' 
      ) OR 
      ( object_name = 'DBMS_LDAP_API_FFI' and 
      object_type = 'PACKAGE' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP_API_FFI' and 
      object_type = 'PACKAGE BODY' and 
      status = 'VALID' and owner = 'SYS' 
      ) OR 
      ( object_name = 'DBMS_LDAP_API_LIB' and 
      object_type = 'LIBRARY' and 
      status = 'VALID' and owner = 'SYS' 
      );
      
      

   2. Run the file in SQL*Plus. For example, if you named the file test_ldap.sql, the command would look like the following:

      prompt> sqlplus "sys/password as sysdba"
      SQL> @test_ldap.sql
      
        COUNT(*)
      ----------
               9
      
      

      If the command returns a value other than 9, you need to reload the package.

1. Check that the following files exist in the ORACLE_HOME/rdbms/admin directory:

   • catldap.sql

   • dbmsldap.sql

   • prvtldap.plb

   • prvtldh.plb

2. Using SQL*Plus, run the catldap.sql command as the SYS user.

   prompt> cd $ORACLE_HOME/rdbms/admin
   prompt> sqlplus "sys/password as sysdba"
   SQL> @catldap.sql
   
   

10.2.7 Password File Authentication

The database must be set up to use password file authentication. For more information on password file authentication, see the Oracle9i Database Administrator’s Guide.

Password file authentication is required only for running the OracleAS RepCA. It is not required once the metadata repository has been installed.

You can check if the database is set up to use password file authentication, in one of two ways.

• Look up the value of the remote_login_passwordfile initialization parameter by running the following command in SQL*Plus:

  prompt> sqlplus "sys/password as sysdba"
  SQL> show parameters remote_login_passwordfile
  NAME                            TYPE       VALUE
  ------------------------------- ---------- ------------
  remote_login_passwordfile       string     EXCLUSIVE
  
  

  The value of the remote_login_passwordfile initialization parameter must be either EXCLUSIVE or SHARED. If the parameter has a different value or if it is not defined, the database is not set up for password file authentication.

• Try connecting to the database as sysdba through a SQL*Net connection.

  prompt> sqlplus "sys/password@sqlnet_dbname as sysdba"
  
  

  sqlnet_dbname denotes the entry for the database in the tnsnames.ora file. If the database is not set up for password authentication, you will not be able to connect.

To set up a database for password file authentication:

1. Create a password file using the orapwd command (all on one line).

   prompt> $ORACLE_HOME/bin/orapwd file=fullpath_to_pwfile password=password entries=maxUsers
   
   

   Values you need to provide:

   fullpath_to_pwfile - Enter the full path to the file where the password information will be written. The filename must be orapwsid. Typically, the password file is stored in the ORACLE_HOME/dbs directory.

   password - Set the password for the SYS user.

   maxUsers - Specify the maximum number of users that the file can contain.

   The following example sets the password file for a database whose name is "prodmeta":

   prompt> $ORACLE_HOME/bin/orapwd
       file=/opt/oracle/db92/OraHome1/dbs/orapwprodmeta
       password=topsecret entries=9
   
   

2. Set the remote_login_passwordfile initialization parameter to EXCLUSIVE. You can set it to SHARED if you want to use the same password file for multiple databases. If you have a Real Application Clusters database, you must set the parameter to EXCLUSIVE.

3. Restart the database.

10.2.8 Schemas and Tablespaces

The OracleAS RepCA installs the schemas and tablespaces listed in Table 10-8 in your existing database. Ensure that the database does not contain schemas and tablespaces of the same name.

prompt> sqlplus "sys/password as sysdba"
SQL> select username from all_users;

prompt> sqlplus "sys/password as sysdba"
SQL> select name from v$tablespace;

10.2.9 Registration with Oracle Internet Directory

Ensure that the existing database is not already registered with Oracle Internet Directory. You cannot register a database that is already registered with Oracle Internet Directory.

To check if a database is already registered with Oracle Internet Directory, you have to look in Oracle Internet Directory:

1. Connect to Oracle Internet Directory using Oracle Directory Manager.

   1. Start up Oracle Directory Manager.

      prompt> $ORACLE_HOME/bin/oidadmin
      
      

   2. In the Connect screen, enter the connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).

2. Check to see if your database is registered with Oracle Internet Directory. Expand these entries:

   Expand "Entry Management".

   Expand "cn=OracleContext".

   If your database is registered with Oracle Internet Directory, you would see an entry called "cn=your_database_name".

   To remove the registration, see step 2 in Section 10.11, "Cleaning Up a Failed Registration or Deregistering a Metadata Repository".

3. Check to see if your database has a metadata repository that is registered with Oracle Internet Directory. Expand these entries:

   Expand "Entry Management".

   Expand "cn=OracleContext".

   Expand "cn=Products".

   Expand "cn=IAS".

   Expand "cn=IAS Infrastructure Databases".

   If your database has a metadata repository that is registered with Oracle Internet Directory, you would see an entry called "orclReferenceName=your_database_name".

   To remove the registration, see step 3 in Section 10.11, "Cleaning Up a Failed Registration or Deregistering a Metadata Repository".

10.8.1 Overview of Installation Steps

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

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

   You use OracleAS RepCA to do this. See Section 10.8.2, "Installation Steps" for details.

   
   

   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 Section 6.20, "Installing Identity Management Components Only (Including Oracle Internet Directory)" 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.

10.8.2 Installation Steps

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

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

2. Create raw partitions for the OracleAS Metadata Repository.

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

   The command to create raw partitions 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 partitions.

   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 partition file paths with your values. Append a "1" to the tablespace names, as shown in the sample file.

   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 10.2.8, "Schemas and Tablespaces" for a list of tablespaces and schemas in the OracleAS Metadata Repository.

   When you run OracleAS RepCA, 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 the OracleAS RepCA to install the OracleAS Metadata Repository in a Real Application Clusters database. On the screen where OracleAS RepCA would have displayed the data read from the file, it leaves the fields blank, and you need to enter the data manually.

4. Point the DBCA_RAW_CONFIG environment variable to 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:

   Example (C shell):

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

   Example (Bourne or Korn shell):

   $ DBCA_RAW_CONFIG=/opt/oracle/repca/tablespace_map.txt; \
   export DBCA_RAW_CONFIG
   
   

5. Start up the OracleAS RepCA on the computer where the database is installed. See Section 10.6, "Starting OracleAS RepCA". The parameters that you need in this case are -OH, -RAC, and -LOGDIR, if you want to specify a different log directory. For example:

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

6. Follow the screens:

   Table 10-12 Steps for Installing OracleAS Metadata Repository in an Existing Real Application Clusters Database

   	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.	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.
   4.	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 OracleAS RepCA 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 Register Later. Click Next.
   5.	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.
   6.	Loading Repository	The OracleAS RepCA creates and populates the tablespaces and schemas.
   7.	Finish	Click Finish to exit .

   
   

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

10.12.1 OracleAS RepCA Loses Connection to Database (Error Code ORA-03113)

This message appears if you did not run the catpatch.sql script when applying the 9.0.1.5 or 9.2.0.4 database patch set.

To fix this problem, exit OracleAS RepCA and run the catpatch.sql script on the database.