{"id":13173,"date":"2019-12-12T18:59:15","date_gmt":"2019-12-12T17:59:15","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/"},"modified":"2019-12-12T18:59:15","modified_gmt":"2019-12-12T17:59:15","slug":"documentum-migrationutil-5-change-installation-owner","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/","title":{"rendered":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner"},"content":{"rendered":"<p>The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. It is originally determined when the server is installed, in fact, it is the logged-in user that performed the Documentum installation.<!--more--> Of course, it is preferable to install Documentum and never change the installation owner. However, sometimes company policy change and dictates that the original installation must be changed, for example, the user name does not conform to a new naming policy.<\/p>\n<p>This blog is the last one of the MigrationUtil blogs serie (please find links of other blogs below), I will show how to change the Installation Owner using the MigrationUtil. If you want to change only the password please read this <a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-change-password-3-cs-installation-owner\/\" rel=\"noopener noreferrer\" target=\"_blank\">blog<\/a>.<\/p>\n<ul>\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-1-change-docbase-id\/\" rel=\"noopener noreferrer\" target=\"_blank\">Documentum \u2013 MigrationUtil \u2013 1 \u2013 Change Docbase ID<\/a><\/li>\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-2-change-docbase-name\/\" rel=\"noopener noreferrer\" target=\"_blank\">Documentum \u2013 MigrationUtil \u2013 2 \u2013 Change Docbase Name<\/a><\/li>\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-3-change-server-config-name\/\" rel=\"noopener noreferrer\" target=\"_blank\">Documentum \u2013 MigrationUtil \u2013 3 \u2013 Change Server Config Name<\/a><\/li>\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-4-change-host-name\/\" rel=\"noopener noreferrer\" target=\"_blank\">Documentum \u2013 MigrationUtil \u2013 4 \u2013 Change Host Name<\/a><\/li>\n<\/ul>\n<p>The installation owner user is important at the operating system and in the Docbase\/Content Server level, it is given the following privileges:<\/p>\n<ul>\n<li><strong>Operating System<\/strong>:<br \/>\n\t\t&#8211; Rights to start Documentum Services such as Docbase, Docbroker, Java Method Server and other installed Documentum products.<br \/>\n        &#8211; Permission to change the Content Server configuration (i.e. upgrade, create, and delete docbases).<br \/>\n        &#8211; Folder level permission to view data, configuration, and many log files located under the DOCUMENTUM_HOME directory.<\/li>\n<li><strong>Docbase and Content Server<\/strong>:<br \/>\n\t\t&#8211; Superuser and System Administrator rights.<br \/>\n\t\t&#8211; Set as the r_install_owner value in the dm_server_config object.<br \/>\n\t\t&#8211; Set as the operating system user to run several Administrative jobs.<\/li>\n<\/ul>\n<p>As you can deduce, the change of the installer owner is not a minor change within Documentum, so it is very critical. That&#8217;s why you have to prepare very well this operation and determine the best approach to execute it. <\/p>\n<p>Below two change levels to be done:<\/p>\n<ul>\n<li><strong>OS Level change<\/strong>:<br \/>\n\t\t&#8211; Create the new install owner at the operating system level, it should correspond to the <strong>user_os_name<\/strong> of the new docbase user.<\/li>\n<li><strong>Docbase level change<\/strong>:<br \/>\n\t\t&#8211; Create a new user in the docbase to be the installation owner and reassign the previous installation owner\u2019s objects to the new user. The MigrationUtil will be able to this part.<\/li>\n<\/ul>\n<h1>Preparation<\/h1>\n<h2>Before any change<\/h2>\n<ul>\n<li><strong>Clean the environment<\/strong>:<br \/>\n\t\t&#8211; <strong>Run the Consistency Checker job<\/strong>: The report gives you a list of bad data within your system. Cleaning up inconsistent data before making the change will speed up the process.<br \/>\n\t\t&#8211; <strong>Purge all old log files<\/strong>: Changing the installation owner requires updating permissions on Documentum data and log files. The purge will reduce work on &#8220;unneeded data&#8221; and will greatly speed up the process.<\/li>\n<li><strong>Back up<\/strong>:<br \/>\n\t\t&#8211; Back up all the impacted environment before performing any major change within Documentum (Content Server files and the Database).<\/li>\n<\/ul>\n<h2>Create new user &#8211; OS Level<\/h2>\n<p>Add the new installation user at the OS Level, in the same group as the actual installation user :<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@vmtestdctm01 ~]# useradd -g 1004 dmdocbase1\n[root@vmtestdctm01 ~]# passwd dmdocbase1\nChanging password for user dmdocbase1.\nNew password: \nRetype new password: \npasswd: all authentication tokens updated successfully.\n[root@vmtestdctm01 ~]# \n<\/pre>\n<p>To know the group of actual installation user:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@vmtestdctm01 ~]# cat \/etc\/passwd\n...\ndmadmin:x:1002:1004::\/home\/dmadmin:\/bin\/bash\n<\/pre>\n<h2>Create new user &#8211; Docbase Level<\/h2>\n<p>You need to create the user in all docbases, using below dql query :<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\nCREATE dm_user OBJECT\nSET user_name = 'dmdocbase1',\nSET user_password = 'install164',\nSET user_login_name = 'dmdocbase1',\nSET user_address = 'dmdocbase1@dbi-services.com',\nSET description = 'This User is the owner of docbase1',\nSET user_os_name = 'dmdocbase1',\nSET client_capability = 8,\nSET user_privileges = 16,\nSET user_xprivileges = 56,\nSET user_source = 'inline password'\n<\/pre>\n<p>Result:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\nobject_created  \n----------------\n1101e24080000500\n<\/pre>\n<h2>Configure the MigrationUtil<\/h2>\n<p>Adapt the MigrationUtil configuration file like below:<\/p>\n<pre class=\"brush: xml; title: ; notranslate\" title=\"\">\n&#x5B;dmadmin@vmtestdctm01 ~]$ cat $DM_HOME\/install\/external_apps\/MigrationUtil\/config.xml \n&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;\n&lt;!DOCTYPE properties SYSTEM &quot;http:\/\/java.sun.com\/dtd\/properties.dtd&quot;&gt;\n&lt;properties&gt;\n&lt;comment&gt;Database connection details&lt;\/comment&gt;\n&lt;entry key=&quot;dbms&quot;&gt;oracle&lt;\/entry&gt; &lt;!-- This would be either sqlserver, oracle, db2 or postgres --&gt;\n&lt;entry key=&quot;tgt_database_server&quot;&gt;vmtestdctm01&lt;\/entry&gt; &lt;!-- Database Server host or IP --&gt;\n&lt;entry key=&quot;port_number&quot;&gt;1521&lt;\/entry&gt; &lt;!-- Database port number --&gt;\n&lt;entry key=&quot;InstallOwnerPassword&quot;&gt;install164&lt;\/entry&gt;\n&lt;entry key=&quot;isRCS&quot;&gt;no&lt;\/entry&gt;    &lt;!-- set it to yes, when running the utility on secondary CS --&gt;\n\n&lt;!-- &lt;comment&gt;List of docbases in the machine&lt;\/comment&gt; --&gt;\n&lt;entry key=&quot;DocbaseName.1&quot;&gt;docbase1&lt;\/entry&gt;\n\n&lt;!-- &lt;comment&gt;docbase owner password&lt;\/comment&gt; --&gt;\n&lt;entry key=&quot;DocbasePassword.1&quot;&gt;install164&lt;\/entry&gt;\n\n...\n\n&lt;entry key=&quot;ChangeInstallOwner&quot;&gt;yes&lt;\/entry&gt;\n&lt;entry key=&quot;InstallOwner&quot;&gt;dmadmin&lt;\/entry&gt;\n&lt;entry key=&quot;NewInstallOwner&quot;&gt;dmdocbase1&lt;\/entry&gt;\n&lt;entry key=&quot;NewInstallOwnerPassword&quot;&gt;install164&lt;\/entry&gt;\n...\n<\/pre>\n<h1>Migration<\/h1>\n<h2>Stop Docbase(s) and Docbroker(s)<\/h2>\n<p>Before you execute the migration you have to stop the docbase(s) and the docbroker(s).<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n$DOCUMENTUM\/dba\/dm_shutdown_Docbase1\n$DOCUMENTUM\/dba\/dm_stop_DocBroker\n<\/pre>\n<h2>Execute the migration script<\/h2>\n<p>Once every thing stopped, you can execute the migration script:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[dmadmin@vmtestdctm01 ~]$ $DM_HOME\/install\/external_apps\/MigrationUtil\/MigrationUtil.sh\n\nWelcome... Migration Utility invoked.\n \nSkipping Docbase ID Changes...\n\nSkipping Host Name Change...\n\nChanging Install Owner...\nCreated new log File: \/app\/dctm\/product\/16.4\/product\/16.4\/install\/external_apps\/MigrationUtil\/MigrationUtilLogs\/InstallOwnerChange.log\nFinished changing Install Owner...Please check log file for more details\/errors\nFinished changing Install Owner...\n\nSkipping Server Name Change...\n\nSkipping Docbase Name Change...\n\nSkipping Docker Seamless Upgrade scenario...\n\nMigration Utility completed.\n<\/pre>\n<p>Have a look on the Migration log:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[dmadmin@vmtestdctm01 ~]$ cat \/app\/dctm\/product\/16.4\/product\/16.4\/install\/external_apps\/MigrationUtil\/MigrationUtilLogs\/InstallOwnerChange.log\nStart: 2019-12-12 05:14:37.191\nChanging Install Owner\n=====================\nInstallOwner: dmadmin\nNew InstallOwner: dmdocbase1\nChanging InstallOwner for docbase: Docbase1\nRetrieving server.ini path for docbase: Docbase1\nFound path: \/app\/dctm\/product\/16.4\/dba\/config\/Docbase1\/server.ini\n\nDatabase Details:\nDatabase Vendor:oracle\nDatabase Name:dctmdb.local\nDatabse User:Docbase1\nDatabase URL:jdbc:oracle:thin:@vmtestdctm01:1521\/dctmdb.local\nSuccessfully connected to database....\n\nProcessing Database Changes for docbase: Docbase1\nCreated database backup File '\/app\/dctm\/product\/16.4\/product\/16.4\/install\/external_apps\/MigrationUtil\/MigrationUtilLogs\/InstallOwnerChange_Docbase1_DatabaseRestore.sql'\nProcessing _s table...\nselect r_object_id,object_name from dm_sysobject_s where object_name = 'dmadmin'\nupdate dm_sysobject_s set object_name = 'dmdocbase1' where r_object_id = '0c01e24080000105'\nselect r_object_id,r_install_owner from dm_server_config_s where r_install_owner = 'dmadmin'\nupdate dm_server_config_s set r_install_owner = 'dmdocbase1' where r_object_id = '3d01e24080000102'\nselect r_object_id,user_name from dm_user_s where user_name = 'dmadmin'\nupdate dm_user_s set user_name = 'dmdocbase1' where r_object_id = '1101e24080000102'\nselect r_object_id,user_os_name from dm_user_s where user_os_name = 'dmadmin'\nupdate dm_user_s set user_os_name = 'dmdocbase1' where r_object_id = '1101e24080000102'\n...\nupdate dm_workflow_r set r_last_performer = 'dmdocbase1' where r_last_performer = 'dmadmin'\nupdate dm_workflow_s set r_creator_name = 'dmdocbase1' where r_creator_name = 'dmadmin'\nupdate dm_workflow_s set supervisor_name = 'dmdocbase1' where supervisor_name = 'dmadmin'\nSuccessfully updated database values...\nCommitting all database operations...\nFinished processing database changes for docbase: Docbase1\n\nProcessing server.ini changes for docbase: Docbase1\nBacked up '\/app\/dctm\/product\/16.4\/dba\/config\/Docbase1\/server.ini' to '\/app\/dctm\/product\/16.4\/dba\/config\/Docbase1\/server.ini_install_dmadmin.backup'\nUpdated server.ini file:\/app\/dctm\/product\/16.4\/dba\/config\/Docbase1\/server.ini\nUpdating acs.properties for docbase: Docbase1\nBacked up '\/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/configs.jar\/config\/acs.properties' to '\/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/configs.jar\/config\/acs.properties_install_dmadmin.backup'\nUpdated acs.properties: \/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/configs.jar\/config\/acs.properties\nBacked up '\/app\/dctm\/product\/16.4\/dba\/dm_shutdown_Docbase1' to '\/app\/dctm\/product\/16.4\/dba\/dm_shutdown_Docbase1_install_dmadmin.backup'\nUpdated shutdown script: \/app\/dctm\/product\/16.4\/dba\/dm_shutdown_Docbase1\n...\nProcessing Services File Changes...\nBacked up '\/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/DmMethods.war\/WEB-INF\/web.xml' to '\/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/DmMethods.war\/WEB-INF\/web.xml_install_dmadmin.backup'\nUpdated web.xml: \/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/DmMethods.war\/WEB-INF\/web.xml\nWARNING...File \/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/bpm.ear\/bpm.war\/WEB-INF\/web.xml doesn't exist\nNo need to update method server startup script: \/app\/dctm\/product\/16.4\/wildfly9.0.1\/server\/startMethodServer.sh\nFinished processing File changes...\n\nFinished changing Install Owner...\nEnd: 2019-12-12 05:14:39.815\n<\/pre>\n<h2>Change permissions<\/h2>\n<p>Change the permissions of all folders and files under DOCUMENTUM_HOME directory, if your content storage directories are not located under the DOCUMENTUM_HOME directory, change the permissions on each content storage directory as well.<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@vmtestdctm01 ~]$ chown -R dmdocbase1 \/app\/dctm\n<\/pre>\n<h2>Start Docbase(s) and Docbroker(s)<\/h2>\n<p>Start the Docbroker and the docbase:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n$DOCUMENTUM\/dba\/dba\/dm_launch_DocBroker\n$DOCUMENTUM\/dba\/dba\/dm_start_Docbase1\n<\/pre>\n<h1>Post Migration<\/h1>\n<p>Check the docbase logs:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n...\n2019-12-12T05:30:09.982774      13301[13301]    0000000000000000        [DM_MQ_I_DAEMON_START]info:  \"Message queue daemon (pid : 13570, session 0101e24080000456) is started sucessfully.\"\n2019-12-12T05:30:20.255917      13569[13569]    0101e24080000003        [DM_DOCBROKER_I_PROJECTING]info:  \"Sending information to Docbroker located on host (vmtestdctm01) with port (1490).  Information: (Config(Docbase1), Proximity(1), Status(Open), Dormancy Status(Active)).\"\nWed Dec 12 05:30:32 2019 [INFORMATION] [AGENTEXEC 13628] Detected during program initialization: Version: 16.4.0000.0248  Linux64\nWed Dec 12 05:30:35 2019 [INFORMATION] [AGENTEXEC 13628] Detected during program initialization: Agent Exec connected to server Docbase1:  [DM_SESSION_I_SESSION_START]info:  \"Session 0101e24080000500 started for user dmdocbase1.\"\n<\/pre>\n<p>Try to connect with old installation owner to Docbase1 throw idql:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n...\nConnecting to Server using docbase Docbase1\nCould not connect\n[DM_SESSION_E_AUTH_FAIL]error:  \"Authentication failed for user dmadmin with docbase Docbase1.\"\n<\/pre>\n<p>This is the expected behavior, the old installation owner is no more active.<\/p>\n<p>The environment I used to make this test is a very simple one ( with only one Docbase, no HA, no FullText, aso) and created only for this purpose. It worked fine on my environment, but be careful if you have a more complex environment!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. It is originally determined when the server is installed, in fact, it is the logged-in user that performed the Documentum installation.<\/p>\n","protected":false},"author":46,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[1213,129,15],"type_dbi":[],"class_list":["post-13173","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-docbase","tag-documentum","tag-migration"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner - 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-migrationutil-5-change-installation-owner\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner\" \/>\n<meta property=\"og:description\" content=\"The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. It is originally determined when the server is installed, in fact, it is the logged-in user that performed the Documentum installation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-12-12T17:59:15+00:00\" \/>\n<meta name=\"author\" content=\"David Diab\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Diab\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 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-migrationutil-5-change-installation-owner\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\"},\"author\":{\"name\":\"David Diab\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86\"},\"headline\":\"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner\",\"datePublished\":\"2019-12-12T17:59:15+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\"},\"wordCount\":951,\"commentCount\":0,\"keywords\":[\"docbase\",\"Documentum\",\"Migration\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\",\"name\":\"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-12-12T17:59:15+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner\"}]},{\"@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\/deb907c3360cacdc6c7df54b4bac3c86\",\"name\":\"David Diab\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"caption\":\"David Diab\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/david-diab\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner - 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-migrationutil-5-change-installation-owner\/","og_locale":"en_US","og_type":"article","og_title":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner","og_description":"The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. It is originally determined when the server is installed, in fact, it is the logged-in user that performed the Documentum installation.","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/","og_site_name":"dbi Blog","article_published_time":"2019-12-12T17:59:15+00:00","author":"David Diab","twitter_card":"summary_large_image","twitter_misc":{"Written by":"David Diab","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/"},"author":{"name":"David Diab","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86"},"headline":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner","datePublished":"2019-12-12T17:59:15+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/"},"wordCount":951,"commentCount":0,"keywords":["docbase","Documentum","Migration"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/","name":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-12-12T17:59:15+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-migrationutil-5-change-installation-owner\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum \u2013 MigrationUtil \u2013 5 \u2013 Change Installation Owner"}]},{"@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\/deb907c3360cacdc6c7df54b4bac3c86","name":"David Diab","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","caption":"David Diab"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/david-diab\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13173","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\/46"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=13173"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13173\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13173"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}