Moving Documentum to a new server - cluster issue

danielpreuss
edited November 18, 2016 in Documentum #1

Hi, We have:

Documentum 6.5.0.322 SP3

Running on AIX and ORACLE database

Previously it was running on two clustered hosts:

hostname: AIX_OLD_1

hostname: AIX_OLD_2

there is one service name with one IP: archiving_system

Documentum was running on one server - in case of failer it was switchng to another one.

Whole filesystem $DOCUMENTUM was switch during failover

Depending which host was working at the time - it was responding to "archiving_system" name

After failover everything was working fine.

Now:

we have migrated to new AIX hosts:

hostname: AIX_NEW_1

hostname: AIX_NEW_2

Documentum didn't want to start

In:

dmcli.ini

we have:

host = archiving_system

port = 9022

In:

dm_launch_qdocbroker

we have

host=archiving_system

In:

Server.ini

we have:

[DOCBROKER_PROJECTION_TARGET]

host = archiving_system

port = 9022

I have checked ALL files in $DOCUMENTUM - and there is no file pointing to AIX_OLD_1 or AIX_OLD_2

everywhere we have pointing to archiving_system

Issue:

After migration to:

hostname: AIX_NEW_1

hostname: AIX_NEW_2

when starting Documentum there is an error in:

.../dba/log/XXXX.log

Tue Nov 15 23:00:21 2016 [INFORMATION] [AGENTEXEC 16187510] Detected during program initialization: Version: 6.5.0.322 SP3 AIX

Tue Nov 15 23:00:23 2016 [ERROR] [AGENTEXEC 16187510] Detected during program initialization: Command Failed: connect,DATABASE,proper_user_name,'',,,try_native_first, status: 0, with error message [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "archiving_system:9012" failed

[DM_SESSION_E_RPC_ERROR]error:  "Server communication failure"

And when tring to login to tomcat:

[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "archiving_system:9012" failed

So, I have manully changed in ORACLE database:

update DM_SERVER_CONFIG_S set R_HOST_NAME = 'AIX_NEW_1' where R_OBJECT_ID = '0000proper_number0000';

or

update DM_SERVER_CONFIG_S set R_HOST_NAME = 'AIX_NEW_2' where R_OBJECT_ID = '0000proper_number0000';

depending on which server Documentum is running at this moment

It is not possible to start Documentum without changing R_HOST_NAME in DM_SERVER_CONFIG_S

What should I change to have automatically change  R_HOST_NAME in DM_SERVER_CONFIG_S?

Comments

  • Haroon_A
    edited November 18, 2016 #2

    if i recall, you need to have 2 entries in your /etc/services for documentum. i.e. 9012 and 9022, on the content server

  • danielpreuss
    edited November 18, 2016 #3

    I do have entries the same on new AIX_NEW and AIX_OLD


    AIX_NEW_1: cat /etc/services | grep docbro

    ddocbroker      9012/tcp        #Documentum docbroker

    ddocbroker      9012/udp        #Documentum docbroker

    qdocbroker      9022/tcp        #Content Repository 2 Secure

    qdocbroker      9022/udp        #Content Repository 2 Secure

    pdocbroker      9032/tcp        #Documentum docbroker

    pdocbroker      9032/udp        #Documentum docbroker

    where:

    ddocbroker - is for DEV system

    qdocbroker - is for TST system

    pdocbroker - is for PRD system