IBM Support

JR53602: BPMMIGRATIONPREVALIDATION FAILED DURING MIGRATION FROM WPS TO BPM 8.5.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Client performed a migration from WPS v6.2.0.3 to BPM v8.5.5.
    During
    the step of Checking for migration readiness, they failed to
    execute
    the command BPMMigrationPreValidation.
    
    Error Message: CWMCB2103E: Can not determine
    source database type.
    
    Complete Error Reported:
    ---------------
    May 29, 2015 1:51:55 PM SEVERE:
    com.ibm.bpm.migration.prevalidation.BPMPreValidation.main() -
    CWMCO2216E: Exception occurred when running migration
    prevalidation.
    Check the log file under
    /wastemp/CMS-migration/remoteMigrationUtilities/logs/migration
    for
    details.
    com.ibm.bpm.config.util.ConfigException: CWMCB2103E: Can not
    determine
    source database type.
     at
    com.ibm.bpm.migration.prevalidation.BPMPreValidation.init(BPMPre
    Validati
    on.java:190)
     at
    com.ibm.bpm.migration.prevalidation.BPMPreValidation.main(BPMPre
    Validati
    on.java:110)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.jav
    a:60)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Accessor
    Impl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at
    com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:23
    4)
     at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
     at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.jav
    a:60)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Accessor
    Impl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at
    org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodW
    ithExcep
    tion(EclipseAppContainer.java:587)
     at
    org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseApp
    Handle.j
    ava:198)
     at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run
    Applicat
    ion(EclipseAppLauncher.java:110)
     at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta
    rt(Eclip
    seAppLauncher.java:79)
     at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
    er.java:
    369)
     at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
    er.java:
    179)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.jav
    a:60)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Accessor
    Impl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at
    org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
     at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
     at org.eclipse.core.launcher.Main.run(Main.java:981)
     at
    com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLaunche
    r.java:3
    98)
     at
    com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:16
    1)
    Caused by: com.ibm.bpm.config.util.ConfigException: CWMCB2103E:
    Can not
    determine source database type.
     at
    com.ibm.bpm.config.export.helper.ConfigExportHelper.getDbTypeInS
    ourceEnv
    (ConfigExportHelper.java:552)
     at
    com.ibm.bpm.config.export.utils.EnvironmentInfo.initialize(Envir
    onmentIn
    fo.java:194)
     at
    com.ibm.bpm.migration.prevalidation.BPMPreValidation.init(BPMPre
    Validati
    on.java:185)
     ... 27 more
    

Local fix

  • -Noticed that the SCA related SIB bus have non-default jndi
    format like jdbc/sib/SCA.APPLICATION.wshostNetwork1.Bus.
    
    -Change the SCA related two bus name
    from
    jdbc/sib/SCA.SYSTEM.wshostNetwork1.Bus to
     jdbc/com.ibm.ws.sib/XXX.Messaging-SCA.SYSTEM.wshostNetwork1.Bus
    Here xxx means DE name
    
    jdbc/sib/SCA.APPLICATION.wshostNetwork1.Bus to
     jdbc/com.ibm.ws.sib/XXX.Messaging-SCA.APPLICATION.wshostNetwork
    .Bus
    

Problem summary

  • When you use the BPMMigrationPreValidation script to validate a
    migration source environment, the script doesn't run
    successfully because the source environment database type cannot
    be retrieved.
    The following stack trace is in the log file:
    
    CWMCB2103E: Can not determine source database type.
    com.ibm.bpm.config.util.ConfigException: CWMCB2103E: Can not
    determine source database type.
     at
    com.ibm.bpm.config.export.helper.ConfigExportHelper.getDbTypeInS
    ourceEnv(ConfigExportHelper.java:556)
     at
    com.ibm.bpm.config.export.utils.EnvironmentInfo.initialize(Envir
    onmentInfo.java:221)
     at
    com.ibm.bpm.config.export.utils.ConfigExportContext.initializeEx
    portContext(ConfigExportContext.java:178)
     at
    com.ibm.bpm.config.export.utils.ConfigExportContext.<init>(Confi
    gExportContext.java:132)
    at
    com.ibm.bpm.config.BPMConfig$Actions.export(BPMConfig.java:4258)
     at
    com.ibm.bpm.config.cli.MigrateAction.runInner(MigrateAction.java
    :117)
     at
    com.ibm.bpm.config.cli.AbstractConfigAction.run(AbstractConfigAc
    tion.java:127)
     at
    com.ibm.bpm.config.cli.MigrateAction.run(MigrateAction.java:33)
     at com.ibm.bpm.config.BPMConfig.main(BPMConfig.java:272)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    This issue occurs only when you configure the Business Process
    Choreographer data source at the cell scope.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.5.0 and IBM BPM V8.5.6.0
    that corrects this issue so that the BPMMigrationPreValidation
    script runs successfully.
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53602:
    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 JR53558, 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

    JR53602

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-16

  • Closed date

    2015-08-17

  • Last modified date

    2015-10-18

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2015