A fix is available
APAR status
Closed as fixed if next.
Error description
If the customer migrate to an advance profile from a standard profile, the DBUpgrade will fail because some tables lost in the upgrade SQL scripts. This will be noticed when running the DBUpgrade and see the following error in the DBUpgrade log: Sep 17, 2015 9:26:39 AM SEVERE: com.lombardisoftware.tools.dbupgrade.steps.TestDatabases. printExpectedDatabaseInfo - In the Common database(CMNDB), there is no expected table with name FailedEvents. This is followed by this error message: "The configured Common database does not appear to be a valid Common database." This is caused by incorrect sql scripts for the common DB that the upgradeSchemaAll_de_name.sh command runs.
Local fix
To fix this, we will first need to generate some additional scripts. By default, you should have already have ran the follow command: "BPMConfig -create -de" This command generated the upgrade dbscripts. You will also need to run: "BPMConfig -create -sqlfiles " This generated the create dbscripts. We need to remove/backup the following upgrade script files in DmgrProfile\dbscripts\Upgrade\cell_name.de_name\Oracle\ DBUser.CMNDB\ createSchema_Advanced.sql createSchema_Messaging.sql createTable_BusinessSpace.sql and in: DmgrProfile\dbscripts\Upgrade\cell_name\Oracle\DBUser.CMNDB\ createSchema_CommonDBCellOnly.sql In the place of those scripts we removed, we need to place the following sql scripts in the dbscripts generated from the BPMConfig -create -sqlfiles : DmgrProfile\dbscripts\cell_name\Oracle\DBUser\CMNDB\ createSchema_ Advanced.sql DmgrProfile\dbscripts\cell_name.de_name\Oracle\DBUser\CMNDB\ createSchema_Advanced.sql DmgrProfile\dbscripts\cell_name.de_name\Oracle\DBUser\CMNDB\ createSchema_Messaging.sql and put them in the Upgrade scripts folder here: DmgrProfile\dbscripts\Upgrade\cell_name.\Oracle\DBUser.CMNDB\ createSchema_Advanced.sql DmgrProfile\dbscripts\Upgrade\cell_name..de_name\Oracle\ DBUser.CMNDB\createSchema_Advanced.sql DmgrProfile\dbscripts\Upgrade\cell_name..de_name\Oracle\ DBUser.CMNDB\createSchema_Messaging.sql With this work around, the table will be correctly generated. Now the, after restoring your database to a previously working state, you will need to run the database migration steps again and should not encounter any additional issues
Problem summary
As for BPM standard profile migrated to BPM Advanced profile, Migration tools don't support DEScope common DB shared with Cellonly DB, DBUpgrade will fail. But this has been supported in BPM857.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR54657
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
856
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-11-04
Closed date
2015-12-21
Last modified date
2015-12-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R856 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 October 2021