{"id":40188,"date":"2025-08-27T20:16:00","date_gmt":"2025-08-27T18:16:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=40188"},"modified":"2025-10-25T08:12:08","modified_gmt":"2025-10-25T06:12:08","slug":"dctm-oracle-db-permissions-on-recent-versions","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/","title":{"rendered":"Dctm – Oracle DB permissions on recent versions"},"content":{"rendered":"\n

If you have been running Documentum on Oracle in the past, you might have noticed that recent versions of Dctm requires more Database permissions to be able to perform an install\/upgrade. This blog will just be a quick one to show what I used to request for DB permissions for older versions of Documentum as well as what happen if you don’t have the needed permissions on the latest versions. So, let’s get right into it.<\/p>\n\n\n\n

First of all, when working on big environments\/customers, it is pretty rare to get full access to the Database. Therefore, I’ve always created the tablespace and repository owner accounts upfront, with the needed permissions, before starting a new Documentum installation that would then use this dedicated account. If you aren’t in this case, then I guess this blog isn’t very relevant, since the Documentum installer can create the account with the needed permissions by itself (since you provide it with the DB SYSADMIN account). Please also note that using the Dctm installer will grant unlimited tablespace usage to the repository owner, which DBAs don’t really like (and it’s not really required if you do things properly\u2026).<\/p>\n\n\n\n

For as long as I recall, these have been the permissions that I requested\/granted on the repository owner account ( being the dm_dbo account name) for Oracle Databases:<\/p>\n\n\n

\nGRANT CONNECT TO <REPO_NAME>;\nGRANT RESOURCE TO <REPO_NAME>;\nGRANT CREATE SESSION TO <REPO_NAME>;\nGRANT ALTER SESSION TO <REPO_NAME>;\nGRANT CREATE TABLE TO <REPO_NAME>;\nGRANT CREATE CLUSTER TO <REPO_NAME>;\nGRANT CREATE SYNONYM TO <REPO_NAME>;\nGRANT CREATE VIEW TO <REPO_NAME>;\nGRANT CREATE SEQUENCE TO <REPO_NAME>;\nGRANT CREATE DATABASE LINK TO <REPO_NAME>;\nGRANT CREATE PROCEDURE TO <REPO_NAME>;\nGRANT CREATE TRIGGER TO <REPO_NAME>;\nGRANT CREATE MATERIALIZED VIEW TO <REPO_NAME>;\nGRANT CREATE JOB TO <REPO_NAME>;\n<\/pre><\/div>\n\n\n
The documentation does not really give you much details about the exact requirements and the content of the doc itself hasn’t changed much (at all?) either. However, with the above list, you usually had enough permissions to install\/run\/upgrade Documentum as well as perform usual administrative tasks (like create a database link to populate some custom tables with external data (ODBC?) or managing some archiving\/cleanup).<\/p>\n\n\n\n
With recent versions of Documentum though, trying to perform an upgrade, for example from 20.x to 23.x, if you had the above DB permissions only, then the upgrade (or OOTB installation) would fail with the Repository not being able to start. The Repository logs would show something like:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ cat $DOCUMENTUM\/dba\/log\/<REPO_NAME>.log\n\n    OpenText Documentum Content Server (version 23.4.0000.0143  Linux64.Oracle)\n    Copyright (c) 2023. OpenText Corporation\n    All rights reserved.\n\n2024-06-25T14:06:31.324462      13781[13781]    0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> attempting to open"\n\n2024-06-25T14:06:31.324558      13781[13781]    0000000000000000        [DM_SERVER_I_START_KEY_STORAGE_MODE]info:  "Docbase <REPO_NAME> is using database for cryptographic key storage"\n\n2024-06-25T14:06:31.324581      13781[13781]    0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> process identity: user(dmadmin)"\n\n2024-06-25T14:06:31.701344      13781[13781]    0000000000000000        Database Session is shutting down due to (Pq)\n2024-06-25T14:06:31.701461      13781[13781]    0000000000000000        [DM_SERVER_I_START_ID]info:  "Docbase <REPO_NAME> was not successfully opened. Docbase id: (1000001)"\n\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
The above message “Database Session is shutting down due to (XX)” can be caused by missing\/wrong DB details (like username), but it can also be caused by missing permissions on the DB Repository owner account. The problem is that this can happen even if you made sure to execute the “$DM_HOME\/bin\/dmdbtest” utility just before the Repository install\/upgrade. This utility is(was) rather good, to test the DB connection and to make sure that you have(had) enough permissions. However, in this specific case, it doesn’t detect the issue, and it just completes successfully:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ ### Execution with initial DB permissions\n[dmadmin@cs-0 ~]$ $DM_HOME\/bin\/dmdbtest -S<TNS_ALIAS> -U<USER_NAME> -P<PASSWORD>\nDatabase successfully opened.\nTest table successfully created.\nTest view successfully created.\nTest index successfully created.\nInsert into table successfully done.\nIndex successfully dropped.\nView successfully dropped.\nDatabase case sensitivity test successfully past.\nTable successfully dropped.\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
Starting on Dctm 22.x (it was apparently around that time), some additional permissions are definitively required, but this utility either cannot check that, or it wasn’t updated for that (I let you have your own opinion on that matter ;)). To be able to install\/upgrade your environment, you will need these additional permissions now (the first one for “SELECT_CATALOG_ROLE” being the most important):<\/p>\n\n\n
\nGRANT SELECT_CATALOG_ROLE TO <REPO_NAME>;\nGRANT CREATE TYPE TO <REPO_NAME>;\nGRANT CREATE INDEXTYPE TO <REPO_NAME>;\nGRANT CREATE ANY INDEX TO <REPO_NAME>;\n<\/pre><\/div>\n\n\n
After a successful grant, if you would like to check the permissions of the DB account, you can execute these commands:<\/p>\n\n\n\n
    \n
  • SELECT USERNAME, GRANTED_ROLE FROM USER_ROLE_PRIVS;\n
      \n
    • Should display the SELECT_CATALOG_ROLE role<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • SELECT USERNAME, PRIVILEGE FROM USER_SYS_PRIVS;\n
        \n
      • Should display the other three privileges<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
        Note: yes, the documentation has been mentioning the Select Catalog Role as being required for a very long time and it’s part of the Dctm binaries since Aug-2001 (24y ago\u2026) but it wasn’t really required so far, since I installed dozens (hundreds?) of Dctm environment without that role on Oracle (it’s a sensitive one that contains a LOT of accesses), and I never had any issues before, as I recall. But in recent versions, something changed, and we now need more permissions for certain.<\/p>\n\n\n\n
        To check if you are hitting the same issue, you can try to start your repository with SQLTRACE enabled (here I’m showing multiple traces parameters but the 1st one is the one in question):<\/p>\n\n\n
        \n[dmadmin@cs-0 ~]$ $DOCUMENTUM\/dba\/dm_start_<REPO_NAME> -osqltrace -orpctrace -otrace_authentication -otrace_complete_launch -otrace_method_server -otrace_http_post -ohttp_post -oticket_trace -odocbroker_trace -onettrace -onet_ip_addr\nstarting Documentum server for repository: [<REPO_NAME>]\nwith server log: [$DOCUMENTUM\/dba\/log\/<REPO_NAME>.log]\nserver pid: 33822\n[dmadmin@cs-0 ~]$ \n[dmadmin@cs-0 ~]$ cat \/app\/dctm\/server\/dba\/log\/<REPO_NAME>.log\n\n    OpenText Documentum Content Server (version 23.4.0000.0143  Linux64.Oracle)\n    Copyright (c) 2023. OpenText Corporation\n    All rights reserved.\n\n2024-06-25T14:10:52.030355      33822[33822]    0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> attempting to open"\n\n2024-06-25T14:10:52.030458      33822[33822]    0000000000000000        [DM_SERVER_I_TRACING_ENABLED_GLOBAL]info:  "Tracing type: 'sqltrace'"\n\n2024-06-25T14:10:52.030518      33822[33822]    0000000000000000        [DM_SERVER_I_TRACING_ENABLED_GLOBAL]info:  "Tracing type: 'rpctrace'"\n\n2024-06-25T14:10:52.031874      33822[33822]    0000000000000000        [DM_SERVER_I_START_KEY_STORAGE_MODE]info:  "Docbase <REPO_NAME> is using database for cryptographic key storage"\n\n2024-06-25T14:10:52.033437      33822[33822]    0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> process identity: user(dmadmin)"\n\n2024-06-25T14:10:52.034730      33822[33822]    0000000000000000        In disArmSIGPIPEForDBConnection: prev_disp = 0x0\n\n2024-06-25T14:10:52.099466      33822[33822]    0000000000000000        [SQL]   -1      LOGON   0.0578370000\n2024-06-25T14:10:52.099583      33822[33822]    0000000000000000        [SQL]   -1      select username from v$session where audsid = userenv('sessionid')\n2024-06-25T14:10:52.103138      33822[33822]    0000000000000000        [SQL]   -1      EXEC    0.0023280000\n2024-06-25T14:10:52.103172      33822[33822]    0000000000000000        In armSIGPIPEForDBConnection: SIGPIPE is not Armed\n\n2024-06-25T14:10:52.103212      33822[33822]    0000000000000000        [SQL]   -1      select username from v$session where audsid = userenv('sessionid')\n2024-06-25T14:10:52.105888      33822[33822]    0000000000000000        [SQL]   -1      EXEC    0.0014200000\n2024-06-25T14:10:52.105913      33822[33822]    0000000000000000        Database Session is shutting down due to (-)\n2024-06-25T14:10:52.105946      33822[33822]    0000000000000000        [DM_SERVER_I_START_ID]info:  "Docbase <REPO_NAME> was not successfully opened. Docbase id: (1000841)"\n\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
        As you can see above, it’s closing the DB session after trying to access the v$session on Oracle, which is something granted by the SELECT_CATALOG_ROLE usually (along with thousands of other stuff).<\/p>\n\n\n\n
        In any cases, after adding the Repository owner account’s permissions on the Database, if you try to trigger the install\/upgrade again, it should work properly:<\/p>\n\n\n
        \n[dmadmin@cs-0 ~]$ cat $DOCUMENTUM\/dba\/log\/<REPO_NAME>.log\n\n    OpenText Documentum Content Server (version 23.4.0000.0143  Linux64.Oracle)\n    Copyright (c) 2023. OpenText Corporation\n    All rights reserved.\n\n2024-06-25T15:20:28.223973      6372[6372]      0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> attempting to open"\n\n2024-06-25T15:20:28.224045      6372[6372]      0000000000000000        [DM_SERVER_I_START_KEY_STORAGE_MODE]info:  "Docbase <REPO_NAME> is using database for cryptographic key storage"\n\n2024-06-25T15:20:28.224709      6372[6372]      0000000000000000        [DM_SERVER_I_START_SERVER]info:  "Docbase <REPO_NAME> process identity: user(dmadmin)"\n\n2024-06-25T15:20:29.048972      6372[6372]      0000000000000000        [DM_SESSION_I_INIT_BEGIN]info:  "Initialize Post Upgrade Processing."\n\n2024-06-25T15:20:29.050037      6372[6372]      0000000000000000        [DM_SESSION_I_INIT_BEGIN]info:  "Initialize Base Types."\n...\n<\/pre><\/div>\n\n\n
        <\/p>\n","protected":false},"excerpt":{"rendered":"
        If you have been running Documentum on Oracle in the past, you might have noticed that recent versions of Dctm requires more Database permissions to be able to perform an install\/upgrade. This blog will just be a quick one to show what I used to request for DB permissions for older versions of Documentum as […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[525,59],"tags":[2609,3658,96,1760,927,2601],"type_dbi":[],"class_list":["post-40188","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","category-oracle","tag-documentum-2","tag-grant","tag-oracle","tag-repository","tag-role","tag-upgrade-2"],"acf":[],"yoast_head":"\nDctm - Oracle DB permissions on recent versions - 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\/dctm-oracle-db-permissions-on-recent-versions\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dctm - Oracle DB permissions on recent versions\" \/>\n<meta property=\"og:description\" content=\"If you have been running Documentum on Oracle in the past, you might have noticed that recent versions of Dctm requires more Database permissions to be able to perform an install\/upgrade. This blog will just be a quick one to show what I used to request for DB permissions for older versions of Documentum as […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-08-27T18:16:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-25T06:12:08+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=\"4 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\/dctm-oracle-db-permissions-on-recent-versions\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Dctm – Oracle DB permissions on recent versions\",\"datePublished\":\"2025-08-27T18:16:00+00:00\",\"dateModified\":\"2025-10-25T06:12:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\"},\"wordCount\":753,\"commentCount\":0,\"keywords\":[\"Documentum\",\"GRANT\",\"Oracle\",\"repository\",\"role\",\"upgrade\"],\"articleSection\":[\"Enterprise content management\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\",\"name\":\"Dctm - Oracle DB permissions on recent versions - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2025-08-27T18:16:00+00:00\",\"dateModified\":\"2025-10-25T06:12:08+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Dctm – Oracle DB permissions on recent versions\"}]},{\"@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":"Dctm - Oracle DB permissions on recent versions - 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\/dctm-oracle-db-permissions-on-recent-versions\/","og_locale":"en_US","og_type":"article","og_title":"Dctm - Oracle DB permissions on recent versions","og_description":"If you have been running Documentum on Oracle in the past, you might have noticed that recent versions of Dctm requires more Database permissions to be able to perform an install\/upgrade. This blog will just be a quick one to show what I used to request for DB permissions for older versions of Documentum as […]","og_url":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/","og_site_name":"dbi Blog","article_published_time":"2025-08-27T18:16:00+00:00","article_modified_time":"2025-10-25T06:12:08+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Dctm – Oracle DB permissions on recent versions","datePublished":"2025-08-27T18:16:00+00:00","dateModified":"2025-10-25T06:12:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/"},"wordCount":753,"commentCount":0,"keywords":["Documentum","GRANT","Oracle","repository","role","upgrade"],"articleSection":["Enterprise content management","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/","url":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/","name":"Dctm - Oracle DB permissions on recent versions - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2025-08-27T18:16:00+00:00","dateModified":"2025-10-25T06:12:08+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-oracle-db-permissions-on-recent-versions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Dctm – Oracle DB permissions on recent versions"}]},{"@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\/40188","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=40188"}],"version-history":[{"count":2,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/40188\/revisions"}],"predecessor-version":[{"id":41214,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/40188\/revisions\/41214"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=40188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=40188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=40188"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=40188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}