Title: upgrade
Author:
Generator: DocBook XSL-NS Stylesheets v1.76.1 <http://docbook.sf.net/>
Date: 05/28/2013
Manual: Tools Reference
Source: OpenDJ 2.6.0
Language: English
* Define some portability stuff
-----------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://bugs.debian.org/507673
http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------
* set default formatting
-----------------------------------------------------------------
disable hyphenation
disable justification (adjust text to left margin only)
-----------------------------------------------------------------
* MAIN CONTENT STARTS HERE *
-----------------------------------------------------------------
\w'upgrade 'u upgrade {options}
This utility upgrades OpenDJ configuration (schema, directory server configuration, and other configuration files) and application data (primarily directory data) so that it is compatible with the binary files and scripts that are installed.
The upgrade command thus performs only part of the upgrade process, which includes the following phases for a single server.
\h'-04' 1.\h'+01'\c .\}
\h'-04' 2.\h'+01'\c .\}
\h'-04' 3.\h'+01'\c .\}
\h'-04' 4.\h'+01'\c .\}
.it 1 an-trap .nr an-no-space-flag 1 .nr an-break-flag 1
Important
The upgrade command does not back up OpenDJ before you upgrade, nor does it restore OpenDJ if the upgrade command fails. In order to revert a failed upgrade, make sure you back up OpenDJ directory server before you overwrite existing binary and script files.
By default, the upgrade command requests confirmation before making important configuration changes. You can use the --no-prompt option to run the command non-interactively.
When using the --no-prompt option, if the upgrade command cannot complete because it requires confirmation for a potentially very long or critical task, then it exits with an error and a message about how to finish making the changes. You can add the --force option to force a non-interactive upgrade to continue in this case, also performing long running and critical tasks.
After upgrading, see the resulting upgrade.log file for a full list of operations performed.
The following options are supported.
--acceptLicense
Automatically accepts the product license if there is one in the delivery.
--force
Forces a non-interactive upgrade to continue even if it requires user interaction. In particular, long running or critical upgrade tasks, such as re-indexing, which require user confirmation will be skipped. This option may only be used with the --no-prompt option.
--ignoreErrors
Ignores any errors which occur during the upgrade. This option should be used with caution and may be useful in automated deployments where potential errors are known in advance and resolved after the upgrade has completed.
-n, --no-prompt
Use non-interactive mode. Prompt for any required information rather than fail.
-Q, --quiet
Use quiet mode.
-v, --verbose
Use verbose mode.
-V, --version
Display version information.
-?, -H, --help
Display usage information.
0
The command completed successfully.
2
The command was run in non-interactive mode, but could not complete because confirmation was required to run a long or critical task. See the error message or the log for details.
Other
An error occurred.
See the Installation Guide for an example upgrade process for OpenDJ directory server installed from the cross-platform (.zip) delivery, \m[blue]Upgrading From OpenDJ 2.4.5\m[].
Native packages (.deb, .rpm) perform more of the upgrade process, stopping OpenDJ if it is running, overwriting older files with newer files, running this utility, and starting OpenDJ if it was running when you upgraded the package(s).
Copyright \(co 2011-2013 ForgeRock AS