Oracle Internet Directory Administrator's Guide Release 3.0.1 Part Number A90151-01 |
|
This chapter tells you how to upgrade to Oracle Internet Directory release 3.0.1 from Oracle Internet Directory release 2.1.1.
This appendix contains these topics:
You can upgrade one node at a time until you have upgraded all of the nodes in the replication group. In a replicated environment, a node running release 3.0.1 can co-exist with nodes running previous releases of Oracle Internet Directory. Moreover, in a replicated environment, upgrade of one node to release 3.0.1 requires no network downtime. The other nodes can remain available while the upgrade progresses.
Before you upgrade, perform the following tasks:
To upgrade on a single node, follow the instructions in the installation documentation for your operating system.
Upgrading a multi-node Oracle Internet Directory system to release 3.0.1 requires special attention. This section discusses the two ways to upgrade a multi-node Oracle Internet Directory system. It contains these topics:
Use this method if you do not want any system downtime. While the upgrade on one node is in progress, it allows all the other nodes to remain available. However, using this method requires that you clearly understand and strictly follow these guidelines:
Perform the following tasks, first on the MDS, then on the master sites.
Before shutting down the database at the MDS, run the script delasrjobs.sql located in $
ORACLE_HOME/ldap/admin
on the installation CD. This script deletes Oracle9i Replication jobs on other master sites that push changes to the MDS. Deleting these jobs temporarily removes the MDS from the replication environment so that no changes can be applied to it. Other nodes, however, remain operational and continue replicating changes.
If you do not shutdown the database and listener, then Oracle Universal Installer prompts you to do it.
See Also:
|
Run Oracle Universal Installer to upgrade to Oracle Internet Directory release 3.0.1, which uses Oracle9i release 9.0.1. The installer both migrates the database and upgrades Oracle Internet Directory.
After the upgrade is completed, the database and listener are started automatically. Verify that they are running.
See Also:
|
Test the connectivity to other nodes. If connectivity is broken, then use the backup copies of listener.ora
, sqlnet.ora
and tnsnames.ora
and restart the listener. The backup files are named listener
date.bak
, sqlnet
date.bak
and tnsnames
date.bak
.
After you have upgraded the node, create jobs on other nodes. You do this by executing $
ORACLE_HOME/ldap/admin/creasrjobs.sql
on the upgraded node. This script creates on the other nodes the jobs that were deleted in "Task 2: Delete Jobs on Other Nodes". These jobs now start pushing the existing changes and new changes on other nodes to the node you have just upgraded.
The upgrade process automatically starts the OID Monitor, the directory server, and the directory replication server. Be sure that these processes are running.
After upgrading the MDS, upgrade other master sites one at a time. Perform tasks 1 through 12 on each master site until all the nodes are upgraded.
Use this method to upgrade all the nodes at the same time. If you use this method, then the system is unavailable during the upgrade process.
dn: changetype:modify replace:orclservermode orclservermode:r
ldapmodify -D "cn=orcladmin" -w welcome -h host_name -p port_number -f input_file.ldif
Before moving to next step, wait for the change log queue to empty. If you skip this step, then changes in the change log queue will be applied once the nodes are upgraded.
If you do not shutdown the database and listener, then Oracle Universal Installer prompts you to do it.
See Also:
|
Run Oracle Universal Installer to upgrade to Oracle Internet Directory release 3.0.1, which uses Oracle9i release 9.0.1. The installer both migrates the database and upgrades Oracle Internet Directory.
After the upgrade is completed, the database and listener are started automatically. Verify that they are running.
See Also:
|
Test the connectivity to other nodes. If connectivity is broken, then use the backup copies of listener.ora
, sqlnet.ora
and tnsnames.ora
and restart the listener. The backup files are named listener
date.bak
, sqlnet
date.bak
and tnsnames
date.bak
.
The upgrade process automatically starts the OID Monitor, the directory server, and the directory replication server. Be sure that these processes are running.
Normally, you do not need to perform LDIF-based upgrading. Use this method when you cannot successfully run the database-based upgrade process.
Oracle Corporation recommends that you use the LDIF-based backup procedure to backup your existing release of Oracle Internet Directory. This is explained in this section.
The LDIF-based upgrade process requires the following procedures on a node being upgraded:
Be sure that the directory server is not running, then run the script backup_oid.sh located in the $
ORACLE_HOME/ldap/install
directory on the CD.
The syntax to run backup_oid.sh is:
backup_oid.sh -connect net_service_name -pass password_for_DB_account_`ods'
The backup_oid.sh script does the following:
.dmp
files--for example, attr_store.dmp
--in $
ORACLE_HOME
/ldap/load
directory
OID_userdata.ldif
in $
ORACLE_HOME/ldap/load
. The subtree under cn=OracleSchemaVersion
(if it exists) is also backed up as orcl_schemaver.ldif
in the $
ORACLE_HOME/ldap/load
directory.
If you plan to install Oracle Internet Directory release 3.0.1 in the same ORACLE_HOME, then save these generated files in some other location.
To do this:
$
ORACLE_HOME/1dap/load
:
$
ORACLE_HOME/ldap/install
.
The syntax for restore_oid.sh is:
restore_oid.sh -connect net_service_name -pass password_for_DB_account_`ods'
The restore_oid.sh script does the following:
-restore
option
Start OID Monitor and the directory server.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|