| Oracle® Fusion Middleware Upgrade and Migration Guide for Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) Part Number E28971-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Upgrade and Migration Guide for Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) Part Number E28971-01 |
|
|
PDF · Mobi · ePub |
Upgrade and migration options enable you to replace an existing installation of Directory Server Enterprise Edition with the 11g Release 1 (11.1.1.7.0) release. The following topics are contained in this chapter:
Upgrading is supported for all Directory Server Enterprise versions other than Sun Java Directory Server 5.x. For Sun Java Directory Server 5.x, migration is the only option.
When you upgrade an existing 11g Release 1 , 7.x, or 6.x ODSEE instance to 11g Release 1 (11.1.1.7.0), the Directory Server configuration and files are automatically upgraded in place in the instance. You don't have to copy, export, or import anything.
When you migrate a 5.x instance to 11g Release 1 (11.1.1.7.0) using the dsmig command, the dsmig tool generates a new 11g Release 1 (11.1.1.7.0) instance, and then automatically copies over all the configuration from the existing 5.2 instance to the new 11g Release 1 (11.1.1.7.0) instance. If you cannot use the dsmig command, or simply choose not to use it, then you must maually copy the configuration, user data, schema, security components, and plug-ins from the existing 5.2 instance to the new 11g Release 1 (11.1.1.7.0) instance.
Upgrade or migrate to 11g Release 1 (11.1.1.7.0) based upon the existing installation version number, and based upon whether ODSEE was initially installed using a zip distribution or using a native package distribution.
ODSEE 11g Release 1 (11.1.1.7.0) provides the following paths:
When you upgrade an existing 11g Release 1 or 7.x ODSEE instance that was initially installed using a zip distribution, you overwrite the 11g Release 1 or 7.x version with a new installation of the 11g Release 1 (11.1.1.7.0) binaries. Co-existence with the older version is not possible.
When you upgrade an existing 11g Release 1 or 7.x ODSEE instance that was initially installed using a native package distribution, the 11g Release 1 (11.1.1.7.0) binaries are installed next to the older version. The older version can temporarily co-exist on the same machine.
When you upgrade an existing Version 6.x instance, whether initially installed using a zip or native package, the 11g Release 1 (11.1.1.7.0) binaries are installed next to the older version. The older version can temporarily co-exist on the same machine.
Note:
If you are upgrading an existing 6.2 installation to 11g Release 1 (11.1.1.7.0), you must complete important pre-upgrade steps. See Section 1.3, "Completing Pre-Upgrade and Pre-Migration Tasks."
If you use the dsmig tool, the 11g Release 1 (11.1.1.7.0) instance is automatically generated. All configuration and user data, and all other necessary files are copied from the 5.2 instance to the new 11g Release 1 (11.1.1.7.0) instance. The 5.2 instance and 11g Release 1 (11.1.1.7.0) instance cannot co-exist on the same machine.
If you cannot use the dsmig tool or choose not to use it, you must manually create the new 11g Release 1 (11.1.1.7.0) instance. You must also manually copy the existing configuration and user data, security components, and plug-ins from the older 5.2 instance to the new 11g Release 1 (11.1.1.7.0) instance.
Before you begin upgrading or migration, be sure to complete the following preparation steps:
Before upgrading legacy Directory Server and Directory Proxy Server instances, make a backup of all the instances so that they can be restored if you encounter a problem during upgrade. Use a filesystem utility such as tar or cpio to backup the entire filesystem. For example:
$ tar cf BACKUP_INSTANCE INSTANCE_DIRECTORY
If you are upgrading from version 6.2 to 11g Release 1 (11.1.1.7.0), complete the following steps before proceeding with upgrade.
Export database to an LDIF file.
For more information see the dsadm export command in dsadm.
Upgrade Directory Server Enterprise Edition 6.2 installation to version 6.3.
For detailed information, see Sun Directory Server Enterprise Edition 6.3 Installation Guide.
Import data from the LDIF file that was created in Step 1.
For more information, see "Importing Data From an LDIF File" in Administrator's Guide for Oracle Directory Server Enterprise Edition
In some cases, directly upgrading the server instances is not possible. For example, upgrading a version 6 32-bit instance that was running on Red Hat Enterprise Linux or SUSE Linux Enterprise Edition 64-bit platform is no longer possible. The instance has to be 64-bit to run on 64-bit platform. Such cases require extra steps.
If you are upgrading version 6 instances on a platform that is no longer supported, see Section 4.4, "Upgrading Directory Server Enterprise Edition 6 on Unsupported Platforms."
If Directory Server chaining is configured, then delete such configurations before proceeding with upgrade or migration.
Stop the Cacao module. For example:
# INSTALL_PATH/dsee6/cacao_2/usr/sbin/cacaoadm stop
# INSTALL_PATH/dsee7/bin/cacaoadm stop
# INSTALL_PATH/dsee7/bin/cacaoadm stop
# /usr/sbin/cacaoadm stop
See the appropriate documentation for the upgrade or migration option you've chosen:
See Section 2, "Upgrading an Existing 11g Release 1 or 7.x Zip Distribution Installation."
See Chapter 3, "Upgrading an Existing 11g Release 1 or 7.x Native Package Installation."
See Chapter 4, "Upgrading an Existing 6.x Zip or Native Package Installation."
See Chapter 5, "Overview of the Migration Process for Directory Server."
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|