{"id":14293,"date":"2020-06-15T18:00:33","date_gmt":"2020-06-15T16:00:33","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/"},"modified":"2020-06-15T18:00:33","modified_gmt":"2020-06-15T16:00:33","slug":"documentum-upgrade-missing-dars-after-upgrade","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/","title":{"rendered":"Documentum Upgrade &#8211; Missing DARs after upgrade"},"content":{"rendered":"<p>As part of the same migration &amp; upgrade project I talked about in previous blogs already (<a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\" target=\"_blank\" rel=\"noopener noreferrer\">corrupt lockbox<\/a>, <a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-duplicate-jms-and-acs-config-objects\/\" target=\"_blank\" rel=\"noopener noreferrer\">duplicate objects<\/a> &amp; <a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-dm_datadictionarypublisher-with-wrong-target-server\/\" target=\"_blank\" rel=\"noopener noreferrer\">wrong target_server<\/a>), I have seen a very annoying and, this time, absolutely not consistent behavior in some upgrade from Documentum 7.x to 16.x versions. The issue or rather the issues I had was that random DAR files were not installed properly. This makes it rather difficult to anticipate since you basically don&#8217;t know what might fail before you actually do it for real. Performing DryRun helps a lot in anticipating potential (recurring) problems but if the issue itself is random, there isn&#8217;t much you can do without some gifts (if you can see the future, please reach out to me!)&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>In the past couple months, I performed around a dozen {migration+upgrade} and about half of these had issues with random DARs installation during the upgrade process. Even a DryRun and a real execution of the exact same procedure using the exact same source system ended-up with two different results: one worked without issue (the real migration fortunately) while the DryRun ended-up with a missing dar. In the procedure, it is checked whether or not there are any locks on repository objects, whether there are inconsistencies, whether there are any tasks in progress, aso&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>Issues were mostly linked to the following few DARs:<\/p>\n<ul>\n<li>LDAP.dar<\/li>\n<li>MessagingApp.dar<\/li>\n<li>MailApp.dar<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>I. LDAP<\/h3>\n<p>First, regarding the LDAP dar file, it only happened once and it was pretty easy to spot. As part of the migrations, I had to change the LDAP Server used. Since the target system was on Kubernetes using complete CI\/CD, we automated the creation of the LDAP Config Object with all its parameters but this piece failed for one of the migration. Replicating the issue showed the following outcome:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [20,22,24,26,32]\">[dmadmin@stg_cs ~]$ iapi REPO1\nPlease enter a user (dmadmin):\nPlease enter password for dmadmin:\n\n\t\tOpenText Documentum iapi - Interactive API interface\n\t\tCopyright (c) 2018. OpenText Corporation\n\t\tAll rights reserved.\n\t\tClient Library Release 16.4.0170.0080\n\nConnecting to Server using docbase REPO1\n[DM_SESSION_I_SESSION_START]info:  \"Session 010f123450262d3b started for user dmadmin.\"\n\nConnected to OpenText Documentum Server running Release 16.4.0170.0234  Linux64.Oracle\nSession id is s0\nAPI&gt; ?,c,select r_object_id, object_name from dm_ldap_config\nr_object_id       object_name\n----------------  ------------------------\n(0 rows affected)\n\nAPI&gt; create,c,dm_ldap_config\n...\n[DM_DFC_E_CLASS_NOT_FOUND]error:  \"Unable to instantiate the necessary java class: com.documentum.ldap.impl.DfLdapConfig\"\n\njava.lang.ClassNotFoundException: com.documentum.ldap.impl.DfLdapConfig\n\ncom.documentum.thirdparty.javassist.NotFoundException: com.documentum.ldap.impl.DfLdapConfig\n\n\nAPI&gt; ?,c,SELECT r_object_id, r_modify_date, object_name FROM dmc_dar ORDER BY r_modify_date ASC;\nr_object_id       r_modify_date              object_name\n----------------  -------------------------  ------------------------\n080f1234500007a5  12\/1\/2018 09:05:30         LDAP\n080f12345086063d  2\/12\/2020 16:26:12         Smart Container\n080f123450860780  2\/12\/2020 16:26:44         Webtop\n080f1234508607a1  2\/12\/2020 16:26:59         Workflow\n080f1234508607f9  2\/12\/2020 16:27:34         Presets\n...\n\nAPI&gt; exit\nBye\n[dmadmin@stg_cs ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>This kind of error (<em>[DM_DFC_E_CLASS_NOT_FOUND]error: &#8220;Unable to instantiate the necessary java class: com.documentum.ldap.impl.DfLdapConfig&#8221;<\/em>) can happen when the LDAP dar isn&#8217;t installed properly. In this case, during the upgrade it was indeed what happened, the current DAR seemed to be from the source system before the upgrade (<em>r_modify_date<\/em> is much older). The DAR installation log file generated by the upgrade shows that the LDAP one was skipped:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">[dmadmin@stg_cs ~]$ grep \"[ERR\" $DOCUMENTUM\/dba\/config\/REPO1\/dars.log\n[ERROR]  A module 'IDfLdapConfigModule' already exists under folder 'IDfLdapConfigModule'.\n[dmadmin@stg_cs ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>After re-install of the LDAP dar, the issue was resolved.<\/p>\n<p>&nbsp;<\/p>\n<h3>II. MessagingApp<\/h3>\n<p>Then regarding the MessagingApp dar file, this one also only happened once and it was very strange&#8230; While doing sanity checks after the end of the migration, everything was working except for searches from a client application like DA or D2. From the repository itself, full text searches were working properly:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">API&gt; ?,c,SELECT r_object_id, object_name FROM dm_document SEARCH document contains 'TestDocument';\nr_object_id       object_name\n----------------  --------------------\n090f2345600731d6  TestDoc.pdf\n(1 row affected)<\/pre>\n<p>&nbsp;<\/p>\n<p>However, doing the same kind of search on D2 for example showed something completely different:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [8,35]\">2020-03-03 10:30:55,750 UTC [INFO ] ([ACTIVE] ExecuteThread: '70' for queue: 'weblogic.kernel.Default (self-tuning)') - c.e.x3.server.services.RpcDoclistServiceImpl  : Context REPO2-1583231056848-dmadmin-2003987903 with terms = TestDocument\n2020-03-03 10:30:55,751 UTC [DEBUG] ([ACTIVE] ExecuteThread: '70' for queue: 'weblogic.kernel.Default (self-tuning)') - c.emc.d2fs.dctm.aspects.InjectSessionAspect   : Call first service D2SearchService.getQuickSearchContentWithOption(..)\n2020-03-03 10:30:55,751 UTC [DEBUG] ([ACTIVE] ExecuteThread: '70' for queue: 'weblogic.kernel.Default (self-tuning)') - c.emc.d2fs.dctm.aspects.InjectSessionAspect   : InjectSessionAspect::process method: com.emc.d2fs.dctm.web.services.search.D2SearchService.getQuickSearchContentWithOption\n...\n...\n2020-03-03 10:31:01,289 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.common.dctm.queries.D2QueryBuilder    : Query History: IDfQueryEvent(INTERNAL, DEFAULT): [REPO2] returned [Start processing] at [2020-03-03 10:30:56:007 +0000]\nIDfQueryEvent(ERROR, UNKNOWN): [REPO2] returned [[DM_VEL_INSTANTIATION_ERROR]error:  \"Cannot instantiate Java class\"] at [2020-03-03 10:31:01:280 +0000]\nDfServiceInstantiationException:: THREAD: Search Broker:REPO2:processing started at Tue Mar 03 10:30:55 UTC 2020; MSG: [DM_VEL_INSTANTIATION_ERROR]error:  \"Cannot instantiate Java class\"; ERRORCODE: 1902; NEXT: null\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.loadModuleClass(ModuleManager.java:258)\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.getModuleClass(ModuleManager.java:203)\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newModule(ModuleManager.java:154)\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newModule(ModuleManager.java:86)\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newModule(ModuleManager.java:60)\n        at com.documentum.fc.client.DfClient$ClientImpl.newModule(DfClient.java:466)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.ComplexMappingDefinitionManager.getMappingModule(ComplexMappingDefinitionManager.java:352)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.ComplexMappingDefinitionManager.getComplexMappingDefinitionFromDocbase(ComplexMappingDefinitionManager.java:319)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.ComplexMappingDefinitionManager.loadComplexMappingDefinition(ComplexMappingDefinitionManager.java:149)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.ComplexMappingDefinitionManager.getComplexMappingDefinition(ComplexMappingDefinitionManager.java:75)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.loading.legacy.LegacyMappingLoader.loadSearchInterfaces(LegacyMappingLoader.java:42)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.EosMappingLoader.populateLegacyMapping(EosMappingLoader.java:199)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.EosMappingLoader.populateMappingCache(EosMappingLoader.java:112)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.definition.EosMappingLoader.getInterface(EosMappingLoader.java:63)\n        at com.documentum.fc.client.search.impl.generation.docbase.common.sco.mapping.SCOGenerator.isComplexQuery(SCOGenerator.java:38)\n        at com.documentum.fc.client.search.impl.generation.docbase.TargetLanguageSelector.initByQueryBuilder(TargetLanguageSelector.java:85)\n        at com.documentum.fc.client.search.impl.generation.docbase.TargetLanguageSelector.&lt;init&gt;(TargetLanguageSelector.java:39)\n        at com.documentum.fc.client.search.impl.generation.docbase.DocbaseQueryGeneratorManager.generateQueryExecutor(DocbaseQueryGeneratorManager.java:248)\n        at com.documentum.fc.client.search.impl.generation.docbase.DocbaseQueryGeneratorManager.generateQueryExecutor(DocbaseQueryGeneratorManager.java:96)\n        at com.documentum.fc.client.search.impl.execution.adapter.docbase.DocbaseAdapter.execute(DocbaseAdapter.java:83)\n        at com.documentum.fc.client.search.impl.execution.broker.SearchJob.handleProcessingState(SearchJob.java:382)\n        at com.documentum.fc.client.search.impl.execution.broker.SearchJob.doRunLoop(SearchJob.java:477)\n        at com.documentum.fc.client.search.impl.execution.broker.SearchJob.run(SearchJob.java:433)\n        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n        at java.lang.Thread.run(Thread.java:748)\nCaused by: java.lang.ClassNotFoundException: com.documentum.services.complexobjects.impl.ComplexObjectMappingDefImpl\n        at java.net.URLClassLoader.findClass(URLClassLoader.java:382)\n        at com.documentum.fc.client.impl.bof.classmgmt.URLClassLoaderEx.findClass(URLClassLoaderEx.java:49)\n        at com.documentum.fc.client.impl.bof.classmgmt.DelayedDelegationClassLoader.findClass(DelayedDelegationClassLoader.java:241)\n        at com.documentum.fc.client.impl.bof.classmgmt.AbstractTransformingClassLoader.findClass(AbstractTransformingClassLoader.java:122)\n        at com.documentum.fc.client.impl.bof.classmgmt.DelayedDelegationClassLoader.loadClass(DelayedDelegationClassLoader.java:147)\n        at com.documentum.fc.client.impl.bof.classmgmt.AbstractTransformingClassLoader.loadClass(AbstractTransformingClassLoader.java:69)\n        at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.loadModuleClass(ModuleManager.java:254)\n        ... 25 more\n\nIDfQueryEvent(ERROR, UNREACHABLE): [REPO2] returned [Unable to process query] at [2020-03-03 10:31:01:281 +0000]\n, Query Status: 6\n2020-03-03 10:31:01,291 UTC [ERROR] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.common.dctm.queries.D2QueryBuilder    : The search has failed. null\n2020-03-03 10:31:01,307 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Executing xPlore search ended : 6.722s\n2020-03-03 10:31:01,307 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Enter buildItems\n2020-03-03 10:31:01,308 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : FACETS: ObjectID = 080f2345602f4a20\n2020-03-03 10:31:01,310 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : listColNames=[object_name, score, title, a_status, r_modify_date, r_modifier]\n2020-03-03 10:31:01,311 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Exit buildItems\n2020-03-03 10:31:01,311 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : FACETS: leaving getContent\n2020-03-03 10:31:01,354 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : getSearchContent - start building facets\n2020-03-03 10:31:01,355 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Exit buildFacets\n2020-03-03 10:31:01,355 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Query name = lastSearch\n2020-03-03 10:31:01,363 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Enter getObjectName\n2020-03-03 10:31:01,364 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Exit getObjectName\n2020-03-03 10:31:01,364 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : FACETS: attrNameList from query = []\n2020-03-03 10:31:01,364 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : FACETS: attrValueList from query = []\n2020-03-03 10:31:01,365 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : searchTypes = [dm_document]\n2020-03-03 10:31:01,365 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : getSearchContent - done building facets\n2020-03-03 10:31:01,365 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.content.D2cQueryContent     : Exit getSearchContent\n2020-03-03 10:31:01,366 UTC [ERROR] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - c.emc.d2fs.dctm.aspects.InjectSessionAspect   : {}\ncom.documentum.fc.common.DfException: The search has failed.\n[DM_VEL_INSTANTIATION_ERROR]\n        at com.emc.d2fs.dctm.content.D2cQueryContent.getSearchContent(D2cQueryContent.java:598)\n        at com.emc.d2fs.dctm.content.NodeLastSearchContent.getSearchContent(NodeLastSearchContent.java:217)\n        at com.emc.d2fs.dctm.web.services.content.D2ContentService.getContent(D2ContentService.java:391)\n        at com.emc.d2fs.dctm.web.services.content.D2ContentService.getSearchContent_aroundBody14(D2ContentService.java:425)\n        at com.emc.d2fs.dctm.web.services.content.D2ContentService$AjcClosure15.run(D2ContentService.java:1)\n        at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:229)\n        at com.emc.d2fs.dctm.aspects.InjectSessionAspect.process(InjectSessionAspect.java:240)\n        at com.emc.d2fs.dctm.web.services.content.D2ContentService.getSearchContent(D2ContentService.java:403)\n        at com.emc.x3.client.services.search.RpcSearchManagerServiceImpl.getSearchResults(RpcSearchManagerServiceImpl.java:37)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587)\n        at com.emc.x3.server.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:105)\n        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)\n        at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)\n        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)\n        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n        at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)\n        at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)\n        at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n        at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)\n        at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61)\n        at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)\n        at com.custom.d2.auth.filters.NonSSOAuthenticationFilter.executeChain(NonSSOAuthenticationFilter.java:33)\n        at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)\n        at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)\n        at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)\n        at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)\n        at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)\n        at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)\n        at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)\n        at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:387)\n        at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)\n        at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)\n        at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)\n        at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)\n        at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)\n        at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)\n        at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)\n        at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)\n        at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)\n        at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)\n        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)\n        at com.emc.x3.portal.server.filters.X3SessionTimeoutFilter.doFilter(X3SessionTimeoutFilter.java:40)\n        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)\n        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3706)\n        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3672)\n        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:328)\n        at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)\n        at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)\n        at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)\n        at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2443)\n        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2291)\n        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2269)\n        at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1705)\n        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1665)\n        at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:272)\n        at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)\n        at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)\n        at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)\n        at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)\n        at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:652)\n        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)\n        at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)\n2020-03-03 10:31:01,366 UTC [DEBUG] ([ACTIVE] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)') - com.emc.d2fs.dctm.web.services.D2fsContext    : Release session : s1<\/pre>\n<p>&nbsp;<\/p>\n<p>As you can see above, D2 complains about instantiation of a specific class (<em>&#8220;com.documentum.services.complexobjects.impl.ComplexObjectMappingDefImpl&#8221;<\/em>). This class is part of an <em>SBO<\/em> bundled in the <em>MessagingApp.dar<\/em> as mentioned on <a href=\"https:\/\/knowledge.opentext.com\/knowledge\/cs.dll\/kcs\/kbarticle\/view\/KB6289567\" target=\"_blank\" rel=\"noopener noreferrer\">KB6289567<\/a> &amp; <a href=\"https:\/\/knowledge.opentext.com\/knowledge\/cs.dll\/kcs\/kbarticle\/view\/KB6296577\" target=\"_blank\" rel=\"noopener noreferrer\">KB6296577<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p>Therefore, the DAR installation must have failed, right? Well it didn&#8217;t and that&#8217;s the strange thing I was talking about&#8230; I have the evidences of the proper installation of the <em>MessagingApp.dar<\/em> inside the repository the day before:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [8,9,18,20,22,26]\">[INFO]  ******************************************************\n[INFO]  * Headless Composer\n[INFO]  * Version:        16.4.000.0042\n[INFO]  * Java version:   1.8.0_152 (64bit)\n[INFO]  * Java home:      $JAVA_HOME\/jre\n[INFO]  * Set storage type: false\n[INFO]  *\n[INFO]  * DAR file:       $DOCUMENTUM\/product\/16.4\/install\/DARsInternal\/MessagingApp.dar\n[INFO]  * Project name:   MessagingApp\n[INFO]  * Built by Composer: 7.1.0000.0186\n[INFO]  *\n[INFO]  * Repository:     REPO2\n[INFO]  * Server version: 16.4.0170.0234  Linux64.Oracle\n[INFO]  * User name:      dmadmin\n[INFO]  ******************************************************\n[INFO]  Install started...  Mon Mar 02 22:18:00 UTC 2020\n[INFO]  Executing pre-install script\n[INFO]  Pre-install script executed successfully Mon Mar 02 22:18:00 UTC 2020\n...\n[INFO]  Done Overwriting object : 'com.documentum.services.complexobjects.impl.ComplexObjectMappingDefImpl'(dmc_module 0b0f2345600008f9)\n...\n[INFO]  Done Versioning object : 'MessagingApp'(dmc_dar 080f2345608608e9)\n...\n[INFO]  Finished executing post-install actions Mon Mar 02 22:18:30 UTC 2020\n[INFO]  Finished executing post-install script Mon Mar 02 22:18:32 UTC 2020\n[INFO]  Project 'MessagingApp' was successfully installed.<\/pre>\n<p>&nbsp;<\/p>\n<p>There are absolutely no errors and it shows that the missing class <em>&#8220;com.documentum.services.complexobjects.impl.ComplexObjectMappingDefImpl&#8221;<\/em> was upgraded properly but on D2, it doesn&#8217;t work (it was properly installed on both the Global Registry and the Repository used for the search). Re-installing again the DAR file produced exactly the same log file: 100% the same except for the date, obviously. After the re-installation of the DAR, the issue was magically gone. For this issue honestly, I&#8217;m still amazed how this can be possible and I&#8217;m pretty sure I will never find any reason.<\/p>\n<p>&nbsp;<\/p>\n<h3>III. MailApp<\/h3>\n<p>Finally, the last issue is with the MailApp dar file. That&#8217;s the one which had the most occurrences as far as I could see. During an upgrade from 7.3 to 16.4 P17, the dar installation failed and the following was shown inside the &#8220;dars.log&#8221; file:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [19,20,22,27,28,30,31,32,33,34,35,36]\">[INFO]  ******************************************************\n[INFO]  * Headless Composer\n[INFO]  * Version:        16.4.000.0042\n[INFO]  * Java version:   1.8.0_152 (64bit)\n[INFO]  * Java home:      $JAVA_HOME\/jre\n[INFO]  * Set storage type: false\n[INFO]  *\n[INFO]  * DAR file:       $DOCUMENTUM\/product\/16.4\/install\/DARsInternal\/MailApp.dar\n[INFO]  * Project name:   MailApp\n[INFO]  * Built by Composer: 7.1.0000.0186\n[INFO]  *\n[INFO]  * Repository:     REPO3\n[INFO]  * Server version: 16.4.0170.0234  Linux64.Oracle\n[INFO]  * User name:      dmadmin\n[INFO]  ******************************************************\n[INFO]  Install started...  Thu Mar 12 10:08:27 UTC 2020\n[INFO]  Executing pre-install script\n[INFO]  dmbasic.exe output : connecting docbase...REPO3\n[INFO]  dmbasic.exe output : dm_attachment_folder type exists\n[INFO]  dmbasic.exe output : Relation type 'dm_attachments_relation' already exists\n[INFO]  dmbasic.exe output : Disconnect from the docbase.\n[INFO]  Pre-install script executed successfully Thu Mar 12 10:08:31 UTC 2020\n[WARN]  Cannot retrieve object by Object Id. This may happen if an object previously installed by Composer was deleted. Object reference will be returned as null. OID: 0b0f345670000df1, URN: urnd:com.emc.ide.artifact.moduledef\/com.documentum.mailapp.operations.DfPreProcessMessageObject?artifactURI=file:\/C:\/Source\/...\/com.documentum.mailapp.operations.dfpreprocessmessageobject.module#\/\/@dataModel\/@externalInterfaces\n[WARN]  Cannot retrieve object by Object Id. This may happen if an object previously installed by Composer was deleted. Object reference will be returned as null. OID: 0b0f345670000fe9, URN: urnd:com.emc.ide.artifact.aspectmoduledef\/dm_attachmentfolder_aspect?artifactURI=file:\/C:\/Source\/...\/dm_attachmentfolder_aspect.module#\/\/@dataModel\/@miscellaneous\n[WARN]  Cannot retrieve object by Object Id. This may happen if an object previously installed by Composer was deleted. Object reference will be returned as null. OID: 090f345670000e37, URN: urnd:com.emc.ide.artifact.jardef.jardef\/attachmentfolderaspect.jar?artifactURI=file:\/C:\/source\/...\/attachmentfolderaspect.jar%5B1%5D.jardef#\/\/@dataModel\n[WARN]  Cannot retrieve object by Object Id. This may happen if an object previously installed by Composer was deleted. Object reference will be returned as null. OID: 080f345670000e41, URN: urnd:com.emc.ide.artifact.moduledef\/com.message.aspose?artifactURI=file:\/C:\/Users\/...\/com.message.aspose.module#\/\/@dataModel\/@runtimeEnvironmentXML\n[ERROR]  A module 'dm_attachmentfolder_aspect' already exists under folder 'Aspect'.\n[ERROR]  A module 'mdmo_message_aspect' already exists under folder 'Aspect'.\n[WARN]  superTypeName is null. This might happen if the dependent project is not Installed in the same ANT build invocation\n[ERROR]  A module 'com.documentum.mailapp.operations.DfPreProcessMessageObject' already exists under folder 'Operations'.\n[ERROR]  A module 'com.documentum.mailapp.operations.inbound.DfCleanUpLocalMailAppFiles' already exists under folder 'Operations'.\n[ERROR]  A module 'com.documentum.mailapp.operations.inbound.DfFixUpAttachments' already exists under folder 'Operations'.\n[ERROR]  A module 'com.documentum.mailapp.operations.inbound.DfImportMailObject' already exists under folder 'Operations'.\n[ERROR]  A module 'com.documentum.mailapp.operations.inbound.DfSeparateAttachments' already exists under folder 'Operations'.\n[ERROR]  A module 'aspose' already exists under folder 'Modules'.\n[ERROR]  A module 'mailappconfig' already exists under folder 'Modules'.\n[INFO]  MailApp install aborted by user.<\/pre>\n<p>&nbsp;<\/p>\n<p>On another migration with a source that is 7.2 this time and a target that is 16.4 P20, we had another batch of issues. On 7.2, the MailApp didn&#8217;t exist (as far as I know), so the upgrade is supposed to install for the first time this DAR but it fails because some of the pieces already exists. If you look at the logs above, the same type existed already as well but above, it just continued without any problem the &#8220;Pre-install&#8221; script (line 19, 22 above \/\/ line 20, 22 below). Below, it fails on already existing types and in both cases [above for 7.3 and below for 7.2], the flag <em>&#8220;preserve_existing_types&#8221;<\/em> is set to <em>&#8220;T&#8221;<\/em> (True) in the server.ini of all repositories so it doesn&#8217;t make much sense that there is a difference in behavior&#8230; However, that&#8217;s how it is so if you have any explanation, feel free to share! I asked OpenText to look into it but nothing came out of it so far. Anyway, so here are the logs on the 7.2 repository:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [20,22,25,26]\">[INFO]  ******************************************************\n[INFO]  * Headless Composer\n[INFO]  * Version:        16.4.000.0042\n[INFO]  * Java version:   1.8.0_152 (64bit)\n[INFO]  * Java home:      $JAVA_HOME\/jre\n[INFO]  * Set storage type: false\n[INFO]  *\n[INFO]  * DAR file:       $DOCUMENTUM\/product\/16.4\/install\/DARsInternal\/MailApp.dar\n[INFO]  * Project name:   MailApp\n[INFO]  * Built by Composer: 7.1.0000.0186\n[INFO]  *\n[INFO]  * Repository:     REPO4\n[INFO]  * Server version: 16.4.0200.0256  Linux64.Oracle\n[INFO]  * User name:      dmadmin\n[INFO]  ******************************************************\n[INFO]  Install started...  Fri Apr 03 08:32:45 UTC 2020\n[INFO]  Executing pre-install script\n[INFO]  dmbasic.exe output : connecting docbase...REPO4\n[INFO]  dmbasic.exe output : Create dm_state_extension type.\n[INFO]  dmbasic.exe output : [DM_QUERY_E_CREATE_FAILED]error:  \"CREATE TYPE statement failed for type: dm_attachment_folder.\"\n[INFO]  dmbasic.exe output :\n[INFO]  dmbasic.exe output : [DM_TYPE_MGR_E_EXISTING_TABLE]error:  \"Cannot create type dm_attachment_folder because the table dm_attachment_folder_s unexpectedly already exists in the database and the server 'preserve_existing_types' flag is enabled.  To complete this operation the table must first be manually dropped or the server flag disabled.\"\n[INFO]  dmbasic.exe output :\n[INFO]  dmbasic.exe output :\n[INFO]  dmbasic.exe output : Failed to create dm_attachment_folder type\n[ERROR]  Procedure execution failed with dmbasic.exe exit value : 255\n[INFO]  MailApp install failed.\n[ERROR]  Unable to install dar file $DOCUMENTUM\/product\/16.4\/install\/DARsInternal\/MailApp.dar\ncom.emc.ide.installer.PreInstallException: Error running pre-install procedure \"presetup\". Please contact the procedure owner to verify if it is functioning properly. Please also check if the JAVA_HOME is pointing to the correct JDK. In case of multiple installed JDK's, please provide -vm &lt;JDK&gt;bin flag in the composer.ini\/dardeployer.ini files\n        at internal.com.emc.ide.installer.DarInstaller.preInstall(DarInstaller.java:1085)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:495)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:334)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:303)\n        at com.emc.ide.installer.util.IDarInstallerHelper.doInPlaceInstall(IDarInstallerHelper.java:127)\n        at com.emc.ant.installer.api.InstallerAntTask.installDar(InstallerAntTask.java:258)\n        at com.emc.ant.installer.api.InstallerAntTask.execute(InstallerAntTask.java:135)\n        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)\n        at org.apache.tools.ant.Task.perform(Task.java:348)\n        at org.apache.tools.ant.Target.execute(Target.java:392)\n        at org.apache.tools.ant.Target.performTasks(Target.java:413)\n        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)\n        at org.apache.tools.ant.Project.executeTarget(Project.java:1368)\n        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)\n        at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)\n        at org.apache.tools.ant.Project.executeTargets(Project.java:1251)\n        at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:672)\n        at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:537)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)\n        at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)\n        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)\n        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\n        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\n        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)\n        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)\n        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)\n        at org.eclipse.equinox.launcher.Main.run(Main.java:1438)\n        at org.eclipse.equinox.launcher.Main.main(Main.java:1414)\n        at org.eclipse.core.launcher.Main.main(Main.java:34)\nCaused by: com.emc.ide.external.dfc.procedurerunner.ProcedureRunnerException: Procedure execution failed with dmbasic.exe exit value : 255\n        at com.emc.ide.external.dfc.procedurerunner.ProcedureRunnerUtils.executeDmBasic(ProcedureRunnerUtils.java:283)\n        at com.emc.ide.external.dfc.procedurerunner.ProcedureRunner.execute(ProcedureRunner.java:55)\n        at internal.com.emc.ide.installer.DarInstaller.preInstall(DarInstaller.java:1080)\n        ... 42 more\n[ERROR]  Failed to install DAR\nUnable to install dar file $DOCUMENTUM\/product\/16.4\/install\/DARsInternal\/MailApp.dar\n        at com.emc.ant.installer.api.InstallerAntTask.installDar(InstallerAntTask.java:273)\n        at com.emc.ant.installer.api.InstallerAntTask.execute(InstallerAntTask.java:135)\n        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)\n        at org.apache.tools.ant.Task.perform(Task.java:348)\n        at org.apache.tools.ant.Target.execute(Target.java:392)\n        at org.apache.tools.ant.Target.performTasks(Target.java:413)\n        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)\n        at org.apache.tools.ant.Project.executeTarget(Project.java:1368)\n        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)\n        at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)\n        at org.apache.tools.ant.Project.executeTargets(Project.java:1251)\n        at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:672)\n        at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:537)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)\n        at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)\n        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)\n        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\n        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\n        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)\n        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)\n        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n        at java.lang.reflect.Method.invoke(Method.java:498)\n        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)\n        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)\n        at org.eclipse.equinox.launcher.Main.run(Main.java:1438)\n        at org.eclipse.equinox.launcher.Main.main(Main.java:1414)\n        at org.eclipse.core.launcher.Main.main(Main.java:34)\nCaused by: com.emc.ide.installer.PreInstallException: Error running pre-install procedure \"presetup\". Please contact the procedure owner to verify if it is functioning properly. Please also check if the JAVA_HOME is pointing to the correct JDK. In case of multiple installed JDK's, please provide -vm &lt;JDK&gt;bin flag in the composer.ini\/dardeployer.ini files\n        at internal.com.emc.ide.installer.DarInstaller.preInstall(DarInstaller.java:1085)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:495)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:334)\n        at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:303)\n        at com.emc.ide.installer.util.IDarInstallerHelper.doInPlaceInstall(IDarInstallerHelper.java:127)\n        at com.emc.ant.installer.api.InstallerAntTask.installDar(InstallerAntTask.java:258)\n        ... 37 more\nCaused by: com.emc.ide.external.dfc.procedurerunner.ProcedureRunnerException: Procedure execution failed with dmbasic.exe exit value : 255\n        at com.emc.ide.external.dfc.procedurerunner.ProcedureRunnerUtils.executeDmBasic(ProcedureRunnerUtils.java:283)\n        at com.emc.ide.external.dfc.procedurerunner.ProcedureRunner.execute(ProcedureRunner.java:55)\n        at internal.com.emc.ide.installer.DarInstaller.preInstall(DarInstaller.java:1080)\n        ... 42 more<\/pre>\n<p>&nbsp;<\/p>\n<p>If you have the above errors, you can just set the <em>&#8220;preserve_existing_types&#8221;<\/em> flag to <em>&#8220;F&#8221;<\/em> (False), then start again the DAR installation and it should be installing properly this time. Please take care with this flag! If you are copying the repository, it must be set to <em>&#8220;T&#8221;<\/em> (True) otherwise it will most likely cause you big troubles&#8230; But for in-place upgrade, you can and should set it to <em>&#8220;F&#8221;<\/em> (False) before starting the repository upgrade and switch it back to <em>&#8220;T&#8221;<\/em> (True) once the upgrade is completed and all DARs have been installed. So make sure you do that and the number of issues during DAR installations should decrease drastically.<\/p>\n<p>&nbsp;<\/p>\n<p>Anyway, all that to say that there are some best practices to apply to upgrade, even if it&#8217;s not documented anywhere. In addition, you should be careful about the DARs installation logs and really test your application because even when everything seems to went well, you might not be completely safe&#8230; Where would be the fun if you could rely on deterministic systems? \ud83d\ude09<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As part of the same migration &amp; upgrade project I talked about in previous blogs already (corrupt lockbox, duplicate objects &amp; wrong target_server), I have seen a very annoying and, this time, absolutely not consistent behavior in some upgrade from Documentum 7.x to 16.x versions. The issue or rather the issues I had was that [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[907,129,101,1547,1994,1995,1996],"type_dbi":[],"class_list":["post-14293","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-dar","tag-documentum","tag-installation","tag-ldap","tag-mailapp","tag-messagingapp","tag-preserve_existing_types"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum Upgrade - Missing DARs after upgrade - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum Upgrade - Missing DARs after upgrade\" \/>\n<meta property=\"og:description\" content=\"As part of the same migration &amp; upgrade project I talked about in previous blogs already (corrupt lockbox, duplicate objects &amp; wrong target_server), I have seen a very annoying and, this time, absolutely not consistent behavior in some upgrade from Documentum 7.x to 16.x versions. The issue or rather the issues I had was that [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-06-15T16:00:33+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"24 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum Upgrade &#8211; Missing DARs after upgrade\",\"datePublished\":\"2020-06-15T16:00:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/\"},\"wordCount\":1054,\"commentCount\":0,\"keywords\":[\"DAR\",\"Documentum\",\"Installation\",\"ldap\",\"MailApp\",\"MessagingApp\",\"preserve_existing_types\"],\"articleSection\":[\"Application integration &amp; Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/\",\"name\":\"Documentum Upgrade - Missing DARs after upgrade - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2020-06-15T16:00:33+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-upgrade-missing-dars-after-upgrade\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum Upgrade &#8211; Missing DARs after upgrade\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\\\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\\\/\\\/blog.dbi-services.com\\\/author\\\/morgan-patou\\\/\",\"https:\\\/\\\/x.com\\\/MorganPatou\"],\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/morgan-patou\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum Upgrade - Missing DARs after upgrade - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/","og_locale":"en_US","og_type":"article","og_title":"Documentum Upgrade - Missing DARs after upgrade","og_description":"As part of the same migration &amp; upgrade project I talked about in previous blogs already (corrupt lockbox, duplicate objects &amp; wrong target_server), I have seen a very annoying and, this time, absolutely not consistent behavior in some upgrade from Documentum 7.x to 16.x versions. The issue or rather the issues I had was that [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/","og_site_name":"dbi Blog","article_published_time":"2020-06-15T16:00:33+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"24 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum Upgrade &#8211; Missing DARs after upgrade","datePublished":"2020-06-15T16:00:33+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/"},"wordCount":1054,"commentCount":0,"keywords":["DAR","Documentum","Installation","ldap","MailApp","MessagingApp","preserve_existing_types"],"articleSection":["Application integration &amp; Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/","name":"Documentum Upgrade - Missing DARs after upgrade - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2020-06-15T16:00:33+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-missing-dars-after-upgrade\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum Upgrade &#8211; Missing DARs after upgrade"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/14293","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=14293"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/14293\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=14293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=14293"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=14293"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=14293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}