4 Upgrading an Existing 6.x Zip or Native Package Installation

This chapter provides instructions for upgrading an existing version 6.x installation that was initially installed using either a zip or native package distribution. The following topics are included in this chapter:

Before You Begin Upgrading
Upgrading the Administration (DSCC) Host
Upgrading Directory Server and Directory Proxy Server Hosts
Upgrading Directory Server Enterprise Edition 6 on Unsupported Platforms

For information about what happens during upgrading, and about various upgrade and migration options, see Chapter 1, "Determing Whether to Upgrade or Migrate an Existing Installation."

4.1 Before You Begin Upgrading

Be sure you have resolved all issues listed in Section 1.3, "Completing Pre-Upgrade and Pre-Migration Tasks."
Upgrading must be performed by the user account that owns the Directory Server Enterprise Edition installation.
Identify the server that hosts Directory Service Control Center. Always upgrade the Administration (DSCC) host before upgrading its Directory Server host or the Directory Proxy Server host.
Upgrading requires two major procedures:
1. Upgrading the Administration (DSCC) Host
2. Upgrading Directory Server Enterprise Edition 6 on Unsupported Platforms

4.2 Upgrading the Administration (DSCC) Host

To access the Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) instances using DSCC, you must upgrade DSCC 6 to version 11g Release 1 (11.1.1.7.0).

Using DSCC 11g Release 1 (11.1.1.7.0) you can access version 6, 7.0, and 11g Release 1 (11.1.1.5.0 and 11.1.1.3.0) instances.

Stop the Cacao module. For example:
Version 6.x Zip Distribution

# INSTALL_PATH/dsee6/cacao_2/usr/sbin/cacaoadm stop

Versions 11.1.1.3, 11.1.1.5, or 7.x Zip Distributions
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
For Native Package Installations

# /usr/sbin/cacaoadm stop
Install Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0).

For more information, see " Installing Directory Server Enterprise Edition," in Installation Guide for Oracle Directory Server Enterprise Edition.
On Solaris 10 only, disable SMF services associated with Active Directory Server.
Stop the DSCC 6 registry and export its content.

The dsee6-install-path specifies the path where Directory Server Enterprise Edition 6 is installed.
1. Stop the DSCC 6 registry.
```
# dsee6-install-path/ds6/bin/dsadm stop dsee6-install-path/var/dscc6/dcc/ads
```
2. Record the DSCC 6 registry port numbers.
```
# dsee6-install-path/ds6/bin/dsadm info dsee6-install-path/var/dscc6/dcc/ads
```
3. Export the DSCC 6 registry content.
```
# dsee6-install-path/ds6/bin/dsadm export dsee6-install-path/var/dscc6/dcc/ads cn=dscc /tmp/dscc.ldif
```
  The /tmp/dscc.ldif file contains the server configuration.
Create and populate the DSCC 11g Release 1 (11.1.1.7.0) registry with the version 6 registry content.
1. Create the DSCC 11g Release 1 (11.1.1.7.0) registry by using the same ports that DSCC 6 registry has used.
```
# install-path/bin/dsccsetup ads-create -p port -P secure-port
```
2. Stop the registry.
```
# install-path/bin/dsadm stop install-path/var/dcc/ads
```
3. Import the /tmp/dscc.ldif file.
```
# install-path/bin/dsadm import install-path/var/dcc/ads /tmp/dscc.ldif cn=dscc
```
4. Start the registry.
```
# install-path/bin/dsadm start install-path/var/dcc/ads
```
5. Verify all the registrations of the server.
```
# install-path/bin/dsccreg list-servers -p port-number
```
  All the existing servers are displayed. All the registrations are version 6 registrations.
6. You can see all the Directory Server instances.
```
# install-path/bin/dsccmon view-servers -p port-number
```
  The server instances are shown as version 6 instances.
Install a supported application server, and then Deploy the DSCC 11g Release 1 (11.1.1.7.0) WAR file.

See "Appendix A, Deploying the DSCC WAR File," in Oracle Directory Server Enterprise Edition Installation Guide.

If you have upgraded DSCC that was installed by using a zip distribution, you must access DSCC as root.
Uninstall Directory Server Enterprise Edition 6.

For more information, see the Directory Server Enterprise Edition 6 Installation Guide.

4.3 Upgrading Directory Server and Directory Proxy Server Hosts

The following procedure is valid for upgrading native packages -based instances on the Solaris operating system to zip distribution-based instances on the Solaris operating system.

Stop the Cacao module. For example:
Version 6.x Zip Distribution

# INSTALL_PATH/dsee6/cacao_2/usr/sbin/cacaoadm stop

Versions 11.1.1.3, 11.1.1.5, or 7.x Zip Distributions
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
```
# INSTALL_PATH/dsee7/bin/cacaoadm stop
For Native Package Installations

# /usr/sbin/cacaoadm stop
Install Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0).
Before you upgrade the version 6 instances that were created using native packages to the 11g Release 1 (11.1.1.7.0) 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:
```
$ install-path/bin/dsadm autostart --off INSTANCE_PATH
```
- If your instance is registered as a Windows service, type the following command:
```
$ install-path/bin/dsadm disable-service --type WIN_SERVICE INSTANCE_PATH
```
- If your instance is registered as an SMF service, type the following command:
```
$ install-path/bin/dsadm disable-service --type SMF INSTANCE_PATH
```
- If your instance is registered in a cluster, type the following command:
```
$ install-path/bin/dsadm disable-service --type CLUSTER INSTANCE_PATH
```

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

$ install-path/bin/dsadm upgrade [-i] INSTANCE_PATH

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

# install-path/bin/dsadm upgrade /local/example
Directory Server instance '/local/example' will be upgraded to version 11g Release 1 (11.1.1.7.0).
It will no longer be usable with DSEE 6 commands.
Moving legacy scripts into '/local/example/bak/2011-03-28-01-45-18' ...
Adding new files to instance ...
Upgrading dse.ldif ...
Old version of dse.ldif has been moved into '/local/example/bak/2011-03-28-01-45-18'.
Upgrading dse.ldif ...
Old version of dse.ldif has been moved into '/local/example/bak/2011-03-28-01-45-18'.
Old version of 00core.ldif has been moved into '/local/example/bak/2011-03-28-01-45-18'.
Directory Server instance '/local/DSEE-2011-03-28-01-26/instances/SSL_02' is now ready to be used with ODSEE 11g Release 1 (11.1.1.7.0) comm

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

Create a new DSCC agent and add the agent to the DSCC registry.

Create a DSCC agent:

# install-path/bin/dsccagent create
Enter DSCC agent password: ***
Confirm the password: ***
Agent instance install-path/var/dcc/agent has been created successfully
Run the following command to register the agent in the registry: install-path/bin/dsccreg add-agent install-path/var/dcc/agent

Register the new DSCC agent in the DSCC registry.

Use the command displayed at the completion of the previous step. For example:
```
# install-path/bin/dsccreg add-agent install-path/var/dcc/agent
```
If the new DSCC agent doesn't listen on the same part as Cacao, then run the following command:
```
# install-path/bin/dsccreg add-server
```

Create an SNMP agent, and configure Directory Server instances to use the SNMP agent.

Create the SNMP agent.

# install-path/bin/dsccagent enable-snmp

Configure all Directory Server instances you want to manage through SNMP.

Run the following command to obtain the DS port number for an instance you want to manage through SNMP:

# install-path/bin/dsccagent info
Instance Path         :   install-dir/dsee7/var/dcc/agent
Owner                 :   root
JMX port              :   3997
SNMP port             :   3996
DS port               :   3995
State                 :   Stopped
PID                   :   -
DSCC hostname         :   host2
DSCC non-secure port  :   3998
DSCC secure port      :   3999
SNMP v3               :   Disabled
Instance version      :   A-A00

Run the following command using the DS port number obtained in the previous step to set the port number argument:

# install-patch/bin/dsconf set-plugin-prop dssnmp argument:on argument:3995

Remove Directory Server Enterprise Edition 6 with a system command. For example:

# rm -r install-path
(Optional) If you disabled any services prior to upgrading, be sure to re-enable those services now.

After upgrading is complete, when you start DSCC, it uses the new DSCC agent.

Directory Server 6 is Noncompliant with RFC 4522

After upgrading to version 11g Release 1 (11.1.1.7.0), 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.

Upgraded Instances Cannot Be Restored

The legacy instances, once upgraded, cannot be restored to the 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.7.0), you must unregister the Directory Server instances from DSCC 6 and register them with DSCC 11g Release 1 (11.1.1.7.0). For more information about registration and unregistration, refer to dsccreg.

4.4 Upgrading Directory Server Enterprise Edition 6 on Unsupported Platforms

In Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0), some platforms are no more supported. You must perform the specific operations to use your existing data and instances.

For more information about supported platforms, see the ODSEE Certification Matrix. (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

Refer to the following procedure based on your requirements:

To Upgrade Directory Server Enterprise Edition From Legacy Operating System
To Upgrade 32-bit Server Instances

4.4.1 To Upgrade Directory Server Enterprise Edition From Legacy Operating System

For more information on supported operating systems, see the ODSEE Certification Matrix. (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

Stop the Directory Server and Directory Proxy Server instances.
Take a backup of the whole filesystem.

For more information, refer to Backing Up a File System in Binary Backup in Administrator's Guide for Oracle Directory Server Enterprise Edition.

If you need to upgrade only the Directory Proxy Server instances, use only the dpadm backup command.
Upgrade your operating system version or choose a different machine with the supported operating system version installed.

Note:

If you are upgrading your operating system on the same machine, do not forget to copy your back up data to other machine.
Install Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0).

Based on the solution, refer to any of the following procedures:
- Based on your previous installation and platform combination, see the Hardware and Operating System Requirements in Release Notes for Oracle Directory Server Enterprise Editionto find out what type of distribution you can install.
- For detailed installation instructions, see the Installation Guide for Oracle Directory Server Enterprise Edition.
Restore the filesystem that you backed up in Step 2.

In case of only Directory Proxy Server instances, you can restore them using dpadm restore.
Upgrade your legacy server instances.
- For Directory Server instances:
```
install-path/bin/dsadm upgrade INSTANCE_PATH
```
- For Directory Proxy Server instances:
```
install-path/bin/dpadm upgrade INSTANCE_PATH
```

4.4.2 To Upgrade 32-bit Server Instances

There is no direct way to upgrade Directory Server Enterprise Edition 6 32-bit server instances that are running on 64-bit Red Hat Enterprise Linux or SUSE Linux Enterprise Edition operating system. Even though the server instances cannot be upgraded fully automatically, the dsadm upgrade and dpadm upgrade commands upgrade the server configuration successfully.

Refer to the following procedure to upgrade such instances:

If your Directory Server instance is configured to use non-default directories for databases, note the following paths:

For databases:

DSEE_6_install-path/ds6/bin/dsconf get-server-prop -p port-number db-env-path db-log-path

For each suffix:

DSEE_6_install-path/ds6/bin/dsconf get-suffix-prop -p port-number SUFFIX_DN db-path

Export your data using version 6 installation.

DSEE_6_install-path/ds6/bin/dsadm export INSTANCE_PATH SUFFIX_DN LDIF_FILE

Take a backup of all the instances.

$ tar cf BACKUP_INSTANCE INSTANCE_DIRECTORY

Upgrade your legacy server instances.

Note:

If you have a customized schema, that needs to be manually upgraded as well. See the documentation for your version of Directory Server Enterprise Edition for detailed instructions on how to upgrade customized schema. See the Legacy Sun Identity Management Documentation webpage at http://www.oracle.com/technetwork/documentation/legacy-sun-identity-mgmt-193462.html.
- For Directory Server instances:
```
DSEE_7_install-path/bin/dsadm upgrade INSTANCE_PATH
```
- For Directory Proxy Server instances:
```
DSEE_7_install-path/bin/dpadm upgrade INSTANCE_PATH
```
If your Directory Server instance was configured to use non-default directories for databases, the configuration has been reset but files have not been deleted. Before reconfiguring your instance to use non-default directories, you must delete all old databases, caches, and transaction logs.
Import your data in the version 11g Release 1 (11.1.1.7.0) server instance.

For each suffix:
```
install-path/bin/dsadm import INSTANCE_PATH LDIF_FILE SUFFIX_DN
```