BMC56008E Current environment is incompatible for this existing WORKID | TASKID | BASELINE | BLPROFILE | MIGPROFILE

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    CHANGE MANAGER for DB2


    APPLIES TO:

    Error occurs when creating new WORKID, TASKID, BASELINE, BASELINE PROFILE, or MIGRATE PROFILE in ALTER for DB2 or CHANGE MANAGER for DB2



    PROBLEM:

    When creating a new WORKID, TASKID, BASELINE, BASELINE PROFILE, or MIGRATE PROFILE in V12.1
    of ALTER for DB2 or CHANGE MANAGER for DB2, user gets error BMC56008E Current environment is
    incompatible for this existing [WORKID | TASKID | BASELINE | BLPROFILE | MIGPROFILE.


    CAUSE:

    DB2 VERSION column has incorrect data inserted by the product


    SOLUTION:

    NEW: A fix to the product is available so that any new product rows inserted will have the correct DB2 VERSION column data.
    Please apply PTF BPU9595 and complete any HOLD DATA requirements.

    EXISTING: For existing product data rows that have incorrect DB2 VERSION column data, please follow these instructions.
    Here is an UPDATE SQL example to correct existing data. Examples are for tables CM_WORKID and CM_BASELINE.
    There are 5 tables with possible bad DB2_VERSION data.

    CM_BASELINE
    CM_BLPROFILE
    CM_MIGPROFILE
    CM_WORKID
    CP_TASKID

    1) Do a SELECT first to make sure you get the row that is intended. Repeat for additional 3 tables not in examples here.
     
    SELECT WKOWNER, WKNAME, DB2_VERSION
        FROM ACM121.CM_WORKID
    WHERE WKOWNER = '<user workid owner>' AND
                   WKNAME =  ' <user workid name>'
     
    SELECT WKOWNER, WKNAME, DB2_VERSION
        FROM ACM121.CM_BASELINE
    WHERE WKOWNER = '<user baseline owner>' AND
                    WKNAME = '<user baseline name>'
     
    2) To DELETE or remove a row with a bad DB2_VERSION, convert the UPDATE to a DELETE FROM and remove the SET clause. 
    **Also change ACM121 product table owner to the value used during your installation of V12.1.

    UPDATE ACM121.CM_WORKID
    SET   DB2_VERSION = ' '
    WHERE WKOWNER = '<user workid owner>' AND
                   WKNAME =  ' <user workid name>'

    UPDATE ACM121.CM_BASELINE
    SET   DB2_VERSION = ' '
    WHERE WKOWNER = '<user baseline owner>' AND
                    WKNAME = '<user baseline name>'
     
    3) A common routine updates these five tables, so use the SQL to update or delete from these tables if there is any data that has
    invalid DB2_VERSION inserted by V12.1 ALTER for DB2 or CHANGE MANAGER for DB2:

    CM_BASELINE - see above
    CM_WORKID - see above

    The column names in the tables below are slightly different so please make the following modifications to the SQL.
    For the CM_BLPROFILE table use BLPOWNER and BLPNAME in place of WKOWNER and WKNAME
    For the CM_MIGPROFILE table use MIOWNER and MINAME in place of WKOWNER and WKNAME
    For the CP_TASKID table use WRKOWNER and WRKNAME in place of WKOWNER and WKNAME

    **To verify the table qualifier, type ENVI on the command line, then type AL next to any plan.
    You should see a list of aliases and tables. Please check the table qualifier to include in place of ACM121 in the SQL above.


    Article Number:

    000146117


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles