IBM Support

JR56224: CONSTRAINT VIOLATION OCCURS WHILE SEARCH OPTIMIZATION IS ENABLED WITH BUSINESS DATA VARIABLES THAT USE MICROSOFT SQL SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While enabling search optimization with business data variables
    that use Microsoft SQL Server as runtime database, you see a
    constraint violation.
    

Local fix

Problem summary

  • When you use Microsoft SQL Server as the runtime database and
    use the SchemaGenerator tool, SchemaGenerator fails with an
    constraint violation because business data search aliases have
    various spellings, which prevents you to enable the search
    optimization.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.5.0 that handles the various
    spellings of business data search aliases to avoid the
    constraint violation and to save it in one column.
    
     On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR56224:
    
    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 JR56224, 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.
    
     To apply the fix, complete the following steps:
    
     1. Shut down the IBM BPM server in a controlled and complete
    manner to ensure that all transactions completed.
    
     2. Extract the .zip file to a directory. For example, extract
    the file to C:\temp.
    
     3. Add the fix pack repository location in IBM Installation
    Manager:
        a. Start IBM Installation Manager.
        b. In Installation Manager, select File > Preferences >
    Repositories.
        c. Click Add Repository.
        d. Browse to or enter the file path to the repository.config
    file. The repository.config file is located in the directory
    where you extracted the compressed files, for example, enter
    C:\temp\repository.config. Click OK.
    
     4. On the main page of the Installation Manager, click Update.
    
     5. Restart the IBM BPM server.
    
    
    To remove the fix, complete the following steps:
    
     IMPORTANT NOTE:  Remove fixes in the reverse order than the
    order in which they were applied. Do not remove a fix unless all
    fixes applied after it are removed. You may reapply a removed
    fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR56224

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-29

  • Closed date

    2016-07-08

  • Last modified date

    2016-07-08

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

  • Fixed component ID

    5725C9500

Applicable component levels

  • R855 PSY

       UP

  • R857 PSY

       UP

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

Document Information

Modified date:
08 July 2016