{"id":42306,"date":"2026-01-01T15:41:00","date_gmt":"2026-01-01T14:41:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=42306"},"modified":"2026-01-01T10:41:51","modified_gmt":"2026-01-01T09:41:51","slug":"dctm-incorrect-r_object_id-reference-in-otds","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/","title":{"rendered":"Dctm – Incorrect r_object_id reference in OTDS"},"content":{"rendered":"\n

I recently faced another pretty interesting case with an incorrect r_object_id<\/em><\/strong> reference in OTDS. In a non-production (dev) Active Directory (Azure EntraID) that is used as source of truth for the users\/groups, it looked like there was an account which was a bit messed-up. By that, I mean that the mail address, user name and other fields from that account were actually using the values from another account, which was completely separate. That resulted in a bit of mess inside OTDS and inside the Documentum Resource used behind it.<\/p>\n\n\n\n

Dctm user not synchronized<\/h2>\n\n\n\n

The main problem was that at that customer, the Documentum “dm_user.user_name<\/em><\/strong>” is set to a custom “Display Name<\/em><\/strong>” value, which isn’t the default Display Name of the AD but a custom attribute generated\/filled with some logic behind. With OTDS, you can add some logic into the Resource through JavaScript, but you often still rely on the background AD to get correct details. For that specific account (USERID01<\/em><\/strong> below), that custom Display Name was set to the value from another account (USERID02<\/em><\/strong>). Because of that, OTDS mapped the user to a certain Documentum account. Later, the messed-up account was corrected but OTDS wasn’t able to recognize that the Dctm reference that it had stored was, then, incorrect and therefore it couldn’t update the account anymore.<\/p>\n\n\n\n

Initially, the Application Team reached out to me because they weren’t able to see a value for the “dm_user.user_global_unique_id<\/em><\/strong>” field (of USERID01<\/em><\/strong>). That parameter, when using OTDS, is supposed to contain the “oTObjectGUID<\/em><\/strong>” (by default mapped to AD objectGUID<\/em><\/strong>). So, I quickly checked inside the Documentum Repository to see if this account was synched or not, if there were duplicate accounts or some other evident issues:<\/p>\n\n\n

\n[dmadmin@cs-0 mop]$ iapi $DOCBASE_NAME -Udmadmin -Pxxx\n\n        OpenText Documentum iapi - Interactive API interface\n        Copyright (c) 2023. OpenText Corporation\n        All rights reserved.\n        Client Library Release 23.4.0000.0180\n\nConnecting to Server using docbase REPO01\n[DM_SESSION_I_SESSION_START]info:  "Session 010f123480c63b32 started for user dmadmin."\n\nConnected to OpenText Documentum Server running Release 23.4.0000.0143  Linux64.Oracle\nSession id is s0\nAPI> ?,c,select r_object_id, user_login_name, user_name from dm_user where upper(user_login_name) like '%USERID01%';\nr_object_id       user_login_name        user_name\n----------------  ---------------------  -----------------------------\n110f12348000c96b  USERID01               User Display Name 01\n\n(1 row affected)\n\nAPI> dump,c,110f12348000c96b\n...\nUSER ATTRIBUTES\n\n  user_name                       : User Display Name 01\n  user_os_name                    : USERID01\n  user_address                    : user01@domain.com\n  user_group_name                 :\n  user_privileges                 : 0\n  owner_def_permit                : 7\n  world_def_permit                : 3\n  group_def_permit                : 5\n  default_folder                  : \/Home\/User Display Name 01\n  user_db_name                    :\n  description                     :\n  acl_domain                      : User Display Name 01\n  acl_name                        : dm_450f12348000f652\n  user_os_domain                  :\n  home_docbase                    :\n  user_state                      : 0\n  client_capability               : 2\n  globally_managed                : F\n  user_delegation                 :\n  workflow_disabled               : F\n  alias_set_id                    : 0000000000000000\n  user_source                     : OTDS\n  user_ldap_dn                    :\n  user_xprivileges                : 32\n  failed_auth_attempt             : 0\n  user_admin                      :\n  user_global_unique_id           :\n  user_login_name                 : USERID01\n  user_login_domain               :\n  user_initials                   :\n  user_password                   : ****************\n  user_web_page                   :\n  first_failed_auth_utc_time      : nulldate\n  last_login_utc_time             : 1\/3\/2022 13:39:00\n  deactivated_utc_time            : nulldate\n  deactivated_ip_addr             :\n  restricted_folder_ids         []: <none>\n  root_log_dir                    :\n\nSYSTEM ATTRIBUTES\n\n  r_is_group                      : F\n  r_modify_date                   : 11\/6\/2025 07:12:07\n  r_has_events                    : F\n  r_object_id                     : 110f12348000c96b\n\nAPPLICATION ATTRIBUTES\n\n\nINTERNAL ATTRIBUTES\n\n  i_is_replica                    : F\n  i_vstamp                        : 13\n\nAPI> exit\nBye\n[dmadmin@cs-0 mop]$\n<\/pre><\/div>\n\n\n
As you can see above, the “user_global_unique_id<\/em><\/strong>” is empty and some other fields also confirmed that the OTDS synchronization wasn’t done \/ working. Based on the OTDS Resource configuration, there should have been a lot of changes to that account, which wasn’t the case here.<\/p>\n\n\n\n
OTDS user consolidation<\/h2>\n\n\n\n
Therefore, I tried to trigger a consolidation on the user itself from the OTDS UI, to see what the logs were saying:<\/p>\n\n\n
\nThread Id: 654,623      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Enter: update(ObjectClass: __ACCOUNT__, Attribute: {Name=__UID__, Value=[110f12348004510b]}, [Attribute: {Name=__TENANT__, Value=[]}, Attribute: {Name=user_os_name, Value=[]}, Attribute: {Name=AccountDisabled, Value=[false]}, Attribute: {Name=user_global_unique_id, Value=[9ibc9uqrfKafp\/K1LRb0og==]}, Attribute: {Name=user_rename_unlock_locked_obj, Value=[T]}, Attribute: {Name=client_capability, Value=[2]}, Attribute: {Name=user_login_domain, Value=[]}, Attribute: {Name=user_name, Value=[User Display Name 01]}, Attribute: {Name=user_ldap_dn, Value=[CN=USERID01,OU=Users,DC=domain,DC=com]}, Attribute: {Name=user_address, Value=[user01@domain.com]}, Attribute: {Name=user_login_name, Value=[USERID01]}, Attribute: {Name=user_xprivileges, Value=[32]}, Attribute: {Name=create_default_cabinet, Value=[F]}, Attribute: {Name=user_privileges, Value=[0]}, Attribute: {Name=__PARTITION__, Value=[PARTITION01]}, Attribute: {Name=__OTDS_UUID__, Value=[7748abe9-7a51-9d43-b6c4-13ba639481b5]}, Attribute: {Name=user_type, Value=[dm_user]}, Attribute: {Name=user_rename_enabled, Value=[T]}, Attribute: {Name=default_folder, Value=[\/Home\/User Display Name 01]}, Attribute: {Name=__NAME__, Value=[User Display Name 01]}], null)\nThread Id: 654,631      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000051b]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@68f2554c})\nThread Id: 654,634      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000051e]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@6fa3934d})\nThread Id: 654,635      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f123480007dd8]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@41d7fb29})\nThread Id: 654,637      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000451d]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@7a229867})\nThread Id: 654,638      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000451e]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@4e95620c})\nThread Id: 654,665      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Enter: update(ObjectClass: __ACCOUNT__, Attribute: {Name=__UID__, Value=[110f12348004510b]}, [Attribute: {Name=__TENANT__, Value=[]}, Attribute: {Name=user_os_name, Value=[]}, Attribute: {Name=AccountDisabled, Value=[false]}, Attribute: {Name=user_global_unique_id, Value=[9ibc9uqrfKafp\/K1LRb0og==]}, Attribute: {Name=user_rename_unlock_locked_obj, Value=[T]}, Attribute: {Name=client_capability, Value=[2]}, Attribute: {Name=user_login_domain, Value=[]}, Attribute: {Name=user_name, Value=[User Display Name 01]}, Attribute: {Name=user_ldap_dn, Value=[cn=USERID01,ou=users,dc=domain,dc=com]}, Attribute: {Name=user_address, Value=[user01@domain.com]}, Attribute: {Name=user_login_name, Value=[USERID01]}, Attribute: {Name=user_xprivileges, Value=[32]}, Attribute: {Name=create_default_cabinet, Value=[F]}, Attribute: {Name=user_privileges, Value=[0]}, Attribute: {Name=__PARTITION__, Value=[PARTITION01]}, Attribute: {Name=__OTDS_UUID__, Value=[7748abe9-7a51-9d43-b6c4-13ba639481b5]}, Attribute: {Name=user_type, Value=[dm_user]}, Attribute: {Name=user_rename_enabled, Value=[T]}, Attribute: {Name=default_folder, Value=[\/Home\/User Display Name 01]}, Attribute: {Name=__NAME__, Value=[User Display Name 01]}], null)\nThread Id: 654,623      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Exception:\ncom.opentext.otds.connectors.rest.HttpException: Error updating member: 400 Bad Request <!doctype html><html lang="en"><head><title>HTTP Status 400 \u2013 Bad Request<\/title><style type="text\/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}<\/style><\/head><body><h1>HTTP Status 400 \u2013 Bad Request<\/h1><\/body><\/html>\n        at com.opentext.otds.connectors.rest.RestSession.updateMember(RestSession.java:314)\n        at com.opentext.otds.connectors.rest.RestConnector$9.endOfAttributes(RestConnector.java:557)\n        at com.opentext.otds.connectors.rest.RestConnector$9.endOfAttributes(RestConnector.java:526)\n        at com.opentext.otds.connectors.rest.RestAttributeParser.parse(RestAttributeParser.java:29)\n        at com.opentext.otds.connectors.rest.RestConnector.updateMember(RestConnector.java:564)\n        ...\nThread Id: 654,635      Time: 11\/18\/25, 8:53 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Exception:\ncom.opentext.otds.connectors.rest.HttpException: Error adding group members: 404 Not Found <!doctype html><html lang="en"><head><title>HTTP Status 404 \u2013 Not Found<\/title><style type="text\/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}<\/style><\/head><body><h1>HTTP Status 404 \u2013 Not Found<\/h1><\/body><\/html>\n        at com.opentext.otds.connectors.rest.RestSession.addMembersToGroup(RestSession.java:387)\n        at com.opentext.otds.connectors.rest.RestConnector$3.endOfAttributes(RestConnector.java:222)\n        at com.opentext.otds.connectors.rest.RestConnector$3.endOfAttributes(RestConnector.java:172)\n        at com.opentext.otds.connectors.rest.RestAttributeParser.parse(RestAttributeParser.java:29)\n        ...\n<\/pre><\/div>\n\n\n
So OTDS Consolidation ends-up with “400 Bad Request<\/em><\/strong>” and “404 Not Found<\/em><\/strong>” errors. While looking into the message in more details, you can see that it has a “__UID__<\/em><\/strong>” attribute (“Attribute: {Name=__UID__, Value=[110f12348004510b]}<\/em><\/strong>“) which represents the r_object_id<\/em><\/strong> of the dm_user<\/em><\/strong>, normally\u2026 But in this case, it’s different from the one in the dump above. And that r_object_id<\/em><\/strong> doesn’t exist in the Repository anymore:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ iapi $DOCBASE_NAME -Udmadmin -Pxxx << EOC\n> dump,c,110f12348004510b\n> exit\n> EOC\n\n        OpenText Documentum iapi - Interactive API interface\n        Copyright (c) 2023. OpenText Corporation\n        All rights reserved.\n        Client Library Release 23.4.0000.0180\n\nConnecting to Server using docbase REPO01\n[DM_SESSION_I_SESSION_START]info:  "Session 010f123480c63b54 started for user dmadmin."\n\nConnected to OpenText Documentum Server running Release 23.4.0000.0143  Linux64.Oracle\nSession id is s0\nAPI> ...\n[DM_API_E_EXIST]error:  "Document\/object specified by 110f12348004510b does not exist."\n\n[DM_SESSION_W_FETCH_FAILED]warning:  "Fetch of object with handle 110f12348004510b and type NULL failed."\n\nAPI> Bye\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
What happened exactly? I’m not sure, I tried to ask the people that were looking at that case \/ trying to fix the AD account, but nobody could tell me if there was another account that was removed \/ re-assigned. I can only assume OTDS initially created a duplicate account (USERID02<\/em><\/strong>) because it couldn’t map the existing account in the Repository since the user_name was messed-up in the AD. And that someone either deleted or re-assigned the OTDS account to the other account (which was initially created by the LDAP Sync years ago, before the migration to OTDS in the past few days\/weeks).<\/p>\n\n\n\n
Reflection on the way to fix it<\/h2>\n\n\n\n
In any cases, what can be done to fix the situation\u2026? The problem is that now OTDS references a r_object_id<\/em><\/strong> that doesn’t exist in Documentum and that prevent the synchronization to happen properly. Even if an account exists in the Repository with the expected user_login_name<\/em><\/strong> \/ user_name<\/em><\/strong>, since it’s not the one OTDS has internally, it’s not doing anything.<\/p>\n\n\n\n
I could see 2 options to solve the case:<\/p>\n\n\n\n
    \n
  1. Since it’s part of a Synchronized Partition, you cannot delete the OTDS account. Therefore, a first solution could be to exclude this specific account from the Partition (by updating the user filter to specifically exclude that one), execute a consolidation to make sure all references of it disappears before re-adding the account again.<\/li>\n\n\n\n
  2. Find and update the wrong reference in the OTDS DB<\/li>\n<\/ol>\n\n\n\n
    The safest approach is probably the #1, but since I was in the middle of debugging the issue, I wanted to try the second one instead. This is to confirm how OTDS behaves and maybe to get more insights on how the DB is organized\u2026 Who knows, it might be helpful at some point in the future ;).<\/p>\n\n\n\n
    From what I already knew, the users are put inside the “MEMBERS<\/em><\/strong>” table but that would only contain things from the Source system (AD here). The possible external details like the “r_object_id<\/em><\/strong>” I’m looking for here would usually be in the “RESOURCEACCESS<\/em><\/strong>” table instead. Therefore, I found my user through its user id, fetched the UUID<\/em><\/strong> that is the cross-reference used by OTDS and was indeed able to find the wrong reference there:<\/p>\n\n\n
    \nSQL> SET PAGES 999;\nSQL> SET WRAP OFF;\nSQL> SET LINESIZE 50;\nSQL> SELECT UUID, NAME FROM MEMBERS WHERE NAME='USERID01';\n\nUUID                             NAME\n-------------------------------- -----------------\n7BE9748AA57149D3BC641A948363B1B5 USERID01\n\nSQL> SELECT MEMBERID, IDINRESOURCE FROM RESOURCEACCESS WHERE MEMBERID='7BE9748AA57149D3BC641A948363B1B5';\n\nMEMBERID                         IDINRESOURCE\n-------------------------------- -----------------\n7BE9748AA57149D3BC641A948363B1B5 110f12348004510b\n<\/pre><\/div>\n\n\n
    DB Crawler – Preparation<\/h2>\n\n\n\n
    But what if you aren’t certain if this is the only reference in the whole DB\u2026? I was in this position too. I knew I could find what I was looking for in these 2 tables, but I wasn’t 100% certain if it was the only place. Well, I sure hoped so, as having duplicates \/ multiple references for the same thing in the DB could be pretty bad.<\/p>\n\n\n\n
    Let’s crawl the DB to see if there are any other references then! First of all, I created a small SQL file which contains the connection to the DB, the generation of all needed SELECT statements for each column of each table which have a string data_type<\/span> and finally the execution of the generated selects:<\/p>\n\n\n
    \n[dmadmin@cs-0 mop]$ ls -l\ntotal 4\n-rw-r----- 1 dmadmin dmadmin 536 Nov 18 09:03 generate_and_execute_selects.sql\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ cat generate_and_execute_selects.sql\nCONNECT otds-user\/otds-password@otds-tns\nspool selects.sql\nset pagesize 0\nset linesize 10000\nset trims on\nSELECT\n    'SELECT ''' || table_name || ''' AS table_name, ''' ||\n    column_name || ''' AS column_name, "' ||\n    column_name || '" AS value_found ' ||\n    'FROM ' || owner || '.' || table_name ||\n    ' WHERE "' || column_name || '" LIKE ''%110f12348004510b%'';'\n  FROM\n    all_tab_columns\n  WHERE\n    data_type IN ('VARCHAR2','NVARCHAR2','CHAR','NCHAR','CLOB','RAW')\n    AND owner = 'OTDS';\nspool off\nset echo on\n@selects.sql\nquit\n[dmadmin@cs-0 mop]$\n<\/pre><\/div>\n\n\n
    Note 1:<\/em><\/strong> I put the CONNECT<\/em><\/strong> inside the SQL file, but you can obviously set it at command line or through variables, so it doesn’t show in the bash history. It’s just an example.<\/p>\n\n\n\n
    Note 2:<\/em><\/strong> You can change the string that you are looking for, it’s in between the ‘%string%<\/em><\/strong>‘ (line 11 of the SQL file). You can also change the data_type as required (line 15 of the SQL file). For OTDS on Oracle, only VARCHAR2<\/em><\/strong>, CLOB<\/em><\/strong> and RAW<\/em><\/strong> are used.<\/p>\n\n\n\n
    Note 3:<\/em><\/strong> I’m using double quotes (“) around the column_name<\/em><\/strong>. This is because, unfortunately, some columns for OTDS appears to be created by the product with case sensitivity\u2026 Therefore, without these double quotes, you wouldn’t be able to query for the 2 tables: “SCHEMA_HISTORY<\/em><\/strong>” and “BOOTSTRAP_HISTORY<\/em><\/strong>“. Without it, the DB Crawling would succeed for all tables except these 2 where you would get an “invalid identifier” on the column name\u2026 As an example, you can try to execute these two queries:<\/p>\n\n\n
    \nselect * from SCHEMA_HISTORY WHERE description like '%setup%'; -- this might not work\nselect * from SCHEMA_HISTORY WHERE "description" like '%setup%'; -- this works\n<\/pre><\/div>\n\n\n
    DB Crawler – Execution<\/h2>\n\n\n\n
    Once you have the above SQL file, you can execute it. As mentioned, it will start with the generation of another SQL file, containing all needed SELECT<\/em><\/strong> statements for all columns of all tables. And it will then execute all these SELECT<\/strong><\/em> statements one by one. All the logs will be inside the “selects.log<\/em><\/strong>” file in this case:<\/p>\n\n\n
    \n[dmadmin@cs-0 mop]$ sqlplus \/nolog @generate_and_execute_selects.sql > selects.log\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ echo $?\n0\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ ls -l\ntotal 96\n-rw-r----- 1 dmadmin dmadmin   536 Nov 18 09:03 generate_and_execute_selects.sql\n-rw-r----- 1 dmadmin dmadmin 54518 Nov 18 09:03 selects.log\n-rw-r----- 1 dmadmin dmadmin 25122 Nov 18 09:03 selects.sql\n[dmadmin@cs-0 mop]$\n<\/pre><\/div>\n\n\n
    I usually start a first execution with “@selects.sql<\/em><\/strong>” being commented in the “generate_and_execute_selects.sql<\/em><\/strong>” file. This is to generate the SELECT<\/em><\/strong> statements without executing them. I can first verify if everything looks good before cleaning and re-executing without the line commented out.<\/p>\n\n\n\n
    For OTDS, there are 164 SELECT<\/em><\/strong> statements being generated. For this environment, there are 252 columns owned by “OTDS” in total, but 49+39 of these that have a TIMESTAMP<\/em><\/strong>+NUMBER<\/em><\/strong> data_type<\/em><\/strong>, respectively, which gives us the 164 results, as expected:<\/p>\n\n\n
    \n[dmadmin@cs-0 mop]$ cat selects.sql\nSELECT 'ACCESSROLEMEMBERS' AS table_name, 'TENANTID' AS column_name, "TENANTID" AS value_found FROM OTDS.ACCESSROLEMEMBERS WHERE "TENANTID" LIKE '%110f12348004510b%';\nSELECT 'ACCESSROLEMEMBERS' AS table_name, 'ACCESSROLEID' AS column_name, "ACCESSROLEID" AS value_found FROM OTDS.ACCESSROLEMEMBERS WHERE "ACCESSROLEID" LIKE '%110f12348004510b%';\nSELECT 'ACCESSROLEMEMBERS' AS table_name, 'MEMBERID' AS column_name, "MEMBERID" AS value_found FROM OTDS.ACCESSROLEMEMBERS WHERE "MEMBERID" LIKE '%110f12348004510b%';\nSELECT 'SCHEMA_HISTORY' AS table_name, 'version' AS column_name, "version" AS value_found FROM OTDS.SCHEMA_HISTORY WHERE "version" LIKE '%110f12348004510b%';\nSELECT 'SCHEMA_HISTORY' AS table_name, 'description' AS column_name, "description" AS value_found FROM OTDS.SCHEMA_HISTORY WHERE "description" LIKE '%110f12348004510b%';\n...\n...\nSELECT 'JOBS' AS table_name, 'NAME' AS column_name, "NAME" AS value_found FROM OTDS.JOBS WHERE "NAME" LIKE '%110f12348004510b%';\nSELECT 'JOBS' AS table_name, 'TARGET' AS column_name, "TARGET" AS value_found FROM OTDS.JOBS WHERE "TARGET" LIKE '%110f12348004510b%';\nSELECT 'BOOTSTRAP_HISTORY' AS table_name, 'version' AS column_name, "version" AS value_found FROM OTDS.BOOTSTRAP_HISTORY WHERE "version" LIKE '%110f12348004510b%';\nSELECT 'BOOTSTRAP_HISTORY' AS table_name, 'description' AS column_name, "description" AS value_found FROM OTDS.BOOTSTRAP_HISTORY WHERE "description" LIKE '%110f12348004510b%';\nSELECT 'BOOTSTRAP_HISTORY' AS table_name, 'type' AS column_name, "type" AS value_found FROM OTDS.BOOTSTRAP_HISTORY WHERE "type" LIKE '%110f12348004510b%';\nSELECT 'BOOTSTRAP_HISTORY' AS table_name, 'script' AS column_name, "script" AS value_found FROM OTDS.BOOTSTRAP_HISTORY WHERE "script" LIKE '%110f12348004510b%';\nSELECT 'BOOTSTRAP_HISTORY' AS table_name, 'installed_by' AS column_name, "installed_by" AS value_found FROM OTDS.BOOTSTRAP_HISTORY WHERE "installed_by" LIKE '%110f12348004510b%';\n\n164 rows selected.\n\n[dmadmin@cs-0 mop]$\n<\/pre><\/div>\n\n\n
    To verify if all SELECT<\/em><\/strong> statements were executed successfully and to check the list of occurrences of the specific string, you can use such commands:<\/p>\n\n\n
    \n[dmadmin@cs-0 mop]$ grep '^SQL> SELECT' selects.log | wc -l\n164\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ grep -i 'ERROR' selects.log | wc -l\n0\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ grep 'no rows selected' selects.log | wc -l\n163\n[dmadmin@cs-0 mop]$\n[dmadmin@cs-0 mop]$ grep -B1 '[^%]110f12348004510b' selects.log\nSQL> SELECT 'RESOURCEACCESS' AS table_name, 'IDINRESOURCE' AS column_name, "IDINRESOURCE" AS value_found FROM OTDS.RESOURCEACCESS WHERE "IDINRESOURCE" LIKE '%110f12348004510b%';\nRESOURCEACCESS IDINRESOURCE 110f12348004510b\n[dmadmin@cs-0 mop]$\n<\/pre><\/div>\n\n\n
    Fixing the wrong r_object_id reference in OTDS<\/h2>\n\n\n\n
    Therefore, that confirms that all 164 SELECT<\/em><\/strong> statements were executed, there was 0 errors, 163 empty results (no match in the full column) and only a single query that matched. This means that the only reference present for the Documentum r_object_id<\/em><\/strong> in the OTDS DB is indeed stored inside the “RESOURCEACCESS.IDINRESOURCE<\/em><\/strong>” column. So let’s update \/ correct that value:<\/p>\n\n\n
    \nSQL> SELECT MEMBERID, IDINRESOURCE FROM RESOURCEACCESS WHERE MEMBERID='7BE9748AA57149D3BC641A948363B1B5';\n\nMEMBERID                         IDINRESOURCE\n-------------------------------- -----------------\n7BE9748AA57149D3BC641A948363B1B5 110f12348004510b\n\nSQL> UPDATE RESOURCEACCESS SET IDINRESOURCE='110f12348000c96b' WHERE MEMBERID='7BE9748AA57149D3BC641A948363B1B5';\n\n1 row updated.\n\nSQL> SELECT MEMBERID, IDINRESOURCE FROM RESOURCEACCESS WHERE MEMBERID='7BE9748AA57149D3BC641A948363B1B5';\n\nMEMBERID                         IDINRESOURCE\n-------------------------------- -----------------\n7BE9748AA57149D3BC641A948363B1B5 110f12348000c96b\n<\/pre><\/div>\n\n\n
    Now that it’s corrected, the final step is to trigger a new consolidation for that specific account, to see if OTDS is now able to update the account in Documentum:<\/p>\n\n\n
    \nThread Id: 655,026      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Enter: update(ObjectClass: __ACCOUNT__, Attribute: {Name=__UID__, Value=[110f12348000c96b]}, [Attribute: {Name=__TENANT__, Value=[]}, Attribute: {Name=user_os_name, Value=[]}, Attribute: {Name=AccountDisabled, Value=[false]}, Attribute: {Name=user_global_unique_id, Value=[9ibc9uqrfKafp\/K1LRb0og==]}, Attribute: {Name=user_rename_unlock_locked_obj, Value=[T]}, Attribute: {Name=client_capability, Value=[2]}, Attribute: {Name=user_login_domain, Value=[]}, Attribute: {Name=user_name, Value=[User Display Name 01]}, Attribute: {Name=user_ldap_dn, Value=[CN=USERID01,OU=Users,DC=domain,DC=com]}, Attribute: {Name=user_address, Value=[user01@domain.com]}, Attribute: {Name=user_login_name, Value=[USERID01]}, Attribute: {Name=user_xprivileges, Value=[32]}, Attribute: {Name=create_default_cabinet, Value=[F]}, Attribute: {Name=user_privileges, Value=[0]}, Attribute: {Name=__PARTITION__, Value=[PARTITION01]}, Attribute: {Name=__OTDS_UUID__, Value=[7748abe9-7a51-9d43-b6c4-13ba639481b5]}, Attribute: {Name=user_type, Value=[dm_user]}, Attribute: {Name=user_rename_enabled, Value=[T]}, Attribute: {Name=default_folder, Value=[\/Home\/User Display Name 01]}, Attribute: {Name=__NAME__, Value=[User Display Name 01]}], null)\nThread Id: 655,032      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f123480007dd8]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@289175b7})\nThread Id: 655,033      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000051b]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@2551d69b})\nThread Id: 655,036      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000051e]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@3f885a33})\nThread Id: 655,038      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000451d]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@39b49b96})\nThread Id: 655,040      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Enter: create(ObjectClass: DIRECTIONAL_ASSOCIATION, [Attribute: {Name=ToObjClassName, Value=[__GROUP__]}, Attribute: {Name=FromObjClassName, Value=[__MEMBER__]}, Attribute: {Name=From, Value=[[Multiple Members]]}, Attribute: {Name=To, Value=[120f12348000451e]}, Attribute: {Name=Type, Value=[MemberOfGroup]}], OperationOptions: {Members=[Ljava.lang.String;@4504edb8})\nThread Id: 655,066      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Enter: update(ObjectClass: __ACCOUNT__, Attribute: {Name=__UID__, Value=[110f12348000c96b]}, [Attribute: {Name=__TENANT__, Value=[]}, Attribute: {Name=user_os_name, Value=[]}, Attribute: {Name=AccountDisabled, Value=[false]}, Attribute: {Name=user_global_unique_id, Value=[9ibc9uqrfKafp\/K1LRb0og==]}, Attribute: {Name=user_rename_unlock_locked_obj, Value=[T]}, Attribute: {Name=client_capability, Value=[2]}, Attribute: {Name=user_login_domain, Value=[]}, Attribute: {Name=user_name, Value=[User Display Name 01]}, Attribute: {Name=user_ldap_dn, Value=[cn=USERID01,ou=users,dc=domain,dc=com]}, Attribute: {Name=user_address, Value=[user01@domain.com]}, Attribute: {Name=user_login_name, Value=[USERID01]}, Attribute: {Name=user_xprivileges, Value=[32]}, Attribute: {Name=create_default_cabinet, Value=[F]}, Attribute: {Name=user_privileges, Value=[0]}, Attribute: {Name=__PARTITION__, Value=[PARTITION01]}, Attribute: {Name=__OTDS_UUID__, Value=[7748abe9-7a51-9d43-b6c4-13ba639481b5]}, Attribute: {Name=user_type, Value=[dm_user]}, Attribute: {Name=user_rename_enabled, Value=[T]}, Attribute: {Name=default_folder, Value=[\/Home\/User Display Name 01]}, Attribute: {Name=__NAME__, Value=[User Display Name 01]}], null)\nThread Id: 655,026      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[110f12348000c96b]}\nThread Id: 655,033      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[[Multiple Members]__com.opentext.otds.connectors.reserved.string____MEMBER__%%%__GROUP__%%%MemberOfGroup__com.opentext.otds.connectors.reserved.string__120f12348000051b]}\nThread Id: 655,032      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[[Multiple Members]__com.opentext.otds.connectors.reserved.string____MEMBER__%%%__GROUP__%%%MemberOfGroup__com.opentext.otds.connectors.reserved.string__120f123480007dd8]}\nThread Id: 655,066      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.UpdateApiOp      Method: update  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[110f12348000c96b]}\nThread Id: 655,038      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[[Multiple Members]__com.opentext.otds.connectors.reserved.string____MEMBER__%%%__GROUP__%%%MemberOfGroup__com.opentext.otds.connectors.reserved.string__120f12348000451d]}\nThread Id: 655,040      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[[Multiple Members]__com.opentext.otds.connectors.reserved.string____MEMBER__%%%__GROUP__%%%MemberOfGroup__com.opentext.otds.connectors.reserved.string__120f12348000451e]}\nThread Id: 655,036      Time: 11\/18\/25, 9:11 AM Class: org.identityconnectors.framework.api.operations.CreateApiOp      Method: create  Level: OK       Message: Return: Attribute: {Name=__UID__, Value=[[Multiple Members]__com.opentext.otds.connectors.reserved.string____MEMBER__%%%__GROUP__%%%MemberOfGroup__com.opentext.otds.connectors.reserved.string__120f12348000051e]}\n<\/pre><\/div>\n\n\n
    The logs look clean and the same is shown on Documentum:<\/p>\n\n\n
    \n[dmadmin@cs-0 ~]$ iapi $DOCBASE_NAME -Udmadmin -Pxxx << EOC\n> dump,c,110f12348000c96b\n> exit\n> EOC\n\n        OpenText Documentum iapi - Interactive API interface\n        Copyright (c) 2023. OpenText Corporation\n        All rights reserved.\n        Client Library Release 23.4.0000.0180\n\nConnecting to Server using docbase REPO01\n[DM_SESSION_I_SESSION_START]info:  "Session 010f123480c63b66 started for user dmadmin."\n\nConnected to OpenText Documentum Server running Release 23.4.0000.0143  Linux64.Oracle\nSession id is s0\nAPI> ...\nUSER ATTRIBUTES\n\n  user_name                       : User Display Name 01\n  user_os_name                    :\n  user_address                    : user01@domain.com\n  user_group_name                 :\n  user_privileges                 : 0\n  owner_def_permit                : 7\n  world_def_permit                : 3\n  group_def_permit                : 5\n  default_folder                  : \/Home\/User Display Name 01\n  user_db_name                    :\n  description                     :\n  acl_domain                      : User Display Name 01\n  acl_name                        : dm_450f12348000f652\n  user_os_domain                  :\n  home_docbase                    :\n  user_state                      : 0\n  client_capability               : 2\n  globally_managed                : F\n  user_delegation                 :\n  workflow_disabled               : F\n  alias_set_id                    : 0000000000000000\n  user_source                     : OTDS\n  user_ldap_dn                    : cn=USERID01,ou=users,dc=domain,dc=com\n  user_xprivileges                : 32\n  failed_auth_attempt             : 0\n  user_admin                      :\n  user_global_unique_id           : 9ibc9uqrfKafp\/K1LRb0og==\n  user_login_name                 : USERID01\n  user_login_domain               :\n  user_initials                   :\n  user_password                   : ****************\n  user_web_page                   :\n  first_failed_auth_utc_time      : nulldate\n  last_login_utc_time             : 1\/3\/2022 13:39:00\n  deactivated_utc_time            : nulldate\n  deactivated_ip_addr             :\n  restricted_folder_ids         []: <none>\n  root_log_dir                    :\n\nSYSTEM ATTRIBUTES\n\n  r_is_group                      : F\n  r_modify_date                   : 11\/18\/2025 09:11:38\n  r_has_events                    : F\n  r_object_id                     : 110f12348000c96b\n\nAPPLICATION ATTRIBUTES\n\n\nINTERNAL ATTRIBUTES\n\n  i_is_replica                    : F\n  i_vstamp                        : 15\n\nAPI> Bye\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
    The account was just updated, the “user_global_unique_id<\/em><\/strong>” has been populated with some others as well. Therefore, the OTDS synchronization is now correct for that account. In summary, this case was pretty specific, with issues inside the AD directly, which created a bit of a mess in OTDS and Documentum with a mapping to a wrong user which is apparently not present anymore, etc\u2026 But once the AD was fixed, I was able to reset the r_object_id<\/em><\/strong> reference in OTDS, so that it could restore itself to a correct behavior.<\/p>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    I recently faced another pretty interesting case with an incorrect r_object_id reference in OTDS. In a non-production (dev) Active Directory (Azure EntraID) that is used as source of truth for the users\/groups, it looked like there was an account which was a bit messed-up. By that, I mean that the mail address, user name and […]<\/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],"tags":[3798,2609,3500,1909,3797,2039,3799,1997],"type_dbi":[],"class_list":["post-42306","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-db-crawler","tag-documentum-2","tag-otds","tag-partition","tag-r_object_id","tag-resource","tag-synchronization","tag-user_global_unique_id"],"acf":[],"yoast_head":"\nDctm - Incorrect r_object_id reference in OTDS - dbi Blog<\/title>\n<meta name=\"description\" content=\"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.\" \/>\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-incorrect-r_object_id-reference-in-otds\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dctm - Incorrect r_object_id reference in OTDS\" \/>\n<meta property=\"og:description\" content=\"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-01T14:41:00+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=\"7 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-incorrect-r_object_id-reference-in-otds\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Dctm – Incorrect r_object_id reference in OTDS\",\"datePublished\":\"2026-01-01T14:41:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\"},\"wordCount\":1503,\"commentCount\":0,\"keywords\":[\"DB Crawler\",\"Documentum\",\"OTDS\",\"Partition\",\"r_object_id\",\"resource\",\"Synchronization\",\"user_global_unique_id\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\",\"name\":\"Dctm - Incorrect r_object_id reference in OTDS - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2026-01-01T14:41:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"description\":\"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Dctm – Incorrect r_object_id reference in OTDS\"}]},{\"@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 - Incorrect r_object_id reference in OTDS - dbi Blog","description":"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.","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-incorrect-r_object_id-reference-in-otds\/","og_locale":"en_US","og_type":"article","og_title":"Dctm - Incorrect r_object_id reference in OTDS","og_description":"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.","og_url":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/","og_site_name":"dbi Blog","article_published_time":"2026-01-01T14:41:00+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Dctm – Incorrect r_object_id reference in OTDS","datePublished":"2026-01-01T14:41:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/"},"wordCount":1503,"commentCount":0,"keywords":["DB Crawler","Documentum","OTDS","Partition","r_object_id","resource","Synchronization","user_global_unique_id"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/","url":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/","name":"Dctm - Incorrect r_object_id reference in OTDS - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-01-01T14:41:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"description":"It might happen to have an incorrect r_object_id reference in OTDS for some objects. Let's go through the way to find and correct such items.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-incorrect-r_object_id-reference-in-otds\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Dctm – Incorrect r_object_id reference in OTDS"}]},{"@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\/42306","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=42306"}],"version-history":[{"count":2,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/42306\/revisions"}],"predecessor-version":[{"id":42308,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/42306\/revisions\/42308"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=42306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=42306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=42306"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=42306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}