Emerson Exchange 365

Unable to delete a named state when all reference have been removed in recipe, unit parameters and equipment module action block

Hi,

I have a named state "TCU-58563" to be removed from a named set "_TCU_NAME_CHROM. I have removed all referenced recipe, unit parameters and equipment module action block expression. However, inside the named set, it still show the named state "TCU-58563" been referenced.  

So I decided to set named state "TCU-58563" Visible = No and User Selectable = No. I perform a download of batch executive equipment and also the changed set-up data of all nodes in control network. However the named state "TCU-58563" reference remained as YES. Also since i have changed it to Visible = No and User Selectable = No, why the BOI still can have the "TCU-58563" selection provided?

Could anyone have a resolution for this? As the system is validated production system, where they require ALL changes to be done before a download can be performed.

Thanks.

Lay Lan Seah

• 9 Apr 2018 6:13 AM
• Cancel

7 Replies

• Kartik29

  

  • 9 Apr 2018 6:31 AM

  I faced this issue, the option I was having is take the export of the named set, modify it in the text file and import it again.(the reference to the deleted named set value should not exist in database). That worked for me.

  Karma doesn't have any menu, you get serve what you deserve.

  • Cancel
• Jack_France

  

  • 9 Apr 2018 6:32 AM

  Hi
  You have to stop then restart your database to force the engine to redefine its internal cross referencies.
  It may be enough.
  /!\ Stopping database mean that every user will be disconnected from Dv explorer.
  
  Regards

  • Cancel
• Lay Lan Seah

  

  • 9 Apr 2018 6:44 AM

  In reply to Kartik29:

  I try export and update the fhx and re-import. But it failed and give a warning saying that the named set value is reference and could not be deleted.

  • Cancel
• Lay Lan Seah

  

  • 9 Apr 2018 6:47 AM

  In reply to Jack_France:

  Hi Jack, stopping the database will cause any interruption to the running recipe as it is a production system and users all opening control studio etc...Is there any other solutions??

  • Cancel
• Kartik29

  

  • 9 Apr 2018 6:49 AM

  In reply to Lay Lan Seah:

  Take the export of the whole database and search the named set value if still it is existing in the database ?

  Karma doesn't have any menu, you get serve what you deserve.

  • Cancel
• Neil Castro

  

  • 10 Apr 2018 5:03 AM

  In reply to Lay Lan Seah:

  You may need to wait until the system or plant allows restarting the database.
  
  In case the issue still exist after restarting the database then try restarting the PRO+ or do an extended clean of the database. This is an assumption that the named state is no longer referenced.
  
  Regards,
  Neil Castro

  • Cancel
• Andre Dicaire

  

  • 10 Apr 2018 3:27 PM

  In reply to Lay Lan Seah:

  Lay, The Pro Plus database is not used by the run time system, except for users viewing or editing the database with Control Studio or Explorer. No running recipe uses a database connection. You should be able to manage a database action such as stopping the database.
  
  My first recommendation here is to do a full back up of the database, with a full export as well. If you end up needing to recover, the backup will be much faster. But you may need to rebuild from an FHX if you cannot resolve the issue in your database. The back up will have the root of this issue, whatever it is . Do both.
  
  One thing that can happen in the objectivity database is an embedded composite item can be become "orphaned", with references to objects, but no longer referenced by any module. An embedded composite can only be accessed through the module that references it. sometimes, an embedded object persists in the database even though it is no longer referenced in any module. Since this item does not show up in the database tools (explorer) etc, and will not show up in an export, one cannot access, or delete it. Typically the embedded object is destroyed when it is no longer referenced, but under certain circumstances, usually modified user imports, an embedded object reference is changed, without deleting the object.
  
  A Database Clean identifies and removes these unreferenced objects. I don't know if this particular issue will be resolved by this, but I would take the time to clean the database. An Extended Clean also defragments the database files, as well as removing unreferenced objects.
  
  If you've already done a database clean, then you've also stopped the database and we know this does not fix it.
  
  You could also copy the database directory and load it on a separate machine, setting it as the active database. After confirming the issue is still in the copy, try the actions above, knowing you won't disrupt your production system while you find a solution. You will need another Pro Plus and a license dongle. Contact your local service provider to gain access to an SI dongle. You need to Stop the database server before the copy so that there are no changes in any files while they are copied. This gives you an exact copy of your database files, and may be useful if this needs to escalate to the GSC for investigation. Once you determine an action that resolves the issue, you can implement this on the validated system in a timely fashion.

  Andre Dicaire

  • Cancel