Transaction Not Getting Committed In DM_AQ (Doc ID 2614357.1)

Last updated on APRIL 10, 2024

Applies to:

Symptoms

It is assumed that following pre-requisite checks are taken care before following the sequence:

1) Change the Infranet.properties file in $BRM_HOME/sys/eai_js
    Define config file for payload generator:
    infranet.eai.configFile=$BRM_HOME/sys/eai_js/payloadconfig_crm_sync.xml

2) Enable the 'loglevel' in $BRM_HOME/sys/dm_aq pin.conf file.
3) Check the 'dm_aq sm_pw' password in $BRM_HOME/sys/dm_aq pin.conf file and update the password if required.
4) Change the queue name accordingly in $BRM_HOME/sys/dm_aq/aq_queuenames and uncomment the 'ALL' in aq_queuenames file.
5) Go to $BRM_HOME/apps/pin_aq and check the list of the queue:
    perl pin_portal_sync_oracle.pl list -l <USERNAME>/<PASSWORD>@$ORACLE_SID

6) Use below command to drop the queue if required:
    perl pin_portal_sync_oracle.pl drop <queue_name> -l <USERNAME>/<PASSWORD>@$ORACLE_SID

7) Use below command to create the new queue if required:
    perl pin_portal_sync_oracle.pl create -q <queue_name> -t <queue_table> -l <USERNAME>/<PASSWORD>@$ORACLE_SID

8) Stop all the process and start all process and also start_dm_aq.
9) Create the new account.

Steps to reprduce:
Follow Below sequence in testnap session to reproduce the issue

1. Open transaction.
2. Call PCM_OP_CUST_UPDATE_CUSTOMER.
3. Commit transaction.
4. Call PCM_OP_PUBLISH_EVENT.
5. Open transaction
6. Call PCM_OP_CUST_UPDATE_CUSTOMER
7. Commit transaction.
8. Call PCM_OP_PUBLISH_EVENT.

One can notice for the second commit there was no commit triggered.

Changes

Cause

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