IT39308: UNCAUGHT DATABASE ERROR RESULTS IN INCONSISTENT DELIVERY STATUS IN FILEGATEWAY AND MYFILEGATEWAY

APAR status

• Closed as program error.

Error description

• An uncaught database error during the completion of a routed
  file delivery results in inconsistent delivery status as seen in
  myfilegateway for the producer and consumer. Uncaught error was
  for ORA-00054 - Oracle database.
  

Local fix

• STRRTC - B2BISFG-60519
  MRC/MRC
  Circumvention: Issue is caused by Oracle database open_cursors
  value being too low, locking a table.
  

Problem summary

• Users Affected:
  All users
  
  Problem Description:
  The issue was observed on Oracle 19c database when open_cursors
  value was set too low - not recommended level.
  
  Platforms Affected:
  All platforms
  

Problem conclusion

• Resolution Summary:
  The Filegateway router code was updated to log an error message
  "Select for Update Failed" in the situation where the error is
  thrown by the database.
  
  Delivered in:
  6010005
  All future Fix Packs can be found in the Release Timeline Matrix
  - https://www.ibm.com/support/pages/node/6194265.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels