Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 6,5
Information in this document applies to any platform
DESCRIPTION: Customer reported that he had a failure in his system and when the system restarted some of his groups restarted on servers that were not defined as backups in his config file. I had the customer perform a tmuloadcf on the tuxconfig and the output listed backups for groups that did not have backups defined in the ubbconfig file. I was able to replicate this behavior and the test case can be found in /nfs/home4/tfrazier/cases/196656. In an effort to narrow down the root cause I took the following actions followed by unloading the tuxconfig file and reviewing the output: 1. removed the backup machin from the MASTER variable in the config file. - same result 2. removed the MIGRATE option from the OPTION variable - same result 3. removed the backup machine value from the each DEFAULT arg in the file and none of the groups reported having backups in the unload file. 4. Added a backup machine to a groups DEFAULT value and the unload file reported that all groups after that had the DEFAULT values backup server for a backup machine even if there was no backup defined for the group. It appears that if a default value is defined as: DEFAULT: TMSCOUNT=2 LMID=host_gdb001, host_gdb002 TMSNAME=TMS gdb_001 GRPNO=100 and then a group that follows this group in the config file i.e. DEFAULT: TMSCOUNT=2 LMID=host_dq002 TMSNAME=TMS out_002 GRPNO=340 Notice that there is no backup LMID defined for this group, the tmunloadcf shows that this group has the previous groups backup LMID value 'host_gdb002' as its backup as well. It appears that thlmid values are not being handled properly.
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