IBM Support

RS01449: [DC] CANNOT CONNECT TO DC CONSOLE AFTER MIGRATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An exception is thrown upon logging into Decision Center after
    running the migration script.
    
    Caused by: java.lang.RuntimeException:
    java.lang.InstantiationException:
    ilog.rules.teamserver.brm.impl.IlrBaselineImpl
    at
    ilog.rules.teamserver.model.impl.IlrElementFactory.createElement
    Details(IlrElementFactory.java:209)
    at
    ilog.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.retrieve
    DetailsFromStatement(IlrElementDAOJDBC.java:7817)
    at
    ilog.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.findElem
    ents(IlrElementDAOJDBC.java:6412)
    at
    ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.findObjec
    ts(IlrSessionFacadeImpl.java:3447)
    at
    ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.findEleme
    nts(IlrSessionFacadeImpl.java:3623)
    at
    ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.getAccess
    ibleBaselines(IlrSessionFacadeImpl.java:5442)
    ...
    at
    ilog.rules.teamserver.ejb.service.IlrMigrateSnapshotFromEvent.ru
    nMigrationTasks(IlrMigrateSnapshotFromEvent.java:54)
    at
    ilog.rules.teamserver.ejb.service.IlrSessionMigrationTask.runMig
    rationTasks(IlrSessionMigrationTask.java:60)
    at
    ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.login(Ilr
    SessionFacadeImpl.java:372)
    
    The problem occurs when migrating a DC repository to V8.5.0.
    New baseline types were added in 8.5.0, and existing baselines
    need to initialize their type according to the baseline kind.
    The migration script generate this update for most baseline
    kinds, except temporary baselines.
    Then, if the migrated repository contains some temporary
    baselines, connecting to DC console after the migration will
    failed with the above stack trace.
    

Local fix

  • Workaround:
    
    1) Delete the temporary baselines in the original database, drop
    the migrated database and then re-run the migration script
    
    2) Manually fix the migration script, updating the command :
    UPDATE RTSTABLES.Baseline SET type = (SELECT ID FROM
    RTSTABLES.METAMODEL WHERE type = 'brm.Snapshot') WHERE
    baselineKind IN ('Standard') ;
    
    into :
    UPDATE RTSTABLES.Baseline SET type = (SELECT ID FROM
    RTSTABLES.METAMODEL WHERE type = 'brm.Snapshot') WHERE
    baselineKind IN ('Standard', 'Temporary') ;
    
    Drop the migrated database and then re-run the corrected
    migration script
    

Problem summary

  • the migration process does not properly handle temporary
    baselines.
    

Problem conclusion

  • The code is modified to handle the temporary baselines so that
    no error is detected when migrating a repository
    

Temporary fix

Comments

APAR Information

  • APAR number

    RS01449

  • Reported component name

    WS DECISION CTR

  • Reported component ID

    5725B6900

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-05

  • Closed date

    2013-11-13

  • Last modified date

    2013-11-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    WS DECISION CTR

  • Fixed component ID

    5725B6900

Applicable component levels

  • R851 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 November 2021