Page Comparison

Multiple emails get triggered even though only one entry in the table (OD_PENDING_MAIL) from where CT picks up records to be sent as email. In such cases refer these kind of errors found in the SystemOut.log (WebSphere log).

• WTRN0006W: Transaction {0} has timed out after {1} seconds
  
  
  For example:
  

  Code Block
  language powershell
  WTRN0006W: Transaction 00000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000001 has timed out after 120 seconds

  
  

  Solution: Increase the total transaction lifetime timeout and maximum translation timeout in seconds. These settings can be updated through the WebSphere Application Server console, using Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service
  

  Reference links : https://www.ibm.com/support/pages/troubleshooting-java-transaction-service-jts-problems

  https://www.ibm.com/docs/en/was-nd/8.5.5?topic=server-transaction-service-settings
  
  
• WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1f5b7ee3. The error code was XAER_RMERR.
  
  
  Solution:
  Run the following commands as user SYS:

  Code Block
  language powershell
  grant select on pending_trans$ to <user>; grant select on dba_2pc_pending to <user>; grant select on dba_pending_transactions to <user>; grant execute on dbms_system to <user>; //If using Oracle 10.2.0.3 or lower JDBC driver grant execute on dbms_xa to <user>; //If using Oracle 10.2.0.4 or higher JDBC driver

  In the above commands, <user> is the username configured in the Oracle datasource's authentication alias.

  Reference link : https://www.ibm.com/support/pages/exception-occurs-during-recovery-oracle-database-transactions

Refer the CT_DATA_SOURCE_METRICS table, to view the Data builder and SQL query data source performance metrics collection in detail:

Report bursting schedules are executed like a normal report scheduling. Pausing the report-bursting process essentially puts it on hold. The process stops at the point where it was paused. If report bursting is resumed, it fires the missed schedules once and continues with the next upcoming instances based on the given frequency. For example, when a report bursting is paused on August 1 and resumed on August 15, it kick-starts the report bursting on August 15 and continues with the next upcoming instances based on the given frequency.