This chapter tells you how to upgrade from Oracle Internet Directory release 2.1.1.x or release 3.0.1.x to Oracle Internet Directory Release 9.2.1.0.
This appendix contains these topics:
Recommended Upgrade Procedure
To upgrade Oracle Internet Directory, follow the instructions in the Oracle9i Database Server Release 2 (9.2) installation documentation for your operating system.
Alternate Procedure: Upgrading a Standalone Oracle Internet Directory Node
In certain circumstances, it can be awkward to attempt an upgrade for a standalone Oracle Internet Directory node:
- When there is insufficient disk space to install and upgrade Oracle Internet Directory Release 9.2 on the machine where the prior version of Oracle Internet Directory resides
- When the amount of data in the prior Oracle Internet Directory version is huge, and it is more comfortable to export or import data than to do database migration.
Note: If the Oracle Internet Directory node is taking part in replication or is configured for replication, then this procedure should not be used to upgrade the node.:
|
To upgrade the directory in these circumstances, follow the steps in the sections listed here:
Task 1: Stop Oracle Directory Server on the Old Version Node
To stop the Oracle directory server, run the following command from $
ORACLE_HOME
/bin/
on the node:
oidctl connect=<db_connect_string> server=oidldapd instance=1 stop
Task 2: Backup the Sponsor Node by Using Export Utility
- Create a new file, oidexp.dat, containing the following:
FILE=oid.data
OWNER=ods, odscommon
GRANTS=y
ROWS=y
- Run the following command (from $ORACLE_HOME/bin/) against the identified sponsor node:
exp system/manager PARFILE=oidexp.dat
Note: OID schema and data will be backed up in oid.data file. Move this file to the new node before performing the next task.:
|
Task 3: Load Data into the New Node by Using the Import Utility
- Run the following SQL scripts:
cd $ORACLE_HOME/ldap/admin/
sqlplus system/manager @ldapdrop.sql
sqlplus system/manager @ldapxact.sql
sqlplus system/manager @ldapxsec.sql
- Create a new file, oidimp1.dat, containing the following:
FILE=oid.data
FROMUSER=ods
TOUSER=ods
- Run the following commands against the new node:
imp system/manager PARFILE=oidimp1.dat
Note: Make sure the backup oid.data file is present in the
current directory:
|
- Create a new file, oidimp2.dat, containing the following:
FILE=oid.data
FROMUSER=odscommon
TOUSER=odscommon
- Run the following commands against the new node:
imp system/manager PARFILE=oidimp2.dat
Note: Make sure the backup oid.data file is present in the
current directory:
|
Task 4: Perform Oracle Internet Directory Schema Upgrade
- Launch the OID Configuration Assistant by running
$
ORACLE_HOME
/bin/oidca
- Click Next at the Welcome Screen.
- Select the option `Upgrade an existing OID' and click Next.
- The Database Migration Screen comes up. Here you are required to provide the information about the database to which Oracle Internet Directory data has been imported. (New version OID). Enter the following information
- Database SID
- Passwords for the database users, `SYSTEM' and `ODS' respectively
- Oracle home
- Location of the INIT.ORA file.
- Listener Port for the OID database
- Connect String for the OID database
- Click Next. (When this operation completes, the Oracle Internet Directory base schema has been upgraded to Oracle Internet Directory version 9.0.2.1.0.)
- In the next screen, provide the following information about the Oracle directory server:
- Non-SSL port on which the directory server needs to be started. The default value specified is 389.
- SSL port on which the directory server needs to be started. The default value specified is 636.
- The super-user distinguished name.
- The corresponding super-user password.
- Click Next. In the next step, Oracle-context-related information and the Oracle Directory Integration Platform-related information will be upgraded.
- The Upgrading Subscriber screen appears. Here, you need to enter the distinguished name (DN) that identifies the root of your organization--for example,
o=acme, dc=com
. This domain is then upgraded to become the default subscriber.
- Click Next. The User Data Migration screen appears. This step might take a long time if you have a large directory. If you have a large directory--that is, more than 10,000 users--then Oracle Corporation recommends that you postpone your data migration and do it as a postinstallation step.
- However, if you want to do the user data migration as a part of this OID Configuration Assistant operation, select Yes and click Next. This completes the user data migration.
At the end of the upgrade, the directory server is running, listening to the specified Non-SSL and SSL ports.
Post-Upgrade Task: Migrate User Data
If you have a large directory--that is, greater than 10,000 entries--then Oracle Corporation recommends that you migrate the user data as a post-upgrade task.
- Use ldapsearch to output all the encrypted user passwords to a file.
ldapsearch -L -h OID_host_name -p OID_Non-SSL_port -D OID_Super_User_DN -w
OID_Super_User_Password -b "" -s sub "objectclass=*" dn userpassword
$ORACLE_HOME/ldap/install/pwdin.ldif
- Use the passwordconvert tool to convert the user passwords in the file
$
ORACLE_HOME
/ldap/install/pwdin.ldif
from hex to base-64.
passwordconvert -m hex2base64 -f modify
$ORACLE_HOME/ldap/install/pwdin.ldif
$ORACLE_HOME/ldap/install/pwdout.ldif
- Use ldapmodify to upload the base-64 encoded user passwords in the file
$
ORACLE_HOME/ldap/install/pwdout.ldif
into the directory server.
ldapmodify -h OID_host_name -p ID_Non-SSL_port -D ID_Super_User_DN -w ID_
Super_User_Password -f $ORACLE_HOME/ldap/install/pwdout.ldif.