Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 6.4, 6.5, 6.51, 7.1
Information in this document applies to any platform
When a data-dependent routing is used and the server is not available for a particular data routing, the ULOG shows a mis-leading error message in GP_CAT:1283 with an incorrect GROUP name. Instead of printing out the GROUP name of the server that the data is supposed to be routed to, it always prints the last group name in the routing table. For example, the following error message gets printed in the ULOG when the server in GRP1 is not available with the following routing configuration. ulog excerpt: GP_CAT:1283: ERROR: Service TOUPPER not available in group GRP3 ubb routing section: *ROUTING SRVCNM FIELD="SRVCNM" BUFTYPE="FML" RANGES="'TOUPPER':GRP1, 'TOLOWER':GRP2, 'NOTHING':GRP3"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms