You must consider the following points before applying the Directory Server Enterprise Edition 6.3 patch.
Native package based distribution. All Directory Server and Directory Proxy Server instances, including the DSCC registry, must be stopped before the Directory Server Enterprise Edition 6.3 patch is applied.
If you apply the patch without stopping the server instances, the instances might crash the next time you restart them.
On Windows, the following dsadm command fails to stop the DSCC registry.
dsadm.exe stop C:\Program Files\Sun\JavaES5\DSEE\var\dscc6\dcc\ads |
As a workaround, kill the bin_slapd.exe process using Task Manager and login as Administrator. You can now start and stop the DSCC registry successfully. The owner of the DSCC registry remains the same, that is, SYSTEM.
For native package based distribution: after applying patches to upgrade Directory Server Enterprise Edition, you must restart Sun Web Console using the following command:
# smcwebserver restart |
To use the localized console, apply the Directory Server Enterprise Edition 6.3 patch before the Directory Server Enterprise Edition 6.3 localized patch. Then run the following commands in the specified order.
# dsccsetup console-unreg |
# dsccsetup console-reg |
For more information, see bug 6583131 in Known Directory Server Issues in 6.3.
Zip based distribution. All Directory Server and Directory Proxy Server instances must be stopped before the Directory Server Enterprise Edition 6.3 zip distribution is applied on top of one of the applicable zip installations:
Directory Server Enterprise Edition 6.0
Directory Server Enterprise Edition 6.1
Directory Server Enterprise Edition 6.2
This check is done by the dsee_deploy command itself, but is not performed on the Microsoft Windows 2000 platform. For more information, see 6660462 in Known Directory Server Issues in 6.3.
If you apply the patch without stopping the server instances, the instances might crash the next time you restart them.
Note that the patchzip is not applied to the Directory Service Control Center until you undeploy and then redeploy the WAR file. This requirement is related to bug 6583131 in Known Directory Server Issues in 6.3.