IT23807: DATABASE EXCEPTION OCCURS WHEN AN XSLT TEMPLATE IS CREATED IN IBM STERLING B2B INTEGRATOR

APAR status

• Closed as program error.

Error description

• When client does one of the following actions in IBM Sterling
  B2B Integrator dashboard:
  -create XSLT
  -import XSLT
  -modify a BP
  
  The following errors are reported in ops.log and
  visibility.log files:
  
  
  [2017-09-13 11:15:14.624] ERROR
  DmiVisEventWarehouseQueue.Worker.executeStatementsAsExecutor had
   a SQL exception from pstmnt: PreparedStatementHelper: SQL:
  INSERT INTO ADMIN_AUDIT (ADMIN_AUDIT_ID, OBJECT_TYPE,
  OBJECT_NAME, ACTION_TYPE, ACTION_VALUE, PRINCIPAL, TIME,
  ARCHIVE_DATE) VALUES(?, ?, ?, ?, ?, ?, ?, ?) Values:
  [81974815e7a835334node1, Template Objects, Test_ORA_ERROR_IBM,
  Create, , jiadm, 2017-09-13 11:15:14.329, 2017-09-27
  11:15:14.329]
  
  [2017-09-13 11:15:14.624] ERROR [1505294114624] ORA-01400:
  cannot insert NULL into ("SBI"."ADMIN_AUDIT"."ACTION_VALUE")
  
  This symptom was observed on IBM Sterling B2B Integrator
  V5.2.5_12 with Oracle as the database.
  

Local fix

• RTC No: 576402
  

Problem summary

• Users Affected:
  All
  
  Problem Description:
  A database exception occurs when an XSLT template is created in
  IBM Sterling B2B Integrator as the template version is passed as
  null, which is a non-null field.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  
  A code fix is provided.
  
  Delivered In:
  5020500_18
  5020601_10
  5020602_6
  5020603_6
  

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