Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 6.4, 6.5, 6.51
Information in this document applies to any platform
PRODUCT: Tuxedo VERSION: 6.5, patchlevel 227 OS: AIX 4.3 The application is an MP configuration that implements Domains. Before the application is migrated, all the services are advertised successfully. If 'dmadmin' is run, then 'pd -d DGW3A' for the local domain name 'DGW3A', the output is successful: Local domain :DGW3A Connected domains: Then, the application is migrated from the Master to the Slave using the commands: From the Master: 1) tmshutdown -R -l P1 (where P1 is the master LMID) 2) migm P1 Result: The servers shutdown succcessfully, and the migration is also successful. However, on the Master, when 'dmadmin', 'pd -d DGW3A' is run again, the following error message is displayed: CMDGW_CAT:2077: ERROR: Specified Local domain DGW3A not active or not configured Also, on the Slave machine, the following error messages are written to the ULOG: 165313.lcaix5b!GWTDOMAIN.3960: LIBGW_CAT:3037: ERROR: Can't attach initial shared memory segment to the gateway process 165313.lcaix5b!GWTDOMAIN.3960: LIBGW_CAT:3015: ERROR: Can't attach to the shared memory segment(s) 165313.lcaix5b!GWTDOMAIN.3960: LIBTUX_CAT:250: ERROR: tpsvrinit() failed 165316.lcaix5b!restartsrv.17784: server DGW3A/20: CMDTUX_CAT:1684: ERROR: Application initialization failure 165316.lcaix5b!restartsrv.17784: server DGW3A/20: CMDTUX_CAT:587: INFO: Cannot restart server, scheduling for cleanup Another problem observed is regarding the IPC resources on the slave machine. When the application is migrated back to the master, and 'tmshutdown -y' is executed, all the servers shutdown successfully. However, on the slave machine, there are still IPC resources existing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms