This article is NOT intended to be a replacement for the Oracle manuals!

The intention of this article is to have a rough outline for seasoned Oracle DBAs to manually install Oracle Internet Directory (OID) 10gR2 in an existing database, since I haven't been able to find a single source for how to install OID from scratch with the intention of migrating from Oracle Names to OID.

Why not “just” use the DBCA and other wizards? I believe that they install many more options of the Oracle database than are needed for a production database. I'll site the ubiquitous SCOTT schema as an example. I am an Oracle minimalist, preferring to do without the management overhead of unnecessary schemas and options and their associated security implications. I think that it's also a very good excersizeexercise to become intimately familiar with an Oracle option before using it in a production environment. A manual installation of an Oracle database is a good start.

Therefore, to be able to use this article, you must already know how to create an Oracle database, how to manage it, and how to restore it from your backup in case you mangle it.

In addition, you will need to follow the directions of several Metalink articles. This will require a support contract from Oracle Corp. Sorry, but I don't believe it would be legal to duplicate the content of the Metalink articles here.

This article was created from information used to install replicated OID on a pair Sun V100s (yes, this entire procedure must be followed twice in order to replicate OID!), each with a single CPU and 1GB of RAM. All performance estimates listed here were done using this spartan hardware. Your times will vary (hopefully much much better!).

Also, I originally started this article in 2006. Some changes and updates, especially in Metalink articles, have been noted here. Any feedback would be most welcome for other users of this article. The content could no doubt use some "adjusting" as well.

A final note: I use a slightly modified form of the wonderful Optimal Flexible Architecture (“OFA”, found at http://download.oracle.com/docs/html/A97297_01/appg_ofa.htm). For example, while OFA states that an ORACLE_HOME might be placed at /u01/app/oracle/product/10.2.0, I prefer an abbreviated version of /opt/oracle/10.2.0. (at least for this version of Oracle). The reasons behind my choice are beyond the scope of this article, but I think it's important to realize in order to make the most of the information presented here and apply it to your own Oracle environment.

• For Solaris, download the validation tarball from MetaLink 334567.1

Update: The above link describes the Oracle HCVE tool, which has been superseded by RDA, documented in: Metalink 250262.1

• For other platforms, search for “pre-installation checklist” on Metalink.
• While some failures from the validation are not critical, most are. In particular, these are definitely vital:
  • OS certified?
  • User in /etc/passwd?
  • Group in /etc/passwd?
  • Umask set to 022?
  • ulimits OK?
• Ideally, all items in the validation should pass before installation completes.

• Install the Oracle 10g software.
• On the first screen, choose “Advanced installation”. The Installer will restart in Advanced Mode.
• Choose “Custom” installation type.
• Enter a name for the new ORACLE_HOME and a path. A typical path might be /opt/oracle/10.2.0
• 
• 
• 
• 
• 
• Approximate install time: 10 minutes.

• UltraSearch is required by the MRCA.
• Java NCOMP software must be loaded (off of the Companion CD).

• @?/rdbms/admin/catblock in SQLPlus, connected as SYSDBA.
• Install JVM. See Metalink 276554.1
• Install Oracle Text. See Metalink 280713.1
• Create WKSYS schema and objects.
  • For 10gR2, see Metalink 337992.1
  • Untested on other versions.

• 
• 
• 
• 
• 
  

• After the Companion CD install, patch the install to the latest release (“minipack”), if available. Currently, it's 10.2.0.2.0.

• This DB will be used to house the metadata repository for OID.
• This should be version 10g, preferrablypreferably 10gR2 if the wizards will allow it.
• The following parameter values are recommended for the OID Metadata Repository DB:
  • sga_target = 600M
  • db_cache_size = 150M
  • shared_pool_size = 175M
  • java_pool_size = 120M
  • pga_aggregate_target = 100M
  • aq_tm_processes = 1
  • sessions = 400
  • compatible = 10.2.0.0 ALL digits are significant and this MUST be set at time of DB creation!!!
• Approximate time to create the database: 50 minutes.

• Continue with Oracle UltraSearch from above
  • Approximate install times
    • JVM: 30 minutes
    • OracleText: 15-20 minutes
    • UltraSearch/WKSYS: 3 minutes
• Install Oracle XML Database (aka “XDB”) with the XDK public synonyms (the default).
  • Make sure to manually create the XDB TS first!

CREATE TABLESPACE XDB

DATAFILE '/oracle/noidro/xdb_01_NOIDRO.dbf'

SIZE 100M REUSE AUTOEXTEND ON NEXT 100M MAXSIZE 2048M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K

SEGMENT SPACE MANAGEMENT AUTO;

• See Metalink 243554.1
• Approximate time to install: 7-8 minutes
• Install Oracle Spatial DESPITE THIS NOT BEING DOCUMENTED AS A REQUIREMENT. See Metalink 270588.1
• Approximate time to install: 45 minutes

• Oracle moved the OID software into the Oracle Application Server domain.
• This version was downloaded from http://www.oracle.com/technology/software/products/ias/htdocs/101202.html
• Download all CDs of Application Server 10g Release 2 for the chosen server platform (e.g. there are 4 CDs for Solaris)
• Also download the Metadata Repository Creation Assistant (“MRCA¨) for a similar version from the same page. In this install, the MRCA was version 10.1.2.0.3

• http://www.oracle.com/technology/documentation/1012_solaris/docs.htm
• http://download-east.oracle.com/docs/cd/B14099_19/manage.htm
• Read “Installation Guide”. Pay attention to necessary OS changes!!!
• Read “OracleAS Metadata Repository Creation Assistant User's Guide”
• Read “Oracle Application Server Administrator's Guide” for backup/recovery procedures/issues.

• Approximate time to install: 2 hours 20 minutes
• /opt/oracle/MRCA/runRepca
• 
• 
• 
• 
• 
• 
• 
• 
• 

If the ODS account exists at this point, it must be GRANTed ALTER SESSION priv in order to avoid ORA-1031 errors from showing up in trace files, as per the resolution of an SR filed with Oracle Support.

• 
  
• Choose Oracle Application Server Infrastructure 10g
• 
  

• Choose Identity Management
• 
  
• Check the *Root Privileges” box and click Next.
• 
  
• Choose Oracle Internet Directory
• UNSELECT Oracle Application Server Single Sign-On
• UNSELECT Oracle Application server Delegated Administration
• SELECT High Availability and Replication ONLY for the Consumer Node!
• 
• Choose Automatic for Port Configuration Options.
• 
  
• Choose a DBA login for the Repository DB (e.g. user “SYSTEM”).
• 
  
• For Replication on Consumer Node ONLY
  • Choose Replication for the High Availability or Replication Option.
  • Choose LDAP for Oracle Internet Directory Replication Mode.
  • Choose the Master Node and Port 389 for Oracle Internet Directory Node.
  • Choose cn=orcladmin and it's password for the Master Oracle Internet Directory Login.
• Choose Custom Namespace
  • e.g. dc=mycompany,dc=com
  • 
    
• Specify Instance Name and ias_admin Password.
  • Not sure where this would be used, if at all, on an OID-only installation.
  • For Instance Name:, choose the node name.
  • For the passwords, choose any password
  • 
  
• 
• 
  
• After the installation is complete, shut down the extraneous procs that the Installer starts.
  1. Change ORACLE_HOME to the OID installation
  2. $ORACLE_HOME/opmn/bin/opmnctl stopall
  3. emctl stop iasconsole

• Use Single-Master replication group type
  • One Supplier node, one Consumer node.
  • As opposed to Multi-Master or Fan-Out.
• Use LDAP-based replication agreements (as opposed to AR).