Transaction logs are no longer deleted if the db2bak command-line utility is cancelled. Database transaction log removal is temporarily disabled while db2bak is running, and is not reenabled if the command terminates prematurely. To avoid this problem, it is strongly recommended that you use db2bak. Workaround Stop the server, modify the nsslapd-db-logfile-size attribute in the dse.
On Linux systems, an ldapsearch operation without a host name, such as. This is because on Linux systems, it is possible to resolve a host such as " -p ", so the connect function attempts to do so, and fails.
The online documentation files are contained on the product CD and can be accessed via a browser. In addition, you can download the entire documentation set, in HTML format. This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers. So that we can best assist you in resolving problems, please have the following information available when you contact support:.
Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:. Please include the part number of the document in the subject line of your email. All rights reserved. Use of Directory Server is subject to the terms described in the license agreement accompanying it. Revision History. About Directory Server, Version 5.
Errata and Directory Server Documentation Updates. Enhancements Made and Problems Corrected. How to Report Problems and Provide Feedback. Directory Server Resource Kit Tools Reference errata updated - warning regarding references to documentation on mozilla. Replication fails after recreating schema with new OIDs An update is available for compressed archive versions of Directory Server 5.
Patching compressed archive versions of Directory Server in a localized environment requires the English update utility Patching compressed archive versions of Directory Server in a localized environment causes the Administration Console to display the incorrect name Patching compressed archive versions of Directory Server fails if Windows Event Viewer is open Creating a new role via the console fails with a Java exception Patching compressed archive versions of Directory Server fails if the administration password includes special characters Patching compressed archive versions of Directory Server fails if the administration password is longer than eight characters The mechanism for patching compressed archive versions of Directory Server requires the unzip utility With compressed archive installations, if either Administration Server or Directory Server is installed as root, uninstallation must also be run as root When installing in locales other than C, additional language support packages are required.
A number of issues have been resolved in the Directory Server 5. See Installation Notes for details. Additional documentation required on using referential integrity plug-in with legacy replication Administration Guide errata updated - certain LDAP controls incorrectly exposed with regard to chaining. Installation and Tuning Guide errata updated - HA documentation. Addition to Installation Notes caution regarding use of Administration Server password.
The changelog is not purged by default Multibyte characters at installation cause configuration problems amended to apply to all languages, and not only to the Japanese version. Note on write capability and multi-master replication. Note on initializing replicas in a multi-master replication scenario. Problem with multibyte characters at installation of Japanese version Problem with multibyte characters in suffixes for traditional Chinese version Updated and improved server management console.
Enhanced replication functionality. New replication features include: Support for 4-way multi-master replication. Support for multi-master replication over WAN. Fractional replication the ability to replicate a subset of attributes. Improved replication failover. Note A master initialized from another master in a multi-master configuration will process replication updates and allow read operations, but will return referrals for all write operations from clients.
Large cache support. A server running in bit mode can address more than 4GB of data. Improved product documentation. The 5. Error code documentation in the Reference Manual. New replication documentation in the Deployment and Administration Guides and in the Reference Manual.
Product documentation is no longer installed with the product but is available on the product CD and on the web. Password synchronization with Windows. Database Backend Plug-in Interface. The enhanced pre-operation interface may be used instead of the database backend plug-in interface, to implement plug-ins that are designed to provide access to alternative directory data stores. In addition, the distribution plug-in architecture and functionality will change substantially in a future release of Directory Server.
Only the compressed archive update patchzip is validated on this platform. Sun Linux 5. If you are using the original release of Directory Server 5. The original release of Directory Server 5. Note Directory Server 5. Run the English version of the compressed archive update utility. Extract the patch file appropriate to your locale to the directory in which Directory Server is installed the ServerRoot directory. Run the unzip command with the -o option to overwrite existing files and as the user who owns the ServerRoot directory.
For example. Instead of running the install script directly, create a file filename containing the administration ID and password, for example:. Run the following command:. Directory Server Bugs. VLV indexes did not work correctly on Sparc 64 Merging VLV indexes with no entries after importing of data did not work correctly The ieeeDevice and bootableDevice object classes were not backward compatible The server would crash if changelog trimming was enabled An erroneous reverse-DNS request was issued at server startup The console did not support backslashes in the RDN In the Japanese locale, the Fonts tab in the Console Preferences window did not work correctly In the Japanese locale, the default size of the Create New Domain window was too small Creating a new group with new members through the console caused an LDAP exception error For all Asian locales ja, ko, zh, and zh-TW , the console login online help window did not work correctly In the Chinese Taiwan locale, the online help contents were not displayed when the Launch in Browser button was pressed.
The online help button on the Console login window did not work correctly You must be root to run this command. The automount and automountInformation attributes have been removed.
The list of manadatory attributes for the ieeeDevice objectclass no longer includes cn. The list of manadatory attributes for the bootableDevice objectclass no longer includes cn. If you have customized this file, or if your database refers to the schema contained within it, perform the following steps: For zip installations, remove the 10rfc Copy the following files from the 5.
Note For SASL authentication mechanisms, any bind pre-operation plug-in or post-operation plug-in may be called several times for the same authentication request. In fact, this caution applies only if there are changes that have not been replicated to other servers in the topology when the change log directory is changed. If all changes have been replicated before the change log is moved that is, if all servers are in sync, there is no risk associated with moving the change log directory, and no reinitialization is required.
In the current Directory Server implementation, this is not the case. The online version of the Administration Guide has been updated as follows:. This note is removed in the newer version. For the correct version of this file, consult the online version on docs. Chapter 8, Managing Replication , contains the following with regard to the replication retry algorithm:. Note When installing and configuring the Sun Cluster HA for Directory Server data service, the Solaris packages must be installed on local, non-shared disks.
This path contains database and configuration files that are specific to the given instance. Note Paths specified in this manual use the forward slash format of UNIX and commands are specified without file extensions. Executable files on Windows systems generally have the same names with the. Product Version. For example: pkginfo grep SUNWdsvu.
For example, if you gave the name dirserv to your Directory Server, then the actual path would appear as shown in Table 2. If you have created a Directory Server instance in a different location, adapt the path accordingly. Some supported platforms provide native tools for accessing Directory Server. This software is available at the following location:. To perform full silent installation, you must first create two files containing installation specifications, one for Directory Server, one for Administration Server.
Note Specification files may contain passwords in clear text. Protect such files with appropriate file permissions. You may create a silent installation specification file either by editing a copy of the template file by hand, or by performing interactive configuration using the Directory Server and Administration Server configuration programs.
To create silent installation specification files for Directory Server and for Administration Server interactively, follow these steps:.
Perform Directory Server configuration using the -saveState option. Perform Administration Server configuration using the -saveState option. Adjust the specification files, dirserv-file and admserv-file , before using them to install on other systems. Some silent installation specification file directives, such as FullMachineName , depend directly on the underlying host system and so cannot be generated generically.
Silent installation specification files contain a checksum string corresponding to the build version of the install program. Code Example shows a sample checksum. From the directory containing the software you unpacked as described in "Obtaining Directory Server Software" , run the idsktune utility.
Perform suggested changes to the system manually. Notice that idsktune reports as missing all patches recommended at the time of release and not installed on the system, even patches for packages not installed on the system. Optional When installing interactively as another user, allow access to the display using the xhost 1 command. If the installation program cannot display the graphical user interface, it starts installation in command line mode. Start the installation program in the directory containing the unpacked software.
Do not install this version in the same directory as an earlier version of the Directory Server. If you must reuse the same directory location, first uninstall the earlier version.
To perform a silent installation, you must first create a file containing installation specifications. You may create a silent installation specification file either by editing a copy of the template file by hand, or by performing interactive configuration using the installation program. Start the installation program with the -saveState option.
Adjust the specification file, filename , before using it to install on other systems. The updated checksum can be found in typical. Optional If you installed from a compressed archive, add support to start Directory Server on system reboot. This support is included in the Solaris package version.
If you have installed Directory Server as super user, but have set the user and group ID to that of another account, the Directory Server may not be able to generate a core file during a crash. It is strongly recommended that you plan enough space for core files, and allow Directory Server to generate them during a crash. You may administer core file generation using coreadm 1M , allowing Directory Server to generate core files as follows, for example:. Optional Many command-line scripts written in Perl can now read the bind password interactively -w - option.
To enable this functionality:. Edit each Perl script to read the bind password interactively by uncommenting the appropriate lines. All other Perl script functionality remains available without the Term::ReadKey module.
Run the idsktune utility, which you find in the directory containing the unpacked software. Table suggests where to look for official patches not yet installed on your system. Refer to Chapter 5 "Tuning the Operating System " starting on page 97 for more information.
If you plan to use the Console, install the X Before installing remotely using a locale with fonts not supported for US English, ensure you can access font aliases for remote sessions. When installing Windows , specify that the computer is a stand-alone server, not a member of any existing domain or workgroup, to reduce dependencies on network security services.
Log on as a user with Administrator privileges. Set the TEMP environment variable to a valid folder for temporary files. Double click setup. Do not install this version in the same folder as an earlier version of the Directory Server.
If you must reuse the same folder, first uninstall the earlier version. After installation, manually set special access permissions for the following files such that only the user and group running the Administration Server has read-write access, and all other users have no access. Refer to Windows help for instructions on setting special access permissions for files.
This modification prevents unauthorized users from modifying Administration Server configuration data. Uninstallation removes the software and associated data from a computer. Directory Server becomes unavailable and you lose all settings and data. Uninstallation removes not only server software, but also registry data stored on the system. If you delete files manually before using the uninstallation program, you may corrupt your registry. To avoid corrupting the registry, use the uninstallation program before deleting any product files manually.
If you uninstall a centralized configuration directory that other directories rely on for configuration information, you cannot subsequently administer those directories. How you remove Directory Server software depends on which packaging was used during the installation process, and on whether you want to interact with the uninstall program.
Proceed according to instructions in the appropriate section:. Important If you are completing the upgrade of Directory Server 5. Do NOT remove the other packages listed in these tables. Doing so can render your system unbootable. The selected software is now removed. If the uninstallation program cannot remove all files under the ServerRoot directory, it displays a message.
You may manually remove files remaining under ServerRoot.
0コメント