Fixes are available
APAR status
Closed as program error.
Error description
When you use the configureNode command to configure IBM Business Process Manager (BPM) with an Oracle database and the service name feature is not available, the database connection fails and the database schema cannot be created. You see error messages that are similar to the following error messages: The database [bpmsdev] set in dmgr property [prcsvr.dbName] can not be connected via user name[POCPS8BPMDB] and password[*****]. The database [pdwdev] set in dmgr property [perfDW.dbName] can not be connected via user name[POCPS8PDWDB] and password[*****]. The database [bpmsdev] set in dmgr property [bspace.dbName] can not be connected via user name[POCPS8IBMBUSSP] and password[*****].
Local fix
---
Problem summary
**************************************************************** * USERS AFFECTED: IBM BPM Advanced * * IBM BPM Standard * * IBM BPM Express * **************************************************************** * PROBLEM DESCRIPTION: When you use the configureNode * * command to configure IBM Business * * Process Manager (BPM) with an Oracle * * database and the service name feature * * is not available, the database * * connection fails and the database * * schema cannot be created. * * You see error messages that are * * similar to the following error * * messages: * * The database [bpmsdev] set in dmgr * * property [prcsvr.dbName] can not be * * connected via user name[POCPS8BPMDB] * * and password[*****]. * * The database [pdwdev] set in dmgr * * property [perfDW.dbName] can not be * * connected via user name[POCPS8PDWDB] * * and password[*****]. * * The database [bpmsdev] set in dmgr * * property [bspace.dbName] can not be * * connected via user * * name[POCPS8IBMBUSSP] and * * password[*****]. * **************************************************************** * RECOMMENDATION: * **************************************************************** The configureNode command requires the service name feature to be enabled when configuring IBM BPM with an Oracle database.
Problem conclusion
A fix is available for IBM BPM V8.0.1.1 that enables the configureNode command to fall back to an Oracle SID (system identifier) URL for checking the database connection when the service name feature is not available. This fix also exposes the dbDelayConfig=true option in the deployment manager response file of the configureNode command so that creating the database schema creation can occur in a separate, manual step after the configureNode command runs and creating the database schema does not require the service name feature to be available. In addition, you must change the the database URLs in the IBM BPM data sources and in the WebSphere Lombardi XML files to the SID URLs by using the administrative console and the updateBPMConfig admin command, respectively. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR50257: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR50257, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Comments
APAR Information
APAR number
JR50257
Reported component name
BPM ADV PATTERN
Reported component ID
5725G7600
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-05-15
Closed date
2014-06-24
Last modified date
2014-06-24
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
BPM ADV PATTERN
Fixed component ID
5725G7600
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSV2LR","label":"IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"801","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 October 2021