cs 7.2 relnotes

EMC® Documentum®

Content ServerVersion 7.2

Release Notes

EMC CorporationCorporate Headquarters

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

Legal Notice

Copyright © 1994–2015 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATIONMAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and Adobe PDFLibrary are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarksused herein are the property of their respective owners.

Documentation Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback about how we canmake our documentation better or easier to use, please send us your feedback directly at [email protected]

Table of Contents

Revision History .................................................................................................................. 5

Chapter 1 Overview ..................................................................................................... 7Resources......................................................................................................... 7Documentation and Support ......................................................................... 8EMC Online Communities ............................................................................ 8

Providing Feedback .......................................................................................... 8Documentation Feedback.............................................................................. 8Product Enhancement Requests..................................................................... 8

Chapter 2 Features and Updates ................................................................................. 9Enhanced Trust and Security ............................................................................. 9Support for Lockbox ..................................................................................... 9Support for Stronger AEK ............................................................................. 9RKM Support for Upgraded Repositories....................................................... 10Support for Stronger and Flexible SSL............................................................ 10

WORM Support for Data Domain and Isilon Stores ............................................ 10Support for ViPR Stores .................................................................................... 10

Chapter 3 System Requirements ................................................................................. 11

Chapter 4 Installation and Upgrade ............................................................................. 13

Chapter 5 Fixed Issues ................................................................................................ 15

Chapter 6 Known Issues .............................................................................................. 25Installation and Upgrade .................................................................................. 25Server and Administration ................................................................................ 29Documentation................................................................................................. 35

3

Table of Contents

4

Revision History

Revision Date Description

February 2015 Initial publication.

5

Preface

6

Chapter 1Overview

EMC Documentum Content Server is the core of the EMC Documentum content managementplatform. Content Server governs the content repository and enables a set of content managementservices for controlling content and processes throughout distributed enterprises. Content Serverlets you store, manage, and deploy all types of content, including HTML and XML, graphics, andmultimedia. Content Server provides services such as the following:• Integrated workflow

• Lifecycle and process automation

• Version control

• Security

• Data dictionary for capturing and configuring business rules

With Content Server, users can share and reuse trusted content on demand within and betweenbusiness units. Administrators can define, organize, automate, and monitor all the functions andtasks of complex business processes.

This document includes information about Content Server functionality changes from the previousrelease, and provides information on known issues, if any.

This document also includes information about distributed configurations, which includes but isnot limited to Documentum Messaging Services (DMS) and Accelerated Content Services (ACS).Information about Branch Office Caching Services (which is also a component of distributedconfigurations) is included in the EMC Documentum Branch Office Caching Services Release Notes.

For information about XML Store functionality changes, see EMC Documentum XML Store ReleaseNotes.

Documentum Foundation Services (DFS) is no longer installed with Documentum Content Server.You must install a DFS server on a machine that is different from the one on which Content Serveris installed. For information about DFS functionality changes, see EMC Documentum FoundationServices Release Notes.

ResourcesProduct resources are available on the Web.

7

Overview

Documentation and Support

For the latest product documentation and support materials, including White Papers and TechnicalAdvisories, refer to EMC Online Support (https://support.emc.com). Check regularly for new andupdated documentation to ensure that you have the latest system information.

Note: Documentation installed, or packaged with the product on the download center, is current atthe time of release. Documentation updates made after a release are available for download fromEMC Online Support (https://support.emc.com).

EMC Online Communities

Visit EMC Community Network (community.emc.com) for peer contacts, conversations, and contenton product support and solutions. Interactively engage online with customers, partners and certifiedprofessionals for all EMC Products.

Providing Feedback

Documentation Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you havefeedback about how we can make our documentation better or easier to use, please send us yourfeedback directly at [email protected].

Product Enhancement Requests

Help us to improve the products that you use. Use our Enhancement Request System, available frommany product support pages, to tell us what you would like to see in future releases.

8

https://support.emc.com


https://community.emc.com/

mailto:[email protected]

Chapter 2Features and Updates

This section highlights the major functionality changes included in this release. Refer to the productdocumentation for complete information about these features.

Enhanced Trust and Security

Support for Lockbox

Content Server now supports lockbox. The highlights are:• Provides a secure way to store the Content Server application encryption key (AEK).

• dm_crypto_create utility is enhanced to create a lockbox and to move an existing AEK to a lockbox.

• dm_crypto_boot utility is enhanced to load an AEK into the shared memory.

Support for Stronger AEK

Content Server now supports the 192 and 256 algorithms while creating AEK, in addition to 128algorithm. The highlights are:• Supports the AES_128_CBC, AES_192_CBC, and AES_256_CBC algorithms.

• dm_crypto_create utility is enhanced to specify an algorithm to be used for creating AEK.

• dm_crypto_boot utility is enhanced to load an AEK into the shared memory.

• Installer provides the options to select an algorithm to create AEK while creating a repository.

• New dm_crypto_upgrade.exe utility is introduced to regenerate the docbase key (DBK) usingthe new algorithm for the upgrade process.

9

Features and Updates

RKM Support for Upgraded Repositories

Integration of RKM is now enabled on Content Servers having cryptographic keys stored in thedatabases. The highlights are:• Allows the integration of RKM at the time of installation.

• Enhances the security of data stored in repositories.

Support for Stronger and Flexible SSL

Content Server now supports the use of SHA 256 certificates of 2048 key length.

WORM Support for Data Domain and IsilonStoresContent Server now uses the Write Once Read Many (WORM) functionality provided by DataDomain and Isilon stores for applying retention at the file system level.

Support for ViPR StoresContent Server now supports ViPR stores. The highlights are:• Allows to use ViPR file-managed storage as an object store.

• Helps you to control and scale data storage requirements.

10

Chapter 3System Requirements

The EMC Documentum 7.2 Environment and System Requirements Guide contains the systemrequirements information for your product. This documentation is available from EMC OnlineSupport.

11



System Requirements

12

Chapter 4Installation and Upgrade

Before beginning installation, ensure that your system meets the requirements listed in Chapter 3,System Requirements. After installation, be sure to update your software to the latest patched release.

• The EMC Documentum Content Server Installation Guide contains the instructions on installing andconfiguring Content Server.

• The EMC Documentum System Upgrade and Migration Guide contains the instructions on upgradingContent Server.

• The EMC Documentum Content Server Distributed Configuration Guide contains the instructions oninstalling Documentum Messaging Services (DMS) and Branch Office Caching Services (BOCS).

For instructions on upgrading the entire Documentum system, see the EMC Documentum SystemUpgrade and Migration Guide.

13

Installation and Upgrade

14

Chapter 5Fixed Issues

This section identifies issues that have been resolved in this release.

Issue Number Description

CS-47993 Incorrect error message when supplied datedoes not exist.

CS-47701 Unable to open files with special characters intheir names if Read Notifications are enabled.

CS-47624 dmclean and dmfilescan jobs might getaborted due to a new server.ini parameter’max_ldap_config_objects’.

CS-47609 Unable to set LDAP binding password afterapplying Content Server Patch P28.

CS-47495 dbpassword does not accept the ’&’ character.

CS-47472 "ORDER BY Attribute" in FTDQL is notsupported.

CS-47429 Wrong file separator was stored in file_nameattribute for dm_load_record objects on Win64flavors.

CS-47329 Error message is not handled correctly in IndexAgent.

CS-47324 The UNIQUE constraint is violated when yourun dump and load for a group and user objectsof the same group_name and user_name.

CS-47313 Unable to use the second eSignature template aspart of Trusted Content Services.

CS-47245 An issue with the group cache logic, and thecache was not storing the previous resultsproperly.

CS-47178 Error on Content Server stopping creating folderworkflow step from execution, Access violationis logged in repository log.

CS-47132 Jobs are not running after applying 6.7SP2 P15.

15

Fixed Issues


CS-47050 Content Server does not allow special charactersin method arguments for dmbasic methods.

CS-47008 Incorrect sessions are used.

CS-46801 Sysobject content gets migrated even if they arealready migrated into the target store.

CS-46798 eSign method fails when a property starts withcomma.

CS-46790 QUERY_BATCH_SIZE Cannot be included as aJob Parameter.

CS-46758 DFC does not throw NoSuchAttributeExceptionerror after upgrading to Content Server ifapplication servers are not restarted.

CS-46740 Issue with Configuring repository with existingSQL Server user account and dabase on ChineseOS

CS-46594 Folder navigation takes more time even forlesser number of objects.

CS-46571 dm_launch_server_config_program.sh(Repository creation shows a different versionthan the patch version installed).

CS-46568 TOUCH_CONTENT RPC fails with thefollowing error: [DM_SERVER_E_EXEC_SQL]error

CS-46538 Decrypted data and ticket details are leaked torepository logs.

CS-46501 Inline user crashes the repository afterupgrading from 6.7 SP2 to 7.1.

CS-46497 [DM_WORKFLOW_E_CANT_FETCH]error:"The dmi_wf_timer object (ff000000000PM000)does not exist"

CS-46464 Failed to verify that the last certificate in thechain corresponds to the target server desired tobe authenticated.

CS-46344 Decision Split with expression takes wrongroute for lengthier integer values.

CS-46319 Content Server returns multiple URLs forGET_DIST_WRITE_MAP RPC.

CS-46316 Avoiding ORA-01795 for select statements whilepopulating static and dynamic groups duringuser authentication.

16

Fixed Issues


CS-46263 The value of attachment_file_name fromdm_message_attachment table was different fororiginal and copied emails causing error in theconversion of emcmf emails to .msg emails.

CS-46249 While configuring LDAP in DA, if any sub-typeof dm_user is selected as User Type, someexpressions will not be supported in propertymapping.

CS-46228 Incorrect conditional statement that skippedsome users in a group in the case ofgroup-tree-sync.

CS-46184 Errors in StateFull process initialization.

CS-46175 r_link_cnt on folder is not showing the correctnumbers of objects held by the folder.

CS-46114 Content Server does not clear application codewhen a session is reused.

CS-46097 Controlling number of proc dumps created forServer process.

CS-46019 When D7.1 upgrade fails while running an EBSscript, the failed script is not retried and the restof the EBS scripts are skipped without running.

CS-46014 The dm_GroupRename jobs fails for groupnames that are over 32 characters long.

CS-45993 There was a race condition in LDAPsynchronization user creation.

CS-45925 The alpha_case_user_login_name parameterwas being ignored for group-tree-sync.

CS-45921 Default aspect is NOT triggered when relationobject with aspect customization is executedusing BOF DQL.

CS-45897 Incorrect sessions are used.

CS-45858 In an upgraded 7.1 repository, permissions arenot working when ACL contains group withcomma in name and user is member of group.From 7.0 Content server, comma (,) was used asa delimiter to form a list of groups as a singlestring. But if a group contains comma ’,’ as partof group_name then the name will be split intotwo as comma ’,’ is used as delimiter and basicgroup functionality fails.

CS-45829 Workflows fail to work after applying ContentServer 7.1 P03.

17

Fixed Issues


CS-45827 Behavior of SQL_DEF_RESULT_SET N isneither row-based nor object-based and sameas RETURN_TOP.

CS-45824 Send date of email notification from 64-bit smailis earlier by 1 hour than the actual time.

CS-45803 consistency_checker.ebs does not handlesessions correctly.

CS-45735 Error in server log after applying patch ContentServer 6.7 SP2 P13.

CS-45731 Retrieval of specific XML file from XDBproduces (xml-store) corrupted output.

CS-45695 Server crashes when user is part of groupcontaining croatian symbols (multi-bytecharacter set) and is designated workflowperformer.

CS-45604 User not part of the owner group and not listedin the ACL can edit the documents.

CS-45594 DQL to SQL conversion does not work for aspecific query.

CS-45579 The search fails on an indexed dynamic groupobjects when a ftsearch_security_mode isenabled.

CS-45563 smail.exe crashes on Windows 2008 R2 withContent Server 6.7 SP1 64-bit.

CS-45559 Any DQL for select and update fails when it hastable hint.

CS-45555 Method Server crashes on startup if the locationof the log is changed.

CS-45514 Connection broker crashes (DM_DOCBROKER_E_EXCEPTION_CAUGHT) on using NAT.

CS-45511 The DM_QUERY_E_CURSOR_ERROR occurswhen you run a DQL with sort on more thanone fields in RETURN_RANGE.

CS-45451 The query plug-in incorrectly closes the xPlorequery session issue when they want to return alarge amount of results.

CS-45441 LDAP sync error with ADAM server and 2048bit SSL certs.

CS-45384 Error when using the Kerberos SPN namingsyntax.

18

Fixed Issues


CS-45377 LDAP SSL authentication and LDAPsynchronization job does not work when usingSHA 256 (2048 key length) certificates.

CS-45341 When a user belongs to many groups, ACLevaluation was not correct.

CS-45329 Custom jobs is processed by agentexec whenit is run manually but works when it runs ona schedule.

CS-45308 Workflow Stuck - Missing dmi_workitemsfor workflow, issue using RECOMPUTE_PERFORMER administrative method.

CS-45292 Job Reports do not always contain JobInformation even if they are reported as beingsuccessfully run.

CS-45277 DQL queries with return range hint do not giveresults in order of dm_rnum.

CS-45274 Authentication failures with passwords ofäöü1234

CS-45193 LDAP does not get all users in groups.

CS-45191 Duplicate groups are created during LDAPsynchronization with MSAD.

CS-45153 sysObject.getAcsRequests() returns multipleURLs when using dm_distributedstore objectfor storage.

CS-45122 Inconsistent behavior of isUserInGroup(username) method.

CS-45091 Server crashes with the "failure duringprocessing of request: MultiNext_string.SIGSEGV: segmentation violation: (11) at(MultiNext_string)" message on using thecustom type, while updating objects.

CS-45088 DM_WORKFLOW_E_NO_SUPERVISOR_ACCESS error is thrown while trying to assignas Supervisor a group that inherits RELATEpermission from its parent group

CS-45054 The D7 Kerberos plug-in does not work withmultiple domains in the same forest trust.

CS-45009 Content Server 6.7 SP1 P22 causes ContentServer time to shift by one hour.

CS-44998 Numerous DM_WORKFLOW_E_ASSIGN_TASK_FAIL errors.

19

Fixed Issues


CS-44987 Repository startup hangs, when server scansfiles in the Kerberos directory.

CS-44929 Content Server supports only up to 20 LEFTOUTER JOIN in a DQL.

CS-44886 Checkin of non-current version object fails if theuser does not have version permission on thecurrent version object.

CS-44877 dm_UserRename job does not setuser_delegation value for the target user.

CS-44864 Content Server version 7.1 installer fails to retryscripts if an error is encountered.

CS-44806 Job Reports do not always contain JobInformation even if they are reported as beingsuccessfully run.

CS-44734 WFReporting job incorrectly processes workitemdurations and finally showing up negativevalues.

CS-44731 Server Install fails with Could not createfolder /Documentum during extraction ofServer_linux_ora.zip

CS-44677 Queue item is created for dm_fulltex_index_usereven if this user is not registered.

CS-44655 Several instances of the same job run at the sametime.

CS-44645 DQL to retrieve children of nested virtualdocument query with "IN DOCUMENT IDDESCEND" and WHERE clause do not returnchildren if parent do not qualify.

CS-44641 return_range and distinct clause in sub selectresults in duplicate rows being returned.

CS-44616 Oracle service name cannot be fully shown ifservice name is too long.

CS-44573 Search query is not balanced in xPloremulti-node environment.

CS-44562 Upgraded repositories from 5.3 SPx do nothave i_partition by default, if partition was notenabled, and operations on Virtual Documentsfail.

CS-44558 Child documents in Virtual Document isinvisible on the "Refresh" operation in the targetrepository.

20

Fixed Issues


CS-44538 Content Replication Job failed to replicatecontent due to "Getfile failed" issue.

CS-44487 Groups are not populated with users after theyare imported from AD.

CS-44483 dm_FTIndexAgentBoot job does not work withIA in SSL configuration.

CS-44474 Maintaining Nullable property for attributes inaccordance with the database defaults.

CS-44460 dm_UserRename job fails.

CS-44370 Duplicate entries are created forr_accessor_name and permit type causing issuesin ACL logic.

CS-44346 LDAP Synchronization removes the groupswhen the connection is lost between the LDAPserver and Content Server at the time of runningthe LDAP job.

CS-44337 DQL query causes Access Violation ondmType::GetAttrType after Content Serverupgrade.

CS-44224 Method scheduling a HA setup where methodsneed to be distributed.

CS-44192 Issue with CS and WFA assigning the sameworkitem twice.

CS-44174 [WARNING] [AGENTEXEC XXXX] Detectedduring the main job scheduling loop:Query returned the following warning:[DM_QUERY_I_NUM_UPDATE]info: "Xobjects were affected by your UPDATEstatement."

CS-44153 Generic job method was returning return codeas 0 for both success and failure cases

CS-44069 Unix Password-Policy is not checked byDocumentum on Linux.

CS-43865 Content Server incorrectly processes the timezone information.

CS-43821 Audit - Double records appear in the history ofthe specific object.

CS-43785 Storage object can still be working on afterchanging to offline since Content Server stillgenerates ACS URL for the objects.

CS-43760 LDAP with SSL enabled fails to synchronizeusing chain certificates.

21

Fixed Issues


CS-43753 When you execute dm_DMclean ordm_DMFilescan, an inconsistency occurs inconcurrent_sessions.

CS-43712 Content Server does not recognize empty valuesin alias_value for template ACLs.

CS-43644 Connection broker crashes when addingtranslation to the second connectionbroker with the following error: [DM_DOCBROKER_E_EXCEPTION_CAUGHT]2013-07-26T07:17:32.518470 DocumentumDocbroker: 0x82f1694 encountered exception:SIGABRT: abort process: (6) at (main)

CS-43601 If time_stamp_utc attribute for dm_audittrailis set manually through client code, whileretrieving wrong time is shown.

CS-43497 JMS HA does not work properly.

CS-43260 Certificate limitation for SHA2 2048 certs.

CS-42507 DM_ANNOTATE relation gets deleted when arendition is added to the document.

CS-42180 The mail notification fails with the "Failedto fetch workitem 4a00215c80006521. Error:[DM_API_E_EXIST]error: "Document/objectspecified by 4a00215c80006521 does notexist." error. This issue occurs only fordm_startedworkitem event.

CS-41843 LDAP synchronization job does not trim theattribute value during import and reports anerror.

CS-41756 Changing the attribute a_storage_type changesthe modify date and modifier if a retentionpolicy is applied to the document.

CS-41487 DM_SESSION_E_MAX_LDAP_CONFIG_OBJECTS_EXCEEDED error even if the correctvalue is set for max_ldap_config_objects inserver.ini.

CS-40892 The LDAP config object produces .cntt filesinstead of .cnt files.

22

Fixed Issues


CS-39931 Inefficient SQL query in Workflow agent.

CS-39919 Login delay using Netegrity.

23

Fixed Issues

24

Chapter 6Known Issues

This section identifies known product issues and limitations that may affect your use of the product.

Installation and Upgrade


CS-48941 After consolidation of repositories, on the migrated repository, the net startand net stop operations do not work.

CS-48918 Upgrading AEK with a different passphrase fails with an error.

Workaround: Use the old passphrase for the new key and then manually changethe passphrase after the upgrade process.

CS-48939 After consolidation of repositories, the user_rename operation does not renamethe user on the migrated repository.

CS-48653 Authentication of the xDB superuser password fails while upgrading therepository. This issue occurs in a combination of an environment havingrepositories that are enabled with XML Store and also that are not enabled withXML Store.

Workaround: Add the hostname (hostname value as shown in bold in the example)in the xhiveaddress (xDB hostname) entry in $DOCUMENTUM_SHARED/<JBossversion folder>/server/DctmServer_MethodServer/deployments/XhiveConnector.ear/XhiveConnector.war/WEB-INF/web.xml, restartthe Java Method Server, and then start the upgrade process.

For example:

<init-param>

<param-name>xhiveaddress</param-name>

<param-value>AIXDB26166</param-value></init-param>

25

Known Issues


CS-48532 Uninstalling the repository does not remove the value of dfc.crypto.repository in dfc.properties. Also, the value ofdfc.crypto.repository points to an uninstalled repository.

Workaround: Manually remove or modify the value of dfc.crypto.repository in dfc.properties.

CS-48270 XML Store configuration fails while upgrading the repository. This issue occursbecause of the failure in execution of scripts.

Workaround: Run the failed scripts again.

CS-48172 Running the headstart.ebs script for remote Content Server (RCS) when theLDAP configuration objects exist in the primary server fails with an error.

Workaround: Copy the ldap_<object_id>.cnt files from the primary serverto the remote Content Server.

CS-47788 Configuring the repository fails with an error while connecting to a databaseon Solaris.

Workaround: Add the /usr/sfw/lib/sparcv9 value in LD_LIBRARY_PATH.

CS-46159 Content Server installer does not validate the Keystore file name and Keystorepassword file name values while configuring the connection broker using theUse certificates option.

CS-44291 Repository logs display the [DM_DOCBROKER_E_NO_DOCBROKERS]error:"No DocBrokers are configured" error while configuring the connectionbroker and repository.

Workaround: Ensure the dfc.properties file in $DOCUMENTUM\Config hasthe connection broker information. If there is no connection broker informationin the dfc.properties file, then add it and restart both the connection brokerand repository.

CS-42820 Unable to install any DAR file through Composer headless DAR deployer whenthe Content Server is installed with non-anonymous SSL mode enabled.

Workaround: Disable the non-anonymous SSL mode on the Content Server andinstall the required DAR files using the Composer headless DAR deployer. Onceinstalled, enable the non-anonymous SSL mode.

CS-42794 Java libraries do not honor the expiration date of certificates for non-anonymousSSL communication.

CS-42313 Content Server does not support mapped shared directory drive while configuringrepositories using the SAN or NAS devices.

Workaround: Use the UNC path.

CS-42178 Mixed mode configuration of Content Server/connection broker in anonymousSSL mode and JMS/Content Server in non-anonymous SSL mode is not supported.

CS-42063 Retention or any other native policies of Data Domain is not honored as ContentServer has no native integration with Data Domain as a file store.

26

Known Issues


CS-41951 Unable to install DMS and connect to the Content Server having non-anonymouscertificates. This is because of the mixed mode (a combination of components withand without certificates), which is not supported.

Workaround: Disable the certificates on all components before installing a newcomponent.

CS-41937 When you install Content Server on multiple hosts, the DM_SESSION_E_AUTH_FAIL exception occurs in server.log and ServerApps.log on the remoteContent Server (RCS) side.

Workaround: Perform the following steps:1. Navigate to Documentum Administrator > Client Rights Management >

Privileged Clients > Manage Clients.

All clients for both hosts are displayed.

2. For the appropriate client on the secondary host, select the following options:• Enable trusted login

• Enables trusted server privilege

CS-41733 Logging through IAPI when handling several login requests within a short timeframe takes a long time. This is because the DEVRANDOM variable is not added inthe startup script on Linux for remote Content Server (RCS).

Workaround: Add the following lines in DM_HOME/bin/dm_set_server_env.shbefore starting RCS:

DEVRANDOM=/dev/urandom

export DEVRANDOM

CS-41543 When you configure the global repository after installing Content Server, theDFC_DOCBROKER_EXCLUDED warning message occurs in the JMS, DFC, and ACSlog files. This is because the Teredo Tunneling Pseudo-Interface is enabled.

Workaround: Perform the following:

• From the command prompt, type

netsh interface teredo set state disabled

Or

• Disable the IP Helper service from the Services dialog to disable the tunnelingpermanently.

Restart the machine.

CS-41332 UCF function fails when you upgrade Content Server and RMA. This is becausethe UCF installer adds the following line to the network configuration file causingUCF to use IPv6 which is not supported:

<option value="-Djava.net.preferIPv6Addresses=true"/>

27

Known Issues


CS-40885 [Russian] Character corruption is seen when you invoke the Content Serverinstallation on a Russian Windows 2008 Server (64-bit).

CS-40415 Unable to install Content Server on some localized Windows operating systems.

Workaround: Create a group "Everyone" on the localized server operating systemmanually. Proceed with the Content Server installation.

CS-40397 An error occurs when a user does not set a password for the databaseadministrator user, and then attempts to create a repository. The password field ofdatabase administrator user should not be empty as there would be a security risk.

CS-37399(CS-37500)

The Content Server repository service name has a limitation of 32 characters,which causes problems for long repositories names when you configure ContentServer using the CFSConfiguration utility.

Workaround: Do not use long repository names that exceed 32 characters.

CS-38845 Upgrading from earlier releases containing many system objects to 7.0 takeslonger time than standard upgrades due to schema changes in the root type.

CS-34238 Warnings are displayed in the log directory of DAR(IndexAgentDefaultFilters.dar and MessaginApp.dar) installations inthe upgrade environment. However, you can ignore these warnings since theversion label is not used any where in the BOF service class.

CS-32168 If a database user password has a dollar sign ($) in it, installation of bundledsoftware such as xCP Developer Edition fails and throws a bogus error: Runtimeexecution failed with child process

DC-7310 Warning messages are displayed when DMS is started. For example:

WARN [org.jboss.as.ee] (MSC service thread 1-7) JBAS011006:Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuationdue to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could notfind default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuationat org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) atorg.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)[jboss-as-server-7.1.1.Final.jar:7.1.1.Final] atorg.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)[jboss-msc-1.0.2.GA.jar:1.0.2.GA] atorg.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)[jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent

28

Known Issues

Issue Number Description.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[rt.jar:1.7.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722)[rt.jar:1.7.0_17]

However, you can ignore these warnings. The JBoss website contains moreinformation.

DC-7495 Warning messages are displayed in the server log directory while deployingACS, BOCS, and DMS. For example: Class Path entry <JAR1 NAME>in "<JBOSS 7.x HOME>/server/DctmServer_DMS/deployments/DMS.ear/dms-ws.war/WEB-INF/lib/<JAR2 NAME>” does not point toa valid jar for a Class-Path reference.

However, you can ignore these warnings. The JBoss website contains moreinformation.

DFC-10601 Installation fails on Solaris 11 with the Segmentation fault (core dumped)error.

Workaround: To install on Solaris 11, copy libucb.so.1 from the/usr/ucblib/ folder on Solaris 10 to the /lib folder on Solaris 11.

Server and AdministrationIssue Number Description

CS-48914 When you run workflows, the Method Server crashes in AIX.

CS-48801 When you run the nested groups incremental LDAP synchronization job onSolaris, it fails for the user_rename and group_rename operations and reportsan error in the JMS log.

CS-48656 When you open a file having special characters in its name on Linux, the MethodServer crashes.

CS-46860 If a repository uses an AEK key with a custom passphrase, restarting the machineor VM fails to restart the repository with the following error:

Failed to initialize keystore at C:\Documentum\dba\secure\CSaek.Internal error - 1057226525.

Workaround:1. Kill the running dm_crypto_boot processes, if any.

2. Run dm_crypto_boot -passphrase <test> -all

3. Start the repository.

29

Known Issues


CS-48516 In the Microsoft Cluster environment, LDAP synchronization job does not workwith Microsoft Cluster virtual host name.

CS-47803 LDAP synchronization in SSLmode fails with the DM_LDAP_SYNC_E_EXCEPTION_ERROR: Illegal key size exception.

Workaround: Install the JCE plugin manually before you run the LDAPsynchronization job.

CS-45744 The dm_policy object that is attached with the dm_procedure object can only bedeleted by a superuser irrespective of the owner of the dm_policy object.

Workaround:1. Unlink the dm_procedure object from the dm_policy object.

2. Delete the dm_policy object using the privileges used to create the dm_policyobject.

3. Delete the dm_procedure object using the superuser privileges.

CS-44221 LDAP SSL user authentication does not work on Solaris.

Workaround:1. Start the repository and get the process id on which it is running.

2. Using the process id, run the following command:

truss –f –p <processid> >& aout.log

3. Import the certificate and run the LDAP synchronization job in SSL mode.

4. Authenticate the LDAP user to update the hash value of the certificate inthe aout.log file.

5. Get the hash value of the certificate from the aout.log file.

6. Create a new copy of the existing certificate that you used for running theLDAP synchronization job in the LDAP certdb location, name it with thehash value, and authenticate the user.

Note: An error message appears when you try to run the LDAPsynchronization job again. For example: ERROR: Failed to loadcertificate file /export/home/d72/dctm/dba/secure/ldapdb/9e513170.0: Certificate file name is not named usingits expected SHA1 hash value 9f4080d1. This error occurs becauseit loads the existing certificate and does not load the certificate you created.Ignore the error message.

CS-44167 The EMC RSA plug-in for Documentum that allows Content Server to authenticateusers based on RSA ClearTrust single sign-on tokens does not support RSAclustering. This is a RSA limitation.

30

Known Issues


CS-43925 When you attempt to transfer content through ACS and BOCS with theAsynchronous Write Job turned ’ON’, the DFC deployed in the application contextsends a message to DMS instructing it to store the content located in BOCS.The size of the message is directly proportional to the number of ACS serverconfiguration objects and the number of base URLs in the ACS config objects.

If the number of configuration objects or URLs exceeds 2, the message may gettruncated when it gets stored in the DMS database. Therefore, it is recommendedto avoid such configurations of ACS config object(s). This is a limitation.

CS-43778 In a AIX with DB2 combination, creating a folder with name containing the specialcharacters ^^ results in an error.

CS-43570 If the number of file stores in Content Server are more than 100, anyadditional file stores created do not work and results in the followingerror: [DM_SESSION_E_STORESTAT_OVERFLOW]error: "The sharedmemory segment for caching the ONLINE/OFFLINE status ofthe Documentum Storage areas has reached its maximum size(100). Update access may be incorrectly given to Offline orReadOnly storage area (28003039800002b7).". The file store status ofsome of the stores may be incorrect. This is a limitation.

CS-42237 Auditing aspect attributes does not work.

CS-42094 Change object type to a subtype does not work for lightweight objects.

CS-41576 LDAP synchronization fails when you try to synchronize a high count of user datafrom the Microsoft Active Directory with the java.net.ConnectException:Connection timed out exception.

Workaround: Set the value of the method_arguments attribute in the LDAPsynchronization job to ‘ignore’.

API> retrieve,c,dm_job where object_name='dm_LDAPSynchronization'

API> append,c,l,method_arguments

SET> -referral <follow/ignore>

API> save,c,l

Note: If you do not set this value, or specify some other value, the default value‘follow’ is set.

CS-41400 On UNIX and Linux, when both Content Server and connection broker areconfigured for Certificate-based SSL, if certificate-related errors occur, the server isunable to connect to connection broker. Repository/connection broker control isnot possible using IAPI. You have to manually kill all server started processes toshutdown the server. This is a limitation.

CS-41252 When querying, agent_exec looses time because it also goes through jobs that arededicated to another server.

Workaround: To avoid time loss, set the value of the target_server attribute tocurrent server or ANY SERVER.

31

Known Issues


CS-41027 Redundant joins in newly created SDT views.

Workaround: Perform the following steps:1. Create an environment variable DM_NO_EXTRA_JOINS and set its value as T.

2. Restart Content Server.

To update the existing views, do the following in SQLplus:

UPDATE dm_type_s

SET views_valid = 0;

commit;

Note: The view gets updated whenever you use a type object for the first time inContent Server. Otherwise, the view remains the same.

CS-40838 When two users perform a move operation of two folders simultaneously, ther_folder_path and i_ancestor_id parameters contain incorrect valuescausing folder inconsistencies in Oracle and SQL Server.

Workaround: Add disable_folder_synchronization = T in theserver.ini file. By default, the value is F.

CS-40701 When running the dm_event_sender_java method using the DO_METHODdirectly, the <argument_name>:<argument_value> pair needs to be passed inwhile executing the method. Passing only the argument_value (as done in thedm_event_sender docbasic method) does not work, unless the queue API is called.With queue API, DFC appends the argument_name before the argument_valueduring the execution of the Java method.

All argument names are mandatory and have to be passed to the Java method. If aparticular argument name has no value, pass an empty string.

CS-40563 ACCESS_VIOLATION found in the docbase log while running the business_policysuite. This is because Oracle version 11.2.0.3 is not certified on Microsoft Windows2012 Server.

Note: Oracle plans to certify the 11.2.0.4 database and client on the MicrosoftWindows 2012 Server. 11.2.0.4 is not released yet.

CS-40534 Querying for repeating attributes using DQL displays the result in the same orderas it is stored in the database.

Workaround: Use the "ORDER BY i_position DESC" clause with the DQL query.

CS-40474 Performance issue is encountered when promoting a document in lifecycle, withina transaction. This occurs due to concurrent access to the dmc_tcf_activity object.

32

Known Issues


CS-40238 Unable to edit or perform a search based on the definition of thea_retention_date attribute for immutable objects.

You must run the UpdateDDInfoForRetentionDate.ebs script manually toupdate the data dictionary information for a_retention_date attribute andrepublish the data dictionary information for the a_retention_date attributeof the sysobject and subtypes of the sysobjects for existing repositories.

Execute the UpdateDDInfoForRetentionDate.ebs script on the ContentServer machine where the repository is created, using the following command:• On Windows: dmbasic -f %DM_HOME%\bin\UpdateDDInfoForRetentionDate.ebs -eEntry_Point -- <docbaseName><installOwner> <password>

• On UNIX: dmbasic -f $DM_HOME/bin/UpdateDDInfoForRetentionDate.ebs-eEntry_Point -- <docbaseName> <installOwner> <password>

Note: If you have a new 7.1 or later installation, you do not have to executethe UpdateDDInfoForRetentionDate.ebs script. You must execute theUpdateDDInfoForRetentionDate.ebs script only if you have upgradedrepositories and if you want to allows users to edit or perform a search using thea_retention_date attribute definition of immutable objects. For downloadingthe UpdateDDInfoForRetentionDate.ebs script or the latest Content Serverpatch containing the UpdateDDInfoForRetentionDate.ebs script, refer toEMC Online Support (https://support.emc.com).

CS-40207 DoMail requests fail when static IP address is configured for JMS listen address.This is because DoMail class runs the validateRequestIPAddress method againstthe localhost’s IP address.

Workaround: To prevent DoMail requests from another Content Server (on adifferent host) from failing, you must add an init parameter to DoMail’s web.xml.The name of this parameter must start with the keyword ’ip-’ and its value mustbe the IP address of a trusted host. For example:

<servlet>

<servlet-name>DoMail</servlet-name>

<description>Documentum Mail Servlet></description>

<servlet-class>com.documentum.server.impl.mailservlet.DoMail<

/servlet-class> <init-param>

<param-name>ip-192.168.0.1</param-name>

<param-value>192.168.0.1</param-value>

</init-param>

</servlet>

CS-39933 Using comma in the LDAP binding password results in an error.

Workaround: Use the single quote if the password has a comma. For example:

API> encrypttext,c,'password,123'

33


Known Issues


CS-39852 Content Storage Services (CSS) and Trust Content Services (TCS) may be limitedby the configurations of the underlying storage platform. For example, Centeraretained content cannot be removed as part of a content migration to a new filestore. Also, Centera and Atmos provide their own mechanisms for encryption,compression and de-duplication.

CS-39775 Renaming and deleting users and groups fail in the LDAP synchronization withthe Oracle Internet Directory (OID) Server.

CS-39553 Deletion of nested groups from the LDAP directory server is not properlysynchronized to Content Server.

Workaround: Explicitly provide a value for input argument -full_sync for theLDAP synchronization job through Documentum Administrator before runningit: TRUE for full sync; FALSE for incremental sync.

CS-39232 acl_check_db cannot be set to TRUE with QBS. This is because DFC does notsupport setRange with double security check in Content Server.

CS-37048 Content migration, encryption, de-duplication and compression of content in toAtmos store is not supported.

CS-35195 On Linux, there is a short delay between the dormancy status of a repositorychanges and the new dormancy status is projected to the connection broker. Thisis a limitation.

CS-35117 dm_check_password utility does not work on Windows 2008 domains because ofSamba limitations. Instead, use the LDAP. This is a limitation.

CS-5772 HTML email does not work on Solaris, while the same email can be correctly sentas HTML in Windows.

DC-6297

DC-6084

If one of the following errors occurs on DFC/UCF running on Tomcat 7.0, youmight need to set the HTTP request timeout to a value that is more appropriatefor your environment:

log4j:WARN Detected problem with connection: java.net

.SocketException: Software caused connection abort: socket

write error

java.io.IOException: missing CR

You set this value in either the connectionTimeout or keepAliveTimeoutproperty in server.xml. Values that usually work are between 2 to 4 minutes.

Note: This timeout is caused by an issue in Tomcat 7.0.

34

Known Issues


DC-5999 Importing file through an ACS location from Webtop fails.

When the ACS server and the global registry are of different versions, for example,a 6.7 SP1 ACS and a 7.0 global registry, add the entry for the global registry to theacs.properties file. This file is located in following location:

On Windows: %DOCUMENTUM%\jboss5.1.0\server\DctmServer_MethodServer\deploy\acs.ear\lib\configs.jar\config\acs.properties

On Linux: $DOCUMENTUM/jboss5.1.0/server/DctmServer_MethodServer/deploy/acs.ear/lib/configs.jar/config/acs/properties

Add the following entry to the acs.properties file:

repository.acsconfig.1=ACSCONFIG1 #ACS Config object name for

global registry Content Server repository.name.1=docbase #Global

registry name repository.login.1=Administrator #Global registry

superuser repository.password.1=password #Global registry

superuser password

DFC-11836 [Internationalization] dd_ppoulate.ebs for Loaddatadictionary populateslabels only in two-letter locale names even though the data dictionary file containslocale_name with five-letter locale.

DFC-10894 Invalid license exception occurs during multi-domain authentication whenContent Server internal JDK is used.

DocumentationIssue Number Description

N/A Product documentation might contain references to client applications andfunctionality that are not supported in the 7.x release, though these applicationsand functionality may become compatible in a future release. Only those clientapplications documented as compatible in the EMC Documentum 7.x Environmentand System Requirements Guide are supported in 7.x.

35