A couple months ago, I was working on an upgrade project from Documentum 7.x to 16.4. During this upgrade, I faced a few issues so I will try to write some blogs about all that in the coming weeks, starting today with an alleged “corrupt” Lockbox. This upgrade was part of a migration as well from Virtual Machines to Containers (using Kubernetes), therefore the upgrade was done on a staging environment build specifically for that using the source version. The cloning process was done properly and then the upgrade started.<\/p>\n
<\/p>\n
Upgrading the binaries was done without error but there were some INFO messages that I found interesting:<\/p>\n
[dmadmin@stg-cs ~]$ cd $DCTM_BINARY\/logs\/\n[dmadmin@stg-cs logs]$ grep -i \"lock\" install.log\n08:35:27,490 INFO [main] com.documentum.install.shared.actions.DiActionExtractSystemResourceTarget - Extracting java system resource upgradeLockbox.sh to $DM_HOME\/bin\/upgradeLockbox.sh\n08:35:27,586 INFO [main] com.documentum.install.shared.actions.DiActionSetPermissionTarget - performing chmod 6750 $DM_HOME\/bin\/upgradeLockbox.sh\n08:35:33,897 INFO [main] - Did not find existing lockbox file, don't need to upgrade existing lockbox!\n[dmadmin@stg-cs logs]$<\/pre>\n<\/p>\n
Since it was just an INFO message, I just kept a note about that to check it later and then I proceeded with the patching and repository upgrade. The patching went smoothly as well but it wasn’t the case for the repository upgrade which failed at the beginning:<\/p>\n
[dmadmin@stg-cs logs]$ cd $DM_HOME\/install\/logs\/\n[dmadmin@stg-cs logs]$ cat install.log\n11:07:01,522 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product name is: UniversalServerConfigurator\n11:07:01,522 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product version is: 16.4.0000.0248\n11:07:01,523 INFO [main] -\n11:07:01,554 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - Done InitializeSharedLibrary ...\n11:07:01,578 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBROKER value to TRUE for SERVER\n11:07:01,578 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBASE value to TRUE for SERVER\n11:07:02,581 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer was started using the dm_launch_server_config_program.sh script.\n11:07:02,581 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable DOCUMENTUM.\n11:07:05,581 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable PATH.\n11:07:08,603 INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentConfigurationInstallationValidation - Start to validate docbase parameters.\n11:07:08,610 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerPatchExistingDocbaseAction - The installer will obtain all the DOCBASE on the machine.\n11:07:10,618 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerDocAppFolder - The installer will obtain all the DocApps which could be installed for the repository.\n11:07:10,620 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadDocBaseComponentInfo - The installer will gather information about the component GR_REPO.\n11:07:13,624 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - The installer will check old AEK key status.\n11:07:15,173 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - The installer will validate AEK\/Lockbox fileds.\n11:07:15,180 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - Upgrade docbase use keep aek unchanged in lockbox, will not re-create it\n11:07:16,685 ERROR [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Check AEK key passphrase failed\ncom.documentum.install.shared.common.error.DiException: Check AEK key passphrase failed\n at com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase.executeValidation(DiWAServerValidateLockboxPassphrase.java:133)\n at com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase.setup(DiWAServerValidateLockboxPassphrase.java:115)\n at com.documentum.install.shared.installanywhere.actions.InstallWizardAction.install(InstallWizardAction.java:73)\n at com.zerog.ia.installer.actions.CustomAction.installSelf(Unknown Source)\n ...\n[dmadmin@stg-cs logs]$<\/pre>\n<\/p>\n
At first, I thought that I provided the wrong passphrases for the AEK or Lockbox. Therefore, I tried to reset the server fingerprint to validate the Lockbox passphrase:<\/p>\n
[dmadmin@stg-cs logs]$ dm_crypto_manage_lockbox -lockbox lockbox.lb -lockboxpassphrase ${lockbox_passphrase} -resetfingerprint\nLockbox lockbox.lb\nLockbox Path $DOCUMENTUM\/dba\/secure\/lockbox.lb\nThe Lockbox is corrupt and failed to load.Lockbox open failed \u2592pY\n** Operation failed **\n[dmadmin@stg-cs logs]$<\/pre>\n<\/p>\n
After some investigation, I saw that I could actually work with the lockbox while using the CS 7.x binaries (initial version, already using the lockbox) but it wasn’t working while using the CS 16.4 binaries. So just setting the $DM_HOME to one or the other path (and reloading the environment) changed completely the behavior since one was working but not the other. Since it was therefore linked to the upgrade, I was thinking that maybe the “INFO” message above regarding the upgrade lockbox was actually an issue? So digging deeper, I saw two new parameters in the 16.4 upgrade silent properties:<\/p>\n
SERVER.LOCKBOX_FILE_NAME1=lockbox.lb\nSERVER.LOCKBOX_PASSPHRASE.PASSWORD1=xxx<\/pre>\n<\/p>\n
These two parameters weren’t available as far as I know with the CS 7.3 and they only appeared with the CS 16.4. While trying to upgrade the binaries from 7.x to 16.4, you obviously don’t have the binaries already available in 16.4 and therefore you don’t have access to the silent properties files of 16.4 (unless you go dig them into the compressed archive) so I used the one from 7.x which was therefore without these two parameters. Is this the issue? Well not really… Obviously, if you specify these two parameters, then the lockbox will be upgraded with the binaries (I didn’t test it, hopefully it works…). However, it shouldn’t be mandatory, the repository upgrade should also perform the mandatory lockbox upgrade. The thing here is that we already have to provide the AEK & Lockbox passphrases in the repository upgrade so to avoid duplicating things unnecessarily, I wanted to do that on the repository upgrade directly, where it should be, from my point of view. Therefore, I assumed that this wasn’t really the issue here (I will come back on that later in this blog…).<\/p>\n
<\/p>\n
Why is the repository upgrade failing then? Well as you can see, there is not enough information so far. I found that the passphrases that I used were indeed correct but it still failed because of the so called “corrupt” Lockbox. What I did first is to backup the lockbox and try to upgrade it myself:<\/p>\n
[dmadmin@stg-cs logs]$ cd $DM_HOME\/bin\/\n[dmadmin@stg-cs bin]$\n[dmadmin@stg-cs bin]$ .\/upgradeLockbox.sh lockbox.lb ${lockbox_passphrase}\nLockbox lockbox.lb\nLockbox Path $DOCUMENTUM\/dba\/secure\/lockbox.lb\nRenamed $DOCUMENTUM\/dba\/secure\/lockbox.lb to $DOCUMENTUM\/dba\/secure\/lockbox.lb.bak.2020-2-14.11.33.17\nRenamed $DOCUMENTUM\/dba\/secure\/lockbox.lb.FCD to $DOCUMENTUM\/dba\/secure\/lockbox.lb.FCD.bak.2020-2-14.11.33.17\nCreating initial Lockbox 4.0 file...\nReading old Lockbox file into buffer... $DOCUMENTUM\/dba\/secure\/lockbox.lb.bak.2020-2-14.11.33.17\nSetting pointer to Custom SSV providers...\nImporting data from old Lockbox file into new Lockbox 4.0 handle...\n\nDone!\n[dmadmin@stg-cs bin]$ \n[dmadmin@stg-cs bin]$ diff $DOCUMENTUM\/dba\/secure\/lockbox.lb $DOCUMENTUM\/dba\/secure\/lockbox.lb.bak.2020-2-14.11.33.17\n1c1\n< 4.000000|...\n No newline at end of file\n---\n> 3.100000|...\n No newline at end of file\n[dmadmin@stg-cs bin]$<\/pre>\n<\/p>\n
As you can see above, the upgrade of the lockbox itself is working fine and it does change the version from 3.1 (used by CS 7.x) to 4.0 (used by CS 16.4). Running again the repository upgrade didn’t produce any error anymore so it was able to proceed and complete without any problem once the lockbox was manually upgraded. However, this is only a workaround so I wanted to get to the bottom of the issue and therefore with my second repository, I restored the initial lockbox, reloaded it in the memory with the CS 7.x binaries and enabled the DEBUG logs on the repository upgrade installer. Obviously, the DEBUG logs was quite huge so I won’t put everything in this blog but the relevant section is the following one:<\/p>\n
[dmadmin@stg-cs bin]$ cd $DM_HOME\/install\/logs\/\n[dmadmin@stg-cs logs]$ cat install.log\n12:02:28,957 DEBUG [main] - ###################The variable is: LOG_IS_READY, value is: true\n12:02:28,957 DEBUG [main] - ###################The variable is: FORMATED_PRODUCT_VERSION_NUMBER, value is: 16.4.0000.0248\n12:02:28,958 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product name is: UniversalServerConfigurator\n12:02:28,958 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product version is: 16.4.0000.0248\n12:02:28,958 INFO [main] -\n12:02:28,959 DEBUG [main] - ###################The variable is: DCTM_INSTALLER_TEMP_DIR, value is: \/tmp\/731965.tmp\n...\n12:02:41,075 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - *******************Start action com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld***********************\n12:02:41,075 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - The installer will check old AEK key status.\n12:02:41,079 DEBUG [main] - Before running the following command, the class path is \/tmp\/install.dir.13366\/InstallerData:\/tmp\/install.dir.13366\/InstallerData\/installer.zip:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:\n12:02:41,079 DEBUG [main] - Before running the following command, the path is \/usr\/xpg4\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$DM_HOME\/bin:$ORACLE_HOME\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/dmadmin\/.local\/bin:\/home\/dmadmin\/bin:\/bin:\/usr\/bin:\/sbin:\/usr\/sbin:\/usr\/local\/bin\n12:02:42,569 DEBUG [main] - Command line is \/bin\/sh -c \"$DM_HOME\/bin\/dm_crypto_create -check -noprompt -lockbox lockbox.lb -keyname CSaek >\"$DOCUMENTUM\/temp\/installer\/installlogs\/tempKeyStoreOutput201016218bfd-9e6c-3441-a81e-697068322a7391246586e34ef995978.out\" 2>&1\" and start in \/tmp\/731965.tmp. The return code of this command is 3\n12:02:42,569 DEBUG [main] - After running the above command, the class path is \/tmp\/install.dir.13366\/InstallerData:\/tmp\/install.dir.13366\/InstallerData\/installer.zip:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:\n12:02:42,569 DEBUG [main] - After running the above command, the path is \/usr\/xpg4\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$DM_HOME\/bin:$ORACLE_HOME\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/dmadmin\/.local\/bin:\/home\/dmadmin\/bin:\/bin:\/usr\/bin:\/sbin:\/usr\/sbin:\/usr\/local\/bin\n12:02:42,629 DEBUG [main] - ###################The variable is: SERVER.OLD_KEYSTORE_STATUS, value is: NOT_EXIST\n12:02:42,629 DEBUG [main] - ###################The variable is: SERVER.KEYSTORE_STATUS, value is: NOT_EXIST\n12:02:42,629 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - *******************************end of action********************************\n12:02:42,633 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - Start to resolve variable\n12:02:42,633 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - Start to check condition\n12:02:42,633 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - Start to setup\n12:02:42,633 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - *******************Start action com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs***********************\n12:02:42,633 DEBUG [main] - ###################The variable is: COMMON.EXIST_AEK_FILES, value is: lockbox.lb\n12:02:42,633 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - *******************************end of action********************************\n12:02:42,634 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - Start to resolve variable\n12:02:42,634 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - Start to check condition\n12:02:42,634 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - Start to setup\n12:02:42,634 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - *******************Start action com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation***********************\n12:02:42,634 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - The installer will validate AEK\/Lockbox fileds.\n12:02:42,637 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - *******************************end of action********************************\n12:02:42,638 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - Start to resolve variable\n12:02:42,639 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - Start to check condition\n12:02:42,639 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - Start to setup\n12:02:42,639 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - *******************Start action com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore***********************\n12:02:42,639 DEBUG [main] - ###################The variable is: SERVER.KEYSTORE_FILE, value is: $DOCUMENTUM\/dba\/secure\/CSaek\n12:02:42,642 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - Upgrade docbase use keep aek unchanged in lockbox, will not re-create it\n12:02:42,642 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerCreateKeyStore - *******************************end of action********************************\n12:02:42,643 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Start to resolve variable\n12:02:42,644 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Start to check condition\n12:02:42,644 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Start to setup\n12:02:42,644 DEBUG [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - *******************Start action com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase***********************\n12:02:42,644 DEBUG [main] - Before running the following command, the class path is \/tmp\/install.dir.13366\/InstallerData:\/tmp\/install.dir.13366\/InstallerData\/installer.zip:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:\n12:02:42,644 DEBUG [main] - Before running the following command, the path is \/usr\/xpg4\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$DM_HOME\/bin:$ORACLE_HOME\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/dmadmin\/.local\/bin:\/home\/dmadmin\/bin:\/bin:\/usr\/bin:\/sbin:\/usr\/sbin:\/usr\/local\/bin\n12:02:44,112 DEBUG [main] - Command line is \/bin\/sh -c \"dm_crypto_create -check -noprompt -passphrase ****** -lockbox lockbox.lb -keyname CSaek > \/tmp\/731965.tmp\/dm_crypto_create_check362671.log\" and start in $DM_HOME\/bin. The return code of this command is 3\n12:02:44,113 DEBUG [main] - After running the above command, the class path is \/tmp\/install.dir.13366\/InstallerData:\/tmp\/install.dir.13366\/InstallerData\/installer.zip:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:$DM_HOME\/dctm-server.jar:$DOCUMENTUM\/dctm.jar:$DOCUMENTUM\/config:$DM_HOME\/bin:\n12:02:44,113 DEBUG [main] - After running the above command, the path is \/usr\/xpg4\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$JAVA_HOME\/bin:$DM_HOME\/bin:$DOCUMENTUM\/dba:$ORACLE_HOME\/bin:$DM_HOME\/bin:$ORACLE_HOME\/bin:\/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/home\/dmadmin\/.local\/bin:\/home\/dmadmin\/bin:\/bin:\/usr\/bin:\/sbin:\/usr\/sbin:\/usr\/local\/bin\n12:02:44,165 DEBUG [main] com.documentum.install.shared.common.error.DiException - Check AEK key passphrase failed\n12:02:44,166 ERROR [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Check AEK key passphrase failed\ncom.documentum.install.shared.common.error.DiException: Check AEK key passphrase failed\n at com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase.executeValidation(DiWAServerValidateLockboxPassphrase.java:133)\n at com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase.setup(DiWAServerValidateLockboxPassphrase.java:115)\n at com.documentum.install.shared.installanywhere.actions.InstallWizardAction.install(InstallWizardAction.java:73)\n at com.zerog.ia.installer.actions.CustomAction.installSelf(Unknown Source)\n ...\n[dmadmin@stg-cs logs]$<\/pre>\n<\/p>\n
As you can see above, the first strange thing is that the installer has a “return code of this command is 3<\/em>” while trying to check the “old AEK key status<\/em>“. If you look at the command that is printed in the DEBUG logs, you can see this: $DM_HOME\/bin\/dm_crypto_create -check -noprompt -lockbox lockbox.lb -keyname CSaek<\/em>. This is actually correct if you are using the default AEK passphrase but it’s not if you are using a custom passphrase… If you look a little bit lower in the DEBUG logs, you can see the correct command used later to check the AEK: dm_crypto_create -check -noprompt -passphrase ******<\/strong> -lockbox lockbox.lb -keyname CSaek<\/em>. Maybe it’s just a logging topic where the passphrase was completely removed from the first command while it was replaced by “******<\/em>” on the second command? Anyway, I found that interesting to note…<\/p>\n
<\/p>\n
Since I do not have access to the source code, I needed OpenText to confirm if this was potentially the issue or if it was the first thing I mentioned earlier related to the properties in the CS Upgrade silent properties file. I opened the OpenText Service Request #4436375<\/strong> and after two months, I got the feedback that the lockbox upgrade can only be done during the CS binaries upgrade. This doesn’t make any sense to me. As I said previously, the lockbox is related to a repository, it has nothing to do with the binaries. In addition, you already need to provide lockbox details during the repository upgrade so why doing this in the binaries upgrade which therefore needs you to enter the passwords on yet another silent properties file? An enhancement request would have been possible but as you probably know, Documentum 16.7 removed the support for the Lockbox so it does only impact Documentum 16.4 and this will therefore not change anymore. I guess I will stick with my workaround in our custom silent script package so that the lockbox if upgraded, if needed (present in 7.x & target in 16.4), just before running the repository upgrade. This is all done automatically in our Ansible playbooks so that we can just execute one command and we have the upgrade done from A to Z, successfully.<\/p>\n","protected":false},"excerpt":{"rendered":"
A couple months ago, I was working on an upgrade project from Documentum 7.x to 16.4. During this upgrade, I faced a few issues so I will try to write some blogs about all that in the coming weeks, starting today with an alleged “corrupt” Lockbox. This upgrade was part of a migration as well […]<\/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":[1621,1925,129,916,219],"type_dbi":[],"class_list":["post-14040","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-16-4","tag-7-x","tag-documentum","tag-lockbox","tag-upgrade"],"acf":[],"yoast_head":"\n
Documentum Upgrade - Corrupt Lockbox with CS 16.4 - 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-corrupt-lockbox-with-cs-16-4\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum Upgrade - Corrupt Lockbox with CS 16.4\" \/>\n<meta property=\"og:description\" content=\"A couple months ago, I was working on an upgrade project from Documentum 7.x to 16.4. During this upgrade, I faced a few issues so I will try to write some blogs about all that in the coming weeks, starting today with an alleged “corrupt” Lockbox. This upgrade was part of a migration as well […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-05-03T08:00:30+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=\"14 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-corrupt-lockbox-with-cs-16-4\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum Upgrade – Corrupt Lockbox with CS 16.4\",\"datePublished\":\"2020-05-03T08:00:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\"},\"wordCount\":1048,\"commentCount\":0,\"keywords\":[\"16.4\",\"7.x\",\"Documentum\",\"Lockbox\",\"Upgrade\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\",\"name\":\"Documentum Upgrade - Corrupt Lockbox with CS 16.4 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2020-05-03T08:00:30+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum Upgrade – Corrupt Lockbox with CS 16.4\"}]},{\"@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 & 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 - Corrupt Lockbox with CS 16.4 - 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-corrupt-lockbox-with-cs-16-4\/","og_locale":"en_US","og_type":"article","og_title":"Documentum Upgrade - Corrupt Lockbox with CS 16.4","og_description":"A couple months ago, I was working on an upgrade project from Documentum 7.x to 16.4. During this upgrade, I faced a few issues so I will try to write some blogs about all that in the coming weeks, starting today with an alleged “corrupt” Lockbox. This upgrade was part of a migration as well […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/","og_site_name":"dbi Blog","article_published_time":"2020-05-03T08:00:30+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum Upgrade – Corrupt Lockbox with CS 16.4","datePublished":"2020-05-03T08:00:30+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/"},"wordCount":1048,"commentCount":0,"keywords":["16.4","7.x","Documentum","Lockbox","Upgrade"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/","name":"Documentum Upgrade - Corrupt Lockbox with CS 16.4 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2020-05-03T08:00:30+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-corrupt-lockbox-with-cs-16-4\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum Upgrade – Corrupt Lockbox with CS 16.4"}]},{"@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 & 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\/14040","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=14040"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/14040\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=14040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=14040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=14040"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=14040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}