How to remove a customized field from CA Service Desk Manager and the MDB

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

Introduction:

 

The customization to the schema may some times need to be reverted.

The changes to schema will modify the mdb, but also the object tier, which means some schema files need to be modified.

 

Question: 

 

How to remove a customized field from CA Service Desk Manager and the MDB

This document will provide the steps required for this task

Environment:

Windows, Service Desk Manager 12.x, 14.x, Web Screen Painter

 

 

Answer: 

 

The following steps will ensure that a published customized field is completely removed from both Service Desk Manager as well as the MDB database:

  1. Delete the column/table reference from $NX_ROOT/site/mods/wsp_schema.sch

  2. Delete the column/table reference from $NX_ROOT/site/mods/majic/wsp.mod

  3. Delete the column/table reference from database. Please consult the DBA to accomplish this.
  4. Remove the line makes reference to the column/table from $NX_ROOT/site/ddict.sch
  5. Manually delete the references to the "columns" you want to remove from wspcol table (mdb) and the "tables" you want to remove from wsptbl table (mdb). If necessary, request assistance from DBA for this.
  6. Remove the references to the column/table being deleted from the $NX_ROOT/site/mods/wsp_schema.log.

    Note: The wsp_schema.log is used to determine what has already been created

    Note: If the line relating to the column/table you are deleting is not removed from the wsp_schema.log, you will not be able to recreate the field in the same table again

Warning: The removal of fields will not normally be needed as you will make certain the required field is needed before originally publishing.

Warning: The above procedure should never be performed on a live production installation unless extensive testing is carried out first.

     7. Stop Service Desk Manager service. Make sure the "pdm_status" return "The Daemons are not running".

     8. Remove the content of $NX_ROOT/logs folder (or move its content to another location). Start Service Manager service.

         If anything goes wrong, the stdlog should provide an idea of the cause. Usually, if problem occurred after following this procedure, it may be related to the edited files. You should find references of the parsing problems in stdlog file.

         If you can't determine the cause of the problem, or how to correct it, revert the changes.

Additional Information:

This procedure has been successfully tested in R12.7, but it should also apply to 12.9 and 14.1

Following this procedure, you will need to make changes to config files. Please make sure you have a reliable backup of all files before to modify them. Additionally make a full reliable backup of mdb before to follow this procedure.

In case of a problem, revert the changes using the backed up files and db.