|
Oracle® Application Server Metadata Repository Creation Assistant User's Guide
10g Release 2 (10.1.2) for UNIX Part No. B14129-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Metadata Repository Creation Assistant User's Guide
10g Release 2 (10.1.2) for UNIX Part No. B14129-01 |
|
|
Previous |
Next |
Instead of having the installer create a new database for the OracleAS Metadata Repository, you can install the OracleAS Metadata Repository in an existing database. This chapter describes how to use Oracle Application Server Metadata Repository Creation Assistant ("OracleAS Metadata Repository Creation Assistant"), which is the tool that performs the installation. You can also use OracleAS Metadata Repository Creation Assistant to register OracleAS Metadata Repository with Oracle Internet Directory.
|
Notes:
|
Contents:
Section 1.1, "OracleAS Metadata Repository Creation Assistant Overview"
Section 1.2, "Steps for Running OracleAS Metadata Repository Creation Assistant"
Section 1.3, "Requirements for the Computer Running OracleAS Metadata Repository Creation Assistant"
Section 1.4, "Installing OracleAS Metadata Repository Creation Assistant"
Section 1.7, "Starting OracleAS Metadata Repository Creation Assistant"
You can run OracleAS Metadata Repository Creation Assistant to perform the following operations:
load the OracleAS Metadata Repository in an existing database
register the OracleAS Metadata Repository with Oracle Internet Directory
remove OracleAS Metadata Repository schemas and tablespaces from a database
deregister the OracleAS Metadata Repository from Oracle Internet Directory
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
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.
Before you can run OracleAS Metadata Repository Creation Assistant, you have to install it first.
Install OracleAS Metadata Repository Creation Assistant.
You have to run the installer from the "OracleAS Metadata Repository Creation Assistant" CD-ROM. If you are using the Oracle Application Server DVD-ROM, the installer is in the repca directory.
During the installation, you specify the directory where you want to install OracleAS Metadata Repository Creation Assistant.
Run OracleAS Metadata Repository Creation Assistant from the installed directory.
The computer where you run OracleAS Metadata Repository Creation Assistant must meet the following requirements:
Table 1-1 Requirements for the Computer Running OracleAS Metadata Repository Creation Assistant
| Item | Requirement |
|---|---|
| Operating system | Windows 2000 with Service Pack 3 or later
Windows 2003 Windows XP Solaris 8 Solaris 9 HP-UX 11i (11.11) PA-RISC HP-UX 11i (11.23) PA-RISC Red Hat Enterprise Linux AS/ES 2.1, Update 5 Red Hat Enterprise Linux AS/ES 3.0, Update 3 SUSE Linux Enterprise Server 8, SP3 SUSE Linux Enterprise Server 9 For hardware requirements, see the Oracle Application Server Installation Guide. |
| Disk space | For installing OracleAS Metadata Repository Creation Assistant, you need at least 600 MB.
Note: Each time you run OracleAS Metadata Repository Creation Assistant to perform the loading operation, you need approximately 10 MB of disk space for log files. For disk space required for the database, see Section 1.5.5, "Disk Space Needed for SYSTEM and UNDO Tablespaces" and Section 1.5.6, "Disk Space Needed for OracleAS Metadata Repository Tablespaces". |
| Memory | 512 MB |
| Virtual memory | 1535 MB |
| Display | 256 colors |
To install OracleAS Metadata Repository Creation Assistant:
Insert the "OracleAS Metadata Repository Creation Assistant" CD-ROM or the Oracle Application Server DVD-ROM.
If your computer does not mount CD-ROMs or DVD-ROMs automatically, you need to set the mount point manually.
Start the installer.
CD-ROM: Run runInstaller to start the installer.
DVD-ROM: Navigate to the repca directory and run runInstaller to start the installer.
Welcome screen: Click Next.
Specify File Locations screen: In the Name field, enter a name for this OracleAS Metadata Repository Creation Assistant installation. The name of the Oracle home must be 128 characters or fewer, and can contain only alphanumeric characters and the underscore character. Example: repca10_1_2.
In the Destination Path field, enter a full path to the directory where you want to install OracleAS Metadata Repository Creation Assistant. This guide refers to this directory as the Oracle home for OracleAS Metadata Repository Creation Assistant.
Click Next.
Launch Repository Creation Assistant screen: Select Yes if you want to run OracleAS Metadata Repository Creation Assistant immediately after installation. Otherwise, select No. In either case, you can always run OracleAS Metadata Repository Creation Assistant anytime after installation.
Click Next.
Summary screen: Click Install to start the installation.
Configuration Assistants screen: The installer runs configuration assistants to install OracleAS Metadata Repository Creation Assistant.
|
Note: If you selected Yes in the Launch Repository Creation Assistant screen, the installer starts up OracleAS Metadata Repository Creation Assistant as a configuration assistant. In the Configuration Assistants screen, the status of the "OracleAS Repository Creation Assistant" line stays at "In Progress" as long as OracleAS Metadata Repository Creation Assistant is running. When you exit OracleAS Metadata Repository Creation Assistant, the installer advances to the End of Installation screen.The installer stays running until you exit OracleAS Metadata Repository Creation Assistant. |
End of Installation screen: Click Exit to exit the installer.
The database where you want to install the OracleAS Metadata Repository must meet requirements in the areas listed in Table 1-2.
|
Tip: Run the prerequisite check tool (see Section 1.5.1, "Run the Prerequisite Check Tool") before running OracleAS Metadata Repository Creation Assistant. This tool checks many of the database requirements for you. Although OracleAS Metadata Repository Creation Assistant also checks the requirements for you, the prerequisite tool is easier to use because it checks the requirements without stopping at the first unmet requirement. You can then resolve all unmet requirements at the same time, instead of going through the cycle of resolving an unmet requirement, then rerunning OracleAS Metadata Repository Creation Assistant, and resolving the next unmet requirement.You may have to restart the database to comply with a requirement. Then when you run OracleAS Metadata Repository Creation Assistant, which also checks the requirements, you have a good chance of installing the OracleAS Metadata Repository successfully. Table 1-2 lists the items checked by the prerequisite check tool. |
Table 1-2 Database Requirements
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.
|
Tip: You can run this tool several times, until your database meets all the requirements. |
DBPrereqChecker -DBHOST dbhost -DBPORT dbport -DBNAME dbname -SYSPWD syspassword [-LOGDIR logdir] [-HELP]
Table 1-3 Parameters for DBPrereqChecker
| Parameter | Description |
|---|---|
-DBHOST dbhost
|
Specifies the name of the computer running the database. |
-DBPORT dbport
|
Specifies the port on which the database listener is listening. |
-DBNAME dbname
|
Specifies the service name of the database. |
-SYSPWD syspassword
|
Specifies the password of the SYS user. |
-LOGDIR logdir
|
Specifies the directory where you want the log file to be written. Be sure you have write permission for the directory.
The name of the log file is If this parameter is not specified, the tool writes to the console. |
-HELP
|
Displays the help for the tool. |
Example:
prompt> DBPrereqChecker -DBHOST mydb.mydomain.com -DBPORT 1521
-DBNAME orcl1.mydomain.com -SYSPWD topsecret -LOGDIR /tmp
You can install the OracleAS Metadata Repository in the following database versions:
Table 1-4 Supported Database Versions
| Database Series | Supported Versions | See This Section for Details |
|---|---|---|
| Oracle9i Release 2 (9.2.x) | 9.2.0.6 with some patches, or later |
|
| Oracle Database 10g | 10.1.0.4 or later | -- |
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.
If you have a 9.2.x database, ensure that its version is 9.2.0.6 with some patches (see below), or later.
If you are running a Release 2 (9.2.0.6) database in a Real Application Clusters environment, see also Section 1.5.2.2, "Oracle9i Release 2 (9.2.0.6) Real Application Clusters Databases".
Patches Required
For Oracle9i Release 2 (9.2.0.6) database, you need to apply patch 4015165 before you can load OracleAS Metadata Repository into the database. You can download this patch from OracleMetaLink (http://metalink.oracle.com).
You can upgrade to Release 2 (9.2.0.6) from earlier 9.2.x releases by applying the 9.2.0.6 patch set, which is patch set number 3948480. You can download the patch set from OracleMetaLink (http://metalink.oracle.com).
Ensure that the following steps for upgrading your database to 9.2.0.6 are performed. These steps are documented in the README file for the 9.2.0.6 patch set.
Make sure that the initialization (init.ora) parameters are set as specified in the README file for the patch set, that the SYSTEM and XDB tablespaces have sufficient free space, and that the CLUSTER_DATABASE initialization parameter is set as specified in the README file.
Run utlrp.sql (step 10 in the README file for the patch set).
Run the Oracle Internet Directory step only if you were running Oracle Internet Directory version 9.2.0.x. If Oracle Internet Directory has never been used with this database, you do not have to perform this step.
To check that you have run the catpatch.sql script, you can run the following command in SQL*Plus:
prompt> sqlplus "sys/password as sysdba" SQL> select comp_name, version, status from dba_registry where comp_id = 'CATPROC';
You should get the following results:
COMP_NAME VERSION STATUS ----------------------------- ----------- -------- Oracle9i Packages and Types 9.2.0.6.0 Valid
|
Note: Be sure that thecatpatch.sql script has been run against your database. Even if you have patched your database Oracle home to 9.2.0.6, when you create a new database using the Database Configuration Assistant (DBCA), the new database might not have the catpatch.sql script run against it. This is the case if you created the database using DBCA from the seed template or from a custom template that did not have the catpatch.sql script run against it.
If you have such a database, run |
If you are running a Release 2 (9.2.0.6) database in a Real Application Clusters environment, you need to apply patch 3047933 (ARU 6662789) before you can load the OracleAS Metadata Repository on your database.
You can download the patch from OracleMetaLink (http://metalink.oracle.com).
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.
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.
You need the following amounts of free space for the SYSTEM and UNDO tablespaces:
Table 1-5 Free Space Required for the SYSTEM and UNDO Tablespaces
| Tablespace | Free Space Required |
|---|---|
| SYSTEM | 367,001,600 bytes |
| UNDO | 367,001,600 bytes |
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.
Make sure that you have at least 1.15 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).
You can load the OracleAS Metadata Repository on existing databases running on Windows XP. However, as with most Oracle Application Server installations on Windows XP, this is not supported.
You can run the OracleAS Metadata Repository Creation Assistant tool on Windows XP. This is supported.
For the latest certification updates, check OracleMetaLink (http://metalink.oracle.com).
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.
|
Notes: The value of thedb_block_size parameter must be 8192 or greater. This parameter is set when the database was created and cannot be changed. If your database has a lower value for this parameter, this means that you cannot use this database for the metadata repository.
|
Table 1-6 Initialization Parameters that You Have to Check Manually
| Parameter | Required Value | Parameter Class | Notes |
|---|---|---|---|
nls_length_semantics
|
BYTE
|
Dynamic | Note: OracleAS Metadata Repository Creation Assistant does not check this parameter. You have to check it manually.
The |
max_commit_propagation_delay
|
0 | Static | Note: OracleAS Metadata Repository Creation Assistant does not check this parameter. You have to check it manually.
This parameter is required only if you are loading the OracleAS Metadata Repository into a Real Application Clusters database. |
compatible
|
9.2.0.0.0 or higher
|
Static | Note: OracleAS Metadata Repository Creation Assistant does not check this parameter. You have to check it manually.
Do not set this parameter to a value lower than |
Table 1-7 Initialization Parameters: Required Values (Checked by OracleAS Metadata Repository Creation Assistant)
| Parameter | Required Value | Parameter Class | Notes |
|---|---|---|---|
db_block_size
|
8192 or greater | Not changeable. See "Notes" column. | You cannot change the value of this parameter once the database has been created. |
aq_tm_processes
|
1 or greater | Dynamic | You can change the value of this parameter after installation. |
open_cursors
|
300 or greater | Dynamic | You can change the value of this parameter after installation. |
job_queue_processes
|
1 or greater | Dynamic | You can change the value of this parameter after installation. |
db_cache_size
|
Greater than 144 MB | Dynamic | You can change the value of this parameter after installation. |
shared_pool_size
|
Greater than 175 MB | Dynamic | You can change the value of this parameter after installation. |
java_pool_size
|
Greater than 120 MB | Static | You can change the value of this parameter after installation. |
pga_aggregate_target
|
Greater than 96 MB | Dynamic | You can change the value of this parameter after installation. |
query_rewrite_enabled
|
TRUE
|
Dynamic | Do not change this parameter after installation, because OracleAS Wireless requires this value. |
query_rewrite_integrity
|
trusted or enforced
|
Dynamic | Do not change this parameter after installation, because OracleAS Wireless requires this value. |
sessions
|
400 or greater | Static | You can change the value of this parameter after installation. |
undo_management
|
AUTO
|
Static | You can change the value of this parameter after installation. |
_system_trig_enabled
|
true
|
Dynamic | This is an internal Oracle parameter. Set it to true to enable system triggers.
|
db_create_file_dest
|
The directory where OracleAS Metadata Repository Creation Assistant should create the data files for OracleAS Metadata Repository | Dynamic | This initialization parameter is needed only if you are installing the OracleAS Metadata Repository in a database that uses Oracle-managed files. |
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
The database must have the following database options enabled:
Table 1-8 Required Database Options
| Required Option | How to Check if the Option is Installed in the Database |
|---|---|
| OLAP Window Functions
Parallel load |
To check if the database has these options, query the V$OPTION view (password specifies the password for the SYS user):
prompt> sqlplus "sys/password as sysdba" SQL> select * from v$option; Among the rows returned by the query, you should see these two rows: PARAMETER VALUE --------------------- ----------- OLAP Window Functions TRUE Parallel load TRUE |
| Java |
prompt> sqlplus "sys/password as sysdba" SQL> select count(*) from dba_objects where object_type like 'JAVA%' and owner = 'SYS' and status = 'VALID';The count returned should be greater than 0. |
| Intermedia |
prompt> sqlplus "sys/password as sysdba" SQL> select count(name) from sys.props$ where name = 'EXPORT_VIEWS_VERSION';The count returned should be greater than 0. |
| Oracle Text |
prompt> sqlplus "sys/password as sysdba" SQL> select count(*) from dba_views where owner = 'CTXSYS' and view_name = 'CTX_VERSION';The count should be greater than 0. |
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.
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.
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.
Check that the DBMS_LDAP package is valid. The following SQL command must return 9.
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' );
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
Check that the following files exist in the ORACLE_HOME/rdbms/admin directory:
catldap.sql
dbmsldap.sql
prvtldap.plb
prvtldh.plb
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
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.
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:
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
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.
Restart the database.
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.
Table 1-9 lists the OracleAS Metadata Repository schemas and tablespaces that OracleAS Metadata Repository Creation Assistant will create in your database.
Table 1-9 Schemas and Tablespaces
| Component | Schema | Tablespace | Default Database File |
|---|---|---|---|
| OracleAS Portal
|
PORTAL
|
PORTAL
|
portal.dbf |
| OracleAS Portal
|
PORTAL
|
PORTAL_DOC
|
ptldoc.dbf |
| OracleAS Portal
|
PORTAL
|
PORTAL_IDX
|
ptlidx.dbf |
| OracleAS Portal
|
PORTAL
|
PORTAL_LOG
|
ptllog.dbf |
| OracleAS Portal
|
PORTAL_APP
|
PORTAL
|
portal.dbf |
| OracleAS Portal
|
PORTAL_DEMO
|
PORTAL
|
portal.dbf |
| OracleAS Portal
|
PORTAL_PUBLIC
|
PORTAL
|
portal.dbf |
| OracleAS Single Sign-On
|
ORASSO
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Single Sign-On
|
ORASSO_PA
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Single Sign-On
|
ORASSO_DS
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Single Sign-On
|
ORASSO_PS
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Single Sign-On
|
ORASSO_PUBLIC
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Wireless
|
WIRELESS
|
IAS_META
|
ias_meta01.dbf |
| Oracle Workflow
|
OWF_MGR
|
IAS_META
|
ias_meta01.dbf |
| OracleAS Discoverer
|
DISCOVERER5
|
DISCO_PTM5_META
|
discopltm1.dbf |
| OracleAS Discoverer
|
DISCOVERER5
|
DISCO_PTM5_CACHE
|
discopltc1.dbf |
| OracleAS Distributed Configuration Management (DCM) | DCM
|
DCM
|
dcm.dbf |
| OracleAS Web Clipping Support
|
WCRSYS
|
WCRSYS_TS
|
wcrsys01.dbf |
| OracleAS Integration B2B
|
B2B
|
B2B_RT
|
b2b_rt.dbf |
| OracleAS Integration B2B
|
B2B
|
B2B_DT
|
b2b_dt.dbf |
| OracleAS Integration B2B
|
B2B
|
B2B_IDX
|
b2b_idx.dbf |
| OracleAS Integration B2B
|
B2B
|
B2B_LOB
|
b2b_lob.dbf |
| OracleAS Certificate Authority
|
OCA
|
OCATS
|
oca.dbf |
| OracleAS Certificate Authority
|
ORAOCA_PUBLIC
|
OCATS
|
oca.dbf |
| OracleAS UDDI | UDDISYS
|
UDDISYS_TS
|
uddisys01.dbf |
| Oracle Internet Directory
|
ODS
|
OLTS_ATTRSTORE
|
attrs1_oid.dbf |
| Oracle Internet Directory
|
ODS
|
OLTS_BATTRSTORE
|
battrs1_oid.dbf |
| Oracle Internet Directory
|
ODS
|
OLTS_CT_STORE
|
gcats1_oid.dbf |
| Oracle Internet Directory
|
ODS
|
OLTS_DEFAULT
|
gdefault1_oid.dbf |
| Oracle Internet Directory
|
ODS
|
OLTS_SVRMGSTORE
|
svrmg1_oid.dbf |
| Oracle Ultra Search
|
WKSYS
|
IAS_META
|
ias_meta01.dbf |
| Oracle Ultra Search
|
WKPROXY
|
IAS_META
|
ias_meta01.dbf |
| Oracle Ultra Search
|
WK_TEST
|
IAS_META
|
ias_meta01.dbf |
| Multiple components | DSGATEWAY
|
DSGATEWAY_TAB
|
oss_sys01.dbf |
| Metadata Repository Version | INTERNET_APPSERVER_REGISTRY
|
IAS_META
|
ias_meta01.dbf |
If OracleAS Metadata Repository Creation Assistant finds even one schema of the same name in the existing database, it asks for confirmation before it drops and re-creates the schema with new data.
If you want to save the data in the schema, do not proceed. Back up the data you want to save, restore it under a different schema, and rerun OracleAS Metadata Repository Creation Assistant. This time, you can tell it to drop and re-create the schema.
To get a list of existing schema names in the database, query the ALL_USERS view:
prompt> sqlplus "sys/password as sysdba" SQL> select username from all_users;
password specifies the password for the SYS user.
See Chapter 4, "Deregistering and Removing OracleAS Metadata Repository" if you want to run OracleAS Metadata Repository Creation Assistant to remove schemas and tablespaces used by OracleAS Metadata Repository.
If OracleAS Metadata Repository Creation Assistant finds even one tablespace of the same name in the existing database, it cannot continue. It displays an error dialog. In this case:
Dismiss the error dialog and exit OracleAS Metadata Repository Creation Assistant.
Back up the data in the tablespace (if desired).
Drop the tablespace.
Rerun OracleAS Metadata Repository Creation Assistant.
To get a list of existing tablespace names in the database, query the V$TABLESPACE view:
prompt> sqlplus "sys/password as sysdba" SQL> select name from v$tablespace;
password specifies the password for the SYS user.
|
Note: If you run OracleAS Metadata Repository Creation Assistant and cancel it before it completes, it might have created some of the tablespaces listed in Table 1-9 in your database. You have to drop these tablespaces before you can rerun OracleAS Metadata Repository Creation Assistant.See Chapter 4, "Deregistering and Removing OracleAS Metadata Repository" if you want to run OracleAS Metadata Repository Creation Assistant to remove schemas and tablespaces used by OracleAS Metadata Repository. |
To drop a tablespace, you can run SQL statements manually. You can also run OracleAS Metadata Repository Creation Assistant to remove OracleAS Metadata Repository tablespaces and schemas. See Chapter 4, "Deregistering and Removing OracleAS Metadata Repository".
To run SQL statements manually, perform the following steps. The order of the tasks is important. If you delete the data files first, then you cannot drop the tablespace. If the tablespace exists, you cannot rerun OracleAS Metadata Repository Creation Assistant.
Use SQL*Plus and log in to the database as the SYS user.
prompt> sqlplus "sys/password as sysdba"
Drop the schemas in the tablespace.
SQL> drop user schema_name cascade;
Drop the tablespace.
SQL> drop tablespace tablespace_name including contents cascade constraints; SQL> exit;
Delete the data files (the .dbf files) associated with the tablespace.
If you are using files (as opposed to raw devices) for tablespaces, select the size for each tablespace that OracleAS Metadata Repository Creation Assistant will create.
OracleAS Metadata Repository Creation Assistant offers three size options for each tablespace (see Table 1-10). These sizes represent light usage, moderate usage, and heavy usage of the component. If you have applications that use a component heavily, you should select the biggest size for the component's tablespaces. You should select the minimum size for components that you do not plan on using with this repository.
The tablespace sizes are initial sizes. Extensive use of the component may increase the size of the tablespaces because they are set to AUTOEXTEND.
Table 1-10 Initial Sizes for Tablespaces
| Component | Tablespace | Initial Sizes (in MB) | ||
|---|---|---|---|---|
| Small | Medium | Large | ||
| OracleAS Portal
|
PORTAL
|
75 | 100 | 150 |
| OracleAS Portal
|
PORTAL_DOC
|
25 | 40 | 50 |
| OracleAS Portal
|
PORTAL_IDX
|
30 | 50 | 60 |
| OracleAS Portal
|
PORTAL_LOG
|
30 | 50 | 60 |
| OracleAS Single Sign-On
OracleAS Wireless Oracle Ultra Search Oracle Workflow
|
IAS_META
|
200 | 300 | 500 |
| OracleAS Discoverer
|
DISCO_PTM5_META
|
5 | 10 | 15 |
| OracleAS Discoverer
|
DISCO_PTM5_CACHE
|
5 | 10 | 15 |
| OracleAS Distributed Configuration Management (DCM) | DCM
|
50 | 100 | 200 |
| OracleAS Web Clipping Support | WCRSYS_TS
|
35 | 45 | 55 |
| OracleAS Certificate Authority
|
OCATS
|
15 | 35 | 55 |
| OracleAS UDDI | UDDISYS_TS
|
35 | 50 | 65 |
| Oracle Internet Directory
|
OLTS_ATTRSTORE
|
10 | 15 | 20 |
| Oracle Internet Directory
|
OLTS_BATTRSTORE
|
10 | 15 | 20 |
| Oracle Internet Directory
|
OLTS_CT_STORE
|
10 | 15 | 20 |
| Oracle Internet Directory
|
OLTS_DEFAULT
|
10 | 15 | 20 |
| Oracle Internet Directory
|
OLTS_SVRMGSTORE
|
10 | 15 | 20 |
| Multiple components | DSGATEWAY_TAB
|
25 | 35 | 45 |
If your existing database uses ASM, Oracle-managed files, or raw devices, you do not need to select the sizes for the tablespaces. However, you need to verify that the sizes of the storage devices are adequate for the components (see Table 1-11 and Table 1-12). If you are planning on using a component extensively, make sure the storage device for the tablespace has even more space available.
Table 1-11 Minimum Size for System Tablespaces
| Tablespace | Minimum Size |
|---|---|
| SYSTEM tablespace | 1024 MB |
| TEMP tablespace | 128 MB |
| UNDOTBS1 tablespace | 256 MB |
| UNDOTBS2 tablespace | 256 MB |
| DRSYS tablespace | 64 MB |
Table 1-12 Raw Devices for the OracleAS Metadata Repository
| Raw Device for | Minimum Size | Recommended Name |
|---|---|---|
| PORTAL tablespace | 128 MB | dbname_raw_portal_128m
|
| PORTAL_DOC tablespace | 64 MB | dbname_raw_portaldoc_64m
|
| PORTAL_IDX tablespace | 64 MB | dbname_raw_portalidx_64m
|
| PORTAL_LOG tablespace | 64 MB | dbname_raw_portallog_64m
|
| DCM tablespace | 256 MB | dbname_raw_dcm_256m
|
| OCATS tablespace | 64 MB | dbname_raw_ocats_64m
|
| DISCO_PTM5_CACHE tablespace | 64 MB | dbname_raw_discoptm5cache_64m
|
| DISCO_PTM5_META tablespace | 64 MB | dbname_raw_discoptm5meta_64m
|
| WCRSYS_TS tablespace | 64 MB | dbname_raw_wcrsysts_64m
|
| UDDISYS_TS tablespace | 64 MB | dbname_raw_uddisysts_64m
|
| OLTS_ATTRSTORE tablespace | 128 MB | dbname_raw_oltsattrstore_128m
|
| OLTS_BTTRSTORE tablespace | 64 MB | dbname_raw_oltsbttrstore_64m
|
| OLTS_CT_STORE tablespace | 256 MB | dbname_raw_oltsctstore_256m
|
| OLTS_DEFAULT tablespace | 128 MB | dbname_raw_oltsdefault_128m
|
| OLTS_SVRMGSTORE tablespace | 64 MB | dbname_raw_oltssvrmgstore_64m
|
| IAS_META tablespace | 256 MB | dbname_raw_iasmeta1_256m
|
| DSGATEWAY_TAB tablespace | 64 MB | dbname_raw_dsgatewaytab_64m
|
For information on using raw devices, see the database documentation.
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:
Connect to Oracle Internet Directory using Oracle Directory Manager.
Start up Oracle Directory Manager.
prompt> $ORACLE_HOME/bin/oidadmin
In the Connect screen, enter the connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).
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 B.3, "Manual Steps: Cleaning Up a Failed Registration or Deregistering OracleAS Metadata Repository".
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 B.3, "Manual Steps: Cleaning Up a Failed Registration or Deregistering OracleAS Metadata Repository".
To register the OracleAS Metadata Repository with Oracle Internet Directory, the Oracle Internet Directory must be version 9.0.4 or later. Note that Oracle Internet Directory version 9.2.x is not supported.
To check the Oracle Internet Directory version, run the following command:
prompt> oidldapd -version
The oidldapd command can be found in the ORACLE_HOME/bin directory, where ORACLE_HOME is the directory where you installed Oracle Internet Directory.
To start OracleAS Metadata Repository Creation Assistant:
Check that you have installed OracleAS Metadata Repository Creation Assistant. See Section 1.4, "Installing OracleAS Metadata Repository Creation Assistant" for details.
Ensure the listener for the existing database and the database itself are up and running.
If the NLS_LANG environment variable is set to a non-English locale, unset it or set it to american_america.us7ascii.
prompt> unsetenv NLS_LANG - or - prompt> setenv NLS_LANG american_america.us7ascii
If NLS_LANG is set to a non-English locale, OracleAS Metadata Repository Creation Assistant will fail to load the Workflow schema.
You can set NLS_LANG back to its original value after running OracleAS Metadata Repository Creation Assistant.
Start up OracleAS Metadata Repository Creation Assistant from the Oracle home for OracleAS Metadata Repository Creation Assistant (this is the directory where you installed OracleAS Metadata Repository Creation Assistant):
prompt> cd ORACLE_HOME_RepCA prompt> runRepca
The remaining sections in this chapter describe the procedures for using OracleAS Metadata Repository Creation Assistant.
Loading Operations
For loading operations, with or without registration with Oracle Internet Directory, select the section that matches your database type and storage option:
Table 1-13 Which Section to Read Next
| Database Type | Storage Type | Section to Read |
|---|---|---|
| Non-Real Application Clusters | File system | Section 2.1, "Installing in a Database that Uses the File System"
|
| Non-Real Application Clusters | Raw devices | Section 2.2, "Installing in a Database that Uses Raw Devices"
|
| Real Application Clusters
|
Cluster file system or volume manager | Section 2.3, "Installing in a Real Application Clusters Database"
|
| Real Application Clusters
|
Raw devices | Section 2.3, "Installing in a Real Application Clusters Database"
|
| Automatic Storage Management (ASM) | Disk group | Section 2.4, "Installing in a Database that Uses Automatic Storage Management"
|
| Automatic Storage Management (ASM) | File system | Section 2.4, "Installing in a Database that Uses Automatic Storage Management"
|
| Oracle-managed files | File system | Section 2.5, "Installing in a Database that Uses Oracle-Managed Files"
|
Registration Only Operations
If you just want to register the OracleAS Metadata Repository with Oracle Internet Directory, see Chapter 3, "Registering OracleAS Metadata Repository with Oracle Internet Directory".
Removal or Deregistration Operations
See Chapter 4, "Deregistering and Removing OracleAS Metadata Repository".
