1 OracleAS Metadata Repository Creation Assistant Overview and Requirements

1.1.1 Support for Different Database Storage Types

OracleAS Metadata Repository Creation Assistant can load the OracleAS Metadata Repository in single node databases and Real Application Clusters databases. OracleAS Metadata Repository Creation Assistant can load the OracleAS Metadata Repository on the following storage management options:

• data files created as regular files on the operating system

• data files on cluster file systems

• Automatic Storage Management (ASM) instances

• Oracle-managed files

• raw devices

1.1.2 Support for Local and Remote Databases

When you run OracleAS Metadata Repository Creation Assistant, you need to specify the target database, which is the database on which you want to perform an operation (such as loading, registering, removing, or deregistering the OracleAS Metadata Repository). The database can be running on the same computer as OracleAS Metadata Repository Creation Assistant ("local database"), or on a different computer ("remote database").

For remote databases, the operating system of the computer running the database can be different from the operating system of the computer running OracleAS Metadata Repository Creation Assistant. For example, you can run OracleAS Metadata Repository Creation Assistant on a Windows computer to load the OracleAS Metadata Repository on a database running on a Linux computer.

1.5.1 Run the Prerequisite Check Tool

OracleAS Metadata Repository Creation Assistant comes with a prerequisite check tool, located in the ORACLE_HOME/repca/prereq directory, where ORACLE_HOME is where you installed OracleAS Metadata Repository Creation Assistant. This tool checks most of the database requirements for you. Table 1-2 lists the items checked by the tool.

You should run this tool before running OracleAS Metadata Repository Creation Assistant.

Usage:

DBPrereqChecker -DBHOST dbhost -DBPORT dbport -DBNAME dbname
 -SYSPWD syspassword [-LOGDIR logdir] [-HELP]

Example:

prompt> DBPrereqChecker -DBHOST mydb.mydomain.com -DBPORT 1521
      -DBNAME orcl1.mydomain.com -SYSPWD topsecret -LOGDIR /tmp

1.5.2 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%9i%'
     or product like 'Oracle%Database%';

password specifies the password for the SYS user.

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.6.0   Valid

1.5.3 Standard Edition Databases: Notes

If you are using the Standard Edition of a supported database, you must run the sdopatch.sql script as part of the database's post-install procedure before you run the Oracle Application Server Metadata Repository Creation Assistant.

Note that if you are using the Standard Edition of a supported database, 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.

1.5.4 Swap Space Requirement

You must have at least 512 MB of available swap space on the computer running the database. See Oracle Application Server Installation Guide for information on how to check and increase it, if necessary.

1.5.5 Disk Space Needed for SYSTEM and UNDO Tablespaces

You need the following amounts of free space for the SYSTEM and UNDO tablespaces:

If these tablespaces are set to autoextend, OracleAS Metadata Repository Creation Assistant cannot check the space for you because the tablespaces may use up available space in the file system, and OracleAS Metadata Repository Creation Assistant cannot check the free space on your file system. You have to perform the checks yourself.

If these tablespaces are not set to autoextend, OracleAS Metadata Repository Creation Assistant can check the free space for you, because OracleAS Metadata Repository Creation Assistant can query the database to find out how much space is available in the tablespace.

For directions on enabling and disabling autoextend, see the Oracle Database Administrator's Guide.

1.5.6 Disk Space Needed for OracleAS Metadata Repository Tablespaces

Make sure that you have at least 1.3 GB of disk space for the OracleAS Metadata Repository tablespaces. This is in addition to the space needed for the SYSTEM and UNDO tablespaces (see previous section).

1.5.7 Initialization Parameters

During installation, the database must have its initialization parameters set to the values specified in Table 1-6 and Table 1-7:

• Table 1-6 lists the parameters that are not checked by OracleAS Metadata Repository Creation Assistant. You have to check these parameters yourself.

• Table 1-7 lists the parameters that are checked by OracleAS Metadata Repository Creation Assistant. If OracleAS Metadata Repository Creation Assistant finds parameters that do not meet the requirements, it displays an alert. You need to change the value of the parameter before OracleAS Metadata Repository Creation Assistant can continue.

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

Checking Parameter Values

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;

Changing Parameter Values

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 Oracle Database Administrator's Guide for your database 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;

Changing Values of Internal Parameters

To change the values of internal Oracle parameters such as _system_trig_enabled, you have to enclose the parameter name in double quotes:

prompt> sqlplus "sys/password as sysdba"
SQL> alter system set "_system_trig_enabled"=true;

If the parameter name is not enclosed in double quotes, you will get an error:

prompt> sqlplus "sys/password as sysdba"
SQL> alter system set _system_trig_enabled=true;
                      *
ERROR at line 1: ORA-00911: invalid character

1.5.8 Database Options

The database must have the following database options enabled:

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

PARAMETER                VALUE
---------------------    -----------
OLAP Window Functions    TRUE
Parallel load            TRUE

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

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

prompt> sqlplus "sys/password as sysdba"
SQL> select value from v$option
 where parameter = 'Spatial'

1.5.9 PL/SQL Packages

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

DBMS_DDL

DBMS_LOCK

DBMS_OUTPUT

DBMS_REPUTIL

DBMS_SQL

DBMS_STATS

DBMS_UTILITY

UTL_FILE

UTL_RAW

To check if a package is installed in the database, query the ALL_OBJECTS view. The following example checks for the DBMS_DDL package:

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

Run the query for each package. Replace DBMS_DDL with the name of the package. The count returned should be greater than 0.

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

Reloading the DBMS_LDAP 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 catldap.sql as the SYS user.

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

1.5.11 Knowledge Base Required (Oracle Database 10g Only)

If you plan to install the OracleAS Metadata Repository on Oracle Database 10g and you plan to use OracleAS Portal, then the database must have the Oracle Text supplied knowledge base. The knowledge base is an hierarchical tree of concepts used for indexing themes and performing ABOUT queries.

OracleAS Metadata Repository Creation Assistant checks if your database contains the knowledge base. If your database does not contain it, OracleAS Metadata Repository Creation Assistant displays the following warning:

"Knowledge base not found.

OracleAS RepCA was not able to find the Oracle Text Supplied Knowledge Base in the database specified.

If you are planning to use this repository for installing OracleAS Portal, you have to install Oracle Text Supplied Knowledge Base. Oracle Text Supplied Knowledge Base can be installed in the database using Oracle Database 10g Companion CD.

If you are not planning to use this repository for installing OracleAS Portal, you may continue further.

Do you want to continue?"

If you do not plan to use OracleAS Portal, enter Y to continue. Otherwise, enter N.

If you want to check yourself to see if knowledge base is installed on your database, you can run the following query:

create or replace procedure Check_KB (l_return_value OUT varchar) is
   ORA20000_TEXT_EXCEPTION exception;
   pragma exception_init (ORA20000_TEXT_EXCEPTION, -20000);
   l_test_table constant varchar2(30) := 'WWSRC_INSO_TEST';
   l_test_table_index constant varchar2(30) := 'WWRSC_INSO_TEST_INDEX';

   procedure drop_test_table ( p_test_table in varchar2 ) is
   begin
      for c1 in ( select table_name from user_tables
                  where table_name = p_test_table )
      loop
         execute immediate 'drop table '||c1.table_name;
      end loop;
   end drop_test_table;

   begin
      l_return_value := 'TRUE';
      drop_test_table(l_test_table);
      execute immediate 'create table '||l_test_table||'( id number, content blob,
           query_id number, theme varchar2(2000), weight number,
           CONSTRAINT wwsrc_inso_test_pk PRIMARY KEY(id) )';
      execute immediate 'insert into '||l_test_table||'(id, content)
                      values(1, empty_blob())';
      begin
         execute immediate 'create index '||l_test_table_index||' on '||
              l_test_table||'(content) indextype is ctxsys.context
              PARAMETERS(''filter CTXSYS.INSO_FILTER'')';
         ctx_doc.themes( index_name => l_test_table_index, textkey => '1',
                   restab => l_test_table );
         exception when ORA20000_TEXT_EXCEPTION then
         if (instr(sqlerrm,'DRG-11446') > 0) then
            l_return_value := 'FALSE';
         else
            l_return_value := 'FALSE';
         end if;
      end;

      drop_test_table(l_test_table);
      exception when others then
         drop_test_table(l_test_table);
         l_return_value := 'FALSE';
   end;
/

If the knowledge base is not installed, the following error is displayed when searching in OracleAS Portal with the Oracle Text Enable Themes and Gists option selected:

Error: The Oracle Text Installation is not complete. Knowledge base file or files
are missing. (WWWS-32026)

If your database does not have knowledge base installed, you can install it from the Oracle Database 10g Companion CD-ROM. See the Oracle Database Companion CD Installation Guide for details.

1.5.12 Password File Authentication

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

Password file authentication is required only for running OracleAS Metadata Repository Creation Assistant. 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.

  If you are sure the database is set up for password file authentication, but you get an ORA-01017 error, "Invalid username/password; logon denied", a possible cause is that you changed the SYS password when setting up the password file (the value specified in the password parameter actually sets the password for the SYS user). If this is the case, you just need to change the SYS password to something that you can remember.

  You can still log in as SYS if you have the sysdba operating system privilege. For the password, you can specify anything. The sysdba operating system privilege overrides the password.

  prompt> sqlplus "sys/badPassword as sysdba"
  SQL> alter user sys identified by newPassword;
  SQL> exit
  
  

  Now when you connect to the database with "sys/newPassword@sqlnet_dbname as sysdba", it should work.

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.

   
   

   Note: The value that you specify for password parameter sets the password for the SYS user. If you specify a different value from the current SYS password, you are changing the SYS password.

   
   

   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 "mydb":

   prompt> $ORACLE_HOME/bin/orapwd
       file=/opt/oracle/db92/OraHome1/dbs/orapwmydb
       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.

1.5.13 Schemas and Tablespaces

OracleAS Metadata Repository Creation Assistant installs the schemas and tablespaces listed in Table 1-9 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;

1.5.14 Registration with Oracle Internet Directory

For registration to be successful, check the following points:

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

• Ensure that another database with the same SID is not 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: Entry Management > 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 C.5, "Manual Steps: Cleaning Up a Failed Registration or Deregistering OracleAS Metadata Repository".

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

   Entry Management > cn=OracleContext > cn=Products > cn=IAS > 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 C.5, "Manual Steps: Cleaning Up a Failed Registration or Deregistering OracleAS Metadata Repository".