My Oracle Support Banner

DG4MQ 19c - COMMIT_CONFIRM DOESN'T WORK AS DOCUMENTED (Doc ID 2964093.1)

Last updated on DECEMBER 19, 2023

Applies to:

Oracle Database Gateway for WebSphere MQ - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

Setting the Oracle Database Gateway for Websphere MQ 19c  with TRANSACTION_MODEL=COMMIT_CONFIRM and AUTHORIZATION_MODEL=STRICT  is not authenticating the <username> and you will see in the trace


Entered hoaxini_INItialize.
PG4MQ:   TRACE_LEVEL = 7
PG4MQ:   TRANSACTION_MODEL = COMMIT_CONFIRM
PG4MQ:   TRANSACTION_RECOVERY_USER = <username>
PG4MQ:   TRANSACTION_LOG_QUEUE = <QUEUE_NAME>
PG4MQ:   AUTHORIZATION_MODEL = STRICT
PG4MQ:   QUEUE_MANAGER = <QUEUE_MANAGER>
PG4MQ:   MQSERVER = <MQ_SERVER_TUNNEL>

Entered hoaxln_Log_oN.
PG4MQ:   PG4MQ client model:
PG4MQ:   MQ_USER_ID=<usnermae, MQ_PASSWORD=<password>
PG4MQ:   host = <host(port)>; channel = <CHANNEL>
MQI:   calling MQCONNX().
MQI:      QM Name = QUEUE_MANAGER>
MQI:   returned from MQCONNX().
MQI:      handle=16777222, completion code=0, reason code=0
Entered hoaxuc_Upload_Capabilities.
Entered hoaxud_Upload_Ddtranslations.
Entered hoaxbg_BeGin_trans.


You are hitting the bug


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.