Direct links to fixes
APAR status
Closed as program error.
Error description
If an Oracle LDAP URL is used for the IBM Business Automation Workflow Case Manager data sources, the following error occurs when you run the DBUpgrade command: [Sep 6, 2018 2:50:33 PM] 00000001 FINE: com.lombardisoftware.tools.dbupgrade.UpgradeContext.getDataSourc e - The JDBC URL is: jdbc:oracle:thin:@//hostname:3090/service_name [Sep 6, 2018 2:50:33 PM] 00000001 SEVERE: com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.upgradeCont entDatabases - Exception while upgrading your IBM Business Automation Workflow Content Navigator database. [Sep 6, 2018 2:50:33 PM] 00000001 SEVERE: com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.upgradeCont entDatabases - Check the log files for details. [Sep 6, 2018 2:50:33 PM] 00000001 SEVERE: com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.upgradeCont entDatabases - java.sql.SQLRecoverableException: IO Error: Size Data Unit (SDU) mismatch java.lang.RuntimeException: java.sql.SQLRecoverableException: IO Error: Size Data Unit (SDU) mismatch at com.lombardisoftware.tools.dbupgrade.UpgradeContext.getDataSourc e(UpgradeContext.java:137) at com.lombardisoftware.tools.dbupgrade.UpgradeContext.getConnectio n(UpgradeContext.java:102) at com.lombardisoftware.tools.dbupgrade.steps.InitializeConentNavig atorDatabase.executeSQL(InitializeConentNavigatorDatabase.java:2 76) [Sep 6, 2018 2:50:33 PM] 00000001 SEVERE: com.lombardisoftware.tools.dbupgrade.UpgradeDatabase.upgradeCont entDatabases - java.sql.SQLRecoverableException: IO Error: Size Data Unit (SDU) mismatch java.lang.RuntimeException: java.sql.SQLRecoverableException: IO Error: Size Data Unit (SDU) mismatch at com.lombardisoftware.tools.dbupgrade.UpgradeContext.getDataSourc e(UpgradeContext.java:137) at com.lombardisoftware.tools.dbupgrade.UpgradeContext.getConnectio n(UpgradeContext.java:102) at com.lombardisoftware.tools.dbupgrade.steps.InitializeConentNavig atorDatabase.executeSQL(InitializeConentNavigatorDatabase.java:2 76) Please note that at this time when you configure the case manager configuration the data source is set with the Service String URL BPMConfig.bat -update -profile deployment_manager_profile -de deployment_environment_name -caseConfigure You have to manually change the datasource if you have a requirement to use Oracle LDAP URL format. This fix will only change the DBUgprade code to recognize and use the URL configures for the case manager database source.
Local fix
1. The data sources are generated at the app cluster scope in this file: config\cells\<cellname>\clusters\<App cluster name>\resources.xml To use a different connection URL, manually update the generated data sources in this file or with wsadmin after running the caseConfigure command. These are the datasources: jdbc/FNDOSDSXA jdbc/FNTOSDSXA jdbc/ECMTaskManagerDS jdbc/ECMClientDS jdbc/FNDOSDS jdbc/FNTOSDS 2. Locate the ICN database initialization SQL script at dmgr_profile\dbscripts\Upgrade\<cellName>.<dename>\<icndatabaseN ame>\createTable_ICN.sql. 3. Run the SQL script manually. 4. Create the database upgrade successful flag file by creating an empty file named <dename>.DBUpgrade.success in the dmgrProfile/logs/ folder. 5. Referring to either "Upgrading profiles from IBM Business Process Manager Version 8.6.x to IBM Business Automation Workflow V18.0.0.1" (https://www.ibm.com/support/docview.wss?uid=swg27051095) or "Upgrading profiles from IBM Business Process Manager Version 8.5.x to IBM Business Automation Workflow Version 18.0.0.1" (https://www.ibm.com/support/docview.wss?uid=swg27051096), continue the remaining steps after the DBUpgrade step.
Problem summary
No additional information is available.
Problem conclusion
A fix that ensures the LDAP-based data source URL works for the DBUpgrade command will be available in future releases of IBM Business Automation Workflow.
Temporary fix
Comments
APAR Information
APAR number
JR60009
Reported component name
BUS AUTO WORKFL
Reported component ID
5737H4100
Reported release
I00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-09-12
Closed date
2018-11-04
Last modified date
2018-11-04
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
BUS AUTO WORKFL
Fixed component ID
5737H4100
Applicable component levels
RI00 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 November 2018