domsrvr ERROR, "Cannot associate table Call_Req with Producer in; table already associated with Producer cr", and bpvirtdb_srvr ERROR, "Ignoring registration of producer Call_Req", are in the stdlog

Document ID : KB000019795
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Incorrect customizations may cause system instability.. The messages seen in the stdlog are similar to:

10/10 09:03:19.95 SDMDEVPRI      domsrvr              8508 ERROR        producer.c            1665 Cannot associate table Call_Req with Producer in; table already associated with Producer cr
10/10 09:03:19.95 SDMDEVPRI      domsrvr              8508 ERROR        sql_prod.c             808 Required column (active_flag) for table (Call_Req) is not listed in any majic file objects. This may cause problems if not corrected.
10/10 09:03:19.95 SDMDEVPRI      domsrvr              8508 ERROR        sql_prod.c             808 Required column (customer) for table (Call_Req) is not listed in any majic file objects. This may cause problems if not corrected.
10/10 09:03:19.95 SDMDEVPRI      domsrvr              8508 ERROR        sql_prod.c             808 Required column (log_agent) for table (Call_Req) is not listed in any majic file objects. This may cause problems if not corrected.
10/10 09:03:19.96 SDMDEVPRI      domsrvr              8508 ERROR        sql_prod.c             808 Required column (priority) for table (Call_Req) is not listed in any majic file objects. This may cause problems if not corrected.
10/10 09:03:19.96 SDMDEVPRI      domsrvr              8508 ERROR        sql_prod.c             808 Required column (ref_num) for table (Call_Req) is not listed in any majic file objects. This may cause problems if not corrected.
 
10/10 09:03:20.26 SDMDEVPRI      bpvirtdb_srvr       10188 ERROR        vdbsql.c               841 Ignoring registration of producer Call_Req from domsrvr domsrvr - incompatible with previously registered version

Solution:

To correct the problem, follow these steps:

  1. Review the $NX_ROOT\site\mods\majic\wsp.mods file and find all entries for "OBJECT in" and "OBJECT pr".

    For example, you may find an entry similar to:

    OBJECT in {
    ATTRIBUTES Call_Req {
    ztest SREL bool;
    };
    };

  2. Back out the changes. To do this, following the guidance in the Implementation Guide under Customizing > Schema Customization > Schema Designer Tasks > Change or Delete Site-Defined Columns after Publishing.

  3. Use WSP to create the attributes for the "cr" object instead. Save and Publish within WSP, stop Service Desk Manager services, run pdm_publish, and restart Service Desk Manager services.

Note: As part of best practices, changes should first be made in a pre-production, development, or test environment and then tested and verified before making the equivalent changes in your production environment.