To Upgrade Directory Server Instances (Oracle Fusion Middleware Upgrade and Migration Guide for Oracle Directory Server Enterprise Edition)

Oracle Fusion Middleware Upgrade and Migration Guide for Oracle Directory Server Enterprise Edition

To Upgrade Directory Server Instances

The following procedure is also valid for the following:

Upgrading the native packages based instances on Solaris operating system to zip distribution based instances on Solaris operating system.
Upgrading the zip distribution based instances on Solaris operating system to native packages based instances on Solaris operating system. In this case, step 2 is not applicable.
Upgrading native packages based instances on the platforms that are no more supported for native packages based distribution in this version. On such platforms, the instances must be upgraded to zip distribution instances.

Install Directory Server Enterprise Edition 11g Release 1 (11.1.1).

Before upgrading the version 6 instances created by using native packages, to the 11g Release 1 (11.1.1) zip distribution instances, disable all the features specific to native packages by using the version 6 native packages installation.
- If your instance is registered to start at boot, type the following command:
  $ ./dsadm autostart --off INSTANCE_PATH
- If your instance is registered as a Windows service, type the following command:
  $ ./dsadm disable-service --type WIN_SERVICE INSTANCE_PATH
- If your instance is registered as an SMF service, type the following command:
  $ ./dsadm disable-service --type SMF INSTANCE_PATH
- If your instance is registered in a cluster, type the following command:
  $ ./dsadm disable-service --type CLUSTER INSTANCE_PATH

Type the following command from the version 11g Release 1 (11.1.1) installation to upgrade the Directory Server instances.

$ ./dsadm upgrade [-i] INSTANCE_PATH

For example, to upgrade the /local/example instance, type the following command:

# ./dsadm upgrade /local/example

Directory Server instance '/local/example' will be upgraded to version 7.
It will no longer be usable with DSEE 6 commands.
Do you want to continue [y/n]? y
Moving legacy scripts into '/local/example/bak/2009-08-25-11-23-16' ...
Adding new files to instance ...
Upgrading dse.ldif ...
Old version of dse.ldif has been moved into '/local/example/bak/2009-08-25-11-23-16'.
Directory Server instance '/local/example' is now ready to be used 
with DSEE 7 commands.

Use —i with the dsadm upgrade command to suppress the warning message.

Note –

After upgrading to version 11g Release 1 (11.1.1), the following version 6 behavior is preserved.

Directory Server 6 is noncompliant with RFC 4522 when returning binary attributes in search results. To preserve this behavior, by default, the compat-flag Directory Server configuration property is set to no-rfc4522. To check the value of compat-flag, refer to the following command:

$ dsconf get-server-prop -p port compat-flag

For more information about the compat-flag property, see server(5dsconf).

Upgrade all the Directory Server instances that you want to use with the version 11g Release 1 (11.1.1), by using the dsadm upgrade command.

Note –

The legacy instances once upgraded cannot be restored to its previous installation.

The following dsadm commands do not require legacy instances to be upgraded before using them.

     - info
     - stop
     - disable-service
     - autostart --off
     - get-flags
     - set-flags
     - add-cert
     - add-selfsign-cert
     - export-cert
     - import-cert
     - import-selfsign-cert
     - list-certs
     - remove-cert
     - renew-cert
     - renew-selfsign-cert
     - request-cert/show-cert
     - show-access-log
     - show-error-log
     - delete

To use the upgraded instances with DSCC 11g Release 1 (11.1.1), you must unregister the Directory Server instances from DSCC 6 and register them with DSCC 11g Release 1 (11.1.1). For more information about registration and unregistration, refer dsccreg(1M).

(Optional) Remove Directory Server Enterprise Edition 6.